-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashing cache problem ? #7
Comments
Hm, which version of dashing-icinga2 is that? That looks sort of modified. Furthermore which software versions of ruby, dashing etc are involved here? From a first peek I'd say local browser cache. |
Dashing itself is the binary application which serves the custom dashboards, widgets, jobs. By default it is running thin (which is what you get from ps aux) and allows for additional logging. I would investigate on that part, and probably also try a "default" job runner to see whether it works there, or not. Based on that troubleshooting I'd then try to investigate on the icinga2 job. Sometimes specific browsers and versions do not work with the involves javascript events, or similar. That's why I was asking about the specific versions, browser as well as Dashing plus ruby gems. Though maybe it might be worthwhile to check their issue tracker for similarities. |
I'm having (perhaps) the same problem.
In fact, it only loads when you stop dashing (ctrl-c). This explains the behaviour in the UI. If I reload the html page, I don't get valid data until I restart dashing. Is something blocking on the events page?
|
As previously said, it is tremendously hard to debug Dashing itself. I have seen the refreshing problem a couple of times, but was never able to reliable reproduce nor analyse the issue. It also might be worthwhile to disable several widgets (and their |
Hi. I've the same problem, /events is not working until I stop the daemon, so I can see the dashboard with some data only after that. This is my environment:
|
As said, there is nothing I can do. Dig into the Dashing sources and analyse why the events are failing. Maybe someone finds a Dashing issue id or a patch. |
Ok, thanks. |
dashing hold no data into a cache. |
you can find a dashing logfile here: /tmp/dashing.log can you post the logfile? |
There is no /tmp/dashing.log, I have /usr/share/dashing-icinga2/log/thin.log: |
the connection to the icinga2 is okay and the library reads corrects data: I will try to adjust your problem |
Thanks, please let me know |
i found no problems in my test setup. |
I've tested it on my Windows client, with Firefox 45.9.0 ESR, Firefox Portable 24.7.0 ESR, Internet Explorer 11.0.44, Microsft Edge 38.14393 and Google Chrome 60.0.3112.101, same problem. But I've just tried to test it from a test Linux client, with Firefox 50.1.0, and it works! It seems to be a Windows problem. Have you any idea about it? Please let me know, thanks |
Rumors say that Dashing doesn't work on Windows clients at all, but I did not verify that information. Can you reproduce the issue with a simple demo install of a dashing "default" dashboard, or any other demo dashboard found on the net? |
I've tried this URL: http://dashingdemo.herokuapp.com/sample So it seems a Dashing problem, but in the project page they don't say anything about Windows OS issues, only about IE ... grrr |
This issue go on here |
Please continue in #47 which acts as a general issue to replace thin with something else, or find any other solution. |
Hi !
I have a big problem with the dashing and I think it could possibly comes from the cache (but not sure). It was working really well on all of my computers and suddenly it stopped working on my working laptop. No informations are showed except the ones in the iframe, as you can see there:
Although, I've tested on different dashing demo and... no one is working anymore on my laptop.
What is weird here is that it's working like a charm on my others computer. I've looked with one of my colleague and he has the exact same problem: it works on certains computers and doesn't work anymore on the others...
On computers concairned by the bug: it doesn't work on any browser (from Firefox to Chrome).
Thanks for your help and sorry for the bad english :)
The text was updated successfully, but these errors were encountered: