Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Please confirm that the first one would be the call that we need to analyze.
Just to be sure, include both of them.
DanielB wrote:I'm not sure if I've understood this. The majority of the entries (I think they're 324 errors so far because the number displayed besides the Firebug icon that is on the navigation bar of Iceweasel) I see in Console->Errors seems to say the same when I compare the number of the lines (I do not see columns numbers). But I think the errors shown there are independent of the URLs selected in the "Network" tab, right?
So far I have not seen again JSON errors during the day. Not sure if this can be related to an update I made to Iceweasel 41.0. I could try with Windows Server 2012 that was also where I saw these errors and there I still have Firefox 40.0.3.
jfrickson wrote:
I need the content of the "Response" tab for both of the objectjson.cgi calls.
Here I have the two responses. I will send them via PM. Let me know if you received it, please.
DanielB wrote:Thank you for taking the time to check these files. If you think there's anything else I can do to help, please let me know.
Furthermore, do you believe that the other (non JSON) errors could be related to this problem?
It's possible. If we could get it to fail here, it would be a lot easier to debug.
Sorry but when transcribing on my Horde ticket system the progress we've had on this case, I noticed that you mentioned two patches here. I had only applied the patch to cgi/objectjson.c that was what I saw on the ticket 67. Now I applied the patch on cgi/statusjson.c. After recompiling, it worked perfectly for Iceweasel in Debian Jessie. Nor have I seen errors in the Firebug console for Iceweasel after applying this patch. The other browsers (Chormium and Konqueror) continue running smoothly. I also did a test on Windows Server 2012 and here the problem has been solved for Firefox. Neither it seems to have errors on the Firebug Console for Firefox. Google Chrome and Explorer still do not cause problems here. [Note: the green shading for the icons is not visible in Explorer, but I think that's a minor detail because the important is that the map and the information was displayed correctly]
jfrickson wrote:
DanielB wrote:Good luck with the conference!
Thanks. It will be my first one. Sounds like it will be fun though!
I hope it's a good first experience! Do publish some of the pictures to see some of the guys with whom I have had the opportunity to speak in this forum That always helps to bring people, especially those who are a bit far (here in Argentina).
There are other questions that I have about the network map that I will next week and I hope you can clarify after the conference.
DanielB wrote:
Sorry but when transcribing on my Horde ticket system the progress we've had on this case, I noticed that you mentioned two patches here. I had only applied the patch to cgi/objectjson.c that was what I saw on the ticket 67. Now I applied the patch on cgi/statusjson.c. After recompiling, it worked perfectly for Iceweasel in Debian Jessie. Nor have I seen errors in the Firebug console for Iceweasel after applying this patch. The other browsers (Chormium and Konqueror) continue running smoothly. I also did a test on Windows Server 2012 and here the problem has been solved for Firefox. Neither it seems to have errors on the Firebug Console for Firefox. Google Chrome and Explorer still do not cause problems here. [Note: the green shading for the icons is not visible in Explorer, but I think that's a minor detail because the important is that the map and the information was displayed correctly]
So everything is working except the green shading in Explorer?
jfrickson wrote:
So everything is working except the green shading in Explorer?
Yes, that is what I saw. Sorry for the confusion. I still think that is a good news.
But after having solved this problem, there is another thing would like to mention. If I create a user who has permissions to view a subset of hosts, the "legacy map" shows this subset but the new network map shows only the Nagios process. Do you think this could be a bug?
we'll have to work on it some more next week after the Nagios conference is over.
That always helps to bring people, especially those who are a bit far (here in Argentina).