Hey I made a thread about this a while back but it seems to have been deleted...
Anyway I know Eric said that it was a bug and it only pops up when something in the scripts library is changed. But I can't remember if he said when they expected a fix. Can anyone shed some light on this?
Hey Jason it sounds like your
Hey Jason it sounds like your running a version of asterisk that is experiencing deadlocks when reloading the PBX. We found that upgrading to later versions of asterisk 1.8.10.X and above have fixed the bug pertaining to deadlocks from SIP hints.
@playmaker66 how are you
@playmaker66 how are you finding 1.8 branch with thirdlane? How many endpoints are registered?
@playmaker66: We're running
@playmaker66: We're running Asterisk 1.8.21.0. This was installed from the Thirdlane ISO.
Brian: So far its been rock
Brian: So far its been rock solid, we got about 800 endpoints going through it.
Jason: That version of thirdlane should work just fine. We got a few STE installs on that version of asterisk. However, we NEVER set the PBX to reload after every change.
@playmaker: yeah we have it
@playmaker: yeah we have it set to no... however we're wondering when it actually does do a reload if that is set to no. Or do you guys only do manual reloads through the CLI?
The system WON'T do a reload
The system WON'T do a reload unless you click the reload button at the bottom left handside of the PBX Manager. You can always do reloads in the CLI as well if you prefer.
Oh additionally the asterisk service seems to be locking up. Are the reloads actually happening even though that setting is set to no?
Additionally when changing the option to yes it fails with the following error: "Server returned error code = -1
Error running script /usr/libexec/webmin/asterisk/sql/mysql/drop_change_log_triggers.sql"