Normally qpsmtpd ships it's logs within it's service dir, like:
/var/service/qpsmtpd/log/main
Which is the dir you want to let dlog aware of. The log files are named
"current" and there should be numerous files in the tai64 format and
begin with @ ("@40000000474a50ad3a326a24.s" for instance).
If you changed the log-dir for qpmsptd or you didn't use Dan's service
tools - then it's difficult for me to tell where your logfiles are located.
-Skaarup
Kjetil Kjernsmo wrote:
Hi Rasmus and the rest!
I've just gotten around to install munin on some boxes, which runs fine,
and now I went on to install dlog, which is the most important plugin
that I want to use with munin to monitor my qpsmtpd install, it is a
very interesting thing! I suppose this is a question mainly for Rasmus,
but as others might be interested, I CC the list.
I have a Debian Sarge system that I try this on (my main server), but I
also have a Debian Etch that I can use to test, even a recent Ubuntu if
it seems likely that the problem is due to old software.
I think I got dlog installed properly, no errors in the compilation, and
everything looks fine in /usr/local/dlog/ . Also, I get a usage message
if I run the binaries.
I get no results in my munin graphs, though, and nothing when I try to
run the plugins manually. I found that it wasn't quite clear what
LOGDIR should be, so I started experimenting by calling dodlog.pl on
the command line.
I've tried the following
/usr/local/dlog/bin/dodlog.pl qpsmtpd raw /var/log/qpsmtpd/
/usr/local/dlog/bin/dodlog.pl qpsmtpd raw /var/log/qpsmtpd/qpsmtpd.log
/usr/local/dlog/bin/dodlog.pl qpsmtpd raw /var/log/qpsmtpd/*
/usr/local/dlog/bin/dodlog.pl qpsmtpd raw /var/log/mail.log
/usr/local/dlog/bin/dodlog.pl qpsmtpd raw /var/log/
The third throws an error, none of the others return any result.
I run these commands as root, so I can't see how it could be a
permission problem (also, for the munin usage, I've put the munin user
into the adm group, which should give it access to reading logs).
So, with permissions that should be OK, and having tried different
logdir paths, what else could there be?
Cheers,
Kjetil
