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

[Jay R. Ashworth]

On Wed, Mar 16, 2005 at 12:20:26AM -0500, Glenn Sieb wrote:
> @LogToSyslogConf = ( socket => 'inet' ) unless (@LogToSyslogConf);
> 
> Fully stopped (apachectl stop) & started Apache (apachectl startssl), 
> still getting the error on line 77 of Syslog.pm
> 
> I'm running FreeBSD 4.11, Perl 5.8.6, Apache/2.0.53 (FreeBSD) PHP/4.3.10 
> mod_fastcgi/2.4.2 mod_ssl/2.0.53 OpenSSL/0.9.7e
> 
> The errors follow..
> 
> Thanks in advance.. :-/
> 
> Best,
> --Glenn
> 
> 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.

> The error in RT:
> 
> *error:*  	no connection to syslog available at 
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77
> *context:*  	
> *...*  	
> *265:*  	# whether they should generate a full stack trace (confess() 
> and cluck())
> *266:*  	# or simply report the caller's package (croak() and carp()), 
> respectively.
> *267:*  	# confess() and croak() die, carp() and cluck() warn.
> *268:*  	
> *269:*  	sub croak { die shortmess @_ }
> *270:*  	sub confess { die longmess @_ }
> *271:*  	sub carp { warn shortmess @_ }
> *272:*  	sub cluck { warn longmess @_ }
> *273:*  	
> *...*  	
> 
> *code stack:*  	/usr/local/lib/perl5/5.8.6/Carp.pm:269
> /usr/local/lib/perl5/5.8.6/mach/Sys/Syslog.pm:436
> /usr/local/lib/perl5/5.8.6/mach/Sys/Syslog.pm:299
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm:77
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Output.pm:41
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch.pm:95
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch.pm:74
> /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch.pm:22
> /sw/rt-3.4.1/lib/RT/FM/ArticleCollection_Overlay.pm:78
> /sw/rt-3.4.1/share/html/RTFM/Elements/UpdatedArticles:63
> /sw/rt-3.4.1/share/html/RTFM/index.html:26
> /sw/rt-3.4.1/share/html/autohandler:215
> 
> raw error <http://rt.wingfoot.org/RTFM/index.html#raw>
> 
> The raw error:
> 
> no connection to syslog available at /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77
> 
> Trace begun at /usr/local/lib/perl5/site_perl/5.8.6/HTML/Mason/Exceptions.pm line 131
[ ... ]
> Sys::Syslog::connect at /usr/local/lib/perl5/5.8.6/mach/Sys/Syslog.pm line 299
[ ... ]

That line there is the culprit: Sys::Syslog ought to throw a more
useful error.  

Check your syslogd.conf file; see if there's something hincky in there.
Also your /etc/services file.  And make sure syslogd is a) running and
b) listening on the right ports (and fifos).  It's possible that your
syslog is *not* listening to TCP at all, and that RT is the only app
*not* trying to use a fifo to talk to it...

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

      If you can read this... thank a system adminstrator.  Or two.  --me