Linux: tpeap service failed, but Omada running
I was reviewing logs on my RPI linux server and noticed that the Omada Controller was failing to load. I was surprised as Omada was actually running and the web interface was fully functional. I am running Omada 5.9.31, but on a different port, 8143. I checked the logs in /opt/tplink/EAPController/logs/ and didn't see any failures.
Any ideas on why the controller is working fine, but the service is timing out?
Oct 19 23:39:12 raspberrypi systemd[1]: Starting LSB: Omada Controller...
Oct 19 23:39:12 raspberrypi tpeap[686]: check omada
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: start operation timed out. Terminating.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Failed with result 'timeout'.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Unit process 750 (jsvc) remains running after unit stopped.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Unit process 751 (jsvc) remains running after unit stopped.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Unit process 975 (sh) remains running after unit stopped.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Unit process 976 (mongod) remains running after unit stopped.
Oct 19 23:44:37 raspberrypi systemd[1]: tpeap.service: Unit process 1390 (sleep) remains running after unit stopped.
Oct 19 23:44:37 raspberrypi systemd[1]: Failed to start LSB: Omada Controller.