[syslog-ng] Tracking down a failure between NG and FIFO

Rob Munsch rmunsch at solutionsforprogress.com
Tue Sep 12 21:25:10 CEST 2006


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

Hello,

i've had a running central loghost server for months on end without any
problems.  I've noticed however that something seems to have died and i
can't pinpoint any changes made to any of the involved systems.

After some testing, the central logserver is getting remote messages via
stunnel; syslog-ng is logging locally; and if i tell it to put
everything into a file, the remote as well as local log entries appear
in the file.

MySQL seems to be running and that end seems OK.  The point of failure
seems to be that syslog-ng is no longer putting anything into the named
pipe.  MySQL is patiently waiting for something to appear there to read;
syslog-ng will log to any other destination; but the pipe destination
does not seem to be working.

How can i observe this process?  I can't figure out how to "see" -ng's
attempts to log to the pipe destination.  The destination definition in
question is

- -----
# Local MySQL desination
destination d_mysql {
        pipe("/var/run/mysql.pipe"
                template("INSERT INTO logs (host, facility, priority,
level, tag, timestamp, program, msg, seq)
                VALUES (
'$HOST','$FACILITY','$PRIORITY','$LEVEL','$TAG','$ISODATE','$PROGRAM','$MSG','$SEQ'
);\n")
        template_escape(yes)
        );
};
- -----

exactly as it has been for months.  The log directives are

- -----
# Sending everything to the MySQL table...
log {
        source(s_all);
        destination(d_mysql);
};

# ... and send incoming logs there as well.
log {
        source(stunnel);
        destination(d_mysql);
###     destination(df_messages);  was testing.
};
- -----

As you can see by the commented line above, i had remote logs going to
local messages dest: that worked fine.  Instant results.

Any help would be appreciated, as i'm kind of at a loss.




- --
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBwmVBvBcJFK6xYURAuJnAJ4lKg+94OhZpOvoLsaYcoSAsKoOcgCeLies
XXlL1qf/mXl/262LLXBEelg=
=ajlW
-----END PGP SIGNATURE-----


More information about the syslog-ng mailing list