After a clean install to a new Ubuntu 22.04.4 system, installing the Software Controller (SC) v5.13.30.8 and its pre-requisites, all is running well.

After rebooting the VM, the SC does not start.  I have to start it manually, with tpeap start.

---

An old-style init.d script is used instead of a systemd service definition that would be appropriate for Ubuntu.

Is there a systemd service definition for the SC on Ubuntu?

$ sudo find /opt/tplink/ -type f -name \*service
$

---

I've discovered a few things:

• Init.d is setup correctly
  • These files exist
    • /etc/init.d/tpeap
      • symlinked -> /opt/tplink/EAPController/bin/control.sh
    • /etc/rc0.d/K01tpeap
      /etc/rc1.d/K01tpeap
      /etc/rc2.d/S01tpeap
      /etc/rc3.d/S01tpeap
      /etc/rc4.d/S01tpeap
      /etc/rc5.d/S01tpeap
      /etc/rc6.d/K01tpeap

• An error in syslog:
  • systemd-sysv-generator[451]: stat() failed on /etc/init.d/tpeap, ignoring: No such file or directory

• The server storage layout separates / from /opt. 
  • $ df /
    Filesystem                1K-blocks    Used Available Use% Mounted on
    /dev/mapper/vgub22-lvroot   8378368 2170420   6207948  26% /
  • $ df /opt
    Filesystem               1K-blocks   Used Available Use% Mounted on
    /dev/mapper/vgub22-lvopt   2086912 695760   1391152  34% /opt

• There is nothing in the SC User Guide to indicate / and /opt must be on the same disk.

I believe this separation causes the systemd-sysv-generator error, because the tpeap script in /etc/init.d is symlinked outside of the root filesystem.

Normally, you should be able to cp /opt/tplink/EAPController/bin/control.sh into /etc/init.d/, but it fails when running from there.