• How to modify Wowza Streaming Engine init systems (Linux)

    With Wowza Streaming Engine™ 4.4 media server software, you can run Wowza Streaming Engine as a service on Linux operating systems that require systemd support, as well as those that use the sysvinit/upstart system. This article describes how to convert the init system if you have updated to a newer version of Linux that requires systemd support, such as upgrading from Ubuntu 14.04 to 15.10.

    Notes:
    • Changing the init system services is only relevant if you're running Wowza Streaming Engine as a service.

    • For new installations, the Wowza Streaming Engine installer should detect and use the appropriate init system services. If the installer misidentifies the init system, see Check services on Linux.

    • For more information about init systems, see init Unix process.
    If Wowza Streaming Engine services won't start after upgrading your media server's operating system, you might need to manually change the init system services.

    1. See if the Wowza Streaming Engine services are running. Open a Terminal window and enter the following command:
      ps ax | grep Wowza
      The command should return output similar to:
      1391 ?        S      0:00 /bin/bash /usr/bin/WowzaStreamingEngined /usr/local/WowzaStreamingEngine/bin/setenv.sh /var/run/WowzaStreamingEngine.pid start
      1408 ?        Sl     1:03 /usr/java/latest/bin/java -Xmx1158M -XX:+UseG1GC -XX:MaxGCPauseMillis=100 -server -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote=true -Dcom.wowza.wms.runmode=service -Dcom.wowza.wms.native.base=linux -Dcom.wowza.wms.AppHome=/usr/local/WowzaStreamingEngine -Dcom.wowza.wms.ConfigURL= -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine -cp /usr/local/WowzaStreamingEngine/bin/wms-bootstrap.jar com.wowza.wms.bootstrap.Bootstrap start
      1430 ?        S      0:00 /bin/bash /usr/bin/WowzaStreamingEngineManagerd /usr/local/WowzaStreamingEngine/manager/bin/setmgrenv.sh /var/run/WowzaStreamingEngineManager.pid start
      1437 ?        Sl     0:30 java -Dcom.wowza.wms.ConfigURL="" -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine/manager -Djava.io.tmpdir=/usr/local/WowzaStreamingEngine/manager/temp -Dlog4j.configuration=file:///usr/local/WowzaStreamingEngine/manager/conf/winstone.properties -Djava.net.preferIPv4Stack=true -jar /usr/local/WowzaStreamingEngine/manager/lib/wms-winstone-1.0.5-boot.jar --prefix=/enginemanager --defaultWebApp=/enginemanager --tempDirectory=/usr/local/WowzaStreamingEngine/manager/temp --webroot=/usr/local/WowzaStreamingEngine/manager/temp --warfile=/usr/local/WowzaStreamingEngine/manager/lib/WMSManager.war --httpPort=8088 --ajp13Port=-1 --directoryListings=false > /dev/null
    2. If you don't see processes for WowzaStreamingEngined or WowzaStreamingEngineManagerd, start it. Open a Terminal window and enter one of the following commands, depending on your distribution and the service that needs to be started:
      sudo service WowzaStreamingEngine start
      sudo service WowzaStreamingEngineManager start
      /etc/init.d/WowzaStreamingEngine start
      /etc/init.d/WowzaStreamingEngineManager start
    3. If the Wowza Streaming Engine services won't start, the installer might have misidentified the init system for your operating system. Use one of the following commands to change the init system between sysvinit/upstart and systemd:

      • To change from sysvinit/upstart to systemd, run the following command:
        sudo /usr/local/WowzaStreamingEngine/bin/installsystemd.sh
        This removes the sysvinit/upstart services, and then creates and starts the systemd services.

      • To change from systemd to sysvinit/upstart, run the following command:
        sudo /usr/local/WowzaStreamingEngine/bin/installupstart.sh
        This removes the systemd services, and then creates and starts the sysvinit/upstart services.

    Originally Published: For Wowza Streaming Engine 4.4.0 on 02-02-2016.

    If you're having problems or want to discuss this article, post in our forum.