Syslog-related Error message

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’ve been running RT 3.4.2 in production for about a week and looking
around to make sure things are OK. At unpredictable times when I perform
a transaction using the web interface, I see the following error message.
Usually, the message stops occurring if I retry the transaction once or
twice.

I’ve lost my copy of the full message, including a back trace, that showed
up in the web interface itself. But here’s what appeared at about the
same time in my log (lines wrapped by me for readability):

[Tue Nov 29 17:57:27 2005] [error] [client 128.32.76.10] 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.6/Log/Dispatch/Syslog.pm line 77
[Tue Nov 29 17:57:27 2005] [error] [client 128.32.76.10] FastCGI: server "/usr/local/rt3/bin/mason_handler.fcgi"
stderr: console is not writable at /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77

The problem, as I’ve indicated, is transient. In this case I was just
displaying the content of a ticket when the problem occurred. Because
it’s transient, I wonder if there is some kind of locking or enqueuing
issue relating to syslog itself.

Any ideas.

My environment:

RT 3.4.1
FreeBSD 5.4-RELEASE
Perl 5.8.6
Apache-2.0.54_2
mod_fastcgi-2.4.2

Mike

Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQ40ZGK0bf1iNr4mCEQISvwCg8whcDpktOgskaiIAnugOjCClB1YAoJH9
LZGJXCZJ3avH9oyJyERU7NMN
=BZyi
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’ve been running RT 3.4.2 in production for about a week and looking
around to make sure things are OK. At unpredictable times when I perform
a transaction using the web interface, I see the following error message.
Usually, the message stops occurring if I retry the transaction once or
twice.

I’ve lost my copy of the full message, including a back trace, that showed
up in the web interface itself. But here’s what appeared at about the
same time in my log (lines wrapped by me for readability):

[Tue Nov 29 17:57:27 2005] [error] [client 128.32.76.10] 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.6/Log/Dispatch/Syslog.pm line 77
[Tue Nov 29 17:57:27 2005] [error] [client 128.32.76.10] FastCGI: server "/usr/local/rt3/bin/mason_handler.fcgi"
stderr: console is not writable at /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77

The problem, as I’ve indicated, is transient. In this case I was just
displaying the content of a ticket when the problem occurred. Because
it’s transient, I wonder if there is some kind of locking or enqueuing
issue relating to syslog itself.

Any ideas.
I think problem is in Log::Dispatch, Log::Dispatch::Syslog or in your
syslog configuration.
Easiest you can do is turn off logging to syslog and turn logging to
file in the RT config.
You also could try to update Log::Dispatch module and/or ask devlopers
of the module for help.

My environment:

RT 3.4.1
FreeBSD 5.4-RELEASE
Perl 5.8.6
Apache-2.0.54_2
mod_fastcgi-2.4.2

Mike

Best regards, Ruslan.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I’m still seeing the Log::Dispatch::Syslog errors I mentioned in my
earlier note. It occurs not only when I’m using the web interface, but
also with perl scripts that use the RT API.

Here’s a larger extract from my httpd-error log file:

[Tue Nov 29 02:12:33 2005] [error] [client 128.32.30.78] FastCGI:
 server "/usr/local/rt3/bin/mason_handler.fcgi" stderr:
DBD::mysql::st execute failed: Duplicate entry 'yates@hcreit.com'
for key 2 at /usr/local/lib/perl5/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480.

[Tue Nov 29 02:12:33 2005] [error] [client 128.32.30.78] FastCGI:
 server "/usr/local/rt3/bin/mason_handler.fcgi" stderr:
 RT::Handle=HASH(0x93ac1ac) couldn't execute the query
 'INSERT INTO Users (Comments, RealName, EmailAddress, Creator, Password,
 LastUpdatedBy, Created, id, Name, LastUpdated) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)'
 at /usr/local/lib/perl5/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494.

[Tue Nov 29 14:15:07 2005] [error] [client 128.32.76.8] 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.6/Log/Dispatch/Syslog.pm line 77,
 referer: https://info-sec.berkeley.edu:444/Search/Bulk.html?Order=DESC&Query=Owner%20%3D%20'Nobody'%20AND%20(%20Status%20%3D%20'new'%20OR%20Status%20%3D%20'open')&Rows=50&OrderBy=Priority&Page=1&Format=

[Tue Nov 29 14:15:07 2005] [error] [client 128.32.76.8] FastCGI:
 server "/usr/local/rt3/bin/mason_handler.fcgi" stderr:
 console is not writable at /usr/local/lib/perl5/site_perl/5.8.6/Log/Dispatch/Syslog.pm line 77,
 referer: https://info-sec.berkeley.edu:444/Search/Bulk.html?Order=DESC&Query=Owner%20%3D%20'Nobody'%20AND%20(%20Stat

us%20%3D%20’new’%20OR%20Status%20%3D%20’open’)&Rows=50&OrderBy=Priority&Page=1&Format=

There seem to be two problems here:

(1) mysql database errors.

(2) The Syslog.pm related messages.

My environment:

RT 3.4.2
FreeBSD 5.4-RELEASE
Perl 5.8.6
Apache-2.0.54_2
mod_fastcgi-2.4.2

Any suggestions on what could be going on?

Thanks.

Mike

Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQ44xma0bf1iNr4mCEQKX0wCgxKO/1DRccozo//hnIOLV3vugpSsAoKyZ
eNGxi/Qy6UHQEkaA2agkkPqO
=bdya
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Wed, 30 Nov 2005 at 17:16 (+0300), Ruslan Zakirov wrote:

I think problem is in Log::Dispatch, Log::Dispatch::Syslog or in your
syslog configuration. Easiest you can do is turn off logging to syslog
and turn logging to file in the RT config.

Ruslan,

OK, I’ve done that. We’ll see what happens.

On a related matter, I notice that the log entries in the file show time
in GMT, rather than local time. Whereas, when I was writing to syslog, I
got local time. Is there a configuration option that will cause file
logging also to show local time?

Thanks.

Mike

Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQ46DFq0bf1iNr4mCEQICdwCeM+9bAyRb5TItWN43UWMx/pNEGDwAoNEM
gOO65UK7GzGXYVLIKKoy3oXW
=oIFm
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Question: is there an API method that will return the highest ticket
number thus far assigned by RT?

I can’t just keep loading tickets until I hit the first one that won’t
load, because (as I’ve indicated in an earlier posting) there are now gaps
in my RT’s ticket numbering sequence because some tickets seem to have
’disappeared’ from the database (or at least they’ve become unloadable!

Thanks.

Mike

Mike Friedman System and Network Security
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://ack.Berkeley.EDU/~mikef http://security.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQ46Eha0bf1iNr4mCEQJWWgCfQe1KasN6jOhYJeOT1YdGU8f0CMUAoIX5
PDQgawyCFq+fWwavp7Qfl8zT
=BnTn
-----END PGP SIGNATURE-----