ERROR: Timeout while waiting for panel to start.

[trytopassgfw]

** Waiting for services to start... ✅ libertea-mongodb started ✅ libertea-provider-shadowsocks-v2ray started ✅ libertea-provider-vless-ws started ✅ libertea-log-parser started ✅ libertea-provider-trojan-ws started ✅ libertea-rsyslog started ✅ libertea-haproxy started

• component name: libertea-panel
  • OS: "Ubuntu"
  • OS version: "22.04"
  • Docker version: Docker version 23.0.0, build e92dd87

tail -n 100 /tmp/libertea-panel.log tail: cannot open '/tmp/libertea-panel.log' for reading: No such file or directory

[VZiChoushaDui]

Please run the following command on a root shell and post the results:

cd /root/libertea && uwsgi --master -p 4 --need-app --http 127.0.0.1:1001 -w serve:app

[trytopassgfw]

Thanks for your response. Here the result: Starting uWSGI 2.0.21 (64bit) on [Sun Feb 12 16:26:08 2023] compiled with version: 11.3.0 on 09 February 2023 10:39:12 os: Linux-5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200) nodename: vps63....... machine: x86_64 clock source: unix detected number of CPU cores: 1 current working directory: /root/libertea detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 514595 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on 127.0.0.1:1001 fd 4 uwsgi socket 0 bound to TCP address 127.0.0.1:40733 (port auto-assigned) fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x55d770e072d0 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 364520 bytes (355 KB) for 4 cores Operational MODE: preforking ModuleNotFoundError: No module named 'serve' unable to load app 0 (mountpoint='') (callable not found or import error) no app loaded. GAME OVER

[VZiChoushaDui]

Sorry, I had a mistake in the command. Please run this one and send the result:

cd /root/libertea/panel && uwsgi --master -p 4 --need-app --http 127.0.0.1:1001 -w serve:app

[trytopassgfw]

• [ ] your welcome :)

Starting uWSGI 2.0.21 (64bit) on [Sun Feb 12 20:06:33 2023] compiled with version: 11.3.0 on 09 February 2023 10:39:12 os: Linux-5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200) nodename: vps6... machine: x86_64 clock source: unix detected number of CPU cores: 1 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 514595 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on 127.0.0.1:1001 fd 4 uwsgi socket 0 bound to TCP address 127.0.0.1:37945 (port auto-assigned) fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x5560b70672e0 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 364520 bytes (355 KB) for 4 cores Operational MODE: preforking Initializing... Traceback (most recent call last): File "/root/libertea/panel/./serve.py", line 4, in from panel import create_app File "/root/libertea/panel/./panel/init.py", line 5, in from . import admin File "/root/libertea/panel/./panel/admin.py", line 13, in root_url = '/' + config.get_admin_uuid() + '/' TypeError: can only concatenate str (not "NoneType") to str unable to load app 0 (mountpoint='') (callable not found or import error) no app loaded. GAME OVER

[VZiChoushaDui]

This is weird. It seems to be working as intended. (The error on this line is normal when running it directly).

Can you check systemctl status to see if Libertea is running?

systemctl status libertea-panel.service

[trytopassgfw]

