WaykDen Server appears to be hanging

Hi,

The next time this happens, can you run the following command:

docker ps -a

And capture the command output to post it here. I suspect that one of the containers is terminating for some unknown reason, so we should normally see which one it is with "docker ps -a".

Before doing a Restart-WaykDen, you should extract the logs for the container in question. Assuming it is the 'den-server' container, it would look like this:

docker logs den-server > den-server.txt

You can post the logs here, or send them to wayk@devolutions.net.

Best regards,

Here are the results from ps-a...
looks like it is den-sever

PS C:\Users\Administrator> docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
de4931dc5dec traefik:1.7-windowsservercore-1809 "/traefik --file --c…" 2 hours ago Up 17 minutes 80/tcp, 0.0.0.0:4000->4000/tcp den-traefik
58070434d06d devolutions/den-server:2.7.0-servercore-ltsc2019 "c:\\wayk\\den-server.…" 2 hours ago Exited (0) About an hour ago den-server
f02c1b4fc44f devolutions/den-lucid:3.7.2-servercore-ltsc2019 "c:\\wayk\\lucid.exe" 2 hours ago Up 17 minutes (unhealthy) 4242/tcp den-lucid
36f4d671b782 devolutions/picky:4.5.0-servercore-ltsc2019 "c:\\wayk\\picky-serve…" 2 hours ago Up 10 seconds 1234/tcp den-picky
00c6f918c426 mongo:4.2-windowsservercore-1809 "mongod --bind_ip_all" 2 hours ago Restarting (14) 24 seconds ago den-mongo

Also looks like everything else is restarting on its own... is it supposed to do that?

Logs emailed to wayk@devolutions.net. Subject is WaykDen server logs.

Hi,

I received your logs and replied in private. As for restarting the containers, it looks like they keep restarting but fail to do so because den-server stopped and they rely on it.

By default, all containers are restarted according to the "on-failure" restart policy, which requires that the process fails with a correct exit code. There are many ways in which the container can stop without being recognized as a failure by docker, so one trick could be to change the restart policy to "always":

Set-WaykDenConfig -DockerRestartPolicy 'always'

You can find more information about the docker restart policy behaviour here: https://docs.docker.com/config/containers/start-containers-automatically/

With 'always', your containers will always get started and restarted unless you call "Stop-WaykDen" to stop them explicitly. This would be sufficient to restart it in your case, but we obviously would like to figure out what made it stop in the first place to fix it properly.

Best regards,

I ran the command and set the restart policy. I've also sent the additional logs via email. .