On Mon, Mar 30, 2009 at 9:37 AM, Raymond Dans <[email protected]> wrote: > Ranga wrote: >>Subject: [sipX-dev] SIPXSUPERVISOR on HA system returns >>Version mismatch. >> >>Hello, >> >>I am working on a HA system install. I have managed to work >>through the certificate issues but now I run into : >> >> Version mismatch: software '3.11.12' != config '' >> >>When I click on my secondary server link. >> >>I rebuilt everything from scratch. Not sure why I am seeing this. >> >> >> >>"2009-03-30T13:25:07.151279Z":258:SIP:INFO:sipxpbx:HttpServer-2 >>:B7D2CB90:Supervisor:"OsSSLConnectionSocket::peerIdentity >>0x8e735a8 OsSSL returned trusted" >>"2009-03-30T13:25:07.152556Z":259:SIP:INFO:sipxpbx:HttpServer-2 >>:B7D2CB90:Supervisor:"HttpServer::processRequest >>POST '/RPC2'" >>"2009-03-30T13:25:07.152613Z":260:XMLRPC:INFO:sipxpbx:HttpServe >>r-2:B7D2CB90:Supervisor:"XmlRpcDispatch::processRequest >>requestBody = \n<?xml >>version=\"1.0\"?><methodCall><methodName>ProcMgmtRpc.getStateAl >>l</methodName><params><param><value>sipxtest.example.local</val >>ue></param></params></methodCall>" >>"2009-03-30T13:25:07.152681Z":261:SUPERVISOR:INFO:sipxpbx:HttpS >>erver-2:B7D2CB90:Supervisor:"ProcMgmtRpc::getUserRequestStateAll >>host sipxtest.example.local requested process states" >>"2009-03-30T13:25:07.152868Z":262:XMLRPC:INFO:sipxpbx:HttpServe >>r-2:B7D2CB90:Supervisor:"XmlRpcDispatch::processRequest >>method 'ProcMgmtRpc.getStateAll' response status=OK\n<?xml >>version=\"1.0\" encoding=\"UTF-8\"?>\n<methodResponse><!-- >>ProcMgmtRpc.getStateAll >>-->\n<params>\n<param>\n<value><struct>\n<member>\n<name>CallRe >>solver-Agent</name><value><string>ConfigurationMismatch</string >>></value>\n</member>\n<member>\n<name>ParkServer</name><value>< >>string>Disabled</string></value>\n</member>\n<member>\n<name>Pa >>geServer</name><value><string>Disabled</string></value>\n</memb >>er>\n<member>\n<name>SipXrelay</name><value><string>Configurati >>onMismatch</string></value>\n</member>\n<member>\n<name>ConfigS >>erver</name><value><string>Disabled</string></value>\n</member> >>\n<member>\n<name>SIPXProxy</name><value><string>ConfigurationM >>ismatch</string></value>\n</member>\n<member>\n<name>SIPStatus< >>/name><value><string>Disabled</string></value>\n</member>\n<mem >>ber>\n<name>SIPRegistrar</name><value><string>ConfigurationMism >>atch</string></value>\n</member>\n<member>\n<name>sipXivr</name >>><value><string>Disabled</string></value>\n</member>\n<member>\ >>n<name>MediaServer</name><value><string>Disabled</string></valu >>e>\n\n..." >> >>Any ideas on where to look to get to the bottom of this problem? >> > Did config set the version number for that component? Config is > responsible for calling the XML/RPC SetConfigVersion for the component > in question before it can be successfully started.
Where does to do the check (i.e. in which file is the information stored?). Perhaps there is something in the tar file missing. Thanks Ranga > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
