Hi Group,

I want to share my frustrations - maybe someone even knows the answer.
First: Debian 12 has not reached TP yet. The installation procedure is somewhat outdated.

Omada requieres Mongodb. Current version is 7.x, and it is actually possible to install it - but the installation does not work.
First: you have to add a DEB entry in some file and make sure it also contains the signing. Some suggests key management but I was not successfull doing that:
/etc/apt/sources.list.d make a file like mongodb-org-7.0.list

It should contain:

deb [ arch=amd64,arm64 signed-by=/usr/share/keyrings/mongodb-server-7.0.gpg ] https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/7.0 multiverse

This will make it possible to apt install mongodb-org

Alas the installation will not create a service - and hence it will not start:
Create in /etc/systemd/system a file called mongodb.service containing:

[Unit]
Description=An object/document-oriented database
Documentation=man:mongod(1)
After=network.target

[Service]
User=mongodb
Group=mongodb
ExecStart=/usr/bin/mongod --quiet --config /etc/mongodb.conf

[Install]
WantedBy=multi-user.target

That makes it possible to systemctl enable mongodb - but /etc/mongodb.conf still does not exist. It may look something like (see mongodb manual):

processManagement:
   fork: true
net:
   bindIp: localhost
   port: 27017
storage:
   dbPath: /var/lib/mongodb
systemLog:
   destination: file
   path: "/var/log/mongodb/mongod.log"
   logAppend: true
#storage:
#   journal:
#      enabled: true
 

The thee last lines was copied from an answer in a group, but the service would not start - did not know that directive.

Now it is possible to systemctl start mongodb :-)

Still it is not possible to install and run Omada....
I downloaded the tar.gz from the TP download site, extracted and ran install.sh
------------------------

root@mgr2:/home/freddy# systemctl status tpeap
× tpeap.service - LSB: Omada Controller
     Loaded: loaded (/etc/init.d/tpeap; generated)
     Active: failed (Result: timeout) since Thu 2023-09-07 02:41:59 CEST; 10h ago
       Docs: man:systemd-sysv-generator(8)
    Process: 1425 ExecStart=/etc/init.d/tpeap start (code=killed, signal=TERM)
        CPU: 1min 25.511s

sep 07 02:36:59 mgr2 systemd[1]: Starting tpeap.service - LSB: Omada Controller...
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: start operation timed out. Terminating.
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: Failed with result 'timeout'.
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: Unit process 1463 (jsvc) remains running after unit stopped.
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: Unit process 1464 (jsvc) remains running after unit stopped.
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: Unit process 4340 (sleep) remains running after unit stopped.
sep 07 02:41:59 mgr2 systemd[1]: Failed to start tpeap.service - LSB: Omada Controller.
sep 07 02:41:59 mgr2 systemd[1]: tpeap.service: Consumed 57.384s CPU time.
sep 07 02:42:00 mgr2 tpeap[1425]: Starting Omada Controller. Please wait...........................................

JSVC:
Omada installation manual says to get the source, a compiler and compile the thing.
It is possible to apt install jsvc and that was what i did - assuming the package will be updated by some nice and competent people :-)

journalctl -xeu tpeap.service

basically says the same as the status (a little more detail - and mine is in Danish. I will spare you that experience ;-)


Any thoughts?
Mine is: Why is TP not supporting debian 12 better - so that we all do not need to hack our way thru a jungle of google searches.
Ideally it should be apt install omada - and it works. I can live with a working install.sh adding a deb etc - as long as it works "out of the box".