On Fri, 2008-09-19 at 09:02 -0400, Marden Marshall wrote: > On Sep 19, 2008, at 8:48 AM, Scott Lawrence wrote: > > > > > On Thu, 2008-09-18 at 21:26 -0400, Martin Steinmann wrote: > > > >> [EMAIL PROTECTED] sslcert]# service sipxpbx start [...] > >> sipXpbx: sipXpbx configuration problems found: > >> sipXpbx: > >> sipXpbx: Check sipregistrar > >> sipXpbx: ==== /etc/sipxpbx/mappingrules.xml: > >> sipXpbx: Not readable. > >> sipXpbx: ==== /etc/sipxpbx/fallbackrules.xml: > >> sipXpbx: Not readable. > >> sipXpbx: Can't open /etc/sipxpbx/registrar-config: No such file or > >> directory. > >> sipXpbx: > >> sipXpbx: Check sipXproxy > >> sipXpbx: ==== /etc/sipxpbx/nattraversalrules.xml: > >> sipXpbx: Not readable. > >> sipXpbx: > >> Attempting to start despite configuration problems > > [...] > > I would also like to point out that these startup errors were being > reported against an x86_64 version of sipX for which we still do not > even have the ability to fully compile. The fact that it does not run > should be no surprise and reporting so serves no purpose.
I am seeing these in regular (32 bit) version of sipx as well. I committed several changes over the last couple days that are supposed to stabilize the sipx services support in sipXconfig. According to the logs I have seen, and looking at the files in etc, registrar-config is being correctly replicated once sipXconfig starts. Is this a problem with sipXregistrar trying to read the file before sipXconfig has replicated it? Maybe thats what Scott was saying... not sure. Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
