Не запускается zabbix_server. (code=exited, status=1/FAILURE)

maxxus

Junior Member

Joined: Nov 2020
Posts: 17

Не запускается zabbix_server. (code=exited, status=1/FAILURE)

23-11-2020, 16:11

Всем привет.
С Zabbix только начал разбираться.
Установил на отдельный сервер, настроил некоторые параметры опроса оборудования и все было хорошо пару недель.
Затем я добавил несколько хостов и сервер "упал" из-за нехватки оперативной памяти.
Память расширена и даже часть хостов удалена, а сервер не поднимается.
Система: Debian 10.6
Процессор: Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz
Память: 4 Гб
Zabbix 5.0 LTS

А вот и проблема:

# /etc/init.d/zabbix-server status

Code:

● zabbix-server.service - Zabbix Server
  Loaded: loaded (/lib/systemd/system/zabbix-server.service; enabled; vendor preset: enabled)
  Active: activating (auto-restart) (Result: exit-code) since Mon 2020-11-23 15:50:18 EET; 3s ago
 Process: 22025 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
 Process: 22037 ExecStop=/bin/kill -SIGTERM $MAINPID [COLOR=#ff5454][B](code=exited, status=1/FAILURE)[/B][/COLOR]
Main PID: 22027 (code=exited, status=0/SUCCESS)

ноя 23 15:50:18 SERV systemd[1]: [COLOR=#000000][B]zabbix-server.service: Control process exited, code=exited, status=1/FAILURE[/B][/COLOR]
ноя 23 15:50:18 SERV systemd[1]: [COLOR=#000000][B]zabbix-server.service: Failed with result 'exit-code'.[/B][/COLOR]

Code:

# tail -f zabbix_server.log

Code:

[FONT=monospace][COLOR=#000000]21947:20201123:154913.600 Starting Zabbix Server. Zabbix 5.0.5 (revision eaa427cf19). [/COLOR]
21947:20201123:154913.601 ****** Enabled features ******
21947:20201123:154913.601 SNMP monitoring:           YES
21947:20201123:154913.601 IPMI monitoring:           YES
21947:20201123:154913.601 Web monitoring:            YES
21947:20201123:154913.601 VMware monitoring:         YES
21947:20201123:154913.601 SMTP authentication:       YES
21947:20201123:154913.601 ODBC:                      YES
21947:20201123:154913.601 SSH support:               YES
21947:20201123:154913.601 IPv6 support:              YES
21947:20201123:154913.602 TLS support:               YES
21947:20201123:154913.602 ******************************
21947:20201123:154913.602 using configuration file: /etc/zabbix/zabbix_server.conf
21947:20201123:154913.640 current database version (mandatory/optional): 05000000/05000002
21947:20201123:154913.640 required mandatory version: 05000000
21947:20201123:154913.737 server #0 started [main process]
21954:20201123:154913.738 server #1 started [configuration syncer #1]
21954:20201123:154914.149 __mem_malloc: skipped 0 asked 256 skip_min 18446744073709551615 skip_max 0
21954:20201123:154914.149 [file:dbconfig.c,line:96] __zbx_mem_malloc(): out of memory (requested 256 bytes)
21954:20201123:154914.149 [file:dbconfig.c,line:96] __zbx_mem_malloc(): please increase CacheSize configuration parameter
21954:20201123:154914.149 === memory statistics for configuration cache ===
21954:20201123:154914.149 free chunks of size     24 bytes:       12
21954:20201123:154914.149 free chunks of size     32 bytes:        3
21954:20201123:154914.149 free chunks of size     40 bytes:        6
21954:20201123:154914.149 free chunks of size     48 bytes:        5
21954:20201123:154914.149 free chunks of size     56 bytes:        5
21954:20201123:154914.149 min chunk size:         24 bytes
21954:20201123:154914.150 max chunk size:         56 bytes
21954:20201123:154914.150 memory of total size 7135992 bytes fragmented into 78266 chunks
21954:20201123:154914.150 of those,       1144 bytes are in       31 free chunks
21954:20201123:154914.150 of those,    7134848 bytes are in    78235 used chunks
21954:20201123:154914.150 of those,    1252240 bytes are used by allocation overhead
21954:20201123:154914.150 ================================
21954:20201123:154914.150 === Backtrace: ===
21954:20201123:154914.151 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x3f) [0x55e31fa0bf2b]
21954:20201123:154914.151 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_mem_malloc+0x180) [0x55e31fa06c28]
21954:20201123:154914.151 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x190fdc) [0x55e31f9cdfdc]
21954:20201123:154914.152 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1db5a1) [0x55e31fa185a1]
21954:20201123:154914.152 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_vector_ptr_append+0x1c) [0x55e31fa18763]
21954:20201123:154914.152 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x19c0ef) [0x55e31f9d90ef]
21954:20201123:154914.152 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0xb17) [0x55e31f9da64f]
21954:20201123:154914.152 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x116) [0x55e31f893962]
21954:20201123:154914.152 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x37) [0x55e31fa1ac74]
21954:20201123:154914.152 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0x9cb) [0x55e31f8855ed]
21954:20201123:154914.152 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x2ff) [0x55e31fa0bb37]
21954:20201123:154914.152 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x2f5) [0x55e31f884bd7]
21954:20201123:154914.152 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fe75c09009b]
21954:20201123:154914.152 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2a) [0x55e31f883c8a]
21947:20201123:154914.156 One child process died (PID:21954,exitcode/signal:1). Exiting ...
21947:20201123:154914.170 syncing trend data...
21947:20201123:154914.171 syncing trend data done
21947:20201123:154914.171 Zabbix Server stopped. Zabbix 5.0.5 (revision eaa427cf19).[/FONT]

