• 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
    More resources

    General known issues in Wowza Streaming Engine


    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.

    Failure when deploying Streaming Engine image on Azure Marketplace (Linux)

    Currently, the Azure Dashboard displays a Deployment failed error due to a problem with the Microsoft.Insights.VMDiagnosticsSettings Azure Linux virtual machine agent (VM agent). This error only prevents your virtual machine's Monitoring feature from displaying data, as well as custom logging and reporting. Your virtual machine will deploy successfully but not support monitoring, custom logging and custom reporting.

    Solution

    You can update the Azure Linux VM agent to the latest version to resolve this issue for virtual machines you've already deployed on Linux. This issue will be fixed in a future Wowza Streaming Engine virtual machine update.

    File permissions are incorrectly set to the root user in Wowza Streaming Engine 4.2.0 AMIs

    When using Secure Shell (SSH) to login to your Wowza Streaming Engine 4.2.0 for Amazon EC2 instance, you must login with the user name root (instead of the user name ec2-user) in the SSH client window. If you login with the user name ec2-user, you won't be able to access files in the installation or perform other operations, such as FTP to upload files to the content folder.

    Solution


    This issue is fixed in our latest Wowza Streaming Engine for Amazon EC2 AMIs.

    If you you use Wowza Streaming Engine 4.2.0 AMIs, you can customize your Streaming Engine installation without logging in via SSH by using a startup package. For more information, see Wowza Streaming Engine Configuration Startup Packages in the "Wowza Streaming Engine for Amazon EC2 User's Guide."

    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.

    Java Settings instability (8u78 and greater)

    If you use your own Java Runtime Environment (JRE) with Wowza Streaming Engine, you may encounter an instability issue related to Java settings in JRE builds 8u78 and greater. You may 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 this issue (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.

    More resources



    Originally Published: For Wowza Streaming Engine on 05-20-2015.
    Updated: 08-18-2016.