I broke the supervisor in one of my commits. I introduced iostream exceptions which affected other file operations. I have reverted this in git head. Please wait for the next wave of RPMS. I apologize for this.
On 06/10/2011 03:24 PM, Kumaran wrote: > Hi All, > I had yum update from 26th May build to jun 9th Rpm....It had > completed successfully.Before initiate the yum update I had stop sixpecs > services "/etc/init.d/sipxecs stop"...And after completion of yum update > I issue the command "etc/init.d/sipxecs restart" then I got following > error and core dumps generated from supervisor..But unfortunately I > cannot attached the logs because we had problem in replication of > logs...Because of this sipxecs is not starting.Whether I'm missing > something or this error caused because of some other behavior.. > > Starting sipXpbx: > Starting sipxsupervisor: terminate called after throwing an instance of > 'std::ios_base::failure' > what(): basic_ios::clear > /etc/init.d/sipxecs: line 108: 4459 Aborted (core > dumped) $proc_cmd< /dev/null > [ OK ] > Starting httpd: [ OK ] > [root@stresstest ~]# terminate called after throwing an instance of > 'std::ios_base::failure' > what(): basic_ios::clear > terminate called after throwing an instance of 'std::ios_base::failure' > what(): basic_ios::clear > terminate called after throwing an instance of 'std::ios_base::failure' > what(): basic_ios::clear > > Regards, > Venkateshwaran T > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
