On Thu, 2009-03-19 at 17:24 +0100, Lukasz Kutkowski wrote: > I didn't have any errors in setup.log but CONFIG_HOSTS contained only > sip1.sip40.vw. Question is what should happen when I add Distributed > server via sipxconfig and before I invoke sipxecs-setup on distributed > system? > > For sure I need > > CONFIG_HOSTS : sip1.sip40.vw sip2.sip40.vw
No... that should be just the master hostname. > I have edited domain-config on master system, added sip2.sip40.vw to > domain-config on master system and restart sipxecs. After that I was > able to see status of all services on master server from distributed > system. using what? nothing ever does the request in that direction. > But this isn't solve my sipxconfig problem whit services in "Undefined" > state. > > When I'm sending profile for distributed system I'm getting following > errors in job status: > > Data replication: extension 3/19/09 5:21 PM 3/19/09 5:21 PM > Failed > Data replication: alias 3/19/09 5:21 PM 3/19/09 5:21 PM Failed > File replication: validusers.xml 3/19/09 5:21 PM 3/19/09 5:21 PM > Completed > Data replication: credential 3/19/09 5:21 PM 3/19/09 5:21 PM Failed > Data replication: permission 3/19/09 5:21 PM 3/19/09 5:21 PM Failed > Data replication: caller-alias 3/19/09 5:21 PM 3/19/09 5:21 PM > Failed > Data replication: userlocation 3/19/09 5:21 PM 3/19/09 5:21 PM > Failed > File replication: mappingrules.xml 3/19/09 5:21 PM 3/19/09 5:21 > PM Completed > File replication: authrules.xml 3/19/09 5:21 PM 3/19/09 5:21 PM > Completed > File replication: fallbackrules.xml 3/19/09 5:21 PM 3/19/09 5:21 > PM Completed > File replication: forwardingrules.xml 3/19/09 5:21 PM 3/19/09 > 5:21 PM Completed > File replication: nattraversalrules.xml 3/19/09 5:21 PM 3/19/09 > 5:21 PM Completed > File replication: sipXproxy-config 3/19/09 5:21 PM 3/19/09 5:21 > PM Failed > File replication: registrar-config 3/19/09 5:21 PM 3/19/09 5:21 > PM Failed > File replication: sipxsupervisor-config 3/19/09 5:21 PM 3/19/09 > 5:21 PM Failed > File replication: sipxivr.properties 3/19/09 5:21 PM 3/19/09 > 5:21 PM Completed > File replication: autoattendants.xml 3/19/09 5:21 PM 3/19/09 > 5:21 PM Completed > > I try to replicate one of the failed file manually and this is what I get: > > [r...@sip1 sipXecs]# sipxreplicate -n sip2.sip40.vw -f > /var/sipxdata/sipdb/caller-alias.xml > /usr/lib/ruby/1.8/xmlrpc/client.rb:414:in `call': File > '/var/sipxdata/sipdb/caller-alias.xml' not declared as a resource by any > sipXecs process (XMLRPC::FaultException) > from /usr/bin/sipxreplicate:286 Ah... one or more rpms did not install properly (in this case, the proxy, I believe). On the command line of sip2, execute as root: sipx-snapshot --info-only > /tmp/info and attach that file. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
