search

VZiChoushaDui / Libertea

Easily install and manage a multi-protocol VPN server; with user management, auto fallback and auto update.
MIT License
390 stars 48 forks source link

ERROR: Timeout while waiting for panel to start. #97

Open aksiere opened 2 months ago

aksiere commented 2 months ago

Tested on Ubuntu 20/22 and Debian 12. The result is the same. I tried it on two different servers.

 ** Waiting for services to start...
    ✅ libertea-provider-trojan-ws started
    ✅ libertea-camouflage-nginx-fallback started
    ✅ libertea-provider-vmess-grpc started
    ✅ libertea-provider-vless-ws started
    ✅ libertea-provider-shadowsocks-v2ray started
    ✅ libertea-provider-trojan-grpc started
    ✅ libertea-log-parser started
    ✅ libertea-provider-vless-grpc started
    ✅ libertea-mongodb started
    ✅ libertea-rsyslog started
    ✅ libertea-haproxy started
    ❌ libertea-panel failed to start. Retrying...
*******************************************************
ERROR: Timeout while waiting for panel to start.
       Please open an issue on https://github.com/VZiChoushaDui/Libertea/issues/new
       and include the following information:

       - component name: libertea-panel
       - OS: "Debian GNU/Linux"
       - OS version: "12"
       - Docker version: Docker version 27.2.1, build 9e34c9b
       - Panel listening: False
       - Panel root status code: 000
       - Panel admin status code: 000
       Also include the output of the following command:
           tail -n 100 /tmp/libertea-panel.log
root@debian:~# tail -n 100 /tmp/libertea-panel.log
tail: cannot open '/tmp/libertea-panel.log' for reading: No such file or directory
VZiChoushaDui commented 2 months ago

Hmm. No panel log file? The service hasn't been started at all then.

Is systemd working? Run sudo systemctl status libertea-panel and post the output.

We can't reproduce this atm, perhaps some weird configuration of os on your server provider's side is causing that. Would you mind sharing where you're getting your servers from?

aksiere commented 2 months ago

Hmm. No panel log file? The service hasn't been started at all then.

Is systemd working? Run sudo systemctl status libertea-panel and post the output.

We can't reproduce this atm, perhaps some weird configuration of os on your server provider's side is causing that. Would you mind sharing where you're getting your servers from?

Ubuntu 22 this time:

ERROR: Timeout while waiting for panel to start.
       Please open an issue on https://github.com/VZiChoushaDui/Libertea/issues/new
       and include the following information:

       - component name: libertea-panel
       - OS: "Ubuntu"
       - OS version: "22.04"
       - Docker version: Docker version 27.2.1, build 9e34c9b
       - Panel listening: False
       - Panel root status code: 000
       - Panel admin status code: 000
       Also include the output of the following command:
           tail -n 100 /tmp/libertea-panel.log
root@ubuntu:~# sudo systemctl status libertea-panel
● libertea-panel.service - LiberteaPanel
     Loaded: loaded (/etc/systemd/system/libertea-panel.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Mon 2024-09-16 00:40:52 UTC; 7s ago
    Process: 19345 ExecStart=/bin/bash /root/libertea/panel/serve.sh (code=exited, status=208/STDIN)
   Main PID: 19345 (code=exited, status=208/STDIN)
        CPU: 1ms

VPS at hostup.se

VZiChoushaDui commented 2 months ago

Please also post the output of this command:

tail -n 100 /tmp/libertea-panel.init.log
aksiere commented 2 months ago

Please also post the output of this command:

tail -n 100 /tmp/libertea-panel.init.log
root@ubuntu:~# tail -n 100 /tmp/libertea-panel.init.log
tail: cannot open '/tmp/libertea-panel.init.log' for reading: No such file or directory

there are no any relevant logs in the /tmp folder