Ananda Teertha wrote: > Sent the profile to the default server and monitored /var/run/sipxpbx. > None of the files under /var/run/sipxpbx changed in terms of time which > indicates that the services were not restarted. > > Sending the profile indeed results in the following log entry.. > > 2009-02-19T12:49:54.818165Z:3402:SUPERVISOR:WARNING:sun.qantom.int:HttpServer-3:B7C10B90:Supervisor:'ConfigAgent': > Received u > nexpected event evConfigurationChanged while in state 'Stopping' > 2009-02-19T12:49:54.818190Z:3403:XMLRPC:INFO:sun.qantom.int:HttpServer-3:B7C10B90:Supervisor:XmlRpcDispatch::processRequest >
That might be not related but let's see what sipxsupervisor experts say. I did some investigation and I am pretty sure that what you are seeing now is caused by sipxpage.properties replication failing: http://track.sipfoundry.org/browse/XCF-3278 After my changes that actually is way more 'reliable' in preventing sipXconfig from starting any services. (That probably means that as soon as you go to Paging configuration you'll be able to Send Profiles for a server.) I do not have a proper fix for that yet, but I do have a reasonable workaround that I am going to check in now. D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
