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-359142457 @markusthoemmes * the systemoverload is not saturated * add more debug log later After add more debug log to invoker component, found below error ``` [2018-01-20T03:02:30.125Z] [INFO] [#tid_1598] [DockerContainer] sending initialization to ContainerId(b7b290f53a500c4493fd4f6ee593814a80cfc9b9f4c8c33833523d36f808e779) ContainerAddress(172.17.0.6,8080) [marker:invoker_activationInit_start:16] ...... [2018-01-20T03:03:42.185Z] [INFO] [#tid_1598] [DockerContainer] ==========initialization result one: ConnectionError(java.net.SocketTimeoutException: Read timed out), ContainerId(b7b290f53a500c4493fd4f6ee593814a80cfc9b9f4c8c33833523d36f808e779) ContainerAddress(172.17.0.6,8080) [2018-01-20T03:03:44.207Z] [INFO] [#sid_102] [DockerClientWithFileAccess] running /usr/bin/docker rm -f b7b290f53a500c4493fd4f6ee593814a80cfc9b9f4c8c33833523d36f808e779 (timeout: 1 minute) [marker:invoker_docker.rm_start:1387008] ``` * analyze: the time of send `/init` request to that conainer at `03:02:42`, another daemon is beginning to remove that container at `03:03:44`, because that container's server rejects `/init`(1 minutes don't give response), so will triger the `destroyConainer` action * how to do next, analyze deeply why the container rejects the `/init` * this problem(why the container rejects the `/init`) also happened when the cluster was deployed just now and send action invoke request instantly, which means, the openwhisk cluster was not prepared for the users's action invoke when it is deployed just now(several minutes later, the cluster can was prepared for the user's action invoke fully).
---------------------------------------------------------------- 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
