ERROR manager.c: Could not obtain lock on manager list

any ideals?
we cannot save an changes with the web interface.
keep getting "Could not connect to Asterisk Manager interface"

Keith

maybe up the writetimeout=200 to 1000?

I'm curious, which version of MT are you running?

We are running the newer version on our main switch

this one has a few clients on it that we have not moved over, its running PBX Manager 6.1.1.6
asterisk 1.6.2

keith

Asterisk AMI is required by Communications Manager. You shouldn't be disabling it or you would not be able to manage your system. You should into original issue where Asterisk wouldn't start. Have you had this problem before? How did you restored your system? And did you do anything other than that?

this is the error I was getting in asterisk/full
ERROR manager.c: Could not obtain lock on manager list
never had it before
restored by using the Thirdlane restore page

Keith

I have been pounding google and the only thing I can find is a sippet of code from the actual manager,c

static int ast_manager_register_struct(struct manager_action *act)

{

struct manager_action *cur, *prev = NULL;

struct timespec tv = { 5, };

if (AST_RWLIST_TIMEDWRLOCK(&actions, &tv)) {

ast_log(LOG_ERROR, "Could not obtain lock on manager list\n");

return -1;

}

AST_RWLIST_TRAVERSE(&actions, cur, list) {

int ret = strcasecmp(cur->action, act->action);

if (ret == 0) {

ast_log(LOG_WARNING, "Manager: Action '%s' already registered\n", act->action);

AST_RWLIST_UNLOCK(&actions);

return -1;

What is the output of df -i command?

# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda2 70844416 240776 70603640 1% /
/dev/sda1 26104 37 26067 1% /boot
tmpfs 219817 1 219816 1% /dev/shm

There is no information about this error message. It was removed in v1.8. v1.6.2 is EOL since 2012. You could try restarting your system in case something was locked or hung. But you should really consider updating your system to the latest version.

I agree, but I need to get AMI working so I can import the customers from this last 1.6 server to the new thirdlane…I have rebooted it several times and got the same results, will try the timeout settings to see if it fixes it

anyone else have memories from the 1.6 days?

Is 1.6 still based on flat files in /etc/asterisk? Or is there SQL integration? Couldn't you use data from those files and/or the SQL DB to reconstruct a file that will import into the newer version of TL? I have never used the AMI so I'm not certain what attributes are backed up.

tried writetimeout=200 to 1000 and it did not work either...

Only other thing I would check is file permissions.

A manual transfer/migration to your new system sounds like the way to go.

thanks to Alex got in to our server, he tried to run manager with in the CLI and it would not work, then put in the old original manager.conf, it worked. then replace it with the one we had issues with and BAM it is working perfectly. Now we can migrate the customers over the next couple of weeks. thanks again. He tried something we so simple but it worked, Alex you rock!