Results 1 to 10 of 10

Thread: Auto Restart Stream Targets

  1. #1
    Join Date
    Jul 2015
    Posts
    18

    Question Auto Restart Stream Targets

    Hello,

    We have a stream target configured and upon restart (whether crash recovery or scheduled restart), the stream target is in a 'Waiting...' state and needs to be edited, re-saved and then the state shows as 'Active.'

    Is this an issue with the sending Wowza server or the receiving server? The receiving server is also Wowza configured as a repeater, however we do not control it.

    Thank you.

    Jorge

  2. #2
    Join Date
    Jun 2012
    Posts
    722

    Default

    Hi,

    This is not a normal behavior for the Stream Targets feature. Can you specify which Wowza Streaming Engine version are you currently running?
    We always suggest users to update their server installation to the latest Wowza version (currently at 4.2.0) so that you could benefit from the server fixes that were released in the meantime.

    Zoran

  3. #3
    Join Date
    Jul 2015
    Posts
    18

    Default

    Quote Originally Posted by zoran_u View Post
    Hi,

    This is not a normal behavior for the Stream Targets feature. Can you specify which Wowza Streaming Engine version are you currently running?
    We always suggest users to update their server installation to the latest Wowza version (currently at 4.2.0) so that you could benefit from the server fixes that were released in the meantime.

    Zoran
    Zoran,

    Here is our current version:

    Engine Version
    4.2.0.01 (build 15394)
    Engine Manager Version
    4.2.0.01 (build 15394)

    We updated recently in order to be able to configure Stream Targets through the gui rather than the backend.

    Please advise.

    Jorge

  4. #4
    Join Date
    Jul 2015
    Posts
    18

    Default

    Zoran,

    This entry appears in the Streaming Engine Server error logs and corresponds to when we restarted the server this morning.

    ServerUtils.loadServerListener: Error creating (com.wowza.wms.plugin.collection.serverlistener.ServerListenerStreamPublisher) : java.lang.ClassNotFoundException: com.wowza.wms.plugin.collection.serverlistener.ServerListenerStreamPublisher|at java.net.URLClassLoader$1.run(URLClassLoader.java:202)|at java.security.AccessController.doPrivileged(Native Method)|at java.net.URLClassLoader.findClass(URLClassLoader.java:190)|at java.lang.ClassLoader.loadClass(ClassLoader.java:306)|at java.lang.ClassLoader.loadClass(ClassLoader.java:247)|

    Jorge

  5. #5
    Join Date
    Jun 2012
    Posts
    722

    Default

    Hello,

    Are you generating live stream using scheduled playlists? The StreamPublisher is used when using video on demand playlists to be delivered as a live stream according to a schedule.
    Have you configured Stream Targets to push those generated live stream to an alternate server/CDN?

    Zoran

  6. #6
    Join Date
    Jul 2015
    Posts
    18

    Default

    Quote Originally Posted by zoran_u View Post
    Hello,

    Are you generating live stream using scheduled playlists? The StreamPublisher is used when using video on demand playlists to be delivered as a live stream according to a schedule.
    Have you configured Stream Targets to push those generated live stream to an alternate server/CDN?

    Zoran
    Zoran,

    This was from a previous support request with Wowza. They had us test with scheduled playlists but it turns out it was another issue.

    The current feed is taken live via incoming RTMP and that is configured in Stream Targets to push to the server downstream.

    The 'Waiting...' problem still persists whenever we restart Wowza.

    Jorge

  7. #7
    Join Date
    Jun 2012
    Posts
    722

    Default

    Hi,

    When you restart your Wowza server, the incoming RTMP stream is also dropped. Can you confirm that the Stream Targets "Waiting..." status is also maintend after the incoming RTMP stream is re-published?
    Can you check your "Incoming streams" page and see if that particular RTMP incoming streams is actually published on your server after the Wowza restart?

    Zoran

  8. #8
    Join Date
    Jul 2015
    Posts
    18

    Default

    Zoran,

    I can see the incoming stream is republished because the bytes in/out on the monitoring page reflects that and the Incoming Streams page shows 'Active' but the Stream Targets page still shows 'Waiting...'

    Jorge

  9. #9
    Join Date
    Jun 2012
    Posts
    722

    Default

    Hi,

    Can you open a support ticket by writing an email to support@wowza.com and describe the issue you are facing.
    Also please send copy of the following folders as a .zip (or other archive):
    [wowza-install-dir]/conf
    [wowza-install-dir]/logs
    [wowza-install-dir]/transcoder
    [wowza-install-dir]/manager/logs

    I would need to take closer look at your configuration and log files and see what else might be happening that is causing this behavior.

    Zoran

  10. #10
    Join Date
    Jul 2015
    Posts
    18

    Default

    Zoran,

    WIll be opening a support ticket shortly and sending the logs. We needed to restart our server again and the same issue is occuring -- stream targets require manual intervention to reconnect.

    Jorge

Similar Threads

  1. REST API or Java call to Disable/Enable Stream Targets
    By mtownsend in forum Wowza Streaming Engine REST API
    Replies: 2
    Last Post: 07-30-2015, 11:05 AM
  2. Updated to 4.2, Stream Targets link not found
    By colin_witt in forum General Forum
    Replies: 2
    Last Post: 07-08-2015, 04:53 AM
  3. Restream won't auto start on server restart
    By Christer in forum Live Streaming and Encoders
    Replies: 6
    Last Post: 06-24-2014, 04:42 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •