zabbix-debug4.log
[ZBX-16006] Zabbix server doesn't start Created: 2019 Apr 16 Updated: 2019 Apr 18 Resolved: 2019 Apr 17 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 4.2.0 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Alexander Shapkin | Assignee: | Aigars Kadikis |
| Resolution: | Declined | Votes: | 0 |
| Labels: | crash, pollers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 18.04, PostgreSQL |
||
| Attachments: |
zabbix-debug4.log
|
| Description |
|
Messages from server log: 8819:20190416:130542.535 Starting Zabbix Server. Zabbix 4.2.0 (revision 91746). 8819:20190416:130542.536 ****** Enabled features ****** 8819:20190416:130542.536 SNMP monitoring: NO 8819:20190416:130542.536 IPMI monitoring: YES 8819:20190416:130542.536 Web monitoring: YES 8819:20190416:130542.536 VMware monitoring: YES 8819:20190416:130542.536 SMTP authentication: YES 8819:20190416:130542.536 Jabber notifications: NO 8819:20190416:130542.536 Ez Texting notifications: YES 8819:20190416:130542.536 ODBC: YES 8819:20190416:130542.536 SSH2 support: YES 8819:20190416:130542.536 IPv6 support: NO 8819:20190416:130542.536 TLS support: YES 8819:20190416:130542.536 ****************************** 8819:20190416:130542.536 using configuration file: /etc/zabbix/zabbix_server.conf 8819:20190416:130542.563 current database version (mandatory/optional): 04020000/04020000 8819:20190416:130542.563 required mandatory version: 04020000 8819:20190416:130604.471 server #0 started [main process] 9449:20190416:130604.501 server #1 started [configuration syncer #1] 9469:20190416:130604.533 server #2 started [alerter #1] 9470:20190416:130604.561 server #3 started [alerter #2] 9471:20190416:130604.589 server #4 started [alerter #3] 9472:20190416:130604.617 server #5 started [housekeeper #1] 9473:20190416:130604.645 server #6 started [timer #1] 9474:20190416:130604.672 server #7 started [http poller #1] 9475:20190416:130604.702 server #8 started [discoverer #1] 9477:20190416:130604.737 server #9 started [history syncer #1] 9478:20190416:130604.764 server #10 started [history syncer #2] 9479:20190416:130604.791 server #11 started [history syncer #3] 9480:20190416:130604.818 server #12 started [history syncer #4] 9481:20190416:130604.847 server #13 started [escalator #1] 9482:20190416:130604.874 server #14 started [proxy poller #1] 9483:20190416:130604.900 server #15 started [self-monitoring #1] 9484:20190416:130604.927 server #16 started [task manager #1] 9485:20190416:130604.954 server #17 started [poller #1] 9486:20190416:130604.991 server #18 started [poller #2] 9487:20190416:130605.016 server #19 started [poller #3] 8819:20190416:130605.016 One child process died (PID:9485,exitcode/signal:11). Exiting ... 8819:20190416:130605.178 syncing history data... 8819:20190416:130605.179 syncing history data done 8819:20190416:130605.179 syncing trend data... 8819:20190416:130605.180 syncing trend data done 8819:20190416:130605.181 Zabbix Server stopped. Zabbix 4.2.0 (revision 91746). |
| Comments |
| Comment by Andris Mednis [ 2019 Apr 16 ] |
|
What operating system ? Can you set DebugLevel=4 in zabbix_server.conf to see more evidence what happens ? |
| Comment by Alexander Shapkin [ 2019 Apr 16 ] |
|
Ubuntu 18.04 (postgresql as DB) Zabbix logs with DebugLevel 4 in attach.
|
| Comment by Andris Mednis [ 2019 Apr 16 ] |
|
It looks strange:
Could it be killed by some external process (systemd?)? Do you start Zabbix server manually, by systemd or by some init script? |
| Comment by Alexander Shapkin [ 2019 Apr 17 ] |
|
The problem was incorrect overrides for the systemd service. Thank you for help! Closing issue. |
