![]() ![]() What does status mean other than the interpretation of the last exit code of the given check-script programm?Īnd there is another reaction from monit, which I can't understand, perhaps anybody can explain it to me? I don't understand, why monit is reporting an "error. ![]() To me it seems, that the check-script is returning exit value 0 but status is reported / interpreted as "Status failed". and the following status screen from 'monit status': monit status info : 'lo-check-8101' exec: '/bin/bash /opt/libreoffice/loproc_is_up.sh' error : 'lo-check-8101' status failed (0) - no output Monit log after restart info : Starting Monit 5.25.1 daemon with http interface at :2812 The problem is, that I don't understand, why monit is logging the following entries: The problem I would like to talk about here. if this sounds a little bit complicated, I'm sorry, but that is not The action-scripts (loproc_is_down.sh / loproc_is_up.sh) are adding / deletingĪn iptables rule to pronounce the status to a running haproxy, who is port-checking that Running LibreOffice Process by sending HTML, requesting TEXT and check the The check-script is returning 0 if everything is ok and 101 if there is anĮrror with that LibreOffice Instance. This LibreOffice Instance is listening on port 8101. If status = 0 then exec "/bin/bash /opt/libreoffice/loproc_is_up.sh" If status != 0 then exec "/bin/bash /opt/libreoffice/loproc_is_down.sh" Here is my monit config for this approach: cat /etc/monit/conf.d/libreofficeĬheck program lo-check-8101 with path "/bin/bash /opt/libreoffice/chkloproc.sh TestLOPort8101 8101" ![]() I want to monitor a headless running LibreOffice-Process with monit version 5.25.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |