#Very long server restart

1 messages · Page 1 of 1 (latest)

cloud depot
#

It will execute the action 5-10 minutes later how to solve this?

cloud depot
#

WARN: [Jan 14 21:44:30.988] error while waiting for container stop; terminating process container_id=0665a673-c9ba-4400-9c31-4771e2d815f9 environment=docker error=

Stacktrace:

github.com/pterodactyl/wings/environment/docker.(*Environment).WaitForStop
github.com/pterodactyl/wings/environment/docker/power.go:260
github.com/pterodactyl/wings/server.(*Server).HandlePowerAction
github.com/pterodactyl/wings/server/power.go:141
github.com/pterodactyl/wings/router/websocket.(*Handler).HandleInbound
github.com/pterodactyl/wings/router/websocket/websocket.go:363
github.com/pterodactyl/wings/router.getServerWebsocket.func3
github.com/pterodactyl/wings/router/router_server_ws.go:85
runtime.goexit
runtime/asm_amd64.s:1598

WARN: [Jan 14 21:44:30.988] container stop did not complete in time, terminating process... container_id=0665a673-c9ba-4400-9c31-4771e2d815f9 duration=10m0s environment=docker step=wait
DEBUG: [Jan 14 21:44:31.021] saw server status change event server=0665a673-c9ba-4400-9c31-4771e2d815f9 status=offline

nocturne ridgeBOT
#

There were too many logs to read @cloud depot. Please post 5 or less. Alternatively, please share larger logs using paste sites, such as pteropaste or hastebin.

carmine yew
#

This issue can occur if the node's resources are under heavy load.

#

Restarting wings could work, and otherwise killing the docker container by SSH could also be a solution.