Error while reporting performance in zabbix 3.4.3

[jeorgino]

Dear, I made some changes in the settings of the zabbix server to improve the performance of the server, I made a change in the path of LogSlowQueries = 1000 for LogSlowQueries = 2 to stop after the server started debugging queries from the database then flipping configurations and when I tried to restart the zabbix service it does not start. I checked the server logs and found the following; zabbix server log;
18490: 20171107: 013010.070 server # 186 started [unreachable poller # 53]
18492: 20171107: 013010.082 server # 188 started [unreachable poller # 55]
18301: 20171107: 013010.145 One child process died (PID: 18466, exitcode / signal: 1). Exiting ...
18495: 20171107: 013010.362 server # 191 started [unreachable poller # 58]
18301: 20171107: 013012.147 syncing history data ...
18301: 20171107: 013012.147 syncing history data done
18301: 20171107: 013012.147 syncing trend data ...
18301: 20171107: 013012.147 syncing trend data done
18301: 20171107: 013012.147 Zabbix Server stopped. Zabbix 3.4.3 (revision 73588).
zabbix_server [18495]: [file: 'log.c', line: 245] lock failed: [22] Invalid argument.m
Log / var / log / messages;
7 01:30:12 ASSZABXSV0 kill: -h, --help display this help and exit
Nov 7 01:30:12 ASSZABXSV0 kill: -V, --version output version information and exit
Nov 7 01:30:12 ASSZABXSV0 kill: For more details see kill (1).
Nov 7 01:30:12 ASSZABXSV0 systemd: zabbix-server.service: control process exited, code = exited status = 1
Nov 7 01:34:55 ASSZABXSV0 systemd: Got automount request for / proc / sys / fs / binfmt_misc, triggered by 18507 (sysctl)
Nov 7 01:34:55 ASSZABXSV0 systemd: Mounting Arbitrary Executable File Formats File System ...
Nov 7 01:34:55 ASSZABXSV0 systemd: Mounted Arbitrary Executable File Formats File System.
Nov 7 01:34:55 ASSZABXSV0 kernel: nr_pdflush_threads exported in / proc is scheduled for removal

Someone has idea of what this error may be, I have already done several procedures and the service does not start. What can you help? I'm grateful.

[kaspars.mednis]

Not sure this is reason, but you wrote that you changed LogSlowQueries and server started crashing after that change....

Why you have changed LogSlowQueries from 1000 to 2 ?

LogSlowQueries

How long a database query may take before being logged (in milliseconds).
0 - don't log slow queries.
This option becomes enabled starting with DebugLevel=3.

With your settings zabbix will log all queries that take longer then 2ms, which will be a lot of logging

Default setting logs only very slow queries, that takes more than 1000ms to finish

Regards,
Kaspars

[Gabalino]

I have some problem with Zabbix 3.4.x. If set more then 700 poller

33266:20180123:173257.952 server #809 started [preprocessing manager #1]
32449:20180123:173258.034 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
32450:20180123:173258.037 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
32451:20180123:173258.038 cannot connect to alert manager service: Cannot connect to service "alerter": [111] Connection refused.
33270:20180123:173258.062 server #813 started [preprocessing worker #4]
33267:20180123:173258.103 server #810 started [preprocessing worker #1]
33268:20180123:173258.104 server #811 started [preprocessing worker #2]
33271:20180123:173258.111 server #814 started [preprocessing worker #5]
32445:20180123:173258.183 One child process died (PID:32449,exitcode/signal:1). Exiting ...
32445:20180123:173300.294 Zabbix Server stopped. Zabbix 3.4.6 (revision 76823).