[ZBX-12389] Error 500 when last accessed group is no longer available Created: 2017 Jul 18 Updated: 2018 Jan 07 Resolved: 2018 Jan 07 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 3.2.5 |
Fix Version/s: | 3.4.6rc1, 4.0.0alpha2, 4.0 (plan) |
Type: | Problem report | Priority: | Minor |
Reporter: | Tim Jahn | Assignee: | Oleg Egorov (Inactive) |
Resolution: | Fixed | Votes: | 0 |
Labels: | crash, frontend, usability | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
CentOS |
Attachments: | Zabbix Host Gone.png access_log_last_half_hour.txt error_log latest.php latest.php.patch ssl_error_log |
Team: | Team B |
Sprint: | Sprint 21, Sprint 22, Sprint 23, Sprint 24 |
Story Points: | 0.5 |
Description |
If the last accessed Host group in "Monitoring -> latest data" no longer exists then an error 500 will be returned and the user account has to be deleted and re-created to regain access to this page. Note that this does NOT happen if only one host in a host group is deleted. When just a single host is deleted a user gets the expected result of a reset search page. This result happened in multiple browsers and multiple computers, confirming it was an account related problem. |
Comments |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 18 ] |
Hello, Tim, how I can reproduce this issue step by step.
In description "Host group no longer exists", when host was removed. Sorry, if I something don't understand. |
Comment by Tim Jahn [ 2017 Sep 18 ] |
To reproduce: Visit monitoring -> latest data The only work around I have found to get back to the “latest data” page has been to delete and rebuild a profile that has gotten stuck like this. |
Comment by Tim Jahn [ 2017 Sep 18 ] |
Visit monitoring -> latest data The only work around I have found to get back to the “latest data” page has been to delete and rebuild a profile that has gotten stuck like this. |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 20 ] |
Hello. Tim! |
Comment by Tim Jahn [ 2017 Sep 20 ] |
I found the file path for latest.php in my Zabbix Front End. Looks like it is at /var/www/html/zabbix/latest.php. I do not know how to apply the patch, I am not familiar with PHP. Further, this is a production environment with thousands of hosts so I would need to be sure any changes would not cause down time (or I would need to schedule the change for off hours). |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 20 ] |
latest.php patched file |
Comment by Tim Jahn [ 2017 Sep 20 ] |
I renamed latest.php to latest.old. |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 20 ] |
Can you show web server (apache) error logs? |
Comment by Tim Jahn [ 2017 Sep 20 ] |
This is the ssl error log from our front end (/var/log/httpd/) |
Comment by Tim Jahn [ 2017 Sep 20 ] |
This is the error_log from our front end (/var/log/httpd/). |
Comment by Tim Jahn [ 2017 Sep 20 ] |
Here is the last half hour of the access log (the original file was over 150MB) |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 21 ] |
Ok, thank you! Then restart web server (service httpd restart) |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 21 ] |
(2) [F] No translation string changes. iivs CLOSED |
Comment by Tim Jahn [ 2017 Sep 25 ] |
I increased the available RAM for the Zabbix Front End from 1GB to 3GB. |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 25 ] |
Now you have frontend limit 512M, not 3 GB if in php.ini memory_limit is 512M. |
Comment by Tim Jahn [ 2017 Sep 25 ] |
I checked /var/log/httpd/access_log after first change - no memory errors The only issue we ever have with the front end is if a host group gets deleted then anyone that had that as the last location they were viewing will have a broken latest data screen. The latest data screen will be the only broken screen. |
Comment by Tim Jahn [ 2017 Sep 25 ] |
My mistake, it appears the memory error was from the log /var/log/httpd/error_log |
Comment by Oleg Egorov (Inactive) [ 2017 Sep 26 ] |
resuming normal operations 134217728 bytes is 128 MB, not 512 MB or 3 GB... |
Comment by Oleg Egorov (Inactive) [ 2018 Jan 05 ] |
Fixed in:
|