Ad Widget

**storyteller** · 10-10-2019, 10:10

I guess not. I have the same message on my zabbix servers.

**Atsushi** · 10-10-2019, 11:04

If the PID file cannot be created normally, it may not be able to exit normally when the service is restarted or the server is shut down. I don't think there will be a problem when it is running continuously, but I think it should be resolved after considering future restarts.

Possible causes for this issue are either not using the official Zabbix package or an older version of the package.
Although it depends on the OS distribution and version used, the directory where the PID file is placed may be created on a temporary file system, so that directory is deleted when the OS is restarted. Therefore, if we install using a package, it is configured to automatically create the necessary directories.
If Zabbix is installed from the source, the directory may not be automatically created. In the case of RHEL, the configuration file for Zabbix is placed in the directory /usr/lib/tmpfiles.d/.

**josebildo** · 11-07-2020, 17:41

Hi guys..

i'm using zabbix 5.0 on ubuntu 18.04 and i have the same problem but is NOT running... i increased the cache size..and i realized that the file zabbix_server.pid is not created. this started after a few days. i added about a 100 hosts ...it seems that the changes are not loaded yet 'cause of this.

zabbix_agent is ok.

/var/run/zabbix# ls
zabbix_agentd.pid
/var/run/zabbix#

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 Sat 2020-07-11 12:37:06 -03; 3s ago
Process: 22010 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 21985 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 21994 (code=exited, status=0/SUCCESS)
/var/log/zabbix# service zabbix-agent status
● zabbix-agent.service - Zabbix Agent
Loaded: loaded (/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-07-10 14:20:56 -03; 22h ago
Main PID: 1149 (zabbix_agentd)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/zabbix-agent.service
├─1149 /usr/sbin/zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf
├─1152 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
├─1155 /usr/sbin/zabbix_agentd: listener #1 [waiting for connection]
├─1157 /usr/sbin/zabbix_agentd: listener #2 [waiting for connection]
├─1158 /usr/sbin/zabbix_agentd: listener #3 [waiting for connection]
└─1160 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]

jul 10 14:20:56 monitor systemd[1]: Starting Zabbix Agent...
jul 10 14:20:56 monitor systemd[1]: Started Zabbix Agent.
:/var/log/zabbix# service apache2 status
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) since Fri 2020-07-10 14:20:56 -03; 22h ago
Main PID: 1325 (apache2)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/apache2.service
├─ 1325 /usr/sbin/apache2 -k start
├─10012 /usr/sbin/apache2 -k start
├─10013 /usr/sbin/apache2 -k start
├─10014 /usr/sbin/apache2 -k start
├─10015 /usr/sbin/apache2 -k start
└─10016 /usr/sbin/apache2 -k start

jul 10 14:20:56 monitor systemd[1]: Starting The Apache HTTP Server...
jul 10 14:20:56 monitor apachectl[1108]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using
jul 10 14:20:56 monitor systemd[1]: Started The Apache HTTP Server.
jul 10 14:37:14 monitor systemd[1]: Reloading The Apache HTTP Server.
jul 10 14:37:44 monitor apachectl[6970]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using
jul 10 14:37:44 monitor systemd[1]: Reloaded The Apache HTTP Server.
jul 11 00:08:17 monitor systemd[1]: Reloading The Apache HTTP Server.
jul 11 00:08:47 monitor apachectl[9753]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using
jul 11 00:08:47 monitor systemd[1]: Reloaded The Apache HTTP Server.

the other services are ok.

my log now :

20786:20200711:123140.227 Starting Zabbix Server. Zabbix 5.0.1 (revision c2a0b03480).
20786:20200711:123140.227 ****** Enabled features ******
20786:20200711:123140.227 SNMP monitoring: YES
20786:20200711:123140.227 IPMI monitoring: YES
20786:20200711:123140.227 Web monitoring: YES
20786:20200711:123140.227 VMware monitoring: YES
20786:20200711:123140.227 SMTP authentication: YES
20786:20200711:123140.227 ODBC: YES
20786:20200711:123140.227 SSH support: YES
20786:20200711:123140.227 IPv6 support: YES
20786:20200711:123140.227 TLS support: YES
20786:20200711:123140.227 ******************************
20786:20200711:123140.227 using configuration file: /etc/zabbix/zabbix_server.conf
20786:20200711:123140.234 current database version (mandatory/optional): 05000000/05000000
20786:20200711:123140.234 required mandatory version: 05000000
20786:20200711:123140.245 server #0 started [main process]
20791:20200711:123140.246 server #1 started [configuration syncer #1]
20791:20200711:123140.561 __mem_malloc: skipped 0 asked 136 skip_min 18446744073709551615 skip_max 0
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): out of memory (requested 136 bytes)
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): please increase CacheSize configuration parameter
20791:20200711:123140.561 === memory statistics for configuration cache ===
20791:20200711:123140.562 free chunks of size 24 bytes: 207
20791:20200711:123140.562 free chunks of size 32 bytes: 3
20791:20200711:123140.562 free chunks of size 40 bytes: 7
20791:20200711:123140.562 free chunks of size 120 bytes: 1
20791:20200711:123140.562 min chunk size: 24 bytes
20791:20200711:123140.562 max chunk size: 120 bytes
20791:20200711:123140.562 memory of total size 8388232 bytes fragmented into 76622 chunks
20791:20200711:123140.562 of those, 5464 bytes are in 218 free chunks
20791:20200711:123140.562 of those, 7156832 bytes are in 76404 used chunks
20791:20200711:123140.562 ================================
20791:20200711:123140.562 === Backtrace: ===
20791:20200711:123140.562 14: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x4e) [0x555f4d75b578]
20791:20200711:123140.562 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_mem_malloc+0x180) [0x555f4d7562c7]
20791:20200711:123140.562 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x19c13d) [0x555f4d71b13d]
20791:20200711:123140.562 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert_ext+0x12f) [0x555f4d7617a1]
20791:20200711:123140.562 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert+0x2d) [0x555f4d761670]
20791:20200711:123140.562 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCfind_id+0x9b) [0x555f4d71bb87]
20791:20200711:123140.562 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1a4b9f) [0x555f4d723b9f]
20791:20200711:123140.562 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0xfe4) [0x555f4d728818]
20791:20200711:123140.562 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x116) [0x555f4d5d3f1b]
20791:20200711:123140.562 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x37) [0x555f4d76a9b2]
20791:20200711:123140.562 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0x9e4) [0x555f4d5c52b2]
20791:20200711:123140.562 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x2ff) [0x555f4d75b14b]
20791:20200711:123140.562 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x305) [0x555f4d5c48b8]
20791:20200711:123140.562 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1fa87c3b97]
20791:20200711:123140.562 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2a) [0x555f4d5c391a]
20786:20200711:123140.565 One child process died (PID:20791,exitcode/signal:1). Exiting ...
20786:20200711:123140.566 syncing trend data...
20786:20200711:123140.566 syncing trend data done
20786:20200711:123140.566 Zabbix Server stopped. Zabbix 5.0.1 (revision c2a0b03480).

cache conf..

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=64G

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryCacheSize=2G

### Option: HistoryIndexCacheSize
# Size of history index cache, in bytes.
# Shared memory size for indexing history cache.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryIndexCacheSize=2G

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=2G

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
# ValueCacheSize=64G

i had no problems to run it at the first.. but after the discovery ... restarted and here i am..i've tried a lot of things.
sorry for my english im from argentina.

if anyone knows how solve this..please. thanks

**Atsushi** · 13-07-2020, 03:36

Hi josebildo,

Are the settings as described here?
A line that has "#" as the first character of the line is a comment line. If you specify a value in the comment line, it will not be read by the server process.

ex.

Code:

# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=8M
CacheSize=64M

**josebildo** · 14-07-2020, 00:13

Thanks for the reply Atsushi..
yes i know .. it is a comment line and i've tried both.... with and without the hashtag.
stilll not working. and
I got this message:
31248:20200713:185507.230 using configuration file: /etc/zabbix/zabbix_server.conf
31248:20200713:185507.230 cannot initialize database cache: cannot get private shared memory of size 2147483648 for history cache: [22] Invalid argument

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=64G

CacheSize=64G

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryCacheSize=2G

HistoryCacheSize=64M

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=2G

TrendCacheSize=32M

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
# ValueCacheSize=64G

ValueCacheSize=64M

**josebildo** · 16-07-2020, 16:09

hello ! i wanted to refresh the post to say I finally get the solution..I've increased the cache size like this:

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
CacheSize=32M

I think that my server does not has the memory to increase to 64G.

I hope this helps some one.
thanks atsushi too!

**natty** · 17-07-2020, 15:06

I want to run two agents on one host after my new host configuration files created my agent won't start!!!!
zabbix_agentd -c /root/zabbix_agent/conf/zabbix_agentd2.conf

I get this message in the logfile;

zabbix_agentd [193790]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavaila
ble
zabbix_agentd [211102]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavaila
ble
zabbix_agentd [11669]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailab
le
zabbix_agentd [11998]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailab
le
zabbix_agentd [215488]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavaila
ble
zabbix_agentd [47550]: Is this process already running? Could not lock PID file [/tmp/zabbix_agentd.pid]: [11] Resource temporarily unavailab
le

