ningyougang commented on issue #3203: Error: The action exceeded its time limits of 60000 milliseconds during initialization URL: https://github.com/apache/incubator-openwhisk/issues/3203#issuecomment-359349184 @markusthoemmes #### 1.The root reason may be found. It seems the docker itself bug. in `lambda-exp` invokers nodes. Exist `not recovered network resource` problem, for example, when send `/init`(inject code to action container) to `172.17.0.5:8080`, the `172.17.0.5` is not be recovered even if execute `docker -rf all containers` before, through `ip addr`, we can see the bridge `docker0`'s ports don't be recovered ``` # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 13570: veth6ce5281@if13569: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 02:9a:6a:89:ad:ad brd ff:ff:ff:ff:ff:ff link-netnsid 19 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 76:90:4d:11:08:10 brd ff:ff:ff:ff:ff:ff inet 10.106.140.78/23 brd 10.106.141.255 scope global dynamic eth0 valid_lft 940034134sec preferred_lft 940034134sec 13572: veth3830455@if13571: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether be:89:10:e1:f7:bd brd ff:ff:ff:ff:ff:ff link-netnsid 20 13574: veth5262b93@if13573: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 72:0f:dc:c4:0c:9c brd ff:ff:ff:ff:ff:ff link-netnsid 2 12950: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 02:42:bc:e2:07:d4 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 13478: vetheecaddc@if13477: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 0e:b9:91:20:69:62 brd ff:ff:ff:ff:ff:ff link-netnsid 0 13488: veth635415b@if13487: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether a6:34:71:72:bd:17 brd ff:ff:ff:ff:ff:ff link-netnsid 1 13494: vethd8a823c@if13493: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether d2:36:4a:60:b0:96 brd ff:ff:ff:ff:ff:ff link-netnsid 16 13496: vethfa62eec@if13495: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP link/ether 32:5e:fd:dd:03:05 brd ff:ff:ff:ff:ff:ff link-netnsid 15 ``` #### 2.How to solve above problem? * method1: after execute `docker rm -f all containers`, then, execute `ip link delete <XXX>` to delete docker0 relative network resource maually. * method2: execute `docker-runc delete all relative containers` , if ok, the network resource will be recovered also. #### 3.Why appear the `network resource not recovered problem` Current, we don't appear this problem again except execute restart docker daemon under unknown condition. #### 4.Conclusion When deploy/redeploy the invoker before, if we promise that the invoker node's network resource is recovered, above problem will gone.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
