I am monitoring a dozen Windows servers, 4 of which are domain controllers. Everything works fine except monitoring the File Replication Service event log. That crashes Zabbix.
The item is set up the same way the rest of the event log items are:
Type: ZABBIX agent (active)
Key: eventlog[File Replication Service]
Type of Information: Log
When I disable this item, the server will run without problem for days (so far). When I enable this item, the zabbix_server process crashes within a half hour.
The log file (in debug mode) shows this:
005678:20070403:175726 One server process died. Shutting down...
005678:20070403:175726 0. Killing PID=[5680]
005678:20070403:175726 1. Killing PID=[5681]
005678:20070403:175726 2. Killing PID=[5682]
005678:20070403:175726 3. Killing PID=[5683]
005678:20070403:175726 4. Killing PID=[5687]
005678:20070403:175726 5. Killing PID=[5688]
005678:20070403:175726 6. Killing PID=[5689]
005678:20070403:175726 7. Killing PID=[5690]
005678:20070403:175726 8. Killing PID=[5693]
005678:20070403:175726 9. Killing PID=[5694]
005678:20070403:175726 ZABBIX server is down.
005680:20070403:175726 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005681:20070403:175726 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005682:20070403:175726 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005688:20070403:175726 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005689:20070403:175726 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005690:20070403:175726 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005693:20070403:175726 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005694:20070403:175726 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005687:20070403:175726 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
It's very similar to the net-snmp problems discussed in http://www.zabbix.com/forum/showthread.php?t=2952 but I'm not using net-snmp, and it's an event log that's causing the crash. I had thought that it might be the space in the log name, but the "Directory Services" log runs without problem. Any ideas?
The item is set up the same way the rest of the event log items are:
Type: ZABBIX agent (active)
Key: eventlog[File Replication Service]
Type of Information: Log
When I disable this item, the server will run without problem for days (so far). When I enable this item, the zabbix_server process crashes within a half hour.
The log file (in debug mode) shows this:
005678:20070403:175726 One server process died. Shutting down...
005678:20070403:175726 0. Killing PID=[5680]
005678:20070403:175726 1. Killing PID=[5681]
005678:20070403:175726 2. Killing PID=[5682]
005678:20070403:175726 3. Killing PID=[5683]
005678:20070403:175726 4. Killing PID=[5687]
005678:20070403:175726 5. Killing PID=[5688]
005678:20070403:175726 6. Killing PID=[5689]
005678:20070403:175726 7. Killing PID=[5690]
005678:20070403:175726 8. Killing PID=[5693]
005678:20070403:175726 9. Killing PID=[5694]
005678:20070403:175726 ZABBIX server is down.
005680:20070403:175726 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005681:20070403:175726 Server [2]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005682:20070403:175726 Server [3]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005688:20070403:175726 Server [6]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005689:20070403:175726 Server [7]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005690:20070403:175726 Server [8]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005693:20070403:175726 Server [9]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005694:20070403:175726 Server [10]. Got QUIT or INT or TERM or PIPE signal. Exiting...
005687:20070403:175726 Server [5]. Got QUIT or INT or TERM or PIPE signal. Exiting...
It's very similar to the net-snmp problems discussed in http://www.zabbix.com/forum/showthread.php?t=2952 but I'm not using net-snmp, and it's an event log that's causing the crash. I had thought that it might be the space in the log name, but the "Directory Services" log runs without problem. Any ideas?
Comment