-
Incident report
-
Resolution: Duplicate
-
Trivial
-
None
-
5.2.2
-
None
-
Ubuntu 20
We have recently upgraded from a 4.4 version to 5.2. Running on Ubuntu 20.
Since then we experience crashes every exactly two hours:
1358498:20201216:100903.250 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
1706960:20201216:100951.377 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
1706888:20201216:100952.100 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
1710301:20201216:120901.952 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
1710041:20201216:120903.597 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2061040:20201216:121001.732 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2060961:20201216:121002.481 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2314795:20201216:140901.613 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2413768:20201216:160901.703 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2413692:20201216:160903.099 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
2764479:20201216:160952.158 Got signal [signal:11(SIGSEGV),reason:128,refaddr:(nil)]. Crashing ...
Server logs look as shown in attached file.
Interesting is that the problem always happen at xx:09 hours, in a frequence of two hours. We have tried to "move" the issue time by restarting Zabbix Server in between, but still the issue happens every two hours at xx:09 hours. I cannot see anything else on the server causing this behavior. Memory looks available, all fine.
- duplicates
-
ZBX-18725 Server crashes because of enabled event correlation with Close new event operation.
- Closed