#Wings & Question

7 messages · Page 1 of 1 (latest)

plucky bobcatBOT
#

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

lethal lily
plucky bobcatBOT
#

I have found the following for: https://pastebin.com/v36fmWya
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

jovial scroll
#

@lethal lily You have to stop the wings service before running diagnostics.

sudo systemctl stop wings
sudo wings diagnostics
# Fix whatever the issue is
sudo systemctl start wings

The bot might give you the same advice since it will read the same error message earlier in wings logs, so manually go through the logs until you get to the bottom and then copy any errors just from the bottom part.

lethal lily
plucky bobcatBOT
#

I have found the following for: https://ptero.co/ykoropykij
You already have an instance of Wings running through systemd service and are trying to start another duplicate instance, for example by using the commands wings and wings --debug, or another service is using the port.

Use ss -plnt | grep :8080 (or grep :8443 depending on the port) to find what process is currently running and stop it. You can type killall wings to shutdown any ghost Wings process.

lethal lily