Zabbix server crash after log level change in runtime

[ged0]

Hey guys,
I had a problem when at run time changed log levels server crashed without any notifications.

Zabbix server version: 2.4.8
OS: CentOS

Used commands:
...
zabbix_server -R log_level_increase
zabbix_server -R log_level_decrease
less /var/log/zabbix/zabbix_server.log
...

Logs:
...
1255:20180417:175807.741 End of substitute_discovery_macros():SUCCEED data:''
1248:20180417:175807.741 In lld_make_item()
1337:20180417:175807.741 In zbx_vc_add_value() itemid:211676 value_type:0 timestamp:1523977076.523698724
1255:20180417:175807.741 In substitute_key_macros() data:'IF-MIB::ifOperStatus.{#SNMPINDEX}'
1248:20180417:175807.742 In substitute_key_macros() data:'jnxBgpM2PrefixInPrefixesRejected[{#ASNUM}, {#PEERADDR}]'
12996:20180417:225443.725 Starting Zabbix Server. Zabbix 2.4.8 (revision 59539).
12996:20180417:225443.725 ****** Enabled features ******
12996:20180417:225443.725 SNMP monitoring: YES
12996:20180417:225443.725 IPMI monitoring: YES
12996:20180417:225443.725 WEB monitoring: YES
12996:20180417:225443.725 VMware monitoring: YES
12996:20180417:225443.725 Jabber notifications: YES
...


After log level decrease I was looking at logs and I would notice that logs aren't filling.
From systemctl I saw that zabbix-server service was in running status.

Had this happened only to me or this is known issue? How to prevent it?

[kloczek]

You are using zabbix version which is no longer supported

https://www.zabbix.com/life_cycle_and_release_policy

[ged0]

kloczek,
Yes, I know, but ai'm interested if this problem persisted for other users who used this version. I'm planing to upgrade versio

[kloczek]

AFAIK no one reports similar issues on top of 3.0/3.2/3.4