This turned out to be a simple one to correct. If you have the IM server role enabled, you must have at least one user added with IM enabled. All the symptoms that I reported stopped immediately once this was done.
Thanks to Robert Joly for diagnosing the issue and providing the solution. On Thu, 2010-04-29 at 10:01 -0400, JOLY, ROBERT (ROBERT) wrote: > > > > I am seeing what I think is some odd behavior with Openfire, > > but then it may just be me. > > > > I have installed a sipxecs 4.2 test system on Centos 5.4 > > x86_64 using the YUM repos. sipxecs-setup has been run to do > > the base configuration. > > DNS Advisor reports no issues and the only Configuration > > Diagnostic Test that fails is the DHCP option 120 test. > > > > ACD and SIP Trunking have been disabled. > > > > There are no users or devices configured and there is no SIP > > or XMPP traffic on the network. > > > > In 24 hours this "idling" system generated a 100MB sipxopenfire.log. > > > > The vast majority of the log entries are tagged as > > "JAVA:INFO" and do not seem to be indicating any errors. Is > > this level of logging considered to be normal? > > > > There are some log entries indicating a 404 status but I do > > not understand these. I have attached a log of 5 minutes > > worth of the IM role being renabled. I hope that this isn't > > considered too large for the list. > > The sipXopenfire is trying to SUBSCRIBE to the Resource List Server but it > gets a 404 Not Found back. As a result, it re-attempts the SUBSCRIBE every > 10 seconds (also causing your DNS traffic). Could you send me a short > snapshot (2 minutes would suffice) of your system so that I can figure out > why you run into that scenario? > > > > > I am also seeing the following 10 DNS looks occurring every > > 10 seconds. > > Disabling the IM role stops these occurring, so I assume that > > Openfire is also the cause of these. > > > > Apr 29 20:33:50 dnsdhcp01 named[22379]: client 192.168.42.27#34623: > > query: sipx01.devnull.net.nz IN A + > > Apr 29 20:33:50 dnsdhcp01 named[22379]: client 192.168.42.27#58947: > > query: devnull.net.nz IN A + > > Apr 29 20:33:50 dnsdhcp01 named[22379]: client 192.168.42.27#38121: > > query: _sip._tls.devnull.net.nz IN SRV + Apr 29 20:33:50 > > dnsdhcp01 named[22379]: client 192.168.42.27#37957: > > query: _sip._udp.devnull.net.nz IN SRV + Apr 29 20:33:50 > > dnsdhcp01 named[22379]: client 192.168.42.27#39877: > > query: _sip._tcp.devnull.net.nz IN SRV + Apr 29 20:33:50 > > dnsdhcp01 named[22379]: client 192.168.42.27#54070: > > query: sipx01.devnull.net.nz IN A + > > Apr 29 20:33:50 dnsdhcp01 named[22379]: client 192.168.42.27#56796: > > query: devnull.net.nz IN A + > > Apr 29 20:33:50 dnsdhcp01 named[22379]: client 192.168.42.27#36659: > > query: _sip._tcp.devnull.net.nz IN SRV + Apr 29 20:33:50 > > dnsdhcp01 named[22379]: client 192.168.42.27#54522: > > query: _sip._udp.devnull.net.nz IN SRV + Apr 29 20:33:50 > > dnsdhcp01 named[22379]: client 192.168.42.27#49299: > > query: _sip._tls.devnull.net.nz IN SRV + > > > > > > If there is indeed a problem here let me know what else I can > > provide to try and track it down. > > > > Thanks > > > > Mike > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
