Wowza deb/rpm systemd service
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
Hello @Paul Gration,
Based on your issue description it seems like there might have been something permission or system-level going on when you installed Wowza.
I would recommend uninstalling Wowza Engine, restarting your linux system and trying to install using the latest installer available from here:
https://www.wowza.com/pricing/installer
I checked a local Wowza install on a CentOS linux and did nto see the /etc/init.d/WowzaStreamingEngine script.
Regards,
Alex C.
Wowza Support
Hello,
I face exactly the same problem on a fresh Debian 9.0 (buster) :
root@wowza2:/etc/init.d# systemctl enable WowzaStreamingEngine
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.
and the
/etc/init.d/WowzaStreamingEngine.service file contains the correct header:
#### BEGIN INIT INFO
# Provides: WowzaStreamingEngine
# Required-Start: $syslog $time $local_fs $remote_fs
# Required-Stop: $syslog $time $local_fs $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: S 0 1 6
# Short-Description: Wowza Streaming Engine 4 Init Script
# Description: Wowza Streaming Engine 4 Init Script
### END INIT INFO
Please tell us which version of Engine are you using @yannick barbeaux?
I downloaded the latest version today :
WowzaStreamingEngine-4.7.8-linux-x64-installer.run
That is what I thought. That's great that you did, but it came with some big changes from 4.7.7. Let me check with the engineers on your post and I'll be back here soon.
Tech support is requesting a support ticket on this @yannick barbeaux. They are curious as to why this is happening and need to have full access to your config and logs. You can submit it here:
https://www.wowza.com/support/open-ticket
Thank you.