can someone help? Many Thanks

**Badget1t** · 18-07-2020, 11:43

If we install using a package, it is configured to automatically create the necessary directories mycfavisit.

**weejayrane** · 31-12-2022, 14:19

20786:20200711:123140.227 Starting Zabbix Server. Zabbix 5.0.1 (revision c2a0b03480).
20786:20200711:123140.227 ****** Enabled features ******
20786:20200711:123140.227 SNMP monitoring: YES
20786:20200711:123140.227 IPMI monitoring: YES
20786:20200711:123140.227 Web monitoring: YES
20786:20200711:123140.227 VMware monitoring: YES
20786:20200711:123140.227 SMTP authentication: YES
20786:20200711:123140.227 ODBC: YES
20786:20200711:123140.227 SSH support: YES
20786:20200711:123140.227 IPv6 support: YES
20786:20200711:123140.227 TLS support: YES
20786:20200711:123140.227 ******************************
20786:20200711:123140.227 using configuration file: /etc/zabbix/zabbix_server.conf
20786:20200711:123140.234 current database version (mandatory/optional): 05000000/05000000
20786:20200711:123140.234 required mandatory version: 05000000
20786:20200711:123140.245 server #0 started [main process]
20791:20200711:123140.246 server Home started [configuration syncer #1]
20791:20200711:123140.561 __mem_malloc: skipped 0 asked 136 skip_min 18446744073709551615 skip_max 0
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): out of memory (requested 136 bytes)
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): please increase CacheSize configuration parameter
20791:20200711:123140.561 === memory statistics for configuration cache ===
20791:20200711:123140.562 free chunks of size 24 bytes: 207
20791:20200711:123140.562 free chunks of size 32 bytes: 3
20791:20200711:123140.562 free chunks of size 40 bytes: 7
20791:20200711:123140.562 free chunks of size 120 bytes: 1
20791:20200711:123140.562 min chunk size: 24 bytes
20791:20200711:123140.562 max chunk size: 120 bytes
20791:20200711:123140.562 memory of total size 8388232 bytes fragmented into 76622 chunks
20791:20200711:123140.562 of those, 5464 bytes are in 218 free chunks
20791:20200711:123140.562 of those, 7156832 bytes are in 76404 used chunks
20791:20200711:123140.562 ================================
20791:20200711:123140.562 === Backtrace: ===
20791:20200711:123140.562 14: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x4e) [0x555f4d75b578]
20791:20200711:123140.562 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_mem_malloc+0x180) [0x555f4d7562c7]
20791:20200711:123140.562 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x19c13d) [0x555f4d71b13d]
20791:20200711:123140.562 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert_ext+0x12f) [0x555f4d7617a1]
20791:20200711:123140.562 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert+0x2d) [0x555f4d761670]
20791:20200711:123140.562 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCfind_id+0x9b) [0x555f4d71bb87]
20791:20200711:123140.562 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1a4b9f) [0x555f4d723b9f]
20791:20200711:123140.562 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0xfe4) [0x555f4d728818]
20791:20200711:123140.562 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x116) [0x555f4d5d3f1b]
20791:20200711:123140.562 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x37) [0x555f4d76a9b2]
20791:20200711:123140.562 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0x9e4) [0x555f4d5c52b2]
20791:20200711:123140.562 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x2ff) [0x555f4d75b14b]
20791:20200711:123140.562 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x305) [0x555f4d5c48b8]
20791:20200711:123140.562 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1fa87c3b97]
20791:20200711:123140.562 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2a) [0x555f4d5c391a]
20786:20200711:123140.565 One child process died (PID:20791,exitcode/signal:1). Exiting ...
20786:20200711:123140.566 syncing trend data...
20786:20200711:123140.566 syncing trend data done
20786:20200711:123140.566 Zabbix Server stopped. Zabbix 5.0.1 (revision c2a0b03480).

cache conf..

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=64G

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryCacheSize=2G

### Option: HistoryIndexCacheSize
# Size of history index cache, in bytes.
# Shared memory size for indexing history cache.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryIndexCacheSize=2G

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=2G

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
# ValueCacheSize=64G

**cyber** · 03-01-2023, 11:22

Originally posted by weejayrane

