Ubuntu - Omada Controller Restart not successfull
Hello,
over night, some update seems to have decided to restart tpeap.service. After that restart, the webinterface is not reachable anymore: "Timeout"
These are the logs:
journalctl -b -u tpeap Sep 02 20:14:55 x systemd[1]: Starting tpeap.service - LSB: Omada Controller... Sep 02 20:14:55 x tpeap[1141]: check omada Sep 02 20:15:24 x tpeap[1141]: Starting Omada Controller. Please wait............................ Sep 02 20:15:24 x tpeap[1141]: Started successfully. Sep 02 20:15:24 x tpeap[1141]: You can visit http://localhost:8088 on this host to manage the wireless network. Sep 02 20:15:24 x systemd[1]: Started tpeap.service - LSB: Omada Controller. Sep 04 07:00:13 x tpeap[598147]: Stopping Omada Controller ............................... Sep 04 07:00:13 x tpeap[598147]: Stop failed. going to kill it. Sep 04 07:00:13 x systemd[1]: tpeap.service: Deactivated successfully. Sep 04 07:00:13 x systemd[1]: tpeap.service: Unit process 1287 (jsvc) remains running after unit stopped. Sep 04 07:00:13 x systemd[1]: tpeap.service: Unit process 1288 (jsvc) remains running after unit stopped. Sep 04 07:00:13 x systemd[1]: Stopped tpeap.service - LSB: Omada Controller. Sep 04 07:00:13 x systemd[1]: tpeap.service: Consumed 32min 10.427s CPU time, 2.7G memory peak, 1.1G memory swap peak. Sep 04 07:00:13 x systemd[1]: tpeap.service: Found left-over process 1287 (jsvc) in control group while starting unit. Ignoring. Sep 04 07:00:13 x systemd[1]: tpeap.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 04 07:00:13 x systemd[1]: tpeap.service: Found left-over process 1288 (jsvc) in control group while starting unit. Ignoring. Sep 04 07:00:13 x systemd[1]: tpeap.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 04 07:00:13 x systemd[1]: Starting tpeap.service - LSB: Omada Controller... Sep 04 07:00:13 x tpeap[599602]: Omada Controller is already running. You can visit http://localhost:8088 on this host to manage the wireless network. Sep 04 07:00:13 x systemd[1]: Started tpeap.service - LSB: Omada Controller.
It states 2 left-over processes. Once I kill them and restart the service, everything is back to normal. So it seems that the handling of the service and all of its child processes is not clean and I consider this a bug.
kill -9 1287 1288 systemctl restart tpeap
Sep 04 07:00:13 systemd[1]: Started tpeap.service - LSB: Omada Controller. Sep 05 07:37:44 systemd[1]: Stopping tpeap.service - LSB: Omada Controller... Sep 05 07:37:44 tpeap[1095328]: Omada Controller not running. Sep 05 07:37:44 systemd[1]: tpeap.service: Deactivated successfully. Sep 05 07:37:44 systemd[1]: Stopped tpeap.service - LSB: Omada Controller. Sep 05 07:37:44 systemd[1]: Starting tpeap.service - LSB: Omada Controller... Sep 05 07:37:44 tpeap[1095347]: check omada Sep 05 07:37:59 tpeap[1095347]: Starting Omada Controller. Please wait............... Sep 05 07:37:59 tpeap[1095347]: Started successfully. Sep 05 07:37:59 tpeap[1095347]: You can visit http://localhost:8088 on this host to manage the wireless network. Sep 05 07:37:59 systemd[1]: Started tpeap.service - LSB: Omada Controller.
Voila - everything works again
System:
Controller: 5.14.26.1
Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-41-generic x86_64)
java -version
openjdk version "21.0.4" 2024-07-16
OpenJDK Runtime Environment (build 21.0.4+7-Ubuntu-1ubuntu224.04)
OpenJDK 64-Bit Server VM (build 21.0.4+7-Ubuntu-1ubuntu224.04, mixed mode, sharing)