Important general issues that affect Wowza Streaming Engine software

This article describes important issues that may affect your deployment and management of Wowza Streaming Engine™ media server software. If available, workarounds for these issues are described. Check back often as this article will be updated as new developments occur.
 

Note: Where a third-party issue affects Wowza Streaming Engine software, it's the responsibility of the third-party to fix the problem. Wowza Media Systems works with these companies to help address the issue as soon as possible.

Contents


General known issues in Wowza Streaming Engine
Windows 10 may not start Wowza Streaming Engine services (Services error -1073741502)
Incorrect Wowza CPU statistics in Wowza Streaming Engine Manager (cloud deployments)
SHOUTCast and Icecast stream targets don't work (Wowza Streaming Engine 4.5.0)
Misleading message when uninstalling Wowza Streaming Engine updaters (Wowza Streaming Engine 4.3.0 and later)
Startup delays and hostname resolution problems on Azure Marketplace virtual machines
Wowza Streaming Engine services don't start automatically on the latest Ubuntu 15.04
Antivirus tools falsely detect Luhe.Fiha.AN threat
Latest Linux updates prevent Wowza Streaming Engine from starting (init.d or systemd)
Issues with Java version 8u78 and greater
Custom properties with leading and trailing blank spaces
Updating to Wowza Streaming Engine 4.7.0 breaks existing configurations for HTTPS Manager connections
More resources

General known issues in Wowza Streaming Engine


Windows 10 may not start Wowza Streaming Engine services (Services error -1073741502)

The NSSM service manager can't open a console window when trying to start Wowza Streaming Engine services. This error may appear after a recent Windows 10 update.

Solution

Update your Wowza Streaming Engine installation to Wowza Streaming Engine 4.7.0. If you can't or don't want to update your media server software, do the following:

  1. Open an elevated Command Prompt window (press the Windows Logo+X keys, and then click Command Prompt (Admin) on the power user menu).
  2. In the Command Prompt window, navigate to a Wowza Streaming Engine installation bin folder that has an NSSM EXE file installed. There are two possible locations: [install-dir]/bin and [install-dir]/manager/bin.
  3. Run the following commands:
    nssm set [wowza-streaming-engine-service-name] AppNoConsole 1
    nssm set [wowza-streaming-engine-manager-service-name] AppNoConsole 1

You must use properly formatted service names in these commands. To get the service names, open the Services control panel (press the Windows Logo+R keys, and then type services.msc in the Run dialog box), right-click the Wowza Streaming Engine and Wowza Streaming Engine Manager services in the list, and then click Properties. The service name to use will be highlighted on the General tab in the Properties dialog box.

Example commands for Wowza Streaming Engine 4.6.0

nssm set WowzaStreamingEngine460 AppNoConsole 1
nssm set WowzaStreamingEngineManager460 AppNoConsole 1

Incorrect Wowza CPU statistics in Wowza Streaming Engine Manager (cloud deployments)

Note: Wowza Streaming Engine 4.7.0 and later includes Wowza CPU calculation improvements to address this issue. Get the latest Wowza Streaming Engine software.
If you deploy Wowza Streaming Engine media server software in the cloud, and then log into the web-based Wowza Streaming Engine Manager on the cloud-hosted virtual machine, the Usage graph in the manager may display a higher Wowza CPU value than the actual media server CPU usage. Refreshing the manager webpage may boost the Wowza CPU graph so that it's even more out-of-sync from actual CPU consumption.

Solution

To view Wowza CPU consumption:
 
  • Windows - Look at the running Java.exe processes in Windows Task Manager (be sure to Show processes from all users).
     
  • Linux - Run the following grep command to display running Java processes and filters for Java processes:
    PS - ef  | grep java*
    Then, to see the CPU usage for a particular Java process, run the top command using the Java process identifier (PID).

SHOUTCast and Icecast stream targets don't work (Wowza Streaming Engine 4.5.0)

Wowza Streaming Engine 4.5.0 software has an error that prevents the SHOUTcast and Icecast stream targets from working.

Solution

Install the latest updater for Wowza Streaming Engine software, which has a fix for this issue.

Misleading message when uninstalling Wowza Streaming Engine updaters (Wowza Streaming Engine 4.3.0 and later)

After you uninstall updater versions 4.3.0, 4.3.0.01, 4.3.0.02, 4.3.003, 4.4.0, 4.4.0.01, and 4.4.1, you may see a message that indicates your updater uninstall may have failed:
A required action of the update failed. The update did not complete successfully, see the wowzastreamingengine_update.log for details.

Solution

This message can be misleading. Check for the following message. If it's present, your updater uninstall completed successfully:
Restoration complete

Startup delays and hostname resolution problems on Azure Marketplace virtual machines

When running Wowza Streaming Engine virtual machines on Azure Marketplace, the Wowza Streaming Engine software may start after some delay. After startup, Wowza Streaming Engine Manager may display the virtual machine's private IP address, instead of the public IP address, on the Home, Sources (Live), and Test Players pages. These problems are caused by the way in which Azure Marketplace processes variable lookup metadata.

Solution

Future Azure Marketplace releases may optimize how variable lookup metadata is reported in the Azure platform. To permanently display the public IP address in Wowza Streaming Engine Manager, do the following:
 
  1. Connect to your virtual machine (Windows connection instructions | Linux connection instructions).
     
  2. Open the [install-dir]/conf/VHost.xml] file in a text editor and replace the <Manager>/<TestPlayer>/<IpAddress> value (${com.wowza.cloud.platform.PLATFORM_METADATA_EXTERNAL_IP}) with your virtual machine's public IP address:
    <Manager>
    	<TestPlayer>
    		<IpAddress>[wowza-vm-public-ip-address]</IpAddress> <!--changed for default cloud install. -->
    		<Port>${com.wowza.wms.HostPort.FirstStreamingPort}</Port>
    		<SSLEnable>${com.wowza.wms.HostPort.SSLEnable}</SSLEnable>
    	</TestPlayer>
    	<!-- Properties defined are used by the Manager -->
    	<Properties>
    	</Properties>
    </Manager>
  3. If you were signed in to Wowza Streaming Engine Manager, sign out, and then sign in again.
The Home, Sources (Live), and Test Players pages in the manager should display the virtual machine's public IP address.

Wowza Streaming Engine services don't start automatically on the latest Ubuntu 15.04

Wowza Streaming Engine services on the current Ubuntu server software release (15.04) fail as part of the installation and don't start automatically. This appears to be related to the recent move by Ubuntu from upstart to systemd (see SystemdForUpstartUsers).

Solution

Do ONE of the following:

Start Wowza Streaming Engine manually by running the following as root:
# /etc/init.d/WowzaStreamingEngine start

# /etc/init.d/WowzaStreamingEngineManager start
-OR-

Reinstall the missing upstart functionality, which should ensure that Wowza Streaming Engine services are restarted on reboots:
# apt-get install upstart-sysv

Latest Linux updates prevent Wowza Streaming Engine from starting (init.d or systemd)

Wowza Streaming Engine services fail to start--either as legacy init.d scripts or as systemd services--after Linux is updated. We've observed this with Centos 7.2 updates.

Solution

Create the following service files:

/usr/lib/systemd/system/WowzaStreamingEngine.service
[Unit]
Description=WowzaStreamingEngine
After=syslog.target
After=network.target
After=local-fs.target
After=remote-fs.target

[Service]
Type=simple
User=root
Group=root
ExecStart=/usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine start
ExecStop=/usr/local/WowzaStreamingEngine/bin/WowzaStreamingEngine start
RemainAfterExit=yes

# Give a reasonable amount of time for the server to start up/shut down
TimeoutSec=300

[Install]
WantedBy=multi-user.target
/usr/lib/systemd/system/WowzaStreamingEngineManager.service
[Unit]
Description=WowzaStreamingEngineManager
After=syslog.target
After=network.target
After=local-fs.target
After=remote-fs.target

[Service]
Type=simple
User=root
Group=root
ExecStart=/usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager start
ExecStop=/usr/local/WowzaStreamingEngine/manager/bin/WowzaStreamingEngineManager start
RemainAfterExit=yes

# Give a reasonable amount of time for the server to start up/shut down
TimeoutSec=300

[Install]
WantedBy=multi-user.target
Enable services
systemctl daemon-reload
systemctl enable WowzaStreamingEngine.service
systemctl enable WowzaStreamingEngineManager.service
Start new services
systemctl start WowzaStreamingEngine.service
systemctl start WowzaStreamingEngineManager.service

Antivirus tools falsely detect Luhe.Fiha.AN threat

Some antivirus tools report "Found Luhe.Fiha.AN" in Windows Installer (.msi) files for Wowza Media Server 3 and Wowza Streaming Engine software.

Solution

We believe this to be a false positive. Customers haven't reported any problems.

Issues with Java version 8u78 and greater

If you use your own Java Runtime Environment (JRE) with Wowza Streaming Engine (8u78 and greater), you may not be able to start Wowza Streaming Engine Manager.

You may also encounter an instability issue related to Java settings and see an error message similar to the following:

500 error is thrown: "Sorry there was an error getting to (server/performance/javasettings/edit.htm):
Internal Server Error:500"

Solution

If you use your own JRE, you can install an earlier JRE version that doesn't have these issues (see How to manually install and troubleshoot Java on your Wowza media server) or you can run the latest Wowza Streaming Engine installer, which has an earlier version of the JRE. We'll monitor the Java updates and update this article with the latest findings.

Custom properties with leading and trailing blank spaces

If you use a text editor to add properties to Wowza Streaming Engine XML configuration files, you can't edit the property in Wowza Streaming Engine Manager if the property name or value has a leading (or trailing) blank space. For example, if you add the following property that has leading blank space in its name to an XML file:
<Property>
	<Name>  myCustomProperty</Name>
	<Value>12345</Value>
	<Type>String</Type>
</Property>
When Wowza Streaming Engine Manager starts, it will load the XML file, and then remove the leading blank space from the property name that it displays in its user interface. (It does this because leading and trailing blank spaces are a common source of configuration errors.) For the example property above, the manager will display this as myCustomProperty in its UI.

If you try to edit myCustomProperty in the manager, the property will be saved as a new property to the XML file.
<Property>
	<Name>  myCustomProperty</Name>
	<Value>12345</Value>
	<Type>String</Type>
</Property>
<Property>
	<Name>myCustomProperty</Name>
	<Value>67890</Value>
	<Type>String</Type>
</Property>

Solution

If your media server configuration requires a property with a leading or trailing blank space in its name or value, you must always edit this property in the configuration XML file using a text editor.

Updating to Wowza Streaming Engine 4.7.0 breaks existing configurations for HTTPS Manager connections

Updating to Wowza Streaming Engine 4.7.0 overwrites the startmgr.bat (Windows) or startmgr.sh (Linux) file. This means that if you have configured Wowza Streaming Engine Manager to use a secure socket layer (SSL) certificate so that you can connect using HTTPS, that configuration is lost during the update.

Solution

After you have successfully updated to Wowza Streaming Engine 4.7.0, follow the instructions in How to connect to Wowza Streaming Engine Manager over HTTPS to reconfigure HTTPS connections.

More resources