• How to troubleshoot Wowza Streaming Engine installation

    The install wizard streamlines the process of getting Wowza Streaming Engine™ software deployed, however, problems may still occur. This article covers common errors that may occur when installing the software on a new server and provides troubleshooting steps to help you resolve them.

    Contents


    Troubleshoot Java-related problems
    Troubleshoot installation problems
    Troubleshoot startup problems
    More resources

    Troubleshoot Java-related problems


    When you install Wowza Streaming Engine, it automatically installs the server version of the Java Runtime Environment (JRE) that it requires. If you need help installing or troubleshooting Java for Wowza Streaming Engine, see How to manually install and troubleshoot Java on your Wowza media server.

    Troubleshoot installation problems


    If you encountered problems with the Wowza Streaming Engine software installer, try these steps so that you can complete the installation process.

    Check permissions

    Make sure you're running the installer as an elevated user with administrative privileges. If you're not, you won't be able to run the installer.

    On OS X and Linux, check that the permissions on the installer file allow execution by running the following command:
    ls -la
    You should see file permissions similar to the following:
    -rwxr-xr-x  1 wowza  wowza  206904581 Aug 13 08:48 WowzaStreamingEngine-4.2.0-linux-x64-installer.run
    If the file permissions are not the same, run the following command:
    chmod +x
    Note: On OS X and Linux, Wowza Streaming Engine can run as a named user only after it's been installed by the root/administrator user. If you need to run Wowza Streaming Engine as a named user, see How to run Wowza Streaming Engine as a Named User (Linux and OS X).

    Disable antivirus software

    Make sure you've disabled antivirus software before you try to install Wowza Streaming Engine. Antivirus programs can cause installation errors.

    Check the installer log file

    Open the installer log file and look for any errors or scripts that didn't run. Installation scripts should exit with code: 0 and should end as follows:
    Starting Wowza Streaming Engine Manager
    Creating Uninstaller
    Creating uninstaller 25%
    Creating uninstaller 50%
    Creating uninstaller 75%
    Creating uninstaller 100%
    Uninstaller icon changed
    Installation completed
    Log finished 06/18/2015 at 09:13:13
    Launching https://localhost:8088/enginemanager
    You can find installer log files at the following locations (previous Wowza software installations can result in multiple log files):

    • Windows - C:/Users/[UserName]/AppData/Local/Temp/bitrock_installer.log
    • OS X - /tmp/bitrock_installer.log
    • Linux - /tmp/bitrock_installer.log, as the root user

    Note: In older versions of Windows, installer log files can be found in C:/Documents and Settings/username/Local Settings/Temp/bitrock_installer.log or %temp%/bitrock_installer.log.

    (Linux) Check run levels

    Wowza Streaming Engine software requires that the run level support multi-user mode with network services started and no graphical interface. For Red Hat/Centros distributions, the server should be configured to use run level 3. For Ubuntu/Debian distributions, the server should be configured to use run level 2.

    To check the run level for the user account, open a Terminal window and enter the command:
    who -r
    The run levels for the startup scripts are:
    Default-Start - 2 3 4 5
    Default-Stop - S 0 1 6
    You may have to change the run level if your Linux distribution is blocking installation in one of these run levels. For example, OpenSUSE 11.4 blocks services that start in run level 4. To change the run level, edit the designated runlevels for the /etc/init.d/WowzaStreamingEngine and /etc/init.d/WowzaStreamingEngineManager files.

    (Linux) Look for a noexec flag

    A noexec flag on the mounted file system may result in the following install error:
    Wowza Streaming Engine Setup - Warning: This license key is not valid for version 4. Please enter a valid key.
    Download the latest installer file and run the installer again.

    Install Wowza Streaming Engine services manually

    If you can't get the installer wizard to work, you can try manually installing the Wowza Streaming Engine and Wowza Streaming Engine Manager services.

    Install Wowza Streaming Engine services manually on Windows


    1. Navigate to [install-dir]/bin/ and open the file InstallWowzaStreamingEngine-Service.bat.

    2. Look for and delete the following lines:
      net session >nul 2>&1 
      if NOT %errorLevel% == 0 ( 
      echo Administrator privileges are required to install Wowza Streaming Engine, Please retry with Administrator privileges. 
      echo InstallWSE: no admin privileges. >> installbatch.log 
      goto :end 
      )
    3. Save the file and then double-click it to run it.

    4. Navigate to [install-dir]/manager/bin/ and open the file InstallWowzaStreamingEngineManager-Service.bat.

    5. Look for and delete the following lines:
      net session >nul 2>&1 
      if NOT %errorLevel% == 0 ( 
      echo Administrator privileges are required to install Wowza Streaming Engine Manager. Please retry with Administrator privileges. 
      echo InstallWSEM: no admin privileges. >> installbatch.log 
      goto :end 
      )
    6. Save the file and then double-click it to run it.

    7. Go back to the Services window and see if the Wowza Streaming Engine and Wowza Streaming Engine Manager services have been added and have been started. You may need to refresh the panel.

    Install Wowza Streaming Engine services manually on OS X


    1. Make sure the Wowza Streaming Engine and Wowza Streaming Engine Manager plist files are located in the /Library/LaunchDaemons folder. If the files are missing, copy them from [install-dir]/bin and [install-dir]/manager/bin. Make sure that file permissions are set correctly, similar to the permissions listed below:
      -rw-r--r--   1 root  wheel  1097 Apr 10 12:52 com.wowza.WowzaStreamingEngine.plist
      -rw-r--r--   1 root  wheel  1140 Apr 10 12:52 com.wowza.WowzaStreamingEngineManager.plist
    2. Open a Terminal window and run the following command:
      sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngine.plist
    3. Open a Terminal window and run the following command:
      sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaStreamingEngineManager.plist

    Install Wowza Streaming Engine services manually on Linux


    1. Make sure Wowza Streaming Engine is correctly added to your startup scripts in /etc/init.d by running the command:
      ls -la /etc/init.d | grep Wowza
      You should see output similar to:
      lrwxrwxrwx 1 root root 56 Apr 9 17:19 WowzaStreamingEngine -> /usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine 
      lrwxrwxrwx 1 root root 71 Apr 9 17:19 WowzaStreamingEngineManager -> /usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager
    2. If you don't see these links, add them manually as a service on default run levels by running the following commands:
      ln -s /usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine /etc/init.d/WowzaStreamingEngine 
      ln -s /usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager /etc/init.d/WowzaStreamingEngineManager 
      update-rc.d WowzaStreamingEngine defaults 
      update-rc.d WowzaStreamingEngineManager defaults
      Note: Depending on your Linux distribution, the commands may be different. See your Linux documentation on how to add symbolic links and startup services.

    Troubleshoot startup problems


    If the Wowza Streaming Engine installer appeared to complete successfully but you can't start or use the Wowza Streaming Engine software, try these steps to resolve the issue.

    Confirm that the install directory is present

    The default install directories are:

    • Windows - /Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.x.x/

    • OS X -
      • /Applications/Wowza Streaming Engine 4.x.x/
      • /Library/LaunchDaemons/
      • /Library/WowzaStreamingEngine/ (an alias)
      • /Library/WowzaStreamingEngine-4.x.x/

    • Linux - /usr/local/WowzaStreamingEngine-4.x.x/, as the root user

    If any of the install directories is missing, run the installer again. See How to install and configure Wowza Streaming Engine.

    Confirm that the install directory contains required folders

    Make sure the install directory contains the following folders: applications, bin, conf, lib, lib-native, logs, manager, stats, transcoder, and updates. There may be other folders, but these folders must be present in order for Wowza Streaming Engine software to run. If any of these folders is missing, run the installer again.

    See if the services are running

    By default, the Wowza Streaming Engine installer configures its required services to start automatically. If something happened to those settings, the software won't start and you won't be able to sign in to the Wowza Streaming Engine Manager. So check to see if the services are running and start them if they're not.

    Check services on Windows


    1. Press Win + R.

    2. In the Run dialog box, type services.msc and then click OK.

    3. In the Services window, see if Wowza Streaming Engine 4.x.x and Wowza Streaming Engine Manager 4.x.x show a status of Running and a Startup Type of Automatic (Delayed Start) or Automatic.

    4. If either status is blank, right-click the service and select Start.

      Tip: If the Startup Type is Manual, change it to Automatic by right-clicking the service and selecting Properties. On the General tab of the Properties window, select Automatic for the Startup Type.

    Check services on OS X


    1. Open a Terminal window and enter the following command:
      ps -ax | grep Wowza
      The command should return output similar to:
      2843 ??         0:00.01 /bin/bash /Library/WowzaStreamingEngine/bin/WowzaStreamingEngineOSX
      2846 ??         0:00.01 /bin/bash /Library/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManagerOSX
      2847 ??         0:00.02 /bin/sh /Library/WowzaStreamingEngine/bin/startup.sh service
      2849 ??         0:00.01 /bin/bash /Library/WowzaStreamingEngine/manager/bin/startmgr.sh service
      2856 ??         0:51.07 /usr/bin/java -Dcom.wowza.wms.ConfigURL="" -Dcom.wowza.wms.ConfigHome=/Library/WowzaStreamingEngine/manager -Djava.io.tmpdir=/Library/WowzaStreamingEngine/manager/temp -Dlog4j.configuration=file:///Library/WowzaStreamingEngine/manager/conf/winstone.properties -Djava.net.preferIPv4Stack=true -jar /Library/WowzaStreamingEngine/manager/lib/wms-winstone-1.0.5-boot.jar --prefix=/enginemanager --defaultWebApp=/enginemanager --tempDirectory=/Library/WowzaStreamingEngine/manager/temp --webroot=/Library/WowzaStreamingEngine/manager/temp --warfile=/Library/WowzaStreamingEngine/manager/lib/WMSManager.war --httpPort=8088 --ajp13Port=-1 --directoryListings=false
      2858 ??         0:58.46 /usr/bin/java -Xmx1638M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:NewSize=128m -server -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote=true -Dcom.wowza.wms.runmode=service -Dcom.wowza.wms.native.base=osx -Dcom.wowza.wms.AppHome=/Library/WowzaStreamingEngine -Dcom.wowza.wms.ConfigURL= -Dcom.wowza.wms.ConfigHome=/Library/WowzaStreamingEngine -cp /Library/WowzaStreamingEngine/bin/wms-bootstrap.jar com.wowza.wms.bootstrap.Bootstrap start
    2. If you don't see a process for WowzaStreamingEngineOSX or WowzaStreamingEngineManagerOSX, start it by double-clicking the Start Services application in /Applications/WowzaStreamingEngine-4.2.0.

    Check services on Linux


    Note: Wowza Streaming Engine services fail to start automatically on Ubuntu server software release 15.04, so you will have to start them manually.
    1. 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 you're running Wowza Streaming Engine as a service and it 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.

    Troubleshoot licensing errors

    Licensing errors can prevent Wowza Streaming Engine software from starting. Take the following steps to troubleshoot problems related to licensing.

    1. Make sure your license key file, Server.license, is in the [install-dir]/conf folder.

    2. Make sure Server.license doesn't have a file name extension such as .txt or .rtf.

    3. Open the Server.license file and verify that it contains the correct license key, and that the key is on a line by itself.

    4. Open the Server.license file and verify that it doesn't contain expired license keys or license keys for previous versions of Wowza Streaming Engine software. License keys for Wowza Streaming Engine version 4 have the number 4 in the prefix (for example, ENGM4, EPBP4, EPBU4, or ENGP4).

    5. Verify that your server can access Wowza licensing servers. If you have proxy servers, see How to configure Wowza media server to use proxy server to communicate with license server.

    6. Wowza Streaming Engine periodically tries to connect to the Wowza license servers when it starts. If your license is invalid or your Wowza Streaming Engine server software isn't connected to the Internet, you'll encounter an error. For more information on fixing these types of errors, see Troubleshoot Wowza Streaming Engine licensing errors at startup.

    Troubleshoot network errors

    If you can't sign in to the Wowza Streaming Engine Manager or you can't stream, it may mean that your ports are configured incorrectly. Make sure that you have the appropriate ports open to access the Wowza Streaming Engine and Wowza Streaming Engine Manager services, and that HTTP requests are being routed correctly through these ports.

    The default ports are:

    PORT TYPE DESCRIPTION
    1935 TCP RTMP (all variants), RTSP, Microsoft Smooth Streaming, Apple HLS, MPEG-DASH, HDS, WOWZ™
    6970-9999 UDP Incoming RTP UDP streaming
    8084-8085 TCP JMX/JConsole monitoring and administration
    8086-8087 TCP HTTP administration
    8088 TCP Wowza Streaming Engine Manager
    554 (optional) TCP RTSP
    443 (optional) TCP SSL connections
    80 TCP Licensing server connections

    1. Check that Wowza Streaming Engine services are listening on the ports that you have specified.

      Check listening ports on Windows


      • Open a Command prompt window and run the command:
        netstat -an | findstr "1935 8088"
        You should see output similar to the following:
        TCP    0.0.0.0:1935           0.0.0.0:0              LISTENING
        TCP    0.0.0.0:8088           0.0.0.0:0              LISTENING

      Check listening ports on OS X and Linux


      • Open a Terminal window and enter the command:
        netstat -an | grep '1935|8088'
        You should see output similar to the following:
        tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 
        tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN

      If the appropriate ports aren't open, check your server's firewall configuration to make sure it isn't blocking them.

      Check firewall configuration on Windows


      • Open Windows Firewall with Advanced Security and check the policies.

      Check firewall configuration on OS X


      • Open Security in System Preferences and check the policies.

      Check firewall configuration on Linux


      • Run the iptables command and check the policies.

    2. If you're trying to access Wowza Streaming Engine on a different network, check to make sure that the specified ports are open on the server's public IP address or public domain host name. You can check the ports by using a network sniffer program such as Wireshark.

    3. Make sure you've configured any port forwarding or NAT rules correctly on your router or switch. You can check port forwarding and NAT rules by using a network sniffer program such as Wireshark.

    If you need to block specific ports, you may have to change the port you're using for Wowza Streaming Engine Manager or for streaming. See How to get started as a Wowza Streaming Engine Manager administrator for instructions on how to change the streaming port. See How to modify the Wowza Streaming Engine Manager bind port for instructions on how to change the Wowza Streaming Engine Manager port.

    If you need to limit access to Wowza Streaming Engine Manager through a specific IP address/network card for network security purposes, you can change the IP address that Wowza Streaming Engine Manager listens on:

    1. Navigate to and open one of the following files:

      OS X or Linux - [install-dir]/manager/bin/startmgr.sh

      Windows - [install-dir]/manager/bin/startmgr.bat

    2. Look for the following line:
      "%_EXECJAVA%" %JAVA_OPTS% -jar "%WMSMGR_HOME%libwms-winstone-1.0.5-boot.jar" --prefix="/enginemanager" --defaultWebApp="/enginemanager" --tempDirectory="%WMSMGR_HOME%	emp" --webroot="%WMSMGR_HOME%	emp" --warfile="%WMSMGR_HOME%libWMSManager.war" --httpPort=8088 --ajp13Port=-1 --directoryListings=false
    3. Before the --httpPort=8088 parameter, add the parameter --httpListenAddress=[local-ip-address].

    Manually start Wowza Streaming Engine in standalone mode

    If you can't get Wowza Streaming Engine to run as a service, you can start it in standalone mode. For instructions on how to start Wowza Streaming Engine and Wowza Streaming Engine Manager in standalone mode, see How to start and stop Wowza Streaming Engine software.

    If you start in standalone mode using the Command Prompt or Terminal window, you'll know the software is working if you see output similar to the following:
    Configure logging: file:///C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.x.x/conf/log4j.properties
    INFO server server-start Wowza Streaming Engine 4 Monthly Edition 4.x.x buildxxxx -
    INFO server comment - Server License Key: 
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Maximum Incoming Streams: Unlimited
    INFO server comment - Transcoder Streams Available: Unlimited
    INFO server comment - Transcoder Watermark: No
    INFO server comment - nDVR Available: Yes
    INFO server comment - DRM Available: Yes
    INFO server comment - HTTP Origin Available: Yes
    INFO server comment - Push Publish Available: Yes
    INFO server comment - REST API Available: No
    INFO server comment - Hardware Available Processors: 4
    INFO server comment - Hardware Physical Memory: 2650MB/8069MB
    INFO server comment - Hardware Swap Space: 2584MB/9349MB
    INFO server comment - Max File Descriptor Count: Unlimited
    INFO server comment - OS Name: Windows 8.1
    INFO server comment - OS Version: 6.3
    INFO server comment - OS Architecture: amd64
    INFO server comment - OS CPU: amd64
    INFO server comment - Java Name: Java HotSpot(TM) 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.8.0_25
    INFO server comment - Java VM Version: 25.25-b02
    INFO server comment - Java Spec Version: 1.8
    INFO server comment - Java Home: C:\Program Files\Java\jdk1.8.0_25\jre
    INFO server comment - Java Max Heap Size: 3194MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Locale[user.language]: en
    INFO server comment - Java Locale[user.country]: US
    INFO server comment - Java Locale[user.variant]:
    INFO server comment - Java Locale[file.encoding]: Cp1252
    INFO server comment - Java Timezone[user.timezone]: America/
    INFO server comment - Java Args[0]: -Xmx3227M
    INFO server comment - Java Args[1]: -XX:+UseConcMarkSweepGC
    INFO server comment - Java Args[2]: -XX:+UseParNewGC
    INFO server comment - Java Args[3]: -XX:NewSize=256m
    INFO server comment - Java Args[4]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[5]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.native.base=win
    INFO server comment - Java Args[8]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: win
    INFO server comment - Server threads[h/t]: 240/160
    INFO server comment - RESTServer: Bind attempt ([any]:8087)
    INFO server comment - RESTServer: Bind successful ([any]:8087)
    INFO server comment - Wowza REST API started
    INFO server comment - RESTServer: Using configs from:C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.1.2/
    INFO server comment - RESTServer: SSL:No
    INFO server comment - RESTServer: BasicAuth:No
    INFO server comment - RESTServer: Digest:Yes
    INFO server comment - RESTServer: XML Viewer:No
    INFO server comment - RESTDocumentationServer: Bind attempt ([any]:8089)
    INFO server comment - RESTDocumentationServer: Bind successful ([any]:8089)
    INFO server comment - Wowza REST Documentation Server started
    INFO server comment - RESTDocumentationServer: Using configs from:C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.1.2/
    INFO server comment - RESTDocumentationServer: BasicAuth:No
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO server comment - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:8/4
    INFO server comment - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:500M/25M
    INFO server comment - MediaCache[MediaCache]: Add store: path:C:/Program Files (x86)/Wowza Media Systems/Wowza Streaming Engine 4.1.2/mediacache maxSize:10737418240
    INFO server comment - REST API: ready
    INFO server comment - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:https://
    INFO server comment - MediaCache[MediaCache]: Add source[amazons3]:prefix:amazons3/basePath:https://s3.amazonaws.com/
    INFO server comment - MediaCache[MediaCache]: Flushing cache: start
    INFO server comment - MediaCache[MediaCache]: Flushing cache: done
    INFO server comment - MediaCache[MediaCache]: Start MediaCache GC
    INFO server comment - MediaCache[MediaCache]: Started
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:0/0 home:C:/Program Files (x86)/Wowza Media Systems/WowzaStreaming Engine 4.1.2
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:8)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - VHost.loadConfig: Local XML override: HTTPStreamers.xml
    INFO server comment - VHost.loadConfig: Local XML override: LiveStreamPacketizers.xml
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - StatsManager:startManager() Enabled=true
    INFO server comment - Wowza Streaming Engine is started!
    If you encounter errors when you start in standalone mode, Submit a Wowza Streaming Engine Technical Support Ticket. (Technical support is included with all active monthly subscriptions and maintenance and support contracts.) Copy the error messages and include them in your detailed problem description in the support ticket form.

    Note: You can't run in both services and standalone modes. Make sure Wowza Streaming Engine isn't running as a service before you start in standalone mode.

    More resources



    Originally Published: 09-16-2015.
    Updated: 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.