On Tue, 2008-10-28 at 13:16 -0400, Carolyn Beeton wrote: > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Spitzer, Andy (BL60:9D30) > > Sent: Tuesday, October 28, 2008 11:19 AM > > To: [email protected] > > Subject: [sipX-dev] SUPERVISOR_HOST not defined in > > sipxsupervisor-config > > > > Woof! > > > > My sipxsupervisor-config looks like this: > > SIP_WATCHDOG_XMLRPC_PORT : 8092 > > # Add the fully qualified name of the master when > > configuring HA, comma separated > > SIP_WATCHDOG_XMLRPC_PEERS : woof.us.nortel.com > > > > But when I start sipX (main as of today) I get this error in > > sipxsupervisor.log: > > > > > > "2008-10-28T14:50:19.016596Z":55:SUPERVISOR:ERR:woof:pid-14816 > > :00000000:Supervisor:"initXMLRPCsettings: > > SUPERVISOR_HOST not configured in > > '/usr/local/ecs/main/etc/sipxpbx/sipxsupervisor-config'" > > > > "2008-10-28T14:50:19.016622Z":56:SUPERVISOR:ERR:woof:pid-14816 > > :00000000:Supervisor:"initXMLRPCsettings: > > No configuration servers configured." > > > > And at that point no configuration can be updated, and it > > fails thusly: > > > > > > "2008-10-28T14:51:07.597432Z":693:SUPERVISOR:ERR:woof:HttpConn > > ection-68:B313CB90:Supervisor:"ImdbTable.replace > > failed - 'woof.us.nortel.com' not a configured peer" > > > > So, as nothing gets configured, nothing works. Very annoying > > > > How can I get a correctly configure sipxsupervisor-config, so > > the rest of the system can be configured and I can get this > > thing working again? > > > > --Woof! > > I think the problem could be your domain-config. supervisor-config > should not exist anymore. There is some old code in sipxsupervisor > which is looking in supervisor-config which should be removed, I think. > The warnings about SUPERVISOR_HOST come from the old code which should > be removed, and this is not the real problem. Can you check whether your > domain-config contains SUPERVISOR_PORT and CONFIG_HOST? If not, it > needs to be regenerated (sipx-setup will do it). (These changes were > made in > http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&revision=13758)
Carolyn is mostly right - the problem is that the directives and locations changed and regenerating domain-config will help. The controlling directives moved from sipxsupervisor-config to domain-config: SUPERVISOR_PORT (was SIP_WATCHDOG_XMLRPC_PORT) CONFIG_HOSTS (was SIP_WATCHDOG_XMLRPC_PEERS) The SUPERVISOR_HOST directive in sipxsupervisor-config is read, but is not required. It specifies the host that the supervisor is running on and that host is always added to the internal list of valid peers (CONFIG_HOSTS). _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
