Comments (7)
Here are logs from one of masters 46.101.9.14
the other masters were 46.101.9.249,188.166.157.176
and slave is 46.101.9.201
...
Mar 01 11:52:23 apollo-mesos-master-0 weave[1533]: 548656b1b629: Pull complete
Mar 01 11:52:23 apollo-mesos-master-0 weave[1533]: 1275dac6c4ff: Pull complete
Mar 01 11:52:23 apollo-mesos-master-0 weave[1533]: Digest: sha256:58c88a203a38fb0765ca7fe78d088fe88f6e7817be8dc1bb6395742cd94f570e
Mar 01 11:52:23 apollo-mesos-master-0 weave[1533]: Status: Downloaded newer image for weaveworks/weave:1.4.4
Mar 01 11:52:26 apollo-mesos-master-0 weave[1533]: 2e7762298c48f29c3d157a1f31be9b415e3597e3ebb70e118c9f91ea4835756a
Mar 01 11:52:26 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:26.285640 EMSGSIZE on send, expecting PMTU update (IP packet was 60028 bytes, payload was 60020 bytes)
Mar 01 11:52:26 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:26.286017 ->[188.166.157.176:44772|6e:c9:66:e2:75:05(apollo-mesos-master-2)]: connection fully established
Mar 01 11:52:26 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:26.288430 sleeve ->[188.166.157.176:6783|6e:c9:66:e2:75:05(apollo-mesos-master-2)]: Effective MTU verified at 1438
Mar 01 11:52:26 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:26.346471 Discovered remote MAC 1e:b7:14:e1:6f:c9 at 12:3b:09:08:70:ca(apollo-mesos-slave-0)
Mar 01 11:52:26 apollo-mesos-master-0 weave[1989]: 10.45.85.85
Mar 01 11:52:26 apollo-mesos-master-0 systemd[1]: Started Weave Network Router.
Mar 01 11:52:39 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:39.367483 ->[127.0.0.1:47788] connection accepted
Mar 01 11:52:39 apollo-mesos-master-0 docker[1986]: ERRO: 2016/03/01 11:52:39.373020 ->[127.0.0.1:47788] connection shutting down due to error during handshake: failed to receive remote protocol header: EOF
Mar 01 11:52:47 apollo-mesos-master-0 systemd[1]: Stopping Weave Network Router...
Mar 01 11:52:47 apollo-mesos-master-0 docker[1986]: ERRO: 2016/03/01 11:52:47.933033 ->[46.101.9.201:6783|12:3b:09:08:70:ca(apollo-mesos-slave-0)]: connection shutting down due to error: read tcp4 46.101.9.201:6783: connection reset by peer
Mar 01 11:52:47 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:47.933239 ->[46.101.9.201:6783|12:3b:09:08:70:ca(apollo-mesos-slave-0)]: connection deleted
Mar 01 11:52:47 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:47.939850 Removed unreachable peer 12:3b:09:08:70:ca(apollo-mesos-slave-0)
Mar 01 11:52:48 apollo-mesos-master-0 docker[1986]: ERRO: 2016/03/01 11:52:48.052011 ->[46.101.9.249:6783|42:95:9b:0d:9c:58(apollo-mesos-master-1)]: connection shutting down due to error: read tcp4 46.101.9.249:6783: connection reset by peer
Mar 01 11:52:48 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:48.052097 ->[46.101.9.249:6783|42:95:9b:0d:9c:58(apollo-mesos-master-1)]: connection deleted
Mar 01 11:52:48 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:48.052958 Removed unreachable peer 42:95:9b:0d:9c:58(apollo-mesos-master-1)
Mar 01 11:52:48 apollo-mesos-master-0 docker[1986]: INFO: 2016/03/01 11:52:48.079459 === received SIGINT/SIGTERM ===
Mar 01 11:52:48 apollo-mesos-master-0 docker[1986]: *** exiting
Mar 01 11:52:48 apollo-mesos-master-0 systemd[1]: Stopped Weave Network Router.
from apollo.
The problems seems to occur on flush_handlers
task.
from apollo.
After getting the newest changes in the devel branch, I am also getting an error: 'ERROR: change handler (systemd reload) is not defined', the first time the task [weave | deploy weave service] runs. That happens both in AWS public and Rackspace. Was working fine before I merged. Running the ansible playbook again goes through ok.
from apollo.
having a look - highly likely related to this commit bdf513a
from apollo.
#664 addresses the systemd issue - looks like I messed up a conflict resolution in bdf513a
from apollo.
@sheerun just ran up devel (patched with #664) on digitalocean and I didnt experience any weave issues. Can you confirm you are running the devel branch (as there is actually no "wait for weave to listen" task on that branch)
from apollo.
I still experience this issue.. It happens only first time I run apollo-launch.
from apollo.
Related Issues (20)
- How is etcd important for coreos setup? HOT 11
- disable fleet
- Why is consul started before weave HOT 4
- Run weave on top of early-docker just as flannel
- etcd_discovery_url is causing terraform to reprovision instances when it doesn't need to
- Is it worth adding support for Consul RPC encryption?
- Unable to bootstrap on aws HOT 4
- Error during apollo launch on AWS HOT 2
- Service discovery topological affinity HOT 2
- "RUNNING HANDLER [handlers : wait for weave to listen]" timeout HOT 9
- Zookeeper setup is failing with Ansible 2.0 HOT 3
- better way to run docker from a unit file
- Migrate terraform template_file to null_resource for generating the etcd url discovery file
- Terraform for Digital Ocean crashes: panic: Unary - is only allowed HOT 3
- TASK [traefik : enable traefik] fails
- move sysctl and other tuning to common ansible role
- Ansible failed because of undefined ansible_port
- Message: TypeError: no implicit conversion of nil into String
- Project status?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from apollo.