20786:20200711:123140.227 Starting Zabbix Server. Zabbix 5.0.1 (revision c2a0b03480).
20786:20200711:123140.227 ****** Enabled features ******
20786:20200711:123140.227 SNMP monitoring: YES
20786:20200711:123140.227 IPMI monitoring: YES
20786:20200711:123140.227 Web monitoring: YES
20786:20200711:123140.227 VMware monitoring: YES
20786:20200711:123140.227 SMTP authentication: YES
20786:20200711:123140.227 ODBC: YES
20786:20200711:123140.227 SSH support: YES
20786:20200711:123140.227 IPv6 support: YES
20786:20200711:123140.227 TLS support: YES
20786:20200711:123140.227 ******************************
20786:20200711:123140.227 using configuration file: /etc/zabbix/zabbix_server.conf
20786:20200711:123140.234 current database version (mandatory/optional): 05000000/05000000
20786:20200711:123140.234 required mandatory version: 05000000
20786:20200711:123140.245 server #0 started [main process]
20791:20200711:123140.246 server Home started [configuration syncer #1]
20791:20200711:123140.561 __mem_malloc: skipped 0 asked 136 skip_min 18446744073709551615 skip_max 0
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): out of memory (requested 136 bytes)
20791:20200711:123140.561 [file:dbconfig.c,line:95] __zbx_mem_malloc(): please increase CacheSize configuration parameter
20791:20200711:123140.561 === memory statistics for configuration cache ===
20791:20200711:123140.562 free chunks of size 24 bytes: 207
20791:20200711:123140.562 free chunks of size 32 bytes: 3
20791:20200711:123140.562 free chunks of size 40 bytes: 7
20791:20200711:123140.562 free chunks of size 120 bytes: 1
20791:20200711:123140.562 min chunk size: 24 bytes
20791:20200711:123140.562 max chunk size: 120 bytes
20791:20200711:123140.562 memory of total size 8388232 bytes fragmented into 76622 chunks
20791:20200711:123140.562 of those, 5464 bytes are in 218 free chunks
20791:20200711:123140.562 of those, 7156832 bytes are in 76404 used chunks
20791:20200711:123140.562 ================================
20791:20200711:123140.562 === Backtrace: ===
20791:20200711:123140.562 14: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_backtrace+0x4e) [0x555f4d75b578]
20791:20200711:123140.562 13: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](__zbx_mem_malloc+0x180) [0x555f4d7562c7]
20791:20200711:123140.562 12: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x19c13d) [0x555f4d71b13d]
20791:20200711:123140.562 11: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert_ext+0x12f) [0x555f4d7617a1]
20791:20200711:123140.562 10: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_hashset_insert+0x2d) [0x555f4d761670]
20791:20200711:123140.562 9: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCfind_id+0x9b) [0x555f4d71bb87]
20791:20200711:123140.562 8: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](+0x1a4b9f) [0x555f4d723b9f]
20791:20200711:123140.562 7: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](DCsync_configuration+0xfe4) [0x555f4d728818]
20791:20200711:123140.562 6: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](dbconfig_thread+0x116) [0x555f4d5d3f1b]
20791:20200711:123140.562 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x37) [0x555f4d76a9b2]
20791:20200711:123140.562 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0x9e4) [0x555f4d5c52b2]
20791:20200711:123140.562 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x2ff) [0x555f4d75b14b]
20791:20200711:123140.562 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x305) [0x555f4d5c48b8]
20791:20200711:123140.562 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1fa87c3b97]
20791:20200711:123140.562 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2a) [0x555f4d5c391a]
20786:20200711:123140.565 One child process died (PID:20791,exitcode/signal:1). Exiting ...
20786:20200711:123140.566 syncing trend data...
20786:20200711:123140.566 syncing trend data done
20786:20200711:123140.566 Zabbix Server stopped. Zabbix 5.0.1 (revision c2a0b03480).

cache conf..

### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
#
# Mandatory: no
# Range: 128K-64G
# Default:
# CacheSize=64G

### Option: HistoryCacheSize
# Size of history cache, in bytes.
# Shared memory size for storing history data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryCacheSize=2G

### Option: HistoryIndexCacheSize
# Size of history index cache, in bytes.
# Shared memory size for indexing history cache.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# HistoryIndexCacheSize=2G

### Option: TrendCacheSize
# Size of trend cache, in bytes.
# Shared memory size for storing trends data.
#
# Mandatory: no
# Range: 128K-2G
# Default:
# TrendCacheSize=2G

### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
#
# Mandatory: no
# Range: 0,128K-64G
# Default:
# ValueCacheSize=64G

Not that it really relates to original issue, but you don't seem to have any cache configs, only defaults... increasing any numbers to max values on a line, starting with a # has no effect, it is a comment... IIRC CacheSize defaults to 32M... You should actually add a line with a usable value there, and it does not mean to increase to max values... You should go with smaller steps, doubling a default, if that does not help, double it again... until you get a starting server...

Ad Widget

Should I be worried? can't open pid file /run/zabbix/zabbix_server.pid

Should I be worried? can't open pid file /run/zabbix/zabbix_server.pid

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment