![]() |
![]() |
Subject: | Edit Trigger Button fails to load Dialog |
Author: | Joseph Rowe |
Posted: | 2016-12-21 13:13 |
I have successfully installed Zenoss Core 4.2.5 with the latest service pack via zenup, everything installed great and everything appeared to be working correctly until now.
When I go to the trigger screen, I can add and delete triggers, but when I attempt to edit triggers, it fails to load the dialog. I get "Done" or "error on page" in my status bar, and the dialog will not display.
Worth noting that if I switch to notifications and press the gear button or double click on a notification, it opens the edit dialog no problem.
If I use the exact same VM/Browser to navigate to the web console for the otherzenoss core install I deployed via the VM image, double clicking on a trigger successfully brings up the edit trigger dialog. So it's not a browser issue or anything like that. My manual install is experiencing this issue only.
Any advice I couldn't find anything anywhere about people experiencing this issue.
UPDATE: here is the error that my browseris generating when I attempt to edit a trigger... do you think that perhaps when I was using the pre-installed centos zenoss VM it worked because it was older, but now that I've installed the manual way using the latest service pack that now zenoss expects a newer browser
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Timestamp: Wed, 21 Dec 2016 09:42:28 UTC
Message: Object doesn't support this property or method
Line: 10
Char: 276003
Code: 0
URI: http://192.168.56.101:8080/zport/dmd/Events/zenoss-all.jsv=1481625251.66
ANOTHER UPDATE:
My theory was correct, the latest and greatest version of zenoss 4.2.5 with service packs differed from the vm image I tried in that it no longer properly supports the super old IE browser I was using. I installed a new version of Firefox and all is well.
Maybe leave this up for others who get similar problems, happy holidays!
< |
Previous Zenoss 4.2.5 behind NGINX reverse proxy on a different box. |
Next event notification email fails |
> |