Results 1 to 3 of 3

Thread: VM will try to fix the stack guard now - 'execstack -c <libfile>'

  1. Default VM will try to fix the stack guard now - 'execstack -c <libfile>'

    Hi,

    What does this mean and how can I resolve this? I'm using g2.2xlarge instance and running transcoder application


    INFO server comment - TranscoderSessionNative.loadLibrary: Load transcoder list file: /usr/local/WowzaStreamingEngine/lib-native/linux64/transcoder.list
    Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /usr/local/WowzaStreamingEngine-4.0.3/lib-native/linux64/libmc_bc_dec_avc.so which might have disabled stack guard. The VM will try to fix the stack guard now.
    It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.

    INFO server comment - LiveStreamTranscoder.init[transc/_definst_/myStream]: Load transcoder template: file:///usr/local/WowzaStreamingEngine/transcoder/templates/transrate.xml
    INFO server comment - JNI:TranscoderSession.isCUDAAvailable[_defaultVHost_:transc/_definst_/myStream]: NVidia NVENC hardware acceleration is available
    INFO server comment - JNI:NVidiaCUDAUtils.logCUDAGPUInfo[_defaultVHost_:transc/_definst_/myStream]: GPU[0]: name:"GRID K520" version:3.0 driver:6000 memory:4095MB processors:8 cores:1536 clockRate:797MHz NVENC:yes
    INFO server comment - JNI:TranscoderSession.isQuickSyncAvailable[_defaultVHost_:transc/_definst_/myStream]: Intel Quick Sync hardware acceleration is NOT available.
    INFO stream create - -

    Please provide step by step instructions if possible.

    Sathish
    Last edited by sathishkumarkps; 05-14-2014 at 05:21 AM.

  2. #2
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    Hi Sathish,

    Follow this guide to configure a g2 instance for the Wowza Transcoder

    Assuming you are going to use edge servers to re-stream from, be aware that using the Internal DNS to connect edges to the origin will provide greater network utilization of the origin's 10gbs nic. However there is a 5gbs Java limit. The only way to utilize more is to have two instances of Wowza and Java running on the server, but since you can only have one IP on that kind of EC2 instance (I am pretty sure) you would have to use alternate ports on the 2nd instance, so it is not very practical.

    Richard

  3. Default

    Hi Richard,

    Thanks for your response.

    I have folllowed the metioned guide to configure g2 instance for the Wowza Transcoder.

    I'm not using edge server / restreaming an existing stream. I'm using FMLE and send 1000kbps video only stream to wowza transcoder application to transrate it into 720p, 360p, 240p strems. When the stream starts publishing I got that message and but streams are transrating and playing well.


    # ./startup.sh
    Configure logging: file:///usr/local/WowzaStreamingEngine/conf/log4j.properties
    INFO server server-start Wowza Streaming Engine 4 Monthly Edition 4.0.3 build10989 -
    INFO server comment - Server License Key:
    INFO server comment - Maximum Connections: Unlimited
    INFO server comment - Maximum Incoming Streams: 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 - HTTP Origin Available: Yes
    INFO server comment - Push Publish Available: Yes
    INFO server comment - REST API Available: No
    INFO server comment - Hardware Available Processors: 8
    INFO server comment - Hardware Physical Memory: 13324MB/14532MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 66
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 3.10.38-49.136.amzn1.x86_64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: Java HotSpot(TM) 64-Bit Server VM
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.8.0_05
    INFO server comment - Java VM Version: 25.5-b02
    INFO server comment - Java Spec Version: 1.8
    INFO server comment - Java Home: /usr/local/jdk1.8.0_05/jre
    INFO server comment - Java Max Heap Size: 9933MB
    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]: UTC
    INFO server comment - Java Args[0]: -Xmx10000M
    INFO server comment - Java Args[1]: -XX:+UseConcMarkSweepGC
    INFO server comment - Java Args[2]: -XX:+UseParNewGC
    INFO server comment - Java Args[3]: -XX:NewSize=512m
    INFO server comment - Java Args[4]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[5]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.runmode=standalone
    INFO server comment - Java Args[7]: -Dcom.wowza.wms.native.base=linux
    INFO server comment - Java Args[8]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Java Args[9]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[10]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine
    INFO server comment - Server runmode: standalone
    INFO server comment - Server native.platform: linux
    INFO server comment - Server threads[h/t]: 480/320
    INFO server comment - RESTServer: Bind attempt ([any]:8087)
    INFO server comment - RESTServer: Bind successful ([any]:8087)
    INFO server comment - Wowza REST API started
    INFO server comment - REST API: ready
    INFO server comment - RESTServer: Using configs from:/usr/local/WowzaStreamingEngine/
    INFO server comment - RESTServer: SSL:No
    INFO server comment - RESTServer: BasicAuth:No
    INFO server comment - RESTServer: Digest:Yes
    INFO server comment - RESTServer: XML Viewer:No
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO server comment - MediaCache[MediaCache]: Thread pool size: [writer/readahead]:16/8
    INFO server comment - MediaCache[MediaCache]: MAX Pending size: [writer/readahead]:500M/25M
    INFO server comment - MediaCache[MediaCache]: Add store: path:/usr/local/WowzaStreamingEngine/mediacache maxSize:10737418240
    INFO server comment - MediaCache[MediaCache]: Add source[dvrorigin]: prefix:dvrorigin/ basePath:http://
    INFO server comment - MediaCache[MediaCache]: Flushing cache: start
    INFO server comment - MediaCache[MediaCache]: Flushing cache: done
    INFO server comment - MediaCache[MediaCache]: Start MediaCache GC
    INFO server comment - MediaCache[MediaCache]: Started
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:0/0 home:/usr/local/WowzaStreamingEngine
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:16)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Server.startShutdownHook: Start server shutdown hook
    INFO server comment - StatsManager:startManager() Enabled=true
    INFO server comment - Wowza Streaming Engine is started!
    INFO server comment - MediaCasterStreamValidator.init[transc/_definst_]: Started
    INFO application app-start _definst_ transc/_definst_
    INFO session connect-pending 173.8.207.214 -
    INFO session connect 173.8.207.214 -
    INFO stream create - -
    INFO stream publish streamer -
    INFO server comment - TranscoderSessionNative.loadLibrary: Load transcoder list file: /usr/local/WowzaStreamingEngine/lib-native/linux64/transcoder.list
    Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /usr/local/WowzaStreamingEngine-4.0.3/lib-native/linux64/libmc_bc_dec_avc.so which might have disabled stack guard. The VM will try to fix the stack guard now.
    It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.

    INFO server comment - LiveStreamTranscoder.init[transc/_definst_/streamer]: Load transcoder template: file:///usr/local/WowzaStreamingEngine/transcoder/templates/transrate.xml
    INFO server comment - JNI:TranscoderSession.isCUDAAvailable[_defaultVHost_:transc/_definst_/streamer]: NVidia hardware acceleration is NOT available
    INFO server comment - JNI:TranscoderSession.isQuickSyncAvailable[_defaultVHost_:transc/_definst_/streamer]: Intel Quick Sync hardware acceleration is NOT available.
    INFO stream create - -
    INFO stream publish streamer_720p -
    INFO stream create - -
    INFO stream publish streamer_160p -
    INFO stream create - -
    INFO stream publish streamer_360p -
    INFO stream create - -
    INFO stream publish streamer_240p -
    INFO stream create - -
    INFO stream publish streamer_source -
    WARN server comment - TranscoderWorkerVideoDecoder.handlePacket[_defaultVHost_:transc/_definst_/streamer: decodeIterations:0]: Source stream frame rate is greater sourceStreamMaxFrameRate [80.0]. Using default source stream frame rate: 29.97
    INFO server comment - JNI:TranscoderSession.videoDecoderCreate[_defaultVHost_:transc/_definst_/streamer]: Create video decoder: H.264: default
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer]: Create live stream packetizer: mpegdashstreamingpacketizer:streamer
    INFO transcoder decoder-video-start streamer {codec:H264, profile:Main, level:3.1, frameSize:854x480, displaySize:854x480, frameRate:3000.0}
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer]: chunkDurationTarget: 10000
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer]: chunkDurationTolerance: 500
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer]: playlistChunkCount:4
    INFO server comment - LiveStreamPacketizerPacketHandler.startStream[transc/_definst_/streamer]
    INFO server comment - JNI:VideoDecoderH264.updateDecodeInfo[_defaultVHost_:transc/_definst_/streamer]: aspect:427x240 frame:854x480 display:854x480 frameRate:3000
    INFO server comment - JNI:TranscoderSession.videoEncoderAdd[_defaultVHost_:transc/_definst_/streamer:720p]: Create video encoder: H.264: default
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer]: Create live stream packetizer: sanjosestreamingpacketizer:streamer
    INFO server comment - SanJosePacketHandler.startStream[transc/_definst_/streamer]
    INFO server comment - LiveStreamPacketizerSanJose.handlePacket[transc/_definst_/streamer]: Video codec: H264
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer]: Create live stream packetizer: smoothstreamingpacketizer:streamer
    INFO server comment - JNI:TranscoderSession.videoEncoderAdd[_defaultVHost_:transc/_definst_/streamer:160p]: Create video encoder: H.264: default
    INFO server comment - LiveStreamPacketizerSmoothStreaming.startStream[transc/_definst_/streamer]
    INFO server comment - JNI:TranscoderSession.videoEncoderAdd[_defaultVHost_:transc/_definst_/streamer:360p]: Create video encoder: H.264: default
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer]: chunkDurationTarget: 10000
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer]: audioGroupCount: 3
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer]: playlistChunkCount:3
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer]: Create live stream packetizer: cupertinostreamingpacketizer:streamer
    INFO server comment - CupertinoPacketHandler.startStream[transc/_definst_/streamer]
    INFO server comment - LiveStreamPacketizerCupertino.handlePacket[transc/_definst_/streamer]: Video codec:H264 isCompatible:true
    INFO server comment - LiveStreamPacketizerCupertino.handlePacket[transc/_definst_/streamer][avc1.77.31]: H.264 Video info: {H264CodecConfigInfo: codec:H264, profile:Main, level:3.1, frameSize:854x480, displaySize:854x480, frameRate:3000.0, crop: l:0 r:5 t:0 b:0}
    INFO server comment - JNI:TranscoderSession.videoEncoderAdd[_defaultVHost_:transc/_definst_/streamer:240p]: Create video encoder: H.264: default
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer_source]: Create live stream packetizer: mpegdashstreamingpacketizer:streamer_source
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer_source]: chunkDurationTarget: 10000
    INFO server comment - LiveStreamPacketizerPacketHandler.startStream[transc/_definst_/streamer_source]
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer_source]: chunkDurationTolerance: 500
    INFO server comment - LiveStreamPacketizerSanJose.init[transc/_definst_/streamer_source]: playlistChunkCount:4
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer_source]: Create live stream packetizer: sanjosestreamingpacketizer:streamer_source
    INFO server comment - SanJosePacketHandler.startStream[transc/_definst_/streamer_source]
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer_source]: Create live stream packetizer: smoothstreamingpacketizer:streamer_source
    INFO server comment - LiveStreamPacketizerSanJose.handlePacket[transc/_definst_/streamer_source]: Video codec: H264
    INFO server comment - LiveStreamPacketizerSmoothStreaming.startStream[transc/_definst_/streamer_source]
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer_source]: chunkDurationTarget: 10000
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer_source]: audioGroupCount: 3
    INFO server comment - LiveStreamPacketizerCupertino.init[transc/_definst_/streamer_source]: playlistChunkCount:3
    INFO server comment - MediaStreamMap.getLiveStreamPacketizer[transc/_definst_/streamer_source]: Create live stream packetizer: cupertinostreamingpacketizer:streamer_source
    INFO server comment - CupertinoPacketHandler.startStream[transc/_definst_/streamer_source]
    INFO server comment - LiveStreamPacketizerCupertino.handlePacket[transc/_definst_/streamer_source]: Video codec:H264 isCompatible:true
    INFO server comment - LiveStreamPacketizerCupertino.handlePacket[transc/_definst_/streamer_source][avc1.77.31]: H.264 Video info: {H264CodecConfigInfo: codec:H264, profile:Main, level:3.1, frameSize:854x480, displaySize:854x480, frameRate:3000.0, crop: l:0 r:5 t:0 b:0}
    ^CINFO server comment - ServerShutdownHook.run[shutdown]
    INFO server comment - MediaCache[MediaCache]: Stop
    INFO server comment - Wowza REST API stopped
    INFO server comment - StatsManager:stopManager() stopped
    INFO vhost vhost-stop _defaultVHost_ -
    INFO server comment - TranscodingSession.close[transc/_definst_/streamer]
    INFO stream unpublish streamer -
    INFO application app-stop _definst_ transc/_definst_
    INFO stream destroy streamer -
    INFO server comment - TranscodingSession.shutdown[transc/_definst_/streamer]
    INFO session disconnect 805086276 -
    INFO transcoder decoder-video-stop streamer -
    INFO stream unpublish streamer_720p -
    INFO stream destroy streamer_720p -
    INFO stream unpublish streamer_160p -
    INFO stream destroy streamer_160p -
    INFO stream unpublish streamer_360p -
    INFO stream destroy streamer_360p -
    INFO stream unpublish streamer_240p -
    INFO stream destroy streamer_240p -
    INFO stream unpublish streamer_source -
    INFO stream destroy streamer_source -
    INFO server server-stop - -

Similar Threads

  1. fix unaligned a/v
    By rochre in forum General Forum
    Replies: 1
    Last Post: 09-09-2013, 11:52 AM
  2. Wawza 3.5.0 and WARN: Recycle safe guard issue
    By Denis_Ukraine in forum General Forum
    Replies: 1
    Last Post: 01-22-2013, 07:38 AM
  3. Fix the page
    By ertu22 in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 1
    Last Post: 02-20-2012, 05:44 AM
  4. How to take a Java stack trace
    By charlie in forum Hidden
    Replies: 0
    Last Post: 04-04-2010, 05:57 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
  •