[ZBX-7262] map editor fails in Firefox, but not in Chrome Created: 2013 Oct 31  Updated: 2025 May 30

Status: Reopened
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.9
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: david tomkins Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: frontend, maps, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Server
AIX (oslevel -s: 7100-01-04-1216)
Web Server: Apache/2.2.22 (Unix) PHP/5.5.5
PHP Version 5.5.5 (compiled from source)

Client:
Windows XP Pro
Browsers - Firefox (v.25)
Chrome (Version 30.0.1599.101 m)


Attachments: File map editor - chrome vs firefox.bmp     XML File zbx_export_maps(2).xml    

 Description   

When opening map editor with latest version of Firefox, the error "Map Image Update Failed" is displayed, but in Chrome, the map editor works perfectly.

Happy to provide output of any logfiles / test results and can make changes to existing setup if required....



 Comments   
Comment by Pavels Jelisejevs (Inactive) [ 2013 Nov 01 ]

We cannot reproduce this issue. Could you export the map and any objects it contains and post it here? Of course, strip all of the data that may be sensitive to you.

Comment by david tomkins [ 2013 Nov 01 ]

The map is a blank 800 x 600 map with no objects/elements, but I've exported and uploaded as requested.

I've also checked my addons/plugins in Firefox which may, or may not be the cause of the issue:
Extensions:
iMacros 8.5.1
HttpFox 0.8.12
Elite Proxy Switcher 1.2.0.2

Plugins:
Microsoft DRM 9.0.0.4503
Shockwave Flash 11.9.900.117
Windows Media Player Plug-in Dynamic Library 3.0.2.629
Windows Presentation Foundation 3.5.30729.1

I've checked with one of my colleagues and the problem also appears to exist with IE8 version 8.0.7601

Comment by david tomkins [ 2013 Nov 01 ]

After consulting with one of our senior development gurus (Vlad Gudim), the problem has been identified as being incorrect permissions on a directory the server that is running the Zabbix frontend.

The only way to identify the problem was to enable the "Tools/Web Developer/Network" option in Firefox, and analyse the output.

The reason for this is because the error message was being appended to the back of the JSON response, and as such were being output to the browser - ( and not visible in any logs ).

i.e.

{"result":"f508afaa848fefb2033d262ad7237a5c"}

<table class="msgerr" cellpadding="0" cellspacing="0" id="msg_messages" style="width: 100%;"><tr class=""><td class="msg" colspan="1"><ul class="messages"><li class="error">session_start(): open(/var/lib/php/session/sess_rfr4sqra9vgovjl37m8b6es0j0, O_RDWR) failed: The file access permissions do not allow the specified action. (13) [include/config.inc.php:737]</li><li class="error">session_write_close(): open(/var/lib/php/session/sess_rfr4sqra9vgovjl37m8b6es0j0, O_RDWR) failed: The file access permissions do not allow the specified action. (13) [include/config.inc.php:741]</li><li class="error">session_write_close(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) [include/config.inc.php:741]</li></ul></td></tr></table>

As soon as I updated "/var/lib/php/session" with appropriate permissions, the map editor in Firefox and IE8 started working.

Although I don't have the ability/skills in PHP to provide the solution by modifying the zabbix PHP error handling, I still think that this should be handled more effectively by the frontend, and a meaningful message displayed so that the sysadmin can quickly and easily rectify the (mis)configuration of the PHP installation.
However, in much the same way, perhaps the Apache startup script that can check the syntax check for config files (apachectl -t) could also perform a validity check for values defined within the "php.ini" file? (do you think it's worth proposing this idea to the Apache / PHP developers?)

Either way, I thought I'd share the answer with you (and anyone else who reads this!).

Cheers

Dave

Comment by richlv [ 2013 Nov 01 ]

indeed, it should be either displayed to the user or logged in webserver logs

edit : note that we have fixed something like this in the past (errors not shown to user) - could this be a regression ?

Comment by Kaspars Andersons [ 2025 May 30 ]

closed due to inactivity. If the issue is still active please create new request

Generated at Sat Aug 02 09:01:14 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.