Answer by Daren Johnson · Sep 21, 2015 at 11:36 PM
We are planning to support systemd, but there is not timeframe for availability.
Answer by Daren Johnson · Sep 23, 2015 at 07:37 AM
There are some workarounds.
1/ you can manually start Wowza by running the following as root
# /etc/init.d/WowzaStreamingEngine start
# /etc/init.d/WowzaStreamingEngineManager start
2/ Alternatively, you can reinstall the missing upstart functionality
# apt-get install upstart-sysv
The second option would ensure that Wowza is restarted on machine reboots.
3) A third option would be to try implementing the systemd service. This
forum thread/post seems to have something that was reported as working.
administrateur@zircone:/etc/init.d$ sudo systemctl enable WowzaStreamingEngine.service
Synchronizing state for WowzaStreamingEngine.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d WowzaStreamingEngine defaults
insserv: warning: current stop runlevel(s) (0 1 6) of script `WowzaStreamingEngine' overrides LSB defaults (0 1 6 S).
Executing /usr/sbin/update-rc.d WowzaStreamingEngine enable
update-rc.d: error: WowzaStreamingEngine Default-Start contains no runlevels, aborting.
removed symlink /etc/init.d/WowzaStreamingEngine
removed symlink /etc/init.d/WowzaStreamingEngineManager
Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.
Answers Answers and Comments
2 People are following this question.
Quick JConsole overview 1 Answer
Database logging 3 Answers
Need a serious help on MediaCache with SMIL 2 Answers
How to Limit Stream Name Allowed PER APPLICATIONS? 4 Answers
How to Limit Server to Client Bandwidth for VOD 1 Answer
© 2005–2017 Wowza Media Systems, LLC. All rights reserved. Terms | Privacy | Trademarks | Legal