Results 1 to 9 of 9

Thread: Unexpected Wowza service shutdown

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Jan 2013
    Posts
    12

    Unhappy Unexpected Wowza service shutdown

    Hi,

    We have a 4GB RAM wowza server setup subscribed to daily license that is used mainly for customer's streaming testing.
    A customer with low-latency profile has been streaming it for a number of days on this server.
    During their streaming, we also have customer with low-latency profile and transcoder ON, occasionally used it for streaming event.

    However, we found this afternoon that the wowza service was already stop unexpectedly.
    Looking at the last executed stream in wowza access log:

    2013-03-09 06:33:51 SGT disconnect cupertino INFO 200 912932360 - _defaultVHost_ cust _definst_ 240840.759 x.x.x.x 1935 http://x.x.x.x:1935/cust/streamtest/playlist.m3u8 203.184.213.150 http (cupertino) - Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A403 Safari/8536.25 912932360 0 841329 - 431772726 - - streamtest - - - - - http://x.x.x.x:1935/cust/streamtest/playlist.m3u8 http://x.x.x.x:1935/cust/streamtest/playlist.m3u8 - http://x.x.x.x:1935/cust/streamtest/playlist.m3u8 -
    2013-03-09 07:33:52 SGT comment server INFO 200 - HTTPStreamerSessions.checkHTTPOriginTimeout[_defaultVHost_:cust/_definst_/streamtest[cupertinostreaming]:912932360]: shutdown - - - 244452.727 - - - - - - - - -- - - - - - - - - - - - - - -


    # head wowzamediaserver_access.log.2013-03-10
    #Version: 1.0
    #Start-Date: 2013-03-10 03:37:04 SGT
    #Software: Wowza Media Server 3.5.0 build2989
    #Date: 2013-03-10
    #Fields: date time tz x-event x-category x-severity x-status x-ctx x-comment x-vhost x-app x-appinst x-duration s-ip s-port s-uri c-ip c-proto c-referrer c-user-agent c-client-id cs-bytes sc-bytes x-stream-id x-spos cs-stream-bytes sc-stream-bytesx-sname x-sname-query x-file-name x-file-ext x-file-size x-file-length x-suri x-suri-stem x-suri-query cs-uri-stem cs-uri-query
    2013-03-10 03:37:04 SGT comment server INFO 200 - ServerShutdownHook.run[shutdown] - - - 316645.1 - -- - - - - - - - - - - - - - - - - - - - - --
    2013-03-10 03:37:04 SGT unpublish stream INFO 200 streamtest - _defaultVHost_ cust _definst_ 316634.128 [any] 80 rtmp://x.x.x.x:80/cust x.x.x.x rtmp rtmp://x.x.x.x:80/cust FMLE/3.0 (compatible; FMSc/1.0) 1279557473 12045556380 311928 1 0 12002947763 0 streamtest videoKeyframeFrequency=1&totalDatarate=300 - - -- rtmp://x.x.x.x:80/cust/streamtst?videoKeyframeFrequency=1&totalDatarate=300 rtmp://x.x.x.x:80/cust/streamtest videoKeyframeFrequency=1&totalDatarate=300 rtmp://x.x.x.x:80/cust -


    There's no exception error message on the wowza error log thou.


    Do you have any idea what could possibly trigger this unexpected shutdown ?
    Can long period of streaming trigger unexpected shutdown ?

    Thanks!

  2. #2
    Join Date
    Sep 2011
    Posts
    1,934

    Default

    Hi
    There is no reason that Wowza would shutdown unexpectedly.
    Make sure that the server is tuned and that no management software is shutting down Wowza.

    The tuning guide can be found here is needed,
    http://www.wowza.com/forums/content....ormance-tuning

    Jason

  3. #3
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    There is nothing in the log showing Wowza shutdown. There may have been a network issue, so that you were not able to reach Wowza.

    Richard

  4. #4
    Join Date
    Jan 2013
    Posts
    12

    Default

    Thanks!

    Does it mean when there's the 'network issue', Wowza service will automatically shutdown itself?
    As shown in the log excerpt above, a ServerShutdownHook() was triggered at about 3.37am .. this was the same time where the other logs in the server are rotated.
    We had to start the Wowza service again the same day when we attempt to do another round of testing.


    Quote Originally Posted by rrlanham View Post
    There is nothing in the log showing Wowza shutdown. There may have been a network issue, so that you were not able to reach Wowza.

    Richard

  5. #5
    Join Date
    Jan 2013
    Posts
    12

    Default

    Hi Richard,

    We just had another unexpected service shutdown yesterday afternoon just after a couple of transcoding sessions ended.
    A crash log was located in /usr/local/WowzaMediaServer/bin:

    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    # SIGSEGV (0xb) at pc=0x00007ffc7856cb27, pid=27888, tid=140722399913728
    #
    # JRE version: 7.0_09-b05
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode linux-amd64 compressed oops)
    # Problematic frame:
    # C [libmc_enc_avc.so+0x202b27] h264OutVideoGetAPIExt+0x1d1d97
    #
    # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
    #
    # If you would like to submit a bug report, please visit:
    # http://bugreport.sun.com/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #
    VM Arguments:
    jvm_args: -Xmx3000M -XX:+UseConcMarkSweepGC -XX:+UseLargePages -XX:+UseParNewGC -XX:NewSize=256m -verbose:gc -Xloggc:/usr/local/WowzaMediaServer/logs/gc_2013-03-15-14-16.log -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -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/WowzaMediaServer -Dcom.wowza.wms.ConfigURL= -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    java_command: com.wowza.wms.bootstrap.Bootstrap start
    Launcher Type: SUN_STANDARD



    Any idea what could have lead to this ?

    Thanks.


    Quote Originally Posted by rrlanham View Post
    There is nothing in the log showing Wowza shutdown. There may have been a network issue, so that you were not able to reach Wowza.

    Richard

  6. #6
    Join Date
    Jan 2013
    Posts
    12

    Default

    Hi,

    I just found that there's an identical issue possible caused by the Mainconcept thingy in the following thread:
    http://www.wowza.com/forums/showthread.php?16636-Transcoder-Crashes-Server


    May I know whether the patch WowzaMediaServer3.0.3-patch14 is compatible with Wowza Media Server 3 Daily Edition 3.5.0 build2989 ?

  7. #7
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    The patches are cumulative, so this would be the patch to apply:
    http://www.wowza.com/downloads/Wowza....x.x-3.5.2.zip

    While you are at it, you might as well apply the latest dev patch on top of the above:
    http://www.wowza.com/forums/content....lopment-Builds

    Remember to backup conf files, and remake as necessary using the new configuration files. Don't copy old files.

    Richard

  8. #8
    Join Date
    Jan 2013
    Posts
    12

    Default

    Thanks Jason.
    The server has been tuned previously with the guide provided.

    Quote Originally Posted by JasonH View Post
    Hi
    There is no reason that Wowza would shutdown unexpectedly.
    Make sure that the server is tuned and that no management software is shutting down Wowza.

    The tuning guide can be found here is needed,
    http://www.wowza.com/forums/content....ormance-tuning

    Jason

Similar Threads

  1. Wowza server unexpected shutdown
    By alexitekako in forum General Forum
    Replies: 1
    Last Post: 03-14-2012, 05:50 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
  •