Skip to main content

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

Posted by trinicom on Wed, 06/05/2019

We had to restore from a backup from yesterday of our thirdlane multitenant

asterisk would not start up and threw this error
manager.c: Could not obtain lock on manager list

once I disabled the manager in etc/asterisk/manager.conf everything worked perfectly.

could this be a permissions issue?

thanks again in advance

Keith


Submitted by trinicom on Wed, 06/05/2019 Permalink

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

Keith

Submitted by volodya on Wed, 06/05/2019 Permalink

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?

Submitted by trinicom on Wed, 06/05/2019 Permalink

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;

Submitted by trinicom on Wed, 06/05/2019 Permalink

# 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

Submitted by volodya on Wed, 06/05/2019 Permalink

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.

Submitted by trinicom on Wed, 06/05/2019 Permalink

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?

Submitted by mcampbell@1poi… on Wed, 06/05/2019 Permalink

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.

Submitted by mattdarnell on Wed, 06/05/2019 Permalink

Only other thing I would check is file permissions.

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

Submitted by trinicom on Thu, 06/06/2019 Permalink

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!