● libertea-panel.service - LiberteaPanel Loaded: loaded (/etc/systemd/system/libertea-panel.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sun 2023-02-12 20:24:34 UTC; 128ms ago Process: 355244 ExecStart=/bin/sh -c uwsgi --master -p 4 --need-app --http 127.0.0.1:1000 -w serve:app >> /tmp/libertea-panel.log 2>&1 (code=exited, status=208/STDIN) Main PID: 355244 (code=exited, status=208/STDIN) CPU: 575us

Feb 12 20:24:34 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:24:34 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'.

[VZiChoushaDui]

Hmm. Please send me the result of this one as well:

journalctl --unit=libertea-panel.service -n 100 --no-pager

[trytopassgfw]

Feb 12 20:30:32 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8512. Feb 12 20:30:32 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:30:32 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:30:32 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:30:32 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:30:42 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8513. Feb 12 20:30:42 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:30:42 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:30:42 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:30:42 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:30:52 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8514. Feb 12 20:30:52 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:30:52 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:30:52 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:30:52 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:03 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8515. Feb 12 20:31:03 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:03 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:03 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:03 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:13 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8516. Feb 12 20:31:13 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:13 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:13 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:13 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:23 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8517. Feb 12 20:31:23 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:23 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:23 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:23 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:33 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8518. Feb 12 20:31:33 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:33 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:33 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:33 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:44 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8519. Feb 12 20:31:44 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:44 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:44 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:44 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:31:54 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8520. Feb 12 20:31:54 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:31:54 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:31:54 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:31:54 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:04 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8521. Feb 12 20:32:04 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:04 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:04 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:04 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:14 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8522. Feb 12 20:32:14 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:14 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:14 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:14 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:25 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8523. Feb 12 20:32:25 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:25 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:25 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:25 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:35 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8524. Feb 12 20:32:35 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:35 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:35 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:35 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:45 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8525. Feb 12 20:32:45 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:45 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:45 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:45 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:32:55 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8526. Feb 12 20:32:55 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:32:55 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:32:55 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:32:55 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:33:06 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8527. Feb 12 20:33:06 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:33:06 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:33:06 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:33:06 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:33:16 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8528. Feb 12 20:33:16 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:33:16 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:33:16 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:33:16 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:33:26 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8529. Feb 12 20:33:26 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:33:26 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:33:26 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:33:26 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:33:36 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8530. Feb 12 20:33:36 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:33:36 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:33:36 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:33:36 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 20:33:47 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8531. Feb 12 20:33:47 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 20:33:47 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 20:33:47 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 20:33:47 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'.

[VZiChoushaDui]

This one too.

/bin/sh -c 'set -o allexport && . /root/libertea/.env && cd /root/libertea/panel && uwsgi --master -p 4 --need-app --http 127.0.0.1:1001 -w serve:app'

Make sure your server IP is not present in logs. If it is, redact it before posting.

[trytopassgfw]

Do you think how long it will take? I think it is in a loop.

[VZiChoushaDui]

Just post the first 100 or so lines.

[trytopassgfw]

Starting uWSGI 2.0.21 (64bit) on [Sun Feb 12 20:39:33 2023] compiled with version: 11.3.0 on 09 February 2023 10:39:12 os: Linux-5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200) nodename: vps6..... machine: x86_64 clock source: unix detected number of CPU cores: 1 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 514595 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on 127.0.0.1:1001 fd 4 uwsgi socket 0 bound to TCP address 127.0.0.1:33029 (port auto-assigned) fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x5579d210a930 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 364520 bytes (355 KB) for 4 cores Operational MODE: preforking Initializing... [uwsgi-signal] signum 0 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 1 registered (wid: 0 modifier1: 0 target: default, any worker) Updating HAProxy lists Wrote 0 users to haproxy-lists/valid-user-endpoints.lst Wrote 1 users to haproxy-lists/valid-panel-endpoints.lst Reloading haproxy container libertea-haproxy Ran command 'docker kill -s HUP libertea-haproxy' and got exit code 0 Wrote 0 domains to haproxy-lists/domains.lst Reloading haproxy container libertea-haproxy Ran command 'docker kill -s HUP libertea-haproxy' and got exit code 0 Wrote 1 domains to haproxy-lists/camouflage-hosts.lst Reloading haproxy container libertea-haproxy Ran command 'docker kill -s HUP libertea-haproxy' and got exit code 0 WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x5579d210a930 pid: 355973 (default app) uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) uWSGI is running in multiple interpreter mode spawned uWSGI master process (pid: 355973) spawned uWSGI worker 1 (pid: 356105, cores: 1) spawned uWSGI worker 2 (pid: 356106, cores: 1) spawned uWSGI worker 3 (pid: 356107, cores: 1) spawned uWSGI worker 4 (pid: 356108, cores: 1) spawned uWSGI http 1 (pid: 356109) CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating users stats cache CRON: Updating domains cache CRON: done CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating users stats cache CRON: Updating domains cache CRON: done CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating users stats cache CRON: Updating domains cache CRON: done CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache CRON: Updating domains cache

[VZiChoushaDui]

Oh, this is really weird.

The panel service is running normally when you ran it manually, but it's failing when installed as service.

[VZiChoushaDui]

Can you edit the /etc/systemd/system.conf file, uncomment LogLevel line and set it to debug and save it, then run systemctl daemon-reload, wait a minute, and then run journalctl --unit=libertea-panel.service -n 100 --no-pager again?

[trytopassgfw]

Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Service will restart (restart setting) Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Changed running -> failed Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Unit entered failed state. Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Consumed 762us CPU time. Feb 12 21:11:03 vps6..... systemd[1]: libertea-panel.service: Changed failed -> auto-restart Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 3108063 Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 3108063 Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8750. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Changed auto-restart -> dead Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Job 3108063 libertea-panel.service/restart finished, result=done Feb 12 21:11:13 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Consumed 762us CPU time. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Failed to set 'io.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '100': No such file or directory Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Failed to set invocation ID on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Failed to remove delegate flag on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Passing 0 fds to service Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: About to execute /bin/sh -c "uwsgi --master -p 4 --need-app --http 127.0.0.1:1000 -w serve:app >> /tmp/libertea-panel.log 2>&1" Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Forked /bin/sh as 357417 Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Changed dead -> running Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Job 3108063 libertea-panel.service/start finished, result=done Feb 12 21:11:13 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 21:11:13 vps6..... systemd[357417]: PR_SET_MM_ARG_START failed: Operation not permitted Feb 12 21:11:13 vps6..... systemd[357417]: libertea-panel.service: Failed to set up standard input: Operation not permitted Feb 12 21:11:13 vps6..... systemd[357417]: libertea-panel.service: Failed at step STDIN spawning /bin/sh: Operation not permitted Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Child 357417 belongs to libertea-panel.service. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Service will restart (restart setting) Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Changed running -> failed Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Unit entered failed state. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Consumed 809us CPU time. Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Changed failed -> auto-restart Feb 12 21:11:13 vps6..... systemd[1]: libertea-panel.service: Control group is empty. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 3108187 Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 3108187 Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8751. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Changed auto-restart -> dead Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Job 3108187 libertea-panel.service/restart finished, result=done Feb 12 21:11:24 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Consumed 809us CPU time. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Failed to set 'io.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '100': No such file or directory Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Failed to set invocation ID on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Failed to remove delegate flag on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Passing 0 fds to service Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: About to execute /bin/sh -c "uwsgi --master -p 4 --need-app --http 127.0.0.1:1000 -w serve:app >> /tmp/libertea-panel.log 2>&1" Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Forked /bin/sh as 357436 Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Changed dead -> running Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Job 3108187 libertea-panel.service/start finished, result=done Feb 12 21:11:24 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 21:11:24 vps6..... systemd[357436]: PR_SET_MM_ARG_START failed: Operation not permitted Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Feb 12 21:11:24 vps6..... systemd[357436]: libertea-panel.service: Failed to set up standard input: Operation not permitted Feb 12 21:11:24 vps6..... systemd[357436]: libertea-panel.service: Failed at step STDIN spawning /bin/sh: Operation not permitted Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Child 357436 belongs to libertea-panel.service. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Service will restart (restart setting) Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Changed running -> failed Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Unit entered failed state. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Consumed 567us CPU time. Feb 12 21:11:24 vps6..... systemd[1]: libertea-panel.service: Changed failed -> auto-restart Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 3108311 Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 3108311 Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 8752. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Changed auto-restart -> dead Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Job 3108311 libertea-panel.service/restart finished, result=done Feb 12 21:11:34 vps6..... systemd[1]: Stopped LiberteaPanel. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Consumed 567us CPU time. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Failed to set 'io.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '100': No such file or directory Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Failed to set invocation ID on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Failed to remove delegate flag on control group /system.slice/libertea-panel.service, ignoring: Operation not permitted Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Passing 0 fds to service Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: About to execute /bin/sh -c "uwsgi --master -p 4 --need-app --http 127.0.0.1:1000 -w serve:app >> /tmp/libertea-panel.log 2>&1" Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Forked /bin/sh as 357439 Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Changed dead -> running Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Job 3108311 libertea-panel.service/start finished, result=done Feb 12 21:11:34 vps6..... systemd[1]: Started LiberteaPanel. Feb 12 21:11:34 vps6..... systemd[357439]: PR_SET_MM_ARG_START failed: Operation not permitted Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Feb 12 21:11:34 vps6..... systemd[357439]: libertea-panel.service: Failed to set up standard input: Operation not permitted Feb 12 21:11:34 vps6..... systemd[357439]: libertea-panel.service: Failed at step STDIN spawning /bin/sh: Operation not permitted Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Child 357439 belongs to libertea-panel.service. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Service will restart (restart setting) Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Changed running -> failed Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Unit entered failed state. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Consumed 592us CPU time. Feb 12 21:11:34 vps6..... systemd[1]: libertea-panel.service: Changed failed -> auto-restart

[VZiChoushaDui]

Seems like a permission issue (all those Operation not permitted messages), but no idea why this is happening.

Are you installing Libertea from root user on another user?

[trytopassgfw]

I ran this command: root@vps6...:~# sudo curl -s https://raw.githubusercontent.com/VZiChoushaDui/Libertea/master/bootstrap.sh -o /tmp/bootstrap.sh && bash /tmp/bootstrap.sh update and no difference.

Do you think, reinstalling Ubuntu with version 18.04 will make a difference?

[trytopassgfw]

I've reinstalled on Debian 11 again and got same results.

** Waiting for services to start... ✅ libertea-provider-vless-ws started ✅ libertea-provider-trojan-ws started ✅ libertea-log-parser started ✅ libertea-mongodb started ✅ libertea-rsyslog started ✅ libertea-provider-shadowsocks-v2ray started ✅ libertea-haproxy started

---

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: "11"
• Docker version: Docker version 23.0.1, build a5ee5b1 Also include the output of the following command: tail -n 100 /tmp/libertea-panel.log

[emryysDE]

Hello there :)

Libertea was running fine on my VPS until I ran the latest update where I encountered the same panel timeout error.

I am using Ubuntu 22.04 and did not use root user to install Libertea. I deleted my VPS and re-installed everything, using root or another user, but to no avail, i always receive the panel error in the end ;(

Any idea on how to fix this? As I said, it was running perfectly without any issues for the past months or so...

Any help would be greatly appreciated!

[VZiChoushaDui]

@emryysDE Can you post the result to this command? tail -n 100 /tmp/libertea-panel.log

Also this one: sudo systemctl status libertea-panel.service

[emryysDE]

Thanks for helping out! :)

The result of sudo systemctl status libertea-panel.service

libertea-panel.service - LiberteaPanel Loaded: loaded (/etc/systemd/system/libertea-panel.service; enabled; vendo> Active: activating (auto-restart) (Result: exit-code) since Thu 2023-03-16> Process: 125378 ExecStart=/bin/sh -c uwsgi --disable-logging --master -p 6 > Main PID: 125378 (code=exited, status=208/STDIN)

If I run tail -n 100 /tmp/libertea-panel.log I only get this result:

tail: cannot open '/tmp/libertea-panel.log' for reading: No such file or directory

[VZiChoushaDui]

@emryysDE This is weird. Can you try these instructions and see if you see the same results as @trytopassgfw ?

[emryysDE]

Thanks for getting back to me, results are as followed, as far as I can see it's not the exact same result, but similar kind of loop:

-- Journal begins at Mon 2023-03-20 15:16:53 CET, ends at Wed 2023-03-22 15:43:43 CET. -- Mar 22 15:42:56 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service will restart (restart setting) Mar 22 15:42:56 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed running -> failed Mar 22 15:42:56 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Unit entered failed state. Mar 22 15:42:56 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed failed -> auto-restart Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 901192 Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 901192 Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 16972. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed auto-restart -> dead Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901192 libertea-panel.service/restart finished, result=done Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: Stopped LiberteaPanel. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed to set 'blkio.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '500': No such file or directory Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Passing 0 fds to service Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: About to execute /bin/sh -c 'uwsgi --disable-logging --master -p 6 --need-app --http 127.0.0.1:1000 --listen 512 -w serve:app >> /tmp/libertea-panel.log 2>&1' Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Forked /bin/sh as 73890 Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed dead -> running Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901192 libertea-panel.service/start finished, result=done Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: Started LiberteaPanel. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Child 73890 belongs to libertea-panel.service. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service will restart (restart setting) Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed running -> failed Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Unit entered failed state. Mar 22 15:43:06 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed failed -> auto-restart Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 901245 Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 901245 Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 16973. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed auto-restart -> dead Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901245 libertea-panel.service/restart finished, result=done Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: Stopped LiberteaPanel. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed to set 'blkio.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '500': No such file or directory Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Passing 0 fds to service Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: About to execute /bin/sh -c 'uwsgi --disable-logging --master -p 6 --need-app --http 127.0.0.1:1000 --listen 512 -w serve:app >> /tmp/libertea-panel.log 2>&1' Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Forked /bin/sh as 73895 Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed dead -> running Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901245 libertea-panel.service/start finished, result=done Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: Started LiberteaPanel. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Child 73895 belongs to libertea-panel.service. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service will restart (restart setting) Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed running -> failed Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Unit entered failed state. Mar 22 15:43:16 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed failed -> auto-restart Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 901298 Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 901298 Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 16974. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed auto-restart -> dead Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901298 libertea-panel.service/restart finished, result=done Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: Stopped LiberteaPanel. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed to set 'blkio.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '500': No such file or directory Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Passing 0 fds to service Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: About to execute /bin/sh -c 'uwsgi --disable-logging --master -p 6 --need-app --http 127.0.0.1:1000 --listen 512 -w serve:app >> /tmp/libertea-panel.log 2>&1' Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Forked /bin/sh as 73898 Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed dead -> running Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901298 libertea-panel.service/start finished, result=done Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: Started LiberteaPanel. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Child 73898 belongs to libertea-panel.service. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service will restart (restart setting) Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed running -> failed Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Unit entered failed state. Mar 22 15:43:27 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed failed -> auto-restart Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service RestartSec=10s expired, scheduling restart. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Trying to enqueue job libertea-panel.service/restart/replace Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Installed new job libertea-panel.service/restart as 901351 Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Enqueued job libertea-panel.service/restart as 901351 Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Scheduled restart job, restart counter is at 16975. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed auto-restart -> dead Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901351 libertea-panel.service/restart finished, result=done Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: Stopped LiberteaPanel. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Converting job libertea-panel.service/restart -> libertea-panel.service/start Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed to set 'blkio.bfq.weight' attribute on '/system.slice/libertea-panel.service' to '500': No such file or directory Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Passing 0 fds to service Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: About to execute /bin/sh -c 'uwsgi --disable-logging --master -p 6 --need-app --http 127.0.0.1:1000 --listen 512 -w serve:app >> /tmp/libertea-panel.log 2>&1' Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Forked /bin/sh as 73905 Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed dead -> running Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Job 901351 libertea-panel.service/start finished, result=done Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: Started LiberteaPanel. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: User lookup succeeded: uid=0 gid=0 Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Child 73905 belongs to libertea-panel.service. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Main process exited, code=exited, status=208/STDIN Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Failed with result 'exit-code'. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Service will restart (restart setting) Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed running -> failed Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Unit entered failed state. Mar 22 15:43:37 vps21793352.xxxxxxxx systemd[1]: libertea-panel.service: Changed failed -> auto-restart

[VZiChoushaDui]

@emryysDE Try running this command on a root shell and send me the output (it might not exit, in which case just wait 30 secs and copy whatever it printed)

/bin/sh -c 'set -o allexport && . /root/libertea/.env && cd /root/libertea/panel && uwsgi --master -p 6 --need-app --http 127.0.0.1:1001 --listen 512 -w serve:app'

[emryysDE]

That's the whole output:

Starting uWSGI 2.0.21 (64bit) on [Wed Mar 22 15:54:55 2023] compiled with version: 10.2.1 20210110 on 20 March 2023 14:22:06 os: Linux-5.2.0 #1 SMP Tue Jan 25 12:49:12 MSK 2022 nodename: vps21793352.xxxxxxxxx machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 62987 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) Listen queue size is greater than the system max net.core.somaxconn (128).

[VZiChoushaDui]

@emryysDE Okay, I found and fixed the problem in v1025.

Please update your Libertea installation with the command below:

curl -s https://raw.githubusercontent.com/VZiChoushaDui/Libertea/master/bootstrap.sh -o /tmp/bootstrap.sh && bash /tmp/bootstrap.sh update

It should work fine now. Let me know if it still fails to start.

[emryysDE]

Thank you so much! At first it did not work after updating, but turns out I just needed to reboot and try again - now it's working flawlessly again!

//edit: While the panel is working again, I now receive an "503 service unavailable" error everytime I create a new user and click the link :(

[VZiChoushaDui]

@emryysDE Can you try updating Libertea again (to v1026) and rebooting your server, then checking for this again?

[emryysDE]

I am afraid that actually made it worse, now I can't even access the panel anymore, "error 502 bad gateway The server returned an invalid or incomplete response"

//edit: tried re-installing, now also the original error with the panel failing to load seems to be back

[VZiChoushaDui]

Oh.

Please send me the result of the following three commands again:

tail -n 100 /tmp/libertea-panel.log

tail -n 20 /tmp/libertea-panel.init.log

/bin/sh -c 'set -o allexport && . /root/libertea/.env && cd /root/libertea/panel && uwsgi --master -p 6 --need-app --http 127.0.0.1:1001 --listen 100 -w serve:app'

[emryysDE]

result for tail -n 100 /tmp/libertea-panel.log

could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool Thu Mar 23 14:40:00 2023 - [uwsgi-cron] routing signal 3 SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 3 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 1 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool SIGNAL QUEUE IS FULL: buffer size 212992 bytes (you can tune it with --signal-bufsize) could not deliver signal 0 to workers pool [2023-03-23 14:41:58] Libertea panel serve script exited with code 137 [2023-03-23 14:41:58] Libertea panel serve script [2023-03-23 14:41:58] Current directory: /root/libertea/panel [2023-03-23 14:41:58] Checking net.core.somaxconn value [2023-03-23 14:41:58] net.core.somaxconn value is 128 [2023-03-23 14:41:58] Starting Libertea panel via uwsgi on port 1000 with 6 threads, and listen queue size of 127 Starting uWSGI 2.0.21 (64bit) on [Thu Mar 23 14:41:58 2023] compiled with version: 11.3.0 on 22 March 2023 17:55:38 os: Linux-5.2.0 #1 SMP Tue Jan 25 12:49:12 MSK 2022 nodename: vps21793352.xxxxxxx machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 62987 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on 127.0.0.1:1000 fd 4 uwsgi socket 0 bound to TCP address 127.0.0.1:46359 (port auto-assigned) fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x5580db063d70 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 127 connections your mercy for graceful operations on workers is 60 seconds mapped 510328 bytes (498 KB) for 6 cores Operational MODE: preforking Initializing... [uwsgi-signal] signum 0 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 1 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 2 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 3 registered (wid: 0 modifier1: 0 target: default, any worker) Updating HAProxy lists -- creating mongo client on pid 20486 Wrote 0 users to haproxy-lists/valid-user-endpoints.lst Wrote 1 users to haproxy-lists/valid-panel-endpoints.lst Reloading haproxy container Wrote 0 domains to haproxy-lists/domains.lst Reloading haproxy container Wrote 1 domains to haproxy-lists/camouflage-hosts.lst Reloading haproxy container WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x5580db063d70 pid: 20486 (default app) uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) uWSGI is running in multiple interpreter mode spawned uWSGI master process (pid: 20486) spawned uWSGI worker 1 (pid: 20538, cores: 1) spawned uWSGI worker 2 (pid: 20539, cores: 1) spawned uWSGI worker 3 (pid: 20540, cores: 1) spawned uWSGI worker 4 (pid: 20541, cores: 1) spawned uWSGI worker 5 (pid: 20542, cores: 1) spawned uWSGI worker 6 (pid: 20543, cores: 1) spawned uWSGI http 1 (pid: 20544) libertea-haproxy subprocess 20535 exited with code 0 libertea-haproxy -- creating mongo client on pid 20538 CRON: Updating domains cache -- creating mongo client on pid 20539 CRON: Updating domains cache -- creating mongo client on pid 20540 CRON: Updating domains cache -- creating mongo client on pid 20541 CRON: Updating domains cache -- creating mongo client on pid 20542

result for tail -n 20 /tmp/libertea-panel.init.log

[2023-03-22 18:02:22] Libertea panel serve script [2023-03-22 18:02:22] Current directory: /root/libertea/panel [2023-03-22 18:02:22] Checking net.core.somaxconn value [2023-03-22 18:02:22] net.core.somaxconn value is 128 [2023-03-22 18:02:22] Starting Libertea panel via uwsgi on port 1000 with 6 threads, and listen queue size of 127 [2023-03-22 18:05:00] Libertea panel serve script [2023-03-22 18:05:00] Current directory: /root/libertea/panel [2023-03-22 18:05:00] Checking net.core.somaxconn value [2023-03-22 18:05:00] net.core.somaxconn value is 128 [2023-03-22 18:05:00] Starting Libertea panel via uwsgi on port 1000 with 6 threads, and listen queue size of 127 [2023-03-23 14:41:58] Libertea panel serve script exited with code 137 [2023-03-23 14:41:58] Libertea panel serve script [2023-03-23 14:41:58] Current directory: /root/libertea/panel [2023-03-23 14:41:58] Checking net.core.somaxconn value [2023-03-23 14:41:58] net.core.somaxconn value is 128 [2023-03-23 14:41:58] Starting Libertea panel via uwsgi on port 1000 with 6 threads, and listen queue size of 127

and result for /bin/sh -c 'set -o allexport && . /root/libertea/.env && cd /root/libertea/panel && uwsgi --master -p 6 --need-app --http 127.0.0.1:1001 --listen 100 -w serve:app'

Starting uWSGI 2.0.21 (64bit) on [Thu Mar 23 14:51:42 2023] compiled with version: 11.3.0 on 22 March 2023 17:55:38 os: Linux-5.2.0 #1 SMP Tue Jan 25 12:49:12 MSK 2022 nodename: vps21793352.xxxxxxx machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 62987 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) probably another instance of uWSGI is running on the same address (127.0.0.1:1001). bind(): Address already in use [core/socket.c line 769]

[VZiChoushaDui]

This is weird. Are you still getting 502 when loading the panel?

Kindly please give me the result of these as well:

curl -i localhost:1000

/bin/sh -c 'set -o allexport && . /root/libertea/.env && cd /root/libertea/panel && uwsgi --master -p 6 --need-app --http 127.0.0.1:12301 --listen 127 -w serve:app'

[emryysDE]

after the latest update, I can't even access the panel cause I get the "error: timeout while waiting for the panel to start". that error was fixed with v1025, but v1026 seems to have broken it again.

result of above command:

Starting uWSGI 2.0.21 (64bit) on [Thu Mar 23 18:53:28 2023] compiled with version: 11.3.0 on 22 March 2023 17:55:38 os: Linux-5.2.0 #1 SMP Tue Jan 25 12:49:12 MSK 2022 nodename: vps21793352.xxxxxxxxx machine: x86_64 clock source: unix detected number of CPU cores: 2 current working directory: /root/libertea/panel detected binary path: /usr/local/bin/uwsgi !!! no internal routing support, rebuild with pcre support !!! uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your processes number limit is 62987 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on 127.0.0.1:12301 fd 4 uwsgi socket 0 bound to TCP address 127.0.0.1:37644 (port auto-assigned) fd 3 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) Python version: 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] Python threads support is disabled. You can enable it with --enable-threads Python main interpreter initialized at 0x55d115620960 uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) your server socket listen backlog is limited to 127 connections your mercy for graceful operations on workers is 60 seconds mapped 510328 bytes (498 KB) for 6 cores Operational MODE: preforking Initializing... [uwsgi-signal] signum 0 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 1 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 2 registered (wid: 0 modifier1: 0 target: default, any worker) [uwsgi-signal] signum 3 registered (wid: 0 modifier1: 0 target: default, any worker) Updating HAProxy lists -- creating mongo client on pid 24042 Wrote 0 users to haproxy-lists/valid-user-endpoints.lst Wrote 1 users to haproxy-lists/valid-panel-endpoints.lst Reloading haproxy container Wrote 0 domains to haproxy-lists/domains.lst Reloading haproxy container Wrote 1 domains to haproxy-lists/camouflage-hosts.lst Reloading haproxy container WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x55d115620960 pid: 24042 (default app) uWSGI running as root, you can use --uid/--gid/--chroot options WARNING: you are running uWSGI as root !!! (use the --uid flag) uWSGI is running in multiple interpreter mode spawned uWSGI master process (pid: 24042) spawned uWSGI worker 1 (pid: 24058, cores: 1) spawned uWSGI worker 2 (pid: 24059, cores: 1) spawned uWSGI worker 3 (pid: 24060, cores: 1) spawned uWSGI worker 4 (pid: 24061, cores: 1) spawned uWSGI worker 5 (pid: 24062, cores: 1) spawned uWSGI worker 6 (pid: 24063, cores: 1) spawned uWSGI http 1 (pid: 24064) libertea-haproxy libertea-haproxy subprocess 24050 exited with code 0 libertea-haproxy

[VZiChoushaDui]

@emryysDE Sorry this is getting too long. Please give me the result for the following two commands as well:

1. curl -I http://localhost:1000
2. cd /root/libertea && set -o allexport && . .env && curl -I http://localhost:1000/$PANEL_ADMIN_UUID/

[emryysDE]

No worries, here you go, but I am not sure if that's the desired output:

root@vps21793352:~# curl -I http://localhost:1000 HTTP/1.1 404 NOT FOUND Content-Type: text/html; charset=utf-8 Content-Length: 207

root@vps21793352:~# cd /root/libertea && set -o allexport && . .env && curl -I http://localhost:1000/$PANEL_ADMIN_UUID/ HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Content-Length: 19363

[VZiChoushaDui]

@emryysDE The weird thing is, these result show that panel service is actually already running.

Can you run the Libertea update command once more and see if anything changes?

curl -s https://raw.githubusercontent.com/VZiChoushaDui/Libertea/master/bootstrap.sh -o /tmp/bootstrap.sh && bash /tmp/bootstrap.sh update

[emryysDE]

Unfortunately, the result stays the same :( I even re-installed the server several times, tried Ubuntu as well as Debian. I really don't know why it stopped working, until about three weeks ago Libertea was working perfectly fine, same server same everything.

[VZiChoushaDui]

@emryysDE Is this reproducible with a new server? If so, can you tell me which provider you're using? so we can test it ourserlves.