My Linux WaykDen installation has been running smoothly for a few months now until today. I couldn't connect to the web dashboard of WaykDen this afternoon. However, the client was still showing as connected. I restarted the server and the dashboard was not working and now the client won't reconnect.
When I ran start-waykden, it ran fine until it got to Den-Server and I got this error:
PS /root> start-waykden
docker stop den-mongo
docker rm den-mongo
Starting den-mongo
den-mongo successfully started
docker stop den-picky
docker rm den-picky
Starting den-picky
den-picky successfully started
docker stop den-lucid
docker rm den-lucid
Starting den-lucid
den-lucid successfully started
docker rm den-server
Starting den-server
Exception: /root/.local/share/powershell/Modules/WaykDen/2020.2.3/Public/WaykDenService.ps1:605
Line |
605 | throw "Error starting $($Service.ContainerName)"
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Error starting den-server
So I pulled the den-server logs and this is what I found:
2020-10-15T23:07:25.973918116+00:00 ERROR den_server - An error occured during server execution: UnableToInitializeDenServer("Lucid client can\'t be initialized: error sending request for url (http://den-lucid:4242/client): error trying to connect: tcp connect error: No route to host (os error 113)")
It appears to be having a problem getting to den-lucid... I see the "no route to host" error... but I'm not sure how to fix that.
I saw in the forums where others had a DNS problem where the loopback address was listed as a DNS server.
I checked that and that is not a problem. I have public DNS servers listed in both the adapter config and resolve.conf files.
The only entries in the /etc/hosts file are for localhost.
Can anyone help?
Thanks!!!
I also just noticed that the den-lucid docker container is reporting as unhealthy. So I exported those logs and found this:
[2020-10-16T01:47:57Z INFO lucid::server::server] Loading repositories
[2020-10-16T01:50:09Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:51:13Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:51:43Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:52:15Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:54:52Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:55:24Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:55:57Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:56:29Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:57:08Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:57:41Z ERROR r2d2] No servers available for the provided ReadPreference.
[2020-10-16T01:58:11Z ERROR r2d2] No servers available for the provided ReadPreference.
Hello,
What distro and version of Linux are you using?
Could you provide the full logs (here or by sending me a PM) for den-server and den-lucid:
docker logs den-server > den-server.txt docker logs den-lucid> den-lucid.txt
I also noticed you are using an older version (2020.2.3), by upgrading to the latest stable release (2020.2.5), it will pull the latest dockers images at the same time, which could fix the issue.
Update-Module -Name WaykDen Import-Module WaykDen Restart-WaykDen
Best regards,
Richard Boisvert
Hello,
Could you also provide the log for the database as it may be the culprit.
docker logs den-mongo> den-mongo.txt
Best regards,
Richard Boisvert
will do... I'll run the update now and if it still is not working, I'll post the new logs.
When I run the Import-Module Command, I get this message:
" Import-Module: Assembly with same name is already loaded"
Is that expected & should I continue?
Hello,
You can close posh and reopen it. You should then be able to re-import the module.
Best regards,
Richard Boisvert
So I updated and got pretty much the same error on restart.... but it is reporting 2020.2.5 now, so I think at least the updated worked.
PS /root> Restart-Waykden
Stopping devolutions-jet
Error response from daemon: No such container: devolutions-jet
Stopping den-traefik
Stopping den-server
Stopping den-lucid
Stopping den-picky
Stopping den-mongo
docker rm den-mongo
Starting den-mongo
den-mongo successfully started
docker rm den-picky
Starting den-picky
den-picky successfully started
docker rm den-lucid
Starting den-lucid
den-lucid successfully started
docker rm den-server
Starting den-server
Exception: /root/.local/share/powershell/Modules/WaykDen/2020.2.5/Public/WaykDenService.ps1:687
Line |
687 | throw "Error starting $($Service.ContainerName)"
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Error starting den-server
requested logs are attached.
den-server.txt
den-mongo.txt
den-lucid.txt
Finally found a solution... Everything on the internet kept pointing to a firewall problem... so I stopped the firewall and then den-server would start but den-lucid wouldn't because it needed to call some firewall rules... So I poked around google for a few hours and found the solution...
This one command fixed the problem...
firewall-cmd --zone=public --add-masquerade --permanent
All is well again... all docker containers are running... and the dashboard and clients are back online as well.
Now I can enjoy the weekend...
Thanks!!!
Hello,
Glad you found the issue. I will verify with the engineering team if a check could be added when starting the containers to prevent or at least warn about this.
Best regards,
Richard Boisvert
Hello,
Could you provide the source that gave you the solution? The engineering team would like to dig further into the problem but wanted to see what prompted you to use that command.
Best regards,
Richard Boisvert
Sure... This is page I found the solution on:
https://stackoverflow.com/questions/40214617/docker-no-route-to-host
How I got there is I was researching the "no route to host" error in the den-server logs...
After turning off the firewall, and seeing den-server start, I knew it was something in the firewall blocking it but didn't know what it was... so started searching for firewall issues with Den-Server and that's how I ended up on that page.
If the poster is right... It looks like the issue happens when you have multiple networks on the same system... which is the situation my system falls under. I have private network for management and a public one for external access and clients to connect to.
Hope this helps... :-)