No I did not, I did a yum update, ran through it, rebooted and then failure.
 
What I did to correct it, was chkconfig sipxecs off, then rebooted system. I 
then manually started the services after it came back and it appears everything 
is good, which is weird because I didn't "do" anything. I just added sipxecs 
back to startup so we'll see. 

 
Aaron Pursell, Sr.
Network Systems Administrator
Easter Seals-Goodwill Northern Rocky Mountain, Inc.
4400 Central Ave
Great Falls, Montana  59405

(406) 771-3721
aar...@esgw.org
>>> Tony Graziano <tgrazi...@myitdepartment.net> 9/15/2011 7:30 AM >>>

did you by chance not shutdown services before updatingOn Sep 15, 2011 9:28 AM, 
"Aaron Pursell" <aar...@esgw.org> wrote:
> I think I got it back up, for some reason even if the services where stopped, 
> sipx processes continued to restart or run.
> 
> 
> Aaron Pursell, Sr.
> Network Systems Administrator
> Easter Seals-Goodwill Northern Rocky Mountain, Inc.
> 4400 Central Ave
> Great Falls, Montana 59405
> 
> (406) 771-3721
> aar...@esgw.org
>>>> Tony Graziano <tgrazi...@myitdepartment.net> 9/15/2011 7:26 AM >>>
> 
> if you did a backup before you updated... you can simply reinstall and 
> restore. 5.7 was just released but I don't know if anyone has had an 
> opportunity to see what issues there might be with it yet .On Sep 15, 2011 
> 9:17 AM, "Aaron Pursell" <aar...@esgw.org> wrote:
>> Currently having issues with services staying up. I did a yum update (bad 
>> idea obviously) so I assume my system is 5.7 now however sipXproxy fails 
>> with the below:
>> 
>> SipXproxy: sync.cpp:465: void dbGlobalCriticalSection::enter(): Assertion 
>> `rc == 0' failed.
>> 
>> 
>> Aaron Pursell, Sr.
>> Network Systems Administrator
>> Easter Seals-Goodwill Northern Rocky Mountain, Inc.
>> 4400 Central Ave
>> Great Falls, Montana 59405
>> 
>> (406) 771-3721
>> aar...@esgw.org
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to