Как видно сервер стартует, а затем через секунду падает:

Code:

[FONT=monospace]21947:20201123:154914.156 One child process died (PID:21954,exitcode/signal:1). Exiting ...
21947:20201123:154914.170 syncing trend data...
21947:20201123:154914.171 syncing trend data done
21947:20201123:154914.171 Zabbix Server stopped. Zabbix 5.0.5 (revision eaa427cf19).[/FONT]

При этом в syslog вижу:

Code:

[FONT=monospace][COLOR=#000000]Nov 23 16:01:35 SERV systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart. [/COLOR]
Nov 23 16:01:35 SERV systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 88277.
Nov 23 16:01:35 SERV systemd[1]: Stopped Zabbix Server.
Nov 23 16:01:35 SERV systemd[1]: Starting Zabbix Server...
Nov 23 16:01:35 SERV systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
Nov 23 16:01:35 SERV systemd[1]: Started Zabbix Server.
Nov 23 16:01:36 SERV kill[22904]: Usage:
Nov 23 16:01:36 SERV kill[22904]:  kill [options] <pid> [...]
Nov 23 16:01:36 SERV kill[22904]: Options:
Nov 23 16:01:36 SERV kill[22904]:  <pid> [...]            send signal to every <pid> listed
Nov 23 16:01:36 SERV kill[22904]:  -<signal>, -s, --signal <signal>
Nov 23 16:01:36 SERV kill[22904]:                         specify the <signal> to be sent
Nov 23 16:01:36 SERV kill[22904]:  -l, --list=[<signal>]  list all signal names, or convert one to a name
Nov 23 16:01:36 SERV kill[22904]:  -L, --table            list all signal names in a nice table
Nov 23 16:01:36 SERV kill[22904]:  -h, --help     display this help and exit
Nov 23 16:01:36 SERV kill[22904]:  -V, --version  output version information and exit
Nov 23 16:01:36 SERV kill[22904]: For more details see kill(1).
Nov 23 16:01:36 SERV systemd[1]: zabbix-server.service: Control process exited, code=exited, status=1/FAILURE
Nov 23 16:01:36 SERV systemd[1]: zabbix-server.service: Failed with result 'exit-code'.[/FONT]

Файл /run/zabbix/zabbix_server.pid создается, если смотреть с помощью ls.
И удаляется через секунду после создания.
Такое ощущение, что файл удаляется, а zabbix уже падает из-за отсутствия это файла.

В общем мне не понятно что еще можно посмотреть и траблшутить, чтобы разобраться с этой проблемой.

Если кто сталкивался с подобным или имеет в голове идеи - поделитесь плиз.

Tags: error, zabbix

Hamardaban

Senior Member

Joined: May 2019

Posts: 2713
#2

23-11-2020, 19:52

Вот это в логе не заметили?

21954:20201123:154914.149 [file:dbconfig.c,line:96] __zbx_mem_malloc(): out of memory (requested 256 bytes)
21954:20201123:154914.149 [file:dbconfig.c,line:96] __zbx_mem_malloc(): please increase CacheSize configuration parameter

исправляйте.
Comment
1 - 2

2 comments

#2.1

maxxus commented

30-11-2020, 17:24

Editing a comment

Не знаю как не заметил... затмение, видимо...
Спасибо )

#2.2

Hamardaban commented

30-11-2020, 18:10

Editing a comment

Бывает - глаз замыливается...

Previous template Next

Ad Widget

Не запускается zabbix_server. (code=exited, status=1/FAILURE)

Не запускается zabbix_server. (code=exited, status=1/FAILURE)

Comment