12:05:00.290 Status: dzVents: > protocol: DEFAULT 12:05:00.289 Status: dzVents: > localhostname: raspberrypi 12:05:00.289 Status: dzVents: > controlfile: /etc/monit/monitrc Port response time [0 39m0.456 ms to 127.0.0.1:80 type TCP/IP protocol DEFAULT[0m Port response time [0 39m1.202 s to 127.0.0.1:53 type UDP/IP protocol DEFAULT[0m ![]() After reconnecting to another switch everything was fine again, but somehow the init process must have thought that monit was not running, tried to start it only to find out it was already running.Code: Select all Monit 5.25.2 uptime: 2d 8h 18m Yesterday the switch where this server was connected to died. Replaying a configuration from the backup from the day before yesterday didn't help.įinally I checked /var/log/messages (should have done that at first, but you know how it goes), where I discovered the wonderful "init: Id "mo" respawning too fast: disabled for 5 minutes". However, every five minutes monit sent a SYNC, received a SYNC/ACK, but instead of acknowledging with an ACK the very next package was a RST. When I tcpdumped the traffic on the monit instance everything worked fine: Monit opens a TCP connection and the whole process of sending SYN, SYN/ACK, ACK, traffic and finally FIN, FIN/ACK etc. When I investigated further I discovered that the firewall did open all necessary connections, so it wasn't a fault there. The server, however, *was* reachable and working (as it tested successfully from another server). Sometimes it skipped the five minutes and came back after ten minutes or more (but always a multiple of five), sometimes it jumped one minute ahead and faulted after six minutes, to continue then again after five. Since yesterday I received the message "connection failed, INET[via TCP is not ready for i|o - Interrupted system call" every 5 minutes from a monit instance. I write this purely because googling for the error message did not show up with a single useful entry. ![]() Skip the text and jump to the solution at the bottom if you are not interested in my adventure. hoping that this helps someone somewhere in the future. Script is saved in a file called /bin/xyz, you can call this script from monit Starting an imaginary program (a Java program in this case). Since monit requires all programs to have a pid file, what do I do?Ī: Create a wrapper script and have the script create a pid fileīefore it starts the program. Q: I have a program that does not create its own pid file. Test for zombie processes and will raise an alert if a process has become a Some serversĬan crash and leave a zombie process, and appear to run. ![]() Program is not running and restart it even if a pid file exist. Manner, then the process ID (pid) will not exist and monit will know that the If a program crashes and dies in a "normal" Q: If a program crashes without removing its pid file, will monit recognise that the program is not running?Ī: Yes, Monit will always check that the pid number in a pid fileīelongs to a running process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |