When installing either the deb or rpm for Wowza Streaming Engine 4.7.7 it seems to add sysv init scripts (/etc/init.d/WowzaStreamingEngine and /etc/init.d/WowzaStreamingEngineManager). However I can’t seem to find a way to get these to auto start on boot with Ubuntu 18.04.
There also appears to be systemd init files that get copied to /usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine.service and /usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager.service but these aren’t linked to/installed anywhere that systemd can make use of them which is strange…within these service files there’s no stop link defined so the process is sent a TERM signal and the service files seem to execute a different startup script for Wowza compared to the sysv files.
When trying to add the sysv scripts to systemd with
systemctl enable WowzaStreamingEngine I get the following output despite there being
# Default-Start: 2 3 4 5 defined within the
BEGIN INIT INFO section of the init script:
“WowzaStreamingEngine.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable WowzaStreamingEngine update-rc.d: error: WowzaStreamingEngine Default-Start contains no runlevels, aborting.”
I’m investigating this as ansible isn’t able to enable the WowzaStreamingEngine/WowzaStreamingEngineManager services on boot using the
service module, similarly it complains of missing runlevels.
Thanks in advance