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 >> Checking TLS/SSL configuration: [ OK ] >> Checking Per-process file descriptor limits: [ OK ] >> Starting postgresql service: [ OK ] >> /etc/sipxpbx/cdr/schema.sql: No such file or directory Initializing >> configuration database... >> Checking rpm configuration file updates: [ OK ] >> Checking SELinux is not enforcing: [ OK ] >> Checking Apache configuration: [ OK ] >> Checking hostname is fully qualified: [ OK ] >> Checking localhost address configured: [ OK ] >> Checking localhost name is not shared: [ OK ] >> Checking configuration service hostname and address: [ OK ] >> Checking /tmp directory has correct permissions: [ OK ] >> Checking sipxsupervisor: [ OK ] >> Checking freeswitch: [ OK ] >> Checking sipregistrar: [FAILED] >> Checking sipstatus: [ OK ] >> Checking sipxacd: [ OK ] >> Checking sipxbridge: [ OK ] >> Checking sipxconfig-agent: [ OK ] >> Checking sipxconfig: [ OK ] >> Checking sipxpage: [ OK ] >> Checking sipxpark: [ OK ] >> Checking sipxpresence: [ OK ] >> Checking sipXproxy: [FAILED] >> Checking sipxrelay: [ OK ] >> Checking sipxrls: [ OK ] >> Checking sipXvxml: [ OK ] >> sipXpbx: >> 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 > > We are in an awkward period right now - the sipXconfig team has made > great progress moving the installation of configuration files from the > rpm installations to sipXconfig, but the new sipXsupervisor code that > would prevent a component from starting when its configuration is > missing has not yet taken over control. > > This means that at the moment a new installation will report a lot of > configtest errors, and that many components will fail to start until > after sipXconfig has been run to configure them. This is regretable, > but it's difficult to make changes this large without some times when > things get temporarily worse... hopefully we'll be out of this > situation > shortly. > > In the mean time, please ignore startup errors on a new install unless > they persist after the system has been configured by sipXconfig. >
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. -Mardy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
