Results 1 to 6 of 6

Thread: Wowza destroys livestream

  1. #1
    Join Date
    Aug 2012
    Posts
    2

    Default Wowza destroys livestream

    Hi all
    At the start I want to sorry for my english.

    I have problem with my wowza when i try to publish livestream (rtmp). I use example application "live", Jwplayer and Teradek Cube for streaming video.
    I start stream, everything looks ok, but when i try to play in JWplayer the stream is stoped.

    Here is console output:

    Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties
    INFO server server-start Wowza Media Server 3 Monthly Edition 3.1.2 build1624 -
    INFO server comment - Server License Key: SVRM3-XXXXX-XXXXX-XXXXX-XXXXX-Rn9Nd
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Transcoder Streams Available: Transcoder Not Available (linux-32)
    INFO server comment - nDVR Available: Yes
    INFO server comment - DRM Available: Yes
    INFO server comment - Hardware Available Processors: 4
    INFO server comment - Hardware Physical Memory: 5804MB/7982MB
    INFO server comment - Hardware Swap Space: 15999MB/15999MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 47
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 2.6.32-71.29.1.el6.i686
    INFO server comment - OS Architecture: i386
    INFO server comment - Java Name: OpenJDK Server VM
    INFO server comment - Java Vendor: Sun Microsystems Inc.
    INFO server comment - Java Version: 1.6.0_24
    INFO server comment - Java VM Version: 20.0-b12
    INFO server comment - Java Spec Version: 1.6
    INFO server comment - Java Home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre
    INFO server comment - Java Max Heap Size: 1066MB
    INFO server comment - Java Architecture: 32
    INFO server comment - Java Locale[user.language]: pl
    INFO server comment - Java Locale[user.country]: PL
    INFO server comment - Java Locale[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: Europe/Warsaw
    INFO server comment - Java Args[0]: -Xmx1200M
    INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:/usr/local/WowzaMediaServer
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - Wowza Media Server is started!
    INFO application app-start _definst_ live/_definst_
    INFO session connect-pending 78.88.168.xxx -
    INFO session connect 78.88.168.xxx -
    INFO stream create - -
    INFO stream publish livestream -
    INFO session connect-pending 78.88.168.xxx -
    INFO session connect 78.88.168.xxx -
    INFO stream create - -
    INFO stream play livestream -
    INFO stream stop livestream -
    INFO stream destroy livestream -
    INFO session disconnect 347916161 -
    INFO stream destroy livestream INFO session connect-pending 78.88.168.xxx -
    INFO session connect 78.88.168.xxx -
    INFO stream create - -
    INFO stream play livestream -
    INFO stream stop livestream -
    INFO stream destroy livestream -
    INFO session disconnect 1746515938 -
    INFO server comment - ServerShutdownHook.run[shutdown]
    INFO stream unpublish livestream -
    INFO stream destroy livestream -
    INFO session disconnect 1563913300 -
    What i have checked:
    Its not a connection problem, i tried different providers but the problem still exist, its not a Cube problem, when i use Adobe Flash Media live encoder for streaming i have the same problem.
    When i use red5 server on the same machine, everything works ok.

    Can anyone help me ?

    Thanks

  2. #2
    Join Date
    Dec 2007
    Posts
    25,859

    Default

    Zip up and send conf and logs folders to support@wowza.com.

    Is the server on a public IP?

    Include a link to this thread for reference.

    Richard

  3. #3
    Join Date
    Aug 2012
    Posts
    2

    Default

    Server is on public IP.
    I sent you logs and confs, but confs are stock.
    What i also checked - i installed another version of jre but without success.

  4. #4
    Join Date
    Nov 2012
    Posts
    3

    Default I am having exactly the same problem

    Quote Originally Posted by wiktorsam View Post
    Server is on public IP.
    I sent you logs and confs, but confs are stock.
    What i also checked - i installed another version of jre but without success.

    Hi,
    I am having exactly the same problem, Wowza destroy the stream, while Red5 works fine:

    /usr/local/WowzaMediaServer-3.1.2/bin# ./startup.sh
    Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties
    INFO server server-start Wowza Media Server 3 Monthly Edition 3.1.2 build1624 -
    INFO server comment - Server License Key: SVRM3-XXXXX-XXXXX-XXXXX-XXXXX-x6Qme
    INFO server comment - Maximum Connections: 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 - Hardware Available Processors: 8
    INFO server comment - Hardware Physical Memory: 21151MB/24164MB
    INFO server comment - Hardware Swap Space: 59999MB/59999MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 45
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 3.2.13-grsec-xxxx-grs-ipv6-64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: OpenJDK 64-Bit Server VM
    INFO server comment - Java Vendor: Sun Microsystems Inc.
    INFO server comment - Java Version: 1.6.0_24
    INFO server comment - Java VM Version: 20.0-b12
    INFO server comment - Java Spec Version: 1.6
    INFO server comment - Java Home: /usr/lib/jvm/java-6-openjdk/jre
    INFO server comment - Java Max Heap Size: 1066MB
    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[file.encoding]: UTF-8
    INFO server comment - Java Timezone[user.timezone]: Europe/Paris
    INFO server comment - Java Args[0]: -Xmx1200M
    INFO server comment - Java Args[1]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[2]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[3]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[5]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:/usr/local/WowzaMediaServer
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - Wowza Media Server is started!
    INFO application app-start _definst_ live-record/_definst_
    INFO session connect-pending xx.36.18.xxx -
    INFO session connect xx.36.18.xxx -
    INFO stream create - -
    INFO stream publish test2 -
    INFO session connect-pending xx.36.18.xxx -
    INFO session connect xx.36.18.xxx -
    INFO stream create - -
    INFO stream play test2 -
    INFO stream stop test2 -
    INFO stream destroy test2 -
    INFO session disconnect 1069489588 -


    Sometimes the stream lasts for just a few seconds, while other times it lasts for at most one or even a few minutes.
    I also tried with Oracle java 7, but it is the same problem.
    Moreover, I found the same streaming with RTMP either from ffmpeg or Wirecast.
    Finally, I have tried with different players, including the client example.

    Server is on a Public IP.

    Indeed this error is coming with a new other weird behavior. For instance, if I try to "live-record" a stream named mp4:test2, the player says that it does not find such a stream. But if I remove the "mp4:" prefix, it is able to play those few seconds.
    Also, if I stream many times with the same stream name, there is only one file in the content folder, instead of a set of files with the version suffix in their name.
    In addition, and this is very weird, even when I have stop of live streaming, the player is able to play the recorded video (showing the total length of the video and allowing to seek and pause), but I mean when it is still calling the live-record application! And it happens even when I clear cache! So it must be accessing the content folder.

    Could it happen that it is not taking the live-record application but perhaps only record? or something like that?

    Any idea?

    Thanks!
    Sergio
    Last edited by kalmatv; 11-11-2012 at 04:30 PM.

  5. #5
    Join Date
    Dec 2007
    Posts
    25,859

    Default

    The logs show a stream being published and a client playing it back. The destroy is the playback client, i.e., the outgoing stream being destroyed. The live stream is okay as far as the log snip you show, there is no unpublish and destroy.

    Perhaps it is a high bitrate and is stalling?

    Richard

  6. #6
    Join Date
    Sep 2012
    Posts
    13

    Default

    im getting the same thing but mine shows no client play and stop.

    INFO session connect 50.143.115.38 -
    INFO stream create - -
    INFO stream destroy playboy -
    INFO session disconnect 1880204240 -

    I have it working fine on a 3.1.2 install but the 3.5 update it does not work on.

Posting Permissions

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