@needbb is mongodb service running?

I rebooted my PI and after a few minutes the Web UI becomes available and I can manage my TPlink devices.

Yes, MonoDB loads correctly:

pi@raspberrypi:~ $ systemctl status mongod
● mongod.service - MongoDB Database Server
     Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-10-19 23:39:12 EDT; 21h ago
       Docs: https://docs.mongodb.org/manual
   Main PID: 682 (mongod)
        CPU: 9min 4.196s
     CGroup: /system.slice/mongod.service
             └─682 /usr/bin/mongod --config /etc/mongod.conf

Oct 19 23:39:12 raspberrypi systemd[1]: Started MongoDB Database Server.

What I thought was interesting is the startup log doesn't have any details of actually starting Omada:

pi@raspberrypi:~ $ cat /opt/tplink/EAPController/logs/startup.log
java version "11.0.20"
OpenJDK Runtime Environment (build 11.0.20+8-post-Debian-1deb11u1)
OpenJDK 64-Bit Server VM (build 11.0.20+8-post-Debian-1deb11u1, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 751, parent: 750)

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.6.6)

pi@raspberrypi:~ $

Lastly if I manually start the service it realizes it is already running:

pi@raspberrypi:~ $ sudo systemctl start tpeap

pi@raspberrypi:~ $ journalctl -u tpeap

Oct 20 21:15:18 raspberrypi systemd[1]: tpeap.service: Found left-over process 750 (jsvc) in control group while starti>
Oct 20 21:15:18 raspberrypi systemd[1]: This usually indicates unclean termination of a previous run, or service implem>
Oct 20 21:15:18 raspberrypi systemd[1]: tpeap.service: Found left-over process 751 (jsvc) in control group while starti>
Oct 20 21:15:18 raspberrypi systemd[1]: This usually indicates unclean termination of a previous run, or service implem>
Oct 20 21:15:18 raspberrypi systemd[1]: tpeap.service: Found left-over process 975 (sh) in control group while starting>
Oct 20 21:15:18 raspberrypi systemd[1]: This usually indicates unclean termination of a previous run, or service implem>
Oct 20 21:15:18 raspberrypi systemd[1]: tpeap.service: Found left-over process 976 (mongod) in control group while star>
Oct 20 21:15:18 raspberrypi systemd[1]: This usually indicates unclean termination of a previous run, or service implem>
Oct 20 21:15:18 raspberrypi systemd[1]: Starting LSB: Omada Controller...
Oct 20 21:15:19 raspberrypi tpeap[18540]: Omada Controller is already running. You can visit http://localhost:8088 on t>

What is interesting is that I modified port in my config to not run on port 8088, but it still reports this.
 

Nobody else has this issue?

  @needbb 

I have this problem too, however the web is working... (???)

output of "systemctl status tpeap"

● tpeap.service - LSB: Omada Controller
     Loaded: loaded (/etc/init.d/tpeap; generated)
     Active: failed (Result: timeout) since Tue 2024-01-30 20:11:25 -03; 2min 36s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 929 ExecStart=/etc/init.d/tpeap start (code=killed, signal=TERM)
      Tasks: 246 (limit: 1982)
     Memory: 1.1G
     CGroup: /system.slice/tpeap.service
             ├─1103 omada -cwd /opt/tplink/EAPController/lib -pidfile /var/run/omada.pid -home /usr/lib/jvm/java-8-openjdk-arm64/jre/ -cp /usr/share/java/commons-daemon.jar:/opt/tplink/EAPController/lib/*:/opt/tpl>             ├─1105 omada -cwd /opt/tplink/EAPController/lib -pidfile /var/run/omada.pid -home /usr/lib/jvm/java-8-openjdk-arm64/jre/ -cp /usr/share/java/commons-daemon.jar:/opt/tplink/EAPController/lib/*:/opt/tpl>             ├─1270 sh -c "/opt/tplink/EAPController/bin/mongod" --port 27217 --dbpath "../data/db" -pidfilepath "../data/mongo.pid" --logappend --logpath "../logs/mongod.log" --bind_ip 127.0.0.1 --journal
             └─1272 /opt/tplink/EAPController/bin/mongod --port 27217 --dbpath ../data/db -pidfilepath ../data/mongo.pid --logappend --logpath ../logs/mongod.log --bind_ip 127.0.0.1 --journal

Jan 30 20:05:26 CONTROLLER systemd[1]: Starting LSB: Omada Controller...
Jan 30 20:05:29 CONTROLLER tpeap[929]: check omada
Jan 30 20:11:25 CONTROLLER systemd[1]: tpeap.service: start operation timed out. Terminating.
Jan 30 20:11:25 CONTROLLER systemd[1]: tpeap.service: Failed with result 'timeout'.
Jan 30 20:11:25 CONTROLLER systemd[1]: Failed to start LSB: Omada Controller.
Jan 30 20:11:25 CONTROLLER tpeap[929]: Starting Omada Controller. Please wait.................