[rt-users] RTFM 2.0.4 / RT 3.0.4 Syslog error line 77?

[Glenn Sieb]

Jay R. Ashworth said the following on 3/16/2005 10:47 AM:

>>In my httpd-errors.log I'm seeing:
>>FastCGI: server "/sw/rt/bin/mason_handler.fcgi" stderr: getservbyname 
>>failed for tcp at 
>>/usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77, 
>>referer: http://rt.wingfoot.org/
>>    
>>
>That syntax "getservbyname failed for *tcp*" sounds suspicious to me.
>I think you have a syntax error in *some* configuration file somewhere,
>where "tcp" or "/tcp" appears and it isn't necessary.
>  
>
Ok... given I've not touched any config files in a while, why is this 
suddenly changing?

In /etc/rc.conf:
syslogd_enable="YES"
syslogd_flags="-s -s -l /chroot/named/dev/log"

in /etc/syslog.conf:
# $FreeBSD: src/etc/syslog.conf,v 1.13.2.4 2003/05/12 13:59:23 yar Exp $
#
#       Spaces ARE valid field separators in this file. However,
#       other *nix-like systems still insist on using tabs as field
#       separators. If you are sharing this file between systems, you
#       may want to use only tabs as field separators here.
#       Consult the syslog.conf(5) manpage.
*.err;kern.debug;auth.notice;mail.crit          /dev/console
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err   
/var/log/message
s
security.*                                      /var/log/security
auth.info;authpriv.info                         /var/log/auth.log
mail.info                                       /var/log/maillog
lpr.info                                        /var/log/lpd-errs
cron.*                                          /var/log/cron
*.emerg                                         *
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info                                   /var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
#*.*                                            /var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.*                                            @loghost
# uncomment these if you're running inn
# news.crit                                     /var/log/news/news.crit
# news.err                                      /var/log/news/news.err
# news.notice                                   /var/log/news/news.notice
!startslip
*.*                                             /var/log/slip.log
!ppp
*.*                                             /var/log/ppp.log

And honestly, I don't know where else to check.

I've always run syslog in -s -s mode (as in the past 4 years, it's how I 
installed this box originally, and I've certainly run various RT 
versions over those years). Why would Log::Syslog care about that all of 
a sudden? :-/

Changing to these settings in RT_SiteConfig.pm:
Set($LogToSyslog    , undef);
Set($LogToScreen    , undef);
Set($LogToFile      , 'debug');
Set($LogDir, '/sw/rt/var/log');
Set($LogToFileNamed , "rt.log");    #log to rt.log

And commenting out the @LogToSyslogConf line in RT_SiteConfig.pm has 
done the trick.

I can live with logging to a file. But it is odd how suddenly this would 
be an issue with syslog..?

Anyway, thanks everyone!!

Best,
--Glenn

-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
          ~Benjamin Franklin, Historical Review of Pennsylvania, 1759