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

Make scope deal with weave restarts (or weave starts after scope) #510

Closed
tomwilkie opened this issue Sep 23, 2015 · 1 comment · Fixed by #867
Closed

Make scope deal with weave restarts (or weave starts after scope) #510

tomwilkie opened this issue Sep 23, 2015 · 1 comment · Fixed by #867
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@tomwilkie
Copy link
Contributor

2015/09/23 06:07:17 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:18 report generation took too long (4.194702594s)
2015/09/23 06:07:20 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:21 report generation took too long (3.137524219s)
2015/09/23 06:07:24 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:25 report generation took too long (4.42816017s)
2015/09/23 06:07:27 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:28 report generation took too long (2.781171793s)
2015/09/23 06:07:31 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:32 report generation took too long (4.325375019s)
2015/09/23 06:07:34 error doing ticker: Get http://172.17.0.1:6784/report: dial tcp 172.17.0.1:6784: no route to host
2015/09/23 06:07:36 report generation took too long (3.229815901s)
@tomwilkie tomwilkie added the bug Broken end user or developer functionality; not working as the developers intended it label Sep 23, 2015
@tomwilkie
Copy link
Contributor Author

I'm also missing a connection from scope -> weave after the restart.

@tomwilkie tomwilkie changed the title "no route to host" in scope logs after restarting weave Make scope deal with weave restarts (or weave starts after scope) Nov 10, 2015
@tomwilkie tomwilkie modified the milestones: 0.11.0, 1.0 Nov 30, 2015
@tomwilkie tomwilkie self-assigned this 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

Successfully merging a pull request may close this issue.

1 participant