On 2006-12-14, Christian Christmann <(E-Mail Removed)> wrote:
>
> I use the Nagios plug-in check_log to check my log files for suspecious
> entires. However, the module avails with the error message that the log
> files are not readable. For example:
> -rw-r----- 1 root adm 36490 Dec 14 15:31 /var/log/messages
>
> It is just readable for root and adm but not for the user "nagios" who, as
> I assume, is executing the Nagios plug-ins. So, how can I solve the
> permission problem?
Give user nagios permission to read the logfile. You might try adding
nagios to the adm group (thus giving user nagios access to all the files
owned by group adm), or try chgrp'ing the needed files to group nagios,
or chmod'ing o+r the files in question. It all depends on how paranoid
you are at your site; some sites would not consider allowing any
world-readable log files, others won't care.
> Another problem I have since I installed Nagios are strange entries in my
> /var/log/messages:
>
> nagios: Error: Could not connect to MySQL database '' on host '' using
> username '' and password 'XXXXXX'. Retention data will not be processed or
> saved!
> nagios: Error: Could not re-connect to database server on host '' for
> status data. I'll keep trying every 60 seconds...
>
> Where do they come from and how can I solve them?
You've probably configured nagios to log its status to a mysql database.
Check your nagios config files and either turn this off (if you don't
want this) or fix your config (if you do).
--keith
--
kkeller-(E-Mail Removed)
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
Similar Threads
Linear Mode
