Bug#326958: request-tracker3.4: no connection to syslog available at /opt/machine/perl/lib/site_perl/5.8.2/Log/Dispatch/Syslog.pm line 77

2005-09-07 Thread Stephen Quinney
On Tue, Sep 06, 2005 at 04:25:06PM -0500, Vince Mulhollon wrote:
 Package: request-tracker3.4
 Severity: normal
 
 On my recently updated testing box I get the following error at my initial
 login. I get the login page, then type in the root password, and it fails 
 with this error, when RT is trying to log my successful login attempt:
 
 no connection to syslog available at
 /opt/machine/perl/lib/site_perl/5.8.2/Log/Dispatch/Syslog.pm line 77
 

This strongly suggests to me that you are using a locally
compiled/installed version of Perl and not the one shipped as part of
Debian (that would be in /usr/lib/perl and /usr/share/perl). With this
in mind I am not sure I am going to be able to help you very much as
the problem could just as easily be in the perl as in my
request-tracker3.4 package.

I recommend you run request-tracker3.4 (and all Debian perl packages
for that matter) with the version of perl shipped with Debian and see
if that fixes your problems. If nothing else this will provide an
upgrade from the 5.8.2 version you are using to the 5.8.7 which comes
with testing/etch. We do depend on a version of perl (= 5.8.3) for a
good reason, ignoring dependency lists is going to result in all sorts
of trouble for you.

Stephen Quinney




signature.asc
Description: Digital signature


Bug#326958: request-tracker3.4: no connection to syslog available at /opt/machine/perl/lib/site_perl/5.8.2/Log/Dispatch/Syslog.pm line 77

2005-09-06 Thread Vince Mulhollon
Package: request-tracker3.4
Severity: normal

Hello,

First, thank you for maintaining RT.

On my recently updated testing box I get the following error at my initial
login. I get the login page, then type in the root password, and it fails 
with this error, when RT is trying to log my successful login attempt:

no connection to syslog available at
/opt/machine/perl/lib/site_perl/5.8.2/Log/Dispatch/Syslog.pm line 77

I checked out the RT Wiki at:
http://wiki.bestpractical.com/index.cgi?NoConnectionToSyslog

And all I needed to do was add the following line to
/etc/request-tracker3.4/RT_SiteConfig.pm

@LogToSyslogConf = ( socket = 'inet' ) unless (@LogToSyslogConf);

From what I see on the RT wiki, they are not certain where the bug is
located, if it's theirs or ours.

Perhaps for now, you could modify the docs to mention this, and add 
the provided line, commented out, in RT_SiteConfig.pm

Thanks!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]