-
Incident report
-
Resolution: Duplicate
-
Critical
-
None
-
None
-
None
-
None
I had experienced regarding zabbix4.0.2 and zabbix4.0.2rc1. Unfortunately both of them after installation (through source package) and after first restart or server rebooting don't work with following Error in log.
zabbix-server status is "Active (exited)":
7610:20181207:195302.027 ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
7610:20181207:195302.027 ================================
7610:20181207:195302.027 Please consider attaching a disassembly listing to your bug report.
7610:20181207:195302.028 This listing can be produced with, e.g., objdump -DSswx zabbix_server.
7610:20181207:195302.028 ================================
7603:20181207:195302.032 One child process died (PID:7610,exitcode/signal:1). Exiting ...
zabbix_server [7603]: Error waiting for process with PID 7610: [10] No child processes
7603:20181207:195302.055 syncing history data...
7603:20181207:195302.055 syncing history data done
7603:20181207:195302.055 syncing trend data...
7603:20181207:195302.055 syncing trend data done
7603:20181207:195302.055 Zabbix Server stopped. Zabbix 4.0.2rc1 (revision 87102).
what should I do?
httpd : Apache/2.4.6
MariaDB : mysql Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
- duplicates
-
ZBX-10461 Zabbix (alerter process) crash on CentOS 7
- Closed