[ZBX-19707] Maximum execution time of 300 seconds exceeded in /usr/share/zabbix/include/func.inc.php on line 1427 Created: 2021 Jul 20 Updated: 2021 Oct 21 Resolved: 2021 Oct 21 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | None |
Affects Version/s: | 5.4.2 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Trivial |
Reporter: | Brandon Molletti | Assignee: | Dmitry Krupornitsky |
Resolution: | Won't Do | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() ![]() ![]() ![]() ![]() |
Description |
Randomly, php-fpm children seem to timeout (or are running an infinite loop) which brings my server to a crawl with cpu maxed out. The php-fpm www-error log shows the same function causing the issue (/usr/share/zabbix/include/func.inc.php on line 1427)... function truncateFloat(float $number): float { return (float) sprintf('%.'.(ZBX_FLOAT_DIG - 1).'E', $number); }Same issue / function call in graphs.inc.php Any ideas why this function is timing out??? |
Comments |
Comment by Brandon Molletti [ 2021 Jul 20 ] |
I'm running php v7.4.21 |
Comment by Brandon Molletti [ 2021 Jul 21 ] |
Seems to happen around 9:10 am every day... Attached top screenshot during the issue. Resolves after the 5 min php timeout is reached. |
Comment by Dmitry Krupornitsky [ 2021 Jul 22 ] |
Hello, Brandon, Could you please enclose the full php-fpm log so we could analyze it? Thank you |
Comment by Brandon Molletti [ 2021 Jul 23 ] |
I have attached the logs. |
Comment by Dmitry Krupornitsky [ 2021 Jul 23 ] |
Hello, Brandon. We need to understand what is happening. Most probably the issue is in the yieldGraphScaleInterval(), but we need to check. Do you have any specific settings for your graphs? Could you please try to figure out when this error occurs, possibly on what graph and what are its settings. Thank you. |
Comment by Brandon Molletti [ 2021 Aug 02 ] |
My graphs are simple graphs, nothing special. The item(s) that feed the graphs are returning positive and negative numbers rounded to 2 decimal places. ###.##. |
Comment by Brandon Molletti [ 2021 Aug 03 ] |
I cleared history and trends on the suspect items... haven't had an issue since. |
Comment by Brandon Molletti [ 2021 Aug 19 ] |
Ok, so it's still happening... doesn't seem to be related to the time of day, per say... Might be related to the values of the graph around the same time of day... The graph is monitoring wattage for power going to/from the power grid at my house. This means values can be both positive and negative. Attached are the graphs during time of failure. It seems the graph displayed on my dashboard is the one causing the issue. Again, it's just a simple graph with no special settings. |
Comment by Brandon Molletti [ 2021 Aug 19 ] |
Issue persists in 5.4.3. |
Comment by Brandon Molletti [ 2021 Aug 30 ] |
Any ideas? |
Comment by Dmitry Krupornitsky [ 2021 Sep 06 ] |
Hello, Brandon. Let's start from the beginning. I was trying to reproduce an error and got nothing about that. Most likely you have something wrong in your data after conversion. |