-
Hello. RUNNING HANDLER [openwisp.openwisp2 : Reload uwsgi] ********************************************************************************************************************************************************
fatal: [192.168.0.92]: FAILED! => {"changed": true, "cmd": ["/opt/openwisp2/env/bin/uwsgi", "--reload", "/opt/openwisp2/uwsgi.pid"], "delta": "0:00:00.013943", "end": "2024-07-23 08:56:49.614406", "msg": "non-zero return code", "rc": 1, "start": "2024-07-23 08:56:49.600463", "stderr": "open(\"/opt/openwisp2/uwsgi.pid\"): No such file or directory [core/io.c line 525]", "stderr_lines": ["open(\"/opt/openwisp2/uwsgi.pid\"): No such file or directory [core/io.c line 525]"], "stdout": "", "stdout_lines": []} He says that he cannot find the uwsgi.pid file and it really does not exist, why is it not created? |
Beta Was this translation helpful? Give feedback.
Answered by
SapeNeCo
Jul 23, 2024
Replies: 1 comment 1 reply
-
Okay, the problem was in two services:
After adding modules (in my case it was openwisp-wifi-login-pages), they create configs for them and they must be removed manually if you decide to remove these modules.
Don't forget to delete them if you have disabled the module. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
SapeNeCo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Okay, the problem was in two services:
After adding modules (in my case it was openwisp-wifi-login-pages), they create configs for them and they must be removed manually if you decide to remove these modules.
They are in
Don't forget to delete them if you have disabled the module.
I hope this helps someone.