El 29/04/2010 19:24, Markus Wernicke escribió:
nag...@monitor:/usr/local/nagios/libexec$ ./check_mysql_performance -H 1.2.3.4
-u nagios -p pw123
can't write into /tmp/nagios_mysql_perf_1.2.3.4_a3g/M6.LaOqsM.tmp: No such file
or directory at ./check_mysql_performance line 514
Seems like a permission problem, but when i create that directory manually as
nagios user and run the script again, it works...
Directory /tmp is in ubuntu not the best place to but data, because the
directory will be cleaned every reboot by default. Maybe /var/tmp would be
better.
The fact that the check writes to /tmp is OK (it's meant to be that
way...). In case of server restarts, the temp file will be recreated...
you'll just get one measurement less. If you are executing that plugin
via NRPE, the fact that the MySQL server also restarted will make the
temp file content meaningless anyway ;)
The problem is that the temp file has a "/" in the name, and the plugin
thinks it has to access a directory (that doesn't exist). This seems to
come from the use of crypt() to form the temp filename... I think the
plugin was originally contributed using MD5.
I'll comment this to development to see if it can be fixed.
Cheers,
Jose Luis Martinez
CAPSiDE
jlmarti...@capside.com
_______________________________________________
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users
