fresh setup, sample displays with no data (when viewed remotely)

[Fuzzwah]

I've got dashing setup on a ubuntu host. When I view http://localhost:3030/sample I see the layout I expect, but none of the widgets have any data.... until I hit ctrl+c to shutdown dashing, when magically the data is updated and displayed. Of course dashing now isn't running so no further updates are possible.

All the feedback and messages I get when I'm trying to push data to the dashboard makes it appear everything is working fine:

I've tried using a job and also a curl command:

fuzzy@mk802:~/sweet_dashboard_project$ dashing job sample_job 4Vp46XZ2wEUwmZR3b8MmjM0DDr6Rl11s Data Sent to welcome: {:text=>"work please"}
fuzzy@mk802:~/sweet_dashboard_project$ curl -d '{ "auth_token": "4Vp46XZ2wEUwmZR3b8MmjM0DDr6Rl11s", "text": "Hey, look what I can do!" }' http://localhost:3030/widgets/welcome

I see the following results in the terminal:

127.0.0.1 - - [04/May/2013 10:34:28] "POST /widgets/welcome HTTP/1.1" 204 - 0.0033
127.0.0.1 - - [04/May/2013 10:35:33] "POST /widgets/welcome HTTP/1.1" 204 - 0.0042

But nothing changes on the output website, no data is shown just headings. Until I hit ctrl+c and dashing closes saying this:

^C>> Stopping ...
192.168.0.14 - - [04/May/2013 10:35:58] "GET /events HTTP/1.1" 200 - 509.7169
192.168.0.14 - - [04/May/2013 10:35:58] "GET /events HTTP/1.1" 200 - 429.7513

And BAM the data on the dashboard updates..... but obviously dashing now isn't running anymore so no more updates.....

[Fuzzwah]

I have been digging through other similar issue threads. I attempted to use coffee-script-source 1.4.0 as mentioned in #79 but it didn't make any difference.

I've also noticed that the sample install which is linked to seems to be doing the exact same thing I'm witnessing on my own fresh install. It has the layout, but no data.

http://dashingdemo.herokuapp.com/sample

I've tested both the demo page and my own fresh dashboard install using the lastest versions of Chrome and Firefox. Same issue everywhere.

Little help please? I no longer think this is just some rails newb issue I'm running into, but a larger issue with Dashing.

[Fuzzwah]

I've installed ubuntu desktop into a VM and run through the set up again. It all works when I'm running the brower on the local vm, but not when I try and view the page from another machine.

I take it from the fact that the heroku demo exists at all, that at some stage it was expected that viewing a dashboard from a remote machine was meant to work. Is it that this "feature" has been broken somewhere along the lines?

[Fuzzwah]

I found a branch which mentioned remote views, but after installing it I'm still seeing the same thing.

https://github.com/zsalzbank/dashing/tree/remote-views

[MartynKeigher]

Hey Fuzzy,

I have managed to install dashing using the currently available MASTER.ZIP from this repo. If you need some assistance getting it up and running, and perhaps you might be interested in getting it "auto start" with your server... I can help you with that too!

As for it not running remotely...I can take a look over your config and help you out if you want??

Prob a REALLY stupid question (and im really sorry for asking)...but your are putting ":3030" in your URL to view it remotely?? and can you ping the Ubuntu VM from where you are trying to view it from!?

What does a telnet repsonse give?? And did you perhaps change the port number from 3030 OR do you have something else running on 3030??

I have my dashboard setup in my lab, you can view it here: http://lab.martynkeigher.com:3030

Speak to ya soon.

[Fuzzwah]

I can successfully get to the site I'm working on (I use virtualbox and have NAT'd port 3030 through form the host OS to the guest). When I view the site locally from within the VM it works fine, /sample updates with its random numbers. But when I view from the host OS /sample has the layout, but no data.

Your lab is exhibiting the exact same issue as I'm seeing.

[Fuzzwah]

Same thing is happening to the http://dashingdemo.herokuapp.com/sample page.

[robknight]

I'm seeing the same thing. It works on some browsers but not others - Firefox on Linux seems fine, but both Chrome & Firefox on Windows 7 don't work.

In Chrome developer tools and Firebug, it shows the /events resource as "pending" - it seems to hang on this indefinitely without receiving any data. Quitting dashing via CTRL-C as described by @Fuzzwah causes the connection to close and then the browser receives the data.

Weirdly, Firefox on Linux on another box does not have this problem, and shows event data arriving incrementally in Firebug's network tab.

I thought this might be a proxy server issue but even without using any proxy server it still seems to occur.

[MartynKeigher]

HHmm.... is your dash external facing? If so, whats the URL? I'll see if it can display data for me.

Ive never had issues viewing data on the dashboards like this. I have all browsers installed and check them all regularly. (Reason I have them all...I do website development/design) They're all patched and plugins updated, etc.. wondering why no data pulls through though!! Check your plugins for updates etc...

I primarily use Firefox on Windows 8 (currently version: 21.0) and I have no issues.

Do u have a server you could throw another VM on of Ubuntu Server and see if it happens again?

Another thing you could do, is temporarily disable the firewall on the Ubuntu desktop to see if that for whatever reason could be causing the issue here??? You would do this using the following command:

sudo ufw disable

To re-enable it its:

sudo ufw enable

[Fuzzwah]

Unfortunately my current test bed isn't externally available over the web.

Are you saying that http://dashingdemo.herokuapp.com/sample is working fine for you on Win8 + Firefox? Because it isn't for me (Win8 + Firefox 20.0.1). I have no plugs for Firefox installed (I normally use Chrome).

I now have dashing running on the Ubuntu 12.04 LTS server again and can successfully view dashboards from the Ubuntu 13.04 desktop VM using Firefox (so it isn't an outbound firewall issue). However when I view it from Win8 with either Firefox or Chrome I don't see any data. I can confirm that the same lack of data updates happens if I disable the windows firewall.

[pushmatrix]

Not sure what to say. I tested it out on Windows 8 with Firefox & Chrome, and they are both working for me. Hmmm...

[jeroenvandijk]

http://dashingdemo.herokuapp.com/sample wasn't working for me either. Application.js was loading forever..

I've tried this in Chrome 27.0.1453.93, Safari 6.0.3 (8536.28.10) on Mountain Lion. And same for IPad Chrome and Safari. Now all of a sudden it works in all these devices. As if the server finished compiling application.js...?

The dashboard is still not working on Google TV Chrome , but I'll try again after clearing the cache

[leonkyneur]

http://dashingdemo.herokuapp.com/sample
http://dashingdemo.herokuapp.com/sampletv

above links not working for me - wireshark i can see data data received however nothing presented back to the browser.

This also happens to me on a network install accessible on my LAN

OS: Windows 7 x64

Browsers:
Firefox: 22 (screenshot)
Chrome: Version 27.0.1453.116 m
Opera: Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.15

[tmarconi]

Just chiming in to say that we are seeing this exact same issue on our local install. Chrome is "pending" on events, everything else is coming through fine. Same problem in Firefox and Chrome, doesn't work for me, but does work for 5 of my co-workers. Was working on this workstation yesterday, not working today... rebooted, disabled firewalls, plugins, used incognito mode, etc. All using various OS's, but primarily using Windows 7 with Chrome as the browser. Strange problem.

[joshmmo]

I had the same issue on an EC2 instance. I switched to one of our internal servers and that fixed the issue. Same versions of ubuntu. I have no idea what the difference was. I also get no data on the demos listed.

When I ctrl+c my server I would also get all the data updated on the widgets. Weird behavior.

[Norvares]

Try t use another webserver instead of thin: #193 (comment)

[DSegal92]

Just chiming in to say that I'm experiencing the same issue. I'm running a Webrick server, and to make things even stranger when I check out the server on another computer on the same local network it updates fine (on the remote computer, still nothing locally).

[stuzero]

I solved this by adding 'puma' to my Gemfile
and ran it with:

   puma config.ru

I think the problem is with thin.
FYI - the default port is 9292

[benpatterson]

Could this be related? macournoyer/thin#15

[cmheisel]

I'm experiencing the same thing, I'll try puma as well

[petemyron]

switching to puma also fixed this for me, though I had to fork dashing just to relax the dependency on rack in dashing.gemspec from s.add_dependency('rack', '~> 1.5.2') to 'rack', '~> 1.5' so puma and dashing would play nice together. I now need to make sure the thing doesn't have any issues with a newer version of rack...

[Update] See below, not working--widgets are not updated

[terraboops]

We hope to move Dashing to Puma from Rack, there is an open and almost completed PR for this: #427

[MartynKeigher]

+1. PUMA for the win! ;p

[gottfrois]

You can also use dashing-rails which use puma as well

[petemyron]

I mirrored some of the changes from #427, except I don't want jruby, and it all seems to be working ok--other than the dashboards are requesting 'events' updates every 3 seconds...

[terraboops]

The change in #427 with -jruby is one of the reasons that PR cannot be accepted. The other changes should be fine, except they break the unit tests.

[petemyron]

Other than making sure the thing starts with puma (it does)... actually looking at it today shows that widgets are not updating (via send_event or through curl), though I see the request in the logs:
[66649] 127.0.0.1 - - [17/Jun/2015 15:04:06] "POST /widgets/my_id HTTP/1.1" 204 - 0.0292

Also, puma responds immediately to the GET 'events' request instead of leaving it open like Thin did for one minute (Server-Sent Events)--I'm not sure where to go from here. It certainly bloats Puma's log:
66227] 127.0.0.1 - - [17/Jun/2015 14:54:49] "GET /events HTTP/1.1" 200 - 0.0006 (every 3 seconds)

history.yml is only updated when the server is killed (control + c in my case), which I think is weird, though I think I recall that being the case on Thin as well.

Any ideas?

[aysark]

Ran into this issue, for now my workaround was what @stuzero suggested (using puma as the server).

[pysysops]

I had this issue with the Docker dashing image from @frvi I farked it and pushed an image up which can be found https://hub.docker.com/r/pysysops/docker-dashing/

Just uses puma as discussed above.

[drexlma]

I have the same problem :/

[vishwakumba]

I also had the same problem running on the guest Vagrant Ubuntu Xenial(16.04) OS.
My host was Mac OS Sierra 10.12.4

Chrome browser did not show the dashing widgets with updating data from my Mac OS. So I used
webrick web server

$ rackup -p 3030 webrick

See also
#235