[ZBX-3474] configuration parameter TrapperTimeout does not seem to work Created: 2011 Jan 27 Updated: 2019 Aug 28 Resolved: 2019 Aug 28 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 1.8.4 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Major |
| Reporter: | Aleksandrs Saveljevs | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 1 |
| Labels: | timeout, trapper | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
As a test we had a process which connected to a trapper on Zabbix server and kept the connection open for almost half an hour. Considering that the maximum value for TrapperTimeout is 300 seconds, something did not work as expected. |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2011 Feb 04 ] |
|
We use alarm() to interrupt system calls. It might have happened that the system was so overloaded that SIGALRM was delivered in-between system calls. As we have already discovered in |
| Comment by Glebs Ivanovskis (Inactive) [ 2017 Oct 17 ] |
|
Now there is 128 MB limit, but still... |
| Comment by Vladislavs Boborikins (Inactive) [ 2019 Aug 28 ] |
|
Hello, Since this version of Zabbix is no longer supported, we've decided not to prioritize this bug for the near future and close the issue with "Won't fix" resolution. Please let us know if this decision should be reconsidered. Regards |