zabbix_sender (Zabbix) 6.0.3
Revision 506e2b51e2 4 April 2022, compilation time: May 10 2022 11:57:27
Compiled with OpenSSL 1.1.1n 15 Mar 2022
Running with OpenSSL 1.1.1o 3 May 2022
Linux gateway 5.15.26-gentoo Home SMP Wed Mar 9 08:21:26 -03 2022 x86_64 Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz GenuineIntel GNU/Linux
--------------------------
It all started when I got an error when running a script in crontab:
[CODE]ipcs -s | grep zabbix | wc -l/CODE] showed me I had reached the limit of semaphores configured in the kernel.
Here is the command that I run:
Even after succeded and exited, the semaphore is still active and I have to kill it before it explodes the limit again.
Revision 506e2b51e2 4 April 2022, compilation time: May 10 2022 11:57:27
Compiled with OpenSSL 1.1.1n 15 Mar 2022
Running with OpenSSL 1.1.1o 3 May 2022
Linux gateway 5.15.26-gentoo Home SMP Wed Mar 9 08:21:26 -03 2022 x86_64 Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz GenuineIntel GNU/Linux
--------------------------
It all started when I got an error when running a script in crontab:
Code:
cannot create Semaphore: [28] No space left on device
Here is the command that I run:
Code:
zabbix_sender -z 192.168.1.198 -i /tmp/zabbix_iptable -T -vv
zabbix_sender [16510]: DEBUG: In connect_to_server() [192.168.1.198]:10051 [timeout:60, connection timeout:3]
zabbix_sender [16510]: DEBUG: In is_ip4() ip:'192.168.1.198'
zabbix_sender [16510]: DEBUG: End of is_ip4():SUCCEED
zabbix_sender [16510]: DEBUG: answer [{"response":"success","info":"processed: 28; failed: 0; total: 28; seconds spent: 0.000393"}]
Response from "192.168.1.198:10051": "processed: 28; failed: 0; total: 28; seconds spent: 0.000393"
sent: 28; skipped: 0; total: 28
Comment