On Thu, 2008-06-05 at 07:56 -0700, Kevin Thorley wrote: > keccles wrote: > > I know it's unstable, but does anybody have a guess about why the > > logging is failing? sipXproxy is only logging ERR and NOTICE, even > > though I see > > > > /usr/local/ecs/svn/main/etc/sipxpbxsipXproxy-config.in:SIPX_PROXY_LOG_LEVEL > > : DEBUG > > > > and sipxconfig GUI shows debug as well. > > > > -ke > > > > > > Both sipXproxy-config.in and registrar-config.in are no longer used. > They only remain so that their values can be migrated when the upgrade > support for those two files is implemented. Any changes that need to be > made to sipXproxy-config and registrar-config must be made via > sipXconfig. After making these changes (and waiting a few seconds for > the replication to take place), you should see the correct values in the > sipXproxy-config and registrar-config files. The .in files will no > longer be updated by sipXconfig, and will be deleted as soon as the > upgrade code is in place. > > I'm not sure if this is related to why sipXproxy isn't logging > correctly, but I just want to make sure this point is understood, so as > it doesn't confuse the issue. > > Kevin
OK. on the GUI system/general/logging, all values are set to DEBUG (and have been for days.) Just to be safe, I hit apply and then hit Continue on the restart services page. Debugging/jobstatus shows: Data replication: alias 6/5/08 10:10 AM 6/5/08 10:10 AM Completed but using grep in /usr/local/ecs/svn/main/etc/sipxpbx I see: $ grep SIPX_PROXY_LOG_LEVEL sipXproxy-config* sipXproxy-config:SIPX_PROXY_LOG_LEVEL : NOTICE sipXproxy-config.in:SIPX_PROXY_LOG_LEVEL : DEBUG so for some reason that DEBUG value is not getting to the correct place, unless there is another directory I should look in? -kathy _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
