After updating to 7, server and proxies mysteriously exit on their own

[[email protected]]

After updating to 7, every 10-15 mins all my Zabbix server and proxies all mysteriously exit. The only symptom I see in the log is

1:20240607:125341.669 One child process died (PID:2251,exitcode/signal:255). Exiting ...

No other interesting detail I can find. Upping the debug level to 5 didn't reveal any more clues. The same config was fine of course with Zabbix 6.4..

Any ideas on how to debug this? thanks..

[Markku]

Maybe you could check what process was the one (PID 2251) that unexpectedly died, if that gives you more information about the reason.

Markku

[[email protected]]

How can I do that though, since by the time I get the PID it's dead.. There are no other mentions in the logs about that PID

[Markku]

"ps aux" shows all the processes along with the Zabbix process descriptions, so if your problem occurs every 10-15 minutes, just check the process list and then see the PID that fails a few minutes later.

Markku

[cyber]

How can I do that though, since by the time I get the PID it's dead.. There are no other mentions in the logs about that PID

There should be actually... When you look for Startup line, then after that there is a bunch of lines for starting all kind of processes

 1877:20240418:085055.469 server #0 started [main process]
5257:20240418:085055.471 server #1 started [service manager #1]
5258:20240418:085055.471 server #2 started [configuration syncer #1]

first position on those lines is a PID for that process

[[email protected]]

So I finally managed to track down the offending process by constantly monitoring ps and catching the right pid (thanks Markku ) . cyber it was not in the logs because it's an SSH invocation started by some external items. That ssh invocation occasionally exits with code 255 and that is what is causing zabbix server and proxies to exit. Why that is the case with 7.0 and was not before is left to the reader but at least I can work around it. In any case, it would seem that zabbix processes should not exit in those circumstances..

[Markku]

If you can make a minimally reproducable case about the configuration, you could open a case in Zabbix support portal (shortlinked to prevent post banning).

Markku