I am trying to configure my server running on Ubuntu 14.04 to use HHVM. I've had no issues actually installing it but getting it to run is a another story. I tried the command recommended by Sara Golemon and received the below error from the following command:
hhvm --mode server -vServer.Type=fastcgi -vServer.Port=9000
Error:
mapping self...
mapping self took 0'00" (850613 us) wall time
loading static content...
loading static content took 0'00" (0 us) wall time
WARNING: Logging before InitGoogleLogging() is written to STDERR
E1002 18:00:48.646344 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
shutting down old HPHP server by /stop command
E1002 18:00:49.659973 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:50.673045 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:51.686043 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:52.699100 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:53.712280 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:54.725271 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:55.738396 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:56.751373 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:57.764286 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:58.777184 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:00:59.790115 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:00.803050 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:01.815943 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:02.829088 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:03.842411 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:04.855499 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:05.868418 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:06.881392 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:07.894340 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:08.907320 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:09.920305 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:10.933312 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:11.946321 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:12.959223 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:13.972154 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:14.985043 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:15.997900 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:17.010850 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:18.023761 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:19.036653 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:20.049598 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:21.062446 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:22.075346 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:23.088186 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:24.101089 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:25.114043 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:26.127012 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:27.139890 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:28.152781 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:29.165693 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:30.178823 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:31.191797 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:32.204766 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:33.217674 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:34.230551 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:35.243446 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:36.256441 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:37.269491 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:38.282589 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:39.295550 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:40.308421 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:41.321308 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:42.334256 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:43.347374 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:44.360455 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:45.373364 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:46.386343 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:47.399708 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:48.412644 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
E1002 18:01:49.425597 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
shutting down old HPHP server by pid file
Unable to read pid file www.pid for any meaningful pid
E1002 18:01:50.425833 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
Unable to read pid file www.pid for any meaningful pid
E1002 18:01:51.426054 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
Unable to read pid file www.pid for any meaningful pid
E1002 18:01:52.426269 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
Unable to read pid file www.pid for any meaningful pid
E1002 18:01:53.426494 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
Unable to read pid file www.pid for any meaningful pid
E1002 18:01:54.426728 12377 fastcgi-server.cpp:234] failed to bind to async server socket: [::]:9000: Address already in use
killing anything listening on port 9000
page server started
all servers started
Could anyone help me get this running correctly?
That error is due to something else (perhaps php-fpm) already bound to port 9000. You can stop that process (something like lsof -i | grep 9000 will tell you what it is), or use a different port (say, 9001) for HHVM.
Related
I gave role like this.
env: oracle cloud.
open port: TCP 2377 , UDP TCP 7946 ,UDP 4786
Instance A : manager
Instance B : worker
Local PC : worker
init swarm mode with this cli on A
docker swarm init --advertise-addr <A's IP>
B got
Error response from daemon: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp A's IP:2377: connect: no route to host"
Local PC got
Error response from daemon: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp A's IP:2377: connect: connection refused"
well I have no idea what should I need to do more.
thank you in advance.
the problem was firewall setting on manager node's instance.
sudo firewall-cmd --add-port=2377/tcp --permanent
sudo firewall-cmd --reload
for me #Logan Lee solution perfectly matched.
According to the docker documentation, following ports need to manage accordingly
TCP port 2377 for cluster management communications
TCP and UDP port 7946 for communication among nodes
UDP port 4789 for overlay network traffic
Thanks #Logan Lee
Check the network connectivity between A and B, seems like they are not on the same network.
I am trying to start my PostgreSQL 9.4 database server on my local Windows machine via Ubuntu console. I'm running the command sudo service postgresql start, but I'm receiving the following error output:
The PostgreSQL server failed to start. Please check the log output:
2020-02-25 09:57:30.216 CST [497] LOG: could not bind IPv4 socket: Permission denied
2020-02-25 09:57:30.216 CST [497] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2020-02-25 09:57:30.217 CST [497] WARNING: could not create listen socket for "localhost"
2020-02-25 09:57:30.217 CST [497] FATAL: could not create any TCP/IP sockets [fail]
How do I check if another postmaster is already running on port 5432? If there is one, how would I stop it? Thank you!
i am trying to start a repo which was running fine previously but now when i use docker-compose up or --build also it create the network driver and then create the sqs_1 twice leading to this error
Creating evalai-ngx_sqs_1 …
Creating evalai-ngx_sqs_1 … error
WARNING: Host is already in use by another container
ERROR: for evalai-ngx_sqs_1 Cannot start service sqs: driver failed programming external connectivity on endpoint evalai-ngx_sqs_1 (5103436ff627cbbafe1bde3592eac4b0c654bdb8f19f700e864bc2278b98f459): Bind for 0.0.0.0:9324 failed: port is already allocated
Creating evalai-ngx_db_1 … error
ERROR: for evalai-ngx_db_1 Cannot start service db: driver failed programming external connectivity on endpoint evalai-ngx_db_1 (d0d92e2e853b3d07924be9c66f97c5093a843e0ffab9d929e4dfb7f6bc8870e0): Error starting userland proxy: listen tcp 0.0.0.0:5432: bind: address already in use
ERROR: for sqs Cannot start service sqs: driver failed programming external connectivity on endpoint evalai-ngx_sqs_1 (5103436ff627cbbafe1bde3592eac4b0c654bdb8f19f700e864bc2278b98f459): Bind for 0.0.0.0:9324 failed: port is already allocated
ERROR: for db Cannot start service db: driver failed programming external connectivity on endpoint evalai-ngx_db_1 (d0d92e2e853b3d07924be9c66f97c5093a843e0ffab9d929e4dfb7f6bc8870e0): Error starting userland proxy: listen tcp 0.0.0.0:5432: bind: address already in use
ERROR: Encountered errors while bringing up the project.
I Tried to remove the container , stop it and i even tried prune and unistalled docker once but still it is same.
I previously install postgresql which was indeed disturbing with my db service now i disable it
I have an issue with the docker daemon installed on an Ubuntu 14.04 VM. The logs reveal that ipv6 is enabled hence the docker seems to be listening on this ip address. Essentially, this effects Clair. I have made sure that ipv6 is disabled on the following recommendation here. I also disabled ipv6 in daemon.json as specified in Docker documentation. My docker version is Docker version 17.06.1-ce, build 874a737.
Docker daemon logs :
time="2018-02-20T20:33:17.736203462+01:00" level=info msg="IPv6 enabled; Adding default IPv6 external servers: [nameserver 2001:4860:4860::8888 nameserver 20 01:4860:4860::8844]"
Clair logs:
2018/02/20 20:43:51 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp [::]:6060: connect: cannot assign requested address"; Reconnecting to {[::]:6060 <nil>}
2018/02/20 20:46:14 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp [::]:6060: connect: cannot assign requested address"; Reconnecting to {[::]:6060 <nil>}
It's trying to make an IPv6 connection, but the address is wrong. [::] is IN6ADDR_ANY, not an actual address you can connect to. Provide the correct address in your config.yaml.
Did you mean to connect to localhost?
api:
# v3 grpc/RESTful API server address
addr: "[::1]:6060"
OS: window7
virtualization tool: virtualbox
virtual hypervisor: centos7
linux core as below
[root#localhost ~]# uname -a
Linux localhost.localdomain 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Two host IPs:
192.168.100.101
192.168.100.102
The steps:
curl -L git.io/weave -o /usr/local/bin/weave
chmod a+x /usr/local/bin/weave
[root#localhost ~]# weave launch 192.168.100.102
WARNING: existing iptables rule
'-A FORWARD -j REJECT --reject-with icmp-host-prohibited'
will block name resolution via weaveDNS - please reconfigure your firewall.
cannot locate running docker daemon
Warning: unable to detect proxy TLS configuration. To enable TLS, launch the proxy with ‘weave launch’ and supply TLS options. To suppress this warning, supply the ‘–no-detect-tls’ option.
3227932d5be77917c4e0b780cafe1171287c1029637f2360ece580fe6239cb4f
[root#localhost ~]# weave status
Version: 2.1.1 (failed to check latest version - see logs; next check at 2017/11/28 19:18:07)
Service: router
Protocol: weave 1..2
Name: 06:e0:c4:68:0c:ae(localhost.localdomain)
Encryption: disabled
PeerDiscovery: enabled
Targets: 1
Connections: 1 (1 failed)
Peers: 1
TrustedSubnets: none
Service: ipam
Status: ready
Range: 10.32.0.0/12
DefaultSubnet: 10.32.0.0/12
Service: dns
Domain: weave.local.
Upstream: 135.251.4.190, 135.251.38.218, 192.168.1.1
TTL: 1
Entries: 0
Service: proxy
Address: unix:///var/run/weave/weave.sock
Service: plugin (legacy)
DriverName: weave
[root#localhost ~]# weave version
weave script 2.1.1
weave 2.1.1
As above , the Connections: 1 (1 failed) , the docker run on these two hosts can’t ping each other.
And when I type weave version, it only showed weave script 2.1.1 and weave 2.1.1, not like other articles said it will show weaveexec and plugin or weavedns and so on. Is this the difference between versions or some mistakes I have made ?
Please help , thank you very much!
my docker log as below
[root#localhost ~]# docker logs weave
INFO: 2017/11/29 01:08:07.807752 Command line options: map[dns-effective-listen-address:172.17.0.1 nickname:localhost.localdomain dns-listen-address:172.17.0.1:53 ipalloc-range:10.32.0.0/12 status-addr:127.0.0.1:6782 weave-bridge:weave H:[unix:///var/run/weave/weave.sock] host-root:/host http-addr:127.0.0.1:6784 port:6783 proxy:true resolv-conf:/var/run/weave/etc/resolv.conf datapath:datapath docker-bridge:docker0 plugin:true]
INFO: 2017/11/29 01:08:07.807841 weave 2.1.1
INFO: 2017/11/29 01:08:07.859209 Docker API on unix:///var/run/docker.sock: &[ApiVersion=1.24 GoVersion=go1.8.3 Os=linux BuildTime=2017-10-24T15:40:21.112972404+00:00 PkgVersion=docker-1.12.6-61.git85d7426.el7.centos.x86_64 Version=1.12.6 Arch=amd64 KernelVersion=3.10.0-693.5.2.el7.x86_64 GitCommit=85d7426/1.12.6]
INFO: 2017/11/29 01:08:07.859520 Using docker bridge IP for DNS: 172.17.0.1
INFO: 2017/11/29 01:08:07.863781 proxy listening on unix:///var/run/weave/weave.sock
INFO: 2017/11/29 01:08:08.940871 Bridge type is bridged_fastdp
INFO: 2017/11/29 01:08:08.940885 Communication between peers is unencrypted.
INFO: 2017/11/29 01:08:08.961891 Our name is 06:e0:c4:68:0c:ae(localhost.localdomain)
INFO: 2017/11/29 01:08:08.962058 Restart/resume detected - using persisted peer list: [192.168.100.102]
INFO: 2017/11/29 01:08:08.972210 Docker API on unix:///var/run/docker.sock: &[KernelVersion=3.10.0-693.5.2.el7.x86_64 PkgVersion=docker-1.12.6-61.git85d7426.el7.centos.x86_64 GoVersion=go1.8.3 Os=linux Arch=amd64 BuildTime=2017-10-24T15:40:21.112972404+00:00 Version=1.12.6 ApiVersion=1.24 GitCommit=85d7426/1.12.6]
INFO: 2017/11/29 01:08:08.974990 Checking for pre-existing addresses on weave bridge
INFO: 2017/11/29 01:08:09.009949 [allocator 06:e0:c4:68:0c:ae] Initialising with persisted data
INFO: 2017/11/29 01:08:09.034491 Listening for DNS queries on 172.17.0.1
INFO: 2017/11/29 01:08:09.086102 Sniffing traffic on datapath (via ODP)
INFO: 2017/11/29 01:08:09.114882 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:09.116392 Listening for HTTP control messages on 127.0.0.1:6784
INFO: 2017/11/29 01:08:09.116576 Listening for metrics requests on 127.0.0.1:6782
INFO: 2017/11/29 01:08:09.125917 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:09.151109 Waiting for Weave API Server...
INFO: 2017/11/29 01:08:09.159548 Finished waiting for Weave API Server
INFO: 2017/11/29 01:08:09.159706 Listening on /run/docker/plugins/weave.sock for global scope
INFO: 2017/11/29 01:08:09.159811 Listening on /run/docker/plugins/weavemesh.sock for local scope
INFO: 2017/11/29 01:08:09.159822 Creating default "weave" network
INFO: 2017/11/29 01:08:09.462160 Discovered local MAC 06:e0:c4:68:0c:ae
INFO: 2017/11/29 01:08:09.547179 Discovered local MAC 46:2b:0d:08:12:be
INFO: 2017/11/29 01:08:09.554830 Discovered local MAC 0e:46:f3:dd:57:96
INFO: 2017/11/29 01:08:11.612424 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:11.614477 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:13.980824 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:13.982289 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:18.124543 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:18.125556 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:23.294574 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:23.322022 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:37.070537 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:37.073928 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:08:39.222651 Error checking version: Get https://checkpoint-api.weave.works/v1/check/weave-net?arch=amd64&flag_docker-version=1.12.6&flag_kernel-version=3.10.0-693.5.2.el7.x86_64&os=linux&signature=fvXv9SDD9r8gjV6d2HrXkVdBv5U72%2BeXQ6NT2u0JkKc%3D&version=2.1.1: dial tcp: lookup checkpoint-api.weave.works on 135.252.166.21:53: read udp 192.168.100.101:34840->135.252.166.21:53: i/o timeout
INFO: 2017/11/29 01:08:46.009136 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:08:46.011168 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:09:16.169210 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:09:16.171278 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:09:42.294136 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:09:42.296081 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:10:28.752091 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:10:28.756481 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:12:03.755330 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:12:03.760374 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:14:30.481453 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:14:30.486632 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:17:41.166716 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:17:41.168341 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:22:38.820826 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:22:38.829815 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
INFO: 2017/11/29 01:23:08.968136 Expired MAC 06:e0:c4:68:0c:ae at 06:e0:c4:68:0c:ae(localhost.localdomain)
INFO: 2017/11/29 01:23:08.968199 Expired MAC 46:2b:0d:08:12:be at 06:e0:c4:68:0c:ae(localhost.localdomain)
INFO: 2017/11/29 01:23:08.968219 Expired MAC 0e:46:f3:dd:57:96 at 06:e0:c4:68:0c:ae(localhost.localdomain)
INFO: 2017/11/29 01:30:27.085406 ->[192.168.100.102:6783] attempting connection
INFO: 2017/11/29 01:30:27.089200 ->[192.168.100.102:6783] error during connection attempt: dial tcp4 :0->192.168.100.102:6783: getsockopt: no route to host
but on 192.168.100.101 , I can ping 192.168.100.102
[root#localhost ~]# ping 192.168.100.102
PING 192.168.100.102 (192.168.100.102) 56(84) bytes of data.
64 bytes from 192.168.100.102: icmp_seq=1 ttl=64 time=1.19 ms
64 bytes from 192.168.100.102: icmp_seq=2 ttl=64 time=1.05 ms
64 bytes from 192.168.100.102: icmp_seq=3 ttl=64 time=0.906 ms
^C
--- 192.168.100.102 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.906/1.051/1.195/0.120 ms
The issue has been resolved and shared my experience here.
As I described in my question
[root#localhost ~]# weave launch 192.168.100.102
WARNING: existing iptables rule
'-A FORWARD -j REJECT --reject-with icmp-host-prohibited'
will block name resolution via weaveDNS - please reconfigure your firewall.
cannot locate running docker daemon
Warning: unable to detect proxy TLS configuration. To enable TLS, launch the proxy with ‘weave launch’ and supply TLS options. To suppress this warning, supply the ‘–no-detect-tls’ option.
3227932d5be77917c4e0b780cafe1171287c1029637f2360ece580fe6239cb4f
Then on both hosts ,I run command
[root#localhost ~]# iptables -F
And then stop and rm all docker container and stop weave and then restart docker daemon and then on host 192.168.100.101 ,run command
[root#localhost ~]# weave launch
[root#localhost ~]# eval $(weave env)
[root#localhost ~]# docker run --name bbox1 -itd busybox
[root#localhost ~]# docker run --name bbox2 -itd busybox
and on host 192.168.100.102 , run command
[root#localhost ~]# weave launch 192.168.100.101
[root#localhost ~]# eval $(weave env)
[root#localhost ~]# docker run --name bbox3 -itd busybox
And then test
[root#localhost ~]# docker exec bbox3 ping -c2 bbox1
PING bbox1 (10.32.0.1): 56 data bytes
64 bytes from 10.32.0.1: seq=0 ttl=64 time=0.940 ms
64 bytes from 10.32.0.1: seq=1 ttl=64 time=2.362 ms
--- bbox1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.940/1.651/2.362 ms
Done!
so it seemed that the iptables rule is the root cause. I will learn more iptables rules later so that avoid merely using "iptables -F".
Thanks for #Marc Carré very much.
it only showed weave script 2.1.1 and weave 2.1.1, not like other articles said it will show weaveexec and plugin or weavedns and so on
This is expected with your version of Weave Net.
In prior versions, Weave Net started different containers, but starting Weave Net 2.0, these have been merged together.
See also:
https://github.com/weaveworks/weave/blob/master/CHANGELOG.md#release-200
All of Weave Net now runs in one container
Previously we had three separate containers for routing, Docker API proxy and Docker plugin. Running everything in one simplifies start-up and removes the need to detect various error conditions. #1642,#2897,#2936,#2945,#2946,#2951,#2960
https://www.weave.works/blog/weave-net-2-released
In Weave Net 2.0, the various processes forming Weave Net were merged into a single process.
and what follows.
Would you mind pointing to the docs which caused the confusion, so that we could improve these?