Your message dated Tue, 3 Apr 2007 22:33:56 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326958: syslog
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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!
--- End Message ---
--- Begin Message ---
On Sun, Oct 02, 2005 at 11:31:14AM -0500, Vince Mulhollon wrote:
> The problem in the past seemed to be RT was trying to connect via the unix
> socket thus I had to force it to the default inet socket, although
> upstream claims it was only a documentation change. Also the same
> version of liblog-dispatch-perl is in stable, testing, and unstable.
>
> Today I changed /etc/request-tracker3.4/RT_SiteConfig.pm back to
> @LogToSyslogConf = () unless (@LogToSyslogConf);
> restarted, and don't get the old error.
>
> However this was after I upgraded today per /var/log/dpkg.log
> 2005-10-02 08:37:22 upgrade request-tracker3.4 3.4.2-4 3.4.4-1
>
> I guess file this as unreproducible..
Hi,
the only thing I can think of here is that sysklogd really wasn't running
or not bound to /dev/log for some reason after the first upgrade. Forcing
Log::Dispatch to use an inet socket instead would work around this and
remove the error message.
I don't understand the /opt/machine/... part in the error message either;
I get /usr/share/perl5/... on both Sarge and Etch myself.
Since you're the only one who has reported the bug, and it vanished
for you too, I'm closing this now. Please let us know if you disagree.
I doubt this is ever going to become any clearer, though.
Cheers,
--
Niko Tyni [EMAIL PROTECTED]
--- End Message ---
