> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Steinmann, Martin (BL60:2500) > Sent: Monday, October 13, 2008 7:49 PM > To: sipx-dev > Subject: [sipX-dev] svn 13689, CentOS, 64bit > > Does anyone know why sipXconfig prints log info to the > console when started (see below). Also, there seems to be a > problem with callresolver --martin > > > [EMAIL PROTECTED] sslcert]# service sipxpbx start > Starting postgresql service: [ OK ] > /etc/sipxpbx/cdr/schema.sql: No such file or directory > Initializing configuration database... > > Starting sipXpbx: > Starting sipxsupervisor: [ OK ] > Starting httpd: [ OK ] > [EMAIL PROTECTED] sslcert]# Creating > /etc/sipxpbx/ssl/.authorities.jks was skipped, previous > checksum of contents matched Creating > /etc/sipxpbx/ssl/.ssl.keystore was skipped, previous checksum > of contents matched Parent class loader is: [EMAIL PROTECTED] > > Error: > /usr/lib64/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib/main. > rb not found (installation error). > > > Error at file /etc/sipxpbx/nattraversalrules.xml, line 20, char 10 > Message: Element 'concurrentrelays' is not valid for content model: > '((state,behindnat,useSTUN,stun-server-address,rediscovery-tim e,publicad > dress,publicport,proxyhostport,relayaggressiveness,concurrentr > elays,medi > arelayexternaladdress,mediarelaynativeaddress,mediarelayxml-rp c-port,por > t-range,log-level),log-directory)' > log4j:WARN No appenders could be found for logger > (org.apache.commons.digester.Digester.sax). > log4j:WARN Please initialize the log4j system properly. > parsing: /var/log/sipxpbx/sipxacd_events.log > starting server on port 8120 > Oct 13, 2008 3:51:24 PM net.java.stun4j.stack.NetAccessPoint start > INFO: Bound a socket on ap: > net.java.stun4j.stack.AccessPoint@/192.168.5.170:3479 status: running >
New supervisor, not yet catching child process output. See http://article.gmane.org/gmane.comp.voip.sipx.devel/12967 An issue has been filed for the nattraversalrules.xml problem (XCF-2906). The callresolver issue looks familiar - see XECS-1503 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
