[rt-users] error when searching (long)

Phil Homewood pdh at bestpractical.com
Thu Apr 1 17:50:42 EST 2004

Palle Girgensohn wrote:
> When searching I get an error. "no connection to syslog available at"
> seems bogus, since I get a lot of stuff in my syslog, see below. It
> seems FastCGI tries to write to /dev/conslog, that is stupid. FreeBSD
> has a symlink /dev/log -> /var/run/log, which is a unix domain socket.

Sounds like the old Solaris-tickled bug in Log::Dispatch::Syslog --
the module refuses to work if /dev/log isn't a socket, IIRC.

Workaround: Set($LogToSyslog, undef) and log your debugs to a file

> FastCGI: server "/usr/local/rt3/bin/mason_handler.fcgi" stderr: [Thu Apr  1 12:59:18 2004] [error]: Do not know how to thaw data with code `F' at /usr/local/lib/perl5/site_perl/5.8.3/FreezeThaw.pm line 542

OK, that's interesting. I thought that one was fixed in 3.0.10.
It'd be interesting to see what led up to that -- in particular,
what search criteria were last submitted...

> FastCGI: server "/usr/local/rt3/bin/mason_handler.fcgi" stderr: stream /dev/conslog is not writable at /usr/local/lib/perl5/site_perl/5.8.3/Log/Dispatch/Syslog.pm line 77
> FastCGI: server "/usr/local/rt3/bin/mason_handler.fcgi" stderr: console is not writable at /usr/local/lib/perl5/site_perl/5.8.3/Log/Dispatch/Syslog.pm line 77

These lines might also provide some insight.
»|« http://www.bestpractical.com/rt  -- Trouble Ticketing. Free.

More information about the rt-users mailing list