Skip to content
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

Probe hanging with docker 1.9.1 and coreOS Alpha #715

Closed
paulbellamy opened this issue Dec 2, 2015 · 7 comments
Closed

Probe hanging with docker 1.9.1 and coreOS Alpha #715

paulbellamy opened this issue Dec 2, 2015 · 7 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@paulbellamy
Copy link
Contributor

Seems to be happening for a user on coreOS, docker 1.9.1. See if we can replicate, and if it is on docker 1.9.0 as well.

@paulbellamy paulbellamy changed the title Probe hanging with docker 1.9.1 Probe hanging with docker 1.9.1 and coreOS Alpha Dec 2, 2015
@paulbellamy paulbellamy added the bug Broken end user or developer functionality; not working as the developers intended it label Dec 2, 2015
@tomwilkie tomwilkie added this to the 0.12.0 milestone Dec 10, 2015
@tomwilkie
Copy link
Contributor

Closing in favour of #769, as there is more info there.

@paulbellamy
Copy link
Contributor Author

For reference, user here was using xhyve, not virtualbox.

@2opremio
Copy link
Contributor

This was a different issue, the system wasn't hanging and the probe logs didn't show anything unusual but the UI didn't display anything. One of the possibilities is that the probe is not sending reports or empty reports.

@2opremio 2opremio reopened this Dec 16, 2015
@tomwilkie tomwilkie modified the milestones: 0.13.0, 0.12.0 Jan 19, 2016
@2opremio 2opremio self-assigned this Jan 22, 2016
@2opremio
Copy link
Contributor

I can reproduce it in a Vagrant VM ('coreos-alpha' (v933.0.0)) and scope:latest:

git clone https://github.com/coreos/coreos-vagrant.git
cd coreos-vagrant
cp user-data.sample user-data
cp config.rb.sample config.rb
vagrant up
vagrant ssh
curl -s -L https://raw.githubusercontent.com/weaveworks/scope/master/scope -o scope && chmod +x scope && ./scope launch

The UI shows containers for a while but then they went away and the whole system froze (in a similar way to #769 ) which I believe didn't happen when @rimusz showed us (since according to @paulbellamy he was using xhyve).

@2opremio
Copy link
Contributor

I can confirm that the coreos Vagrant box enables natdnshostresolver causing the same problem as #769:

$ grep -B 1 nat ~/.vagrant.d/boxes/coreos-alpha/935.0.0/virtualbox/Vagrantfile 
    # Fix docker not being able to resolve private registry in VirtualBox
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    vb.customize ["modifyvm", :id, "--natdnsproxy1", "on"]

Which suggests that although natdnshostresolver is not enabled by default, it may be common.

However, after setting those flags to "off", I can launch Scope and everything works as expected (the reports from the probe are definitely reaching the app and containers are displayed).

@rimusz can you please try to reproduce again and, if you can, provide us with specific instructions on how you did it?

@rimusz
Copy link

rimusz commented Jan 27, 2016

all good on my tests with the latest alpha/beta/stable, but I'm not using vagrant but xhyve based coreos installs on my Mac

@2opremio
Copy link
Contributor

Closing then. Thanks @rimusz !

@tomwilkie tomwilkie modified the milestones: 0.12.0, 0.13.0 Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

4 participants