Hi! I have a problem with printers that sometimes reports OK-states when they shouldn't.
It is the toner-checks on some HP-printers that reports warning when they should. We acknowledge the problem and it disappears from unhandled problems like it should. But then at some times the printers all of a sudden reports that the toner is 100% and the service goes green. By the next check it is back to Warning (or whatever) again and we have to acknowledge it again. We keep unhandled problems clean and displayed on the wall. The staff are getting bored at acking the same problem over and over again. I understand that it is the printers that have problem, but fixing them is probably not an option. Does anyone have a solution or some idea I can work from? Maybe it's simple, maybe someone else have seen the same thing, we see it on 12 printers here. Maybe my brain is just slow today ;-) My only idea just now is to write a wrapper-plugin that checks twice with a small delay. The problem is that I don't know for how long the printers reports OK (all I can see in the log is that it is less than 5 minutes...) and I cannot reproduce the state for testing. /Marcus -- Marcus Rejås jabber: mar...@jabber.rejas.se ,= ,-_-. =. Rejås Datakonsult e-mail: mar...@rejas.se ((_/)o o(\_)) Vårgatan 2 web: http://www.rejas.se `-'(. .)`-' s-761 50 Norrtälje gpg-key: http://gpg.rejas.se \_/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
