Fix common Wowza Streaming Engine errors (2023)

This article lists common messages that are written to the Wowza Streaming Engine™ media server software log files (wowzastreamingengine_access.logmiwowzastreamingengine_error.log), scenarios that can cause these messages to be logged, and suggestions for their resolution.

Observation:You can view the messages in the log files in Wowza Streaming Engine Manager. For more details, seeView log messages in Wowza Streaming Engine Manager.

' + "

" + "

    "; var el, título, link, novaLinha; $(".hg-article-body h2, .hg-article-body h3").each(function(i) { el = $(this); title = el. text(); AnchorTitle = el.text().replace(/([~!@#$%^&*()_+=`{}\[\]\|\\:;'<>,.\ //? ])+/g, '-').toLowerCase(); enlace = "#" + AnchorTitle; el.html('' + el.html()); if ('h2:first')){ newLine = '

  • '; }else if ('h2')){ novaLinha = '
  • '; }else if ('h3') &&'.before-you-start')){ newLine = '
  • '; }else if ('h3') && el.not('.before-you-start')){ newLine = '
  • 🇧🇷 }other{ newLine = "
  • "; } newLine += "" + title + "" + "
  • "; ToC += novaLinha; }); ToC += "

    " + "

" + ""; $("#snippet-prepend").before(ToC); });

Wowza Streaming Engine Messaging

server ERROR 500 - server core failed: address already in usevhost WARN 200 _defaultVHost_ Bind failed, try again ([any]: 1935): address already in use

Why:This is usually because another instance of Wowza Streaming Engine is already running. Shut down all instances of Wowza Streaming Engine and reboot. Wowza Streaming Engine can run as a service, in standalone mode, or within the Wowza IDE, but only one at a time.

feedback server ERROR 500: failed to connect: org.apache.mina.common.RuntimeIOException: failed to get session [ConnectException: connection refused].feedback server WARNING 200: RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP/RTP relay . Cannot connect to server: rtsp://[wowza-ip-address]/myStream.sdp

Why:Try to connect to the IP camera with incorrect credentials.

WARN comment server 200 - RTPPacket.write: bad packet: incomplete NAL units.

Why:Packet loss in most cases. Try turning on packet loss logging to see if this is the problem. To seeEnable RTP jitter buffering and packet loss logging (RTP and MPEG-TS) on Wowza Streaming Engine.

feedback server ERROR 500 RTPDePacketizerMPEG4LATM.handleRTPPacket: Invalid packet length: 200:105

Why:This indicates a network connection problem. Try streaming the same file on your local host or on your local network to rule out network issues as a problem.

ERROR HTTPUtils.HTTPRequestToByteArray server comment: http://[ip-address]/latest/meta-data/product-codesWARN Server comment license key specified in [install directory] /conf/ The server.license file is in the wrong format. ERROR Server Comment Error: java.lang.NullPointerExceptionERROR Server Comment ERROR: Cannot write to license key file:

Why:This error is caused by using the wrong license key.

ERROR: Invalid license key or license file does not exist and is running as a service (exiting)

Why:This error is the result of using a perpetual license key for Transcoder, nDVR, or DRM without a valid perpetual license for the server.

Server ERROR Comment: Wowza Media Systems Software Licensing has determined that your serial number is invalid. Make sure you are using the correct serial number. If the problem persists, please visit for updated information. ERROR Server comment: system.exit

Why:This error is due to an unpaid subscription. ContactCustomer Supportresolver.

comentario servidor ERROR PushPublisherRTMP: com.wowza.wms.server.LicensingException: Server.license

Why:This error can be seen when using an older Amazon EC2 AMI in conjunction with the autopublishing API. Wowza Streaming Engine works as expected locally or in test, but the deployment server throws this license error. That specific license restriction has since been lifted. Upgrading to a current AMI resolves this issue.

servidor de comentario ERRO 500 - invocar(onHTTPCupertinoStreamingSessionDestroy): java.lang.NullPointerException: com.ptin.wms.module.AbortSession.onHTTPCupertinoStreamingSessionDestroy(

Why:In this example, there is an error in the custom module named AbortSession on line 10. The custom module developer should resolve the issue.

WARN 200 application folder is missing from the feedback server ([install location]/applications/_defapp_)

Why:This error is generated when you connect to Wowza Streaming Engine without the application name.

Feedback server WARN 200 - Missing application folder ([install location]/applications/:80)

Why:Usually this is because FFmpeg is being used as an encoder and is not sending the application name correctly.

comment server INFO 200 - RTPMediaCaster.create[9936743] - - - 2.469comment server INFO 200 - RTPMediaCaster.init[9936743] - - - 2.47comment server INFO 200 - RTPMediaCaster.Reconnector[9936743:live/_definst_:live/ ]: start: 1 - - - 2,473 feedback server INFO 200 - VHost.startStartupStreams: Stream started successfully [live/_definst_]: flv:live/ - - - 2,486 feedback server ERROR 500 - Failed to connect: org .apache .mina.common.RuntimeIOException: Could not get session [ No route to host]. - - - 5603comment server WARN 200 - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP/RTP stream. Cannot connect to server: rtsp://[wowza-ip-address]/customer.mp4 - - - 5.618comment server ERROR 500 - Failed to connect: org.apache.mina.common.RuntimeIOException: Failed to get the session [ java .net.NoRouteToHostException: No route to host].

Why:This MediaCaster problem is usually caused by some kind of network error. For example, the SHOUTcast server is not enabled. Here we see the start of a live stream and then warnings and errors indicating that the Wowza Streaming Engine has encountered a dependency fault.

ERROR server comment RTPSessionDescriptionDataProviderBasicRTSPConnection.connect[wowza-ip-address]:[port-number]: Could not connect: org.apache.mina.common.RuntimeIOException: Could not get session[ConnectException: Connection refused: no further information]. WARN server comment LiveMediaStreamReceiver.doWatchdog: streamTimeout: Connection reset

Why:Wowza Streaming Engine cannot connect to a MediaCaster stream. It could be a problem with the network or with the source. For example, the camera was reached but it refused the connection. Wowza Streaming Engine will keep trying to reconnect until the stream is available again.

INFO comment server 200 - RTPUDPTransport.bind[live/_definst_]: - - - 556.803INFO comment server 200 - RTPUDPTransport.bind[live/_definst_]: :6001 - - - 556.803comment server INFO 200 - RTPUDPTransport.bind[live/_definst_]: - - - 556.804comment server INFO 200 - RTPUDPTransport.bind[live/_definst_]: 0.0 .0.0 /0.0 .0.0:6003 - - - 556.804comment server INFO 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionStart: PLAY: rtsp://[wowza-ip-address]/myStream.3gp/comment server INFO 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.processResponse: PLAY : rtsp: // [direction-ip-wowza]/myStream.3gp/server of comments INFO 200 - RTPMediaCaster.Reconnector[30149247:live/_definst_:live/]: finished: 2 - - - 556.805server of comments INFO 200 - UDPTransport. firstPacket: - - - 557.044-----other log lines removed for clarity ------------------commentserver INFO 200 - RTPMed iaCaster.shutdown[ 30149247:live/_definst_:live/]: live/myStream.streamcomment server INFO 200 - RTPMediaCaster.disconnect[30149247:live/_definst_:live/] - - - 853.437comment server INFO 200 - RTPMediaCaster.closeRTPSession[30149247:live /_definst_:live/] - - - 853.437information of the comment server 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.close closeSession - - - 853.437information of the comment server 200 - RTPUdTransport.unbin[ live/_definst0_]: .0.0/ - - - 853.438comment server INFO 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose - - - 853.438comment server INFO 200 - RTPSessionTracker.remove[rtsp://[wowza-ip-address ]/myStream.3gp]: 0:true - - - 853.439comment server INFO 200 - RTPUDPTrans port.unbind[live/_definst_]: - - - 853.439comment server INFO 200 - RTPUDPTransport.unbind[live/_definst_]: 0.0. 0.0/ - - - 853.439comment server INFO 200 - RTPUDPTransport.unbind[live/_definst_]: 0. 0.0.0/ - - - 853.439 comment server INFO 200 - RTPUDPTransport.unbind [live/_definst_]: - - - 853,439

Why:2-4 bind lines, quickly followed by 2-4 unbind lines, indicates UDP session failure, ports blocked. Usually the problem is in the firewall of the computer where Wowza Streaming Engine is installed. It can also be the router, the proxy in the environment or the operator network in the RTSP streaming app.

(Video) Record Streams Automatically With a Wowza Streaming Engine Java Module

servidor WARN 200 - RTPDePacketizerWrapperPacketSorter.packetLoss\[miAplicación/_definst_/streamOne.sdp:trackID=2\]: last:13066 curr:25584servidor WARN 200 - RTPDePacketizerWrapperPacketSorter.packetLoss\[miAplicación/_definst_/streamTwo.sdp:trackID=1\] : last:63732 curr:14634server WARN 200 - HTTPStreamerAdapterCupertinoStreaming.getAppInstance: Stream não encontrado \[myApplication/_definst_/streamThree.sdp/playlist_w1234567890.m3u8]: myStream.sdp 68998.779

Why:Another encoder on the same network was sending packets to the same channels, causing a conflict. This behavior makes it appear that some flows are dropping packets.

Note the large discrepancy between the most recent and current values. If it is RTP, the values ​​should be similar. The packet classifier only works if the stream is RTP. Wowza uses a sequence number in the RTP header to reorder the packets. Since the numbers are so far apart, it probably means that the stream in question is not RTP. Possibly, the streams causing these problems are MPEG-TS streams that are not encapsulated in RTP.

RTPDePacketizerWrapperPacketSorter.handleRTPPacket["+contextStr+":"+rtpTrack.getTrackId()+"]: The stream is MPEG-TS, which is not supported by the packet classifier. The packages will be forwarded.

Why:The packet classifier forwards MPEG-TS packets and reports this to the registry. The part in parentheses is theappName/appInstanceNAME/streamName:trackname.

Error parsing VHosts.xml (file:///usr/local/WowzaStreamingEngine/conf/VHosts.xml): java.util.ArrayList cannot be cast to org.w3c.dom.NodeListException on java "main" thread. lang .NoClassDefFoundError : com.wowza.wms.server.Server on java.lang.Class.initializeClass(

Why:These messages appear when trying to start Wowza Streaming Engine. "" indicates that it is an old version of Java that may have been part of a Linux distribution. Install the latest Oracle Java software and verify that it is installed correctly before restarting Wowza Streaming Engine.

server WARN 404 [path to video file][2]: java.lang.Exception: QTUtils.parseQTMediaContainer: missing atom file 'moov'.

Why:An attempt was made to stream a file during recording. When the stream is not published, Wowza Streaming Engine writes the moov atom data to the end of the file. you can use theIMediaWriterActionNotifylistener to listen to the files to complete. If you use Wowza nDVR, you can record while playing a live stream.

You can also get this error if you try to play a file with H.264 content but not an MP4 file and use themp4:prefix.

WARN server comment[2]: java.lang.Exception: QTUtils.parseQTMediaContainer: Invalid atom size: 0.

Why:Occurs when trying to play a file that is not an MP4 file. This error is thrown by the MP4 file parser, indicating that it cannot find the information it expects. Usually the problem is that the wrong prefix is ​​being used.

ERROR server comment QTWriterUtils.loadForAppend[path to video file][index]: Incorrect atom length: -8WARN server comment QTWriterUtils.loadForAppend[path to video file][index]: MOOV Atom is missing Server comment server WARN QTWriterUtils .loadForAppendParseMOOV[path to video file]: WARNING: Add: atom 'stsc' contains incorrect sample count information: missingSampleCount:26 lastChunkCount:1 lastSamplesPerChunk:25 totalSampleCount:79926 samplesAccountedFor:79900

Why:When recording a video, if the file is moved before the recording is complete (not posted), the file cannot be played and you will see the missing moov atom error. When the stream is not published, Wowza Streaming Engine writes the moov atom data to the end of the file. The resulting script would have a problem if there was a problem with the unpublish mechanism, for example if the server crashed or unpublish was not triggered for some reason.

ERROR Server Comment QTWriterUtils.loadForAppend[path to video file][index]: Incorrect atom length: -8WARN Server Comment QTWriterUtils.loadForAppend[path to video file][index]: Missing MDAT Atom

Why:Caused by writing the file. For example, a problem writing to the destination filename specified for recorded video could cause this error. mdat atom is a required top-level atom.

WARN server comment Metadata appears to be incorrect: [stream-name]

Why:This error indicates that the file does not include theinMetaDatapackage. You must provide a sample problem file for analysis.

Missing prefix for MP4 type files (eg.muestra.mp4instead ofmp4:muestra.mp4🇧🇷 Wowza Streaming Engine ignores the file extension, so if the prefix is ​​missing, the server will load MediaReaderFLV by default, but MediaReaderH264 is actually needed. Adding the prefix might fix it.

Comment from server error MediaReaderFactory.getInstance: Missing definition for mov

Why:Try to play a file with the .mov prefix when the file is not of this type of transmission. Too many open files at Method) at at org.apache.mina.transport. socket.nio.SocketAcceptor$Worker.processSessions(Unknown Source) at org.apache.mina.transport.socket.nio.SocketAcceptor$ Source) at Source ) in

Why:Make sure that Wowza Streaming Engine is properly tuned by following the instructions inTune Wowza Streaming Engine for optimal performance.

java.lang.NullPointerException at com.wowza.wms.httpsstreamer.cupertinostreaming.file.MediaReaderH264Cupertino.fillChunk (source unknown) at com.wowza.wms.httpsstreamer.cupertinostreaming.file.HTTPStreamerCupertinoIndexFile.fillChunk (source unknown) at com.wowza. wms.httpsstreamer.cupertinostreaming.file.HTTPStreamerCupertinoIndexBase.getChunk (source unknown) at com.wowza.wms.httpsstreamer.cupertinostreaming.httpsstreamer.HTTPStreamerAdapterCupertinoStreamer.onMe diaFile (source unknown) ----

Why:This is a file structure related error. Try other files or ourdemo filesto determine if it is file specific. Please provide your live stream or VOD file to Support for further review.

Access Forbidden (403)

Why:This error is seen in an encoder trying to connect to Wowza's streaming engine. It is not registered in the Wowza records. This can be caused by specifying a Wowza application that is not configured on Wowza Streaming Engine. It can also be caused by trying to play Wowza Streaming Engine files as if it were a web server, which will not work. The sample.htmlfiles must be opened directly in a web browser.

Feedback server WARN 404[1]: C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine [version]\content\ (The system may 't find the specified file)

Why:Occurs when the sequence cannot be found. Common causes are that theFlows/Flow Typeis not configured correctly inApplication.xmlor the stream is starting with the StreamManager and the wrong MediaCaster type was selected when starting the stream.

feedback server ERROR Please close the RTSP/RTP session. Session timeout: 90000

Why:Timeout limit exceeded. The value can be set toRTP/RTSPSessionTimeoutno[install directory]/conf/[application name]/Application.xml🇧🇷 The value is in milliseconds. Defined as0to never expire. For problematic MediaCaster streams, seeMonitor and restore streams from Wowza Streaming Engine MediaCaster.

WARN Comment on server HTTPStreamerAdapterCupertinoStreamer.onPlaylist: context of application not loaded [dvr/myStream/manifest.f4m?DVR]: dvr/_definst_]: dvr/_definst_WARN Comment on server HTTPStreamerAdapterCupertinoStreamer.onMediaFile: context of application not loaded [vod/ mp4: sample.mp4/ media_w532002815.ts]: vod/_definst_

Why:This message appears when the application name or URL is invalid. If you use the sample players, a common cause is that the app name differs from the default app name by default. Check the URL.

(Video) How to use JW Player 7 with Wowza Streaming Engine

WARN 200 HTTPStreamerAdapterCupertinoStreamer.service server comment: request timeout: 12000

Why:There are no flow connections within the timeout value. Check your live source and encoder.

Comentario del server WARN HTTPStreamerAdapterCupertinoStreamer.onPlaylist: contexto de applicación no cargado [[live/myStream/manifest.f4m]: live/_definst_]: live/_definst_

Why:It occurs when theHTTPStreamersproperty inApplication.xmlit does not include the type of stream you are trying to play.

HTTPStreamerAdapterCupertinoStreamer.onPlaylist[myApplication/_definst_/myStream/playlist_w639247249.m3u8]: Sesión no aceptada[639247249]

Why:The transmission is invalid or the session has expired.

servidor de comentarios ERROR 500 - ModulePushPublishSimpleExample#StreamNotify.onPublish: com.wowza.wms.server.LicensingException: Server.licensecomment server ERROR 500 - ModulePushPublishSimpleExample#StreamNotify.onPublish: com.wowza.wms.server.LicensingException: Server.licensecomment server ERROR 500 - ModulePushPublishSimpleExample#StreamNotify.onPublish: com.wowza.wms.server.LicensingException: Server.license

Why:Make sure you have the latest Push Publishing module.Contact Usto order the module.

ERROR comentario del servidor HTTPUtils.HTTPRequestToByteArray: http://[wowza-ip-address]/latest/meta-data/product-codes

Why:This message appears when running on an Amazon Machine Image (AMI) with a Bring Your Own License (LicKey) subscription or perpetual license key. You can ignore this message.

WARN 200 RTPPacketFragmentListReader.skip: Incorrect number of hops: -123456789

Why:This indicates packet loss or an incomplete packet. This message can appear when the CPU or GPU utilization for acceleration is at or beyond a feasible threshold, or if there is a lot of network traffic. Make sure Wowza Streaming Engine is tuned by following the instructions onTune Wowza Streaming Engine for optimal performance.

ERRO 500 - addDataA[this.size:248620 this.dataA.length:248620 this.startDataLoc:278333 this.dataLoc:278333 data.length:4016 offset:152 size:32 falta:22 ]: java.lang.ArrayIndexOutOfBoundsException

Why:The correct amount of data for the incoming packet is not present. This message can appear when CPU or GPU utilization for acceleration is at full capacity or exceeds a workable threshold, or when there is heavy network traffic. Make sure Wowza Streaming Engine is tuned by following the instructions onTune Wowza Streaming Engine for optimal performance🇧🇷 Packet loss can occur when CPU/GPU utilization or network performance is maxed out.

WARN 200 - RTPDePacketizerWrapperPacketSorter.handleRTPPacket[:mpegts]: The stream is MPEG-TS, which is not supported by the packet classifier. The packages will be forwarded.

Why:Remove the package sorter from yourApplication.xmlsettings if it does not apply to your stream.

Server ERROR 403 ModuleRTMPAuthenticate.checkSecureToken: Action before receiving response: close connection:

Why:A client tries to connect without responding to the secure token request. Make sure the code is correctly embedded in the player. The specified network name is no longer available

Why:Network related error. check if thestorage addressproperty in[install directory]/conf/[application name]/Application.xmlpoints to an available mapped drive or UNC path.

ERROR 500 - Server kernel failed: java.lang.NullPointerException

Why:Possible corrupt installation. Try reinstalling Wowza Streaming Engine.

ERROR server comment Could not connect: org.apache.mina.common.RuntimeIOException: Could not get session [ConnectException: Connection timed out: no more information] ERROR server comment RTPSessionDescriptionDataProviderBasic.getStreamInfo: Timeout for RTSP/RTP streaming.

Why:Both errors are related to network connectivity issues, the inability to connect to the MediaCaster stream. Look at the log lines above for clues. This can also be due to the upper limit being reached on the number of streams the server can handle. It may be necessary to add another server. I recommend configuringMediaCaster Stream Monitor, which monitors and restores bad streams and server monitoring with JConsole.

ERROR server comment configuration options error

Why:Usually caused by network connectivity issues.

ERROR server comment packageSizeReset: 12:345 ERROR server comment Zero size function (client): type: 20 size: 0 index: 123 ERROR server comment Incorrect data format, dropping client connection.

Why:This can be caused by many factors, but is usually caused by a TCP error or a communication error. It usually indicates that Wowza Streaming Engine is overloaded in some way: CPU, I/O, network, or even the GC is running for too long. To seeTune Wowza Streaming Engine for optimal performancefor information on changing GC options and other areas to check.

INFO stream create videos/myStream.smil -[Fatal Error] :2:7: Element type "smil" must end with the corresponding end tag "</smil>".ERROR Server comment MediaListReaderSMIL.readMediaList[myApplication/_definst_ :videos/ myStream.smil]: org.xml.sax.SAXParseException: the element typesmilemust end with the corresponding end tag "</smil>". Server Comment WARN HTTPStreamerCupertinoIndexPlaylist.indexFile[myApplication/_definst_/smil:videos/myStream.smil]: MediaList is empty.

Why:Missing malformed .smil file<head>qualification.

INFO 200 - ShoutCastReceiver.internalConnect: http://www.mywebsite:1234/INFO 200 - ShoutCastReceiver.internalConnect: http://www.mywebsite:1234/ - - - INFO 200 - ShoutCastDecoder.checkHeader[]: ICY Respuesta: ICY 401 Servicio indisponible

Why:Typical causes for a connection to a SHOUTcast/Icecast stream to fail are:

  • The doors are locked. Make sure the ports are not blocked or conflicting with another application.
  • The SHOUTcast/Icecast server is offline, so the connection and retries fail.
  • Incorrect URL. To seeURL to connect to SHOUTcast or Icecast🇧🇷 You must use the media url, not the playlist url.
  • If this is an intermittent issue, the SHOUTcast/Icecast stream may be choppy and inconsistently available.
WARN Server Comment - RTPDePacketizerMPEGTS.handleRTPPacket: out of sync: 0x[nn]

Why:This could be due to two encoders sending a stream to the same port. It may also be that the flow is not aligned. Install the latest version of Wowza Streaming Engine and try to configure thempegtsVideoIsAlignedproperty forfalseas described inFix missing or junk video (MPEG-TS) in Wowza Streaming Engine.

Alternatively, the MPEG-TS encoder may not be correctly aligning TS packets into UDP packets. Add the following property toRTP Container/Propertiesno[installation-dir]/conf/[application]/Application.xml(make sure you get the correct<Properties>container; there are several in the file):

<Property> <Name>rtpDePacketizerWrapper</Name> <Value>com.wowza.wms.rtp.depacketizer.RTPDePacketizerWrapperReChunkMPEGTS</Value></Property>

Wowza's drive motor only allows for a singlertpDePacketizerWrapperworth. If you have configured a jitter buffer or a packet logger that uses the samertpDePacketizerWrapper, they must be removed.

WARN server comment - RTPDePacketizerBase.checkRTCPSSRC: ssrc error: e8b92a:6319b7c8

Why:This usually means that the encoder has been started and stopped and the session has not timed out. When that happens, thessrcchanges in ownership of RTP packets. Wowza Streaming Engine blocks incoming packets because this value has changed. There is a 12 second transmission timeout set for RTP transmissions. As long as the encoder is idle for more than 12 seconds, the stream should restart and be fine.

feedback server WARN 200 - Waiting for RTCP packet. See the docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).

Why:Sender Report (SR) packets, which are sent over the Real Time Control Protocol (RTCP) channel, did not arrive within the timeout period specified by theRTP/MaxRTCPWaitTimeproperty in[install directory]/conf/[application name]/Application.xml🇧🇷 SR packets provide timing information between the audio and video in the incoming RTP stream. If Wowza Streaming Engine does not detect SR packets for the incoming RTP stream, it will write this message to the log file and try to use the RTP timecode values ​​in the RTP packets to synchronize the audio and video channels.

You can extend the amount of time that Wowza Streaming Engine waits to receive SR packets by changing theRTP/MaxRTCPWaitTimeproperty in[install directory]/conf/[application name]/Application.xml, or you can change the default method by which Wowza Streaming Engine synchronizes audio and video by changing theRTP/AVSync methodproperty in[install directory]/conf/[application name]/Application.xmlfrom the default value (shipper report) for anyonertp timecodeosystem clock. It is defined forrtp timecode, Wowza Streaming Engine synchronizes the audio and video channels based on the RTP timecodes in the RTP packets (as mentioned above). If set tosystem clock, Wowza Streaming Engine synchronizes the audio and video channels based on the system time when the first audio and video packets arrive on the server, assuming they arrive at the same time.

(Video) Seamless Integration with Wowza Streaming Engine and Matrox Monarch HD
server feedback INFO 200 - Server.startShutdownHook: start server shutdown hook

Why:This log line is part of the standard Wowza Streaming Engine start lines. The boot line is nothing to worry about. Additional logging can help troubleshoot shutdown issues.

WARN server comment - HTTPStreamerAdapterCupertinoStreamer.onEncKey[myApplication/_definst_/myStream/key_w1063299536.m3u8key]: onEncKey is not enabled.

Why:This notice indicates thatonEncKeydelivery is not enabled onHTTP Transmitter/PropertiesnoApplication.xml🇧🇷 It is disabled by default for security reasons.

<Property> <Name>cupertinoEnableOnEncKey</Name> <Value>true</Value> <Type>Boolean</Type></Property>
HTTPStreamerAdapterCupertinoStreamer.onPlaylist[[application]mp4:anyfile.mp4/playlist.m3u8]: over license limit

Why:oAbout license limitindicates a problem other than the implicit license limit. This usually occurs in scenarios where another error occurs and the transmitter code misinterprets the error as a license failure. install latestproduction constructionMake the Wowza transmission motor.

ERROR server comment [aaaa-mm-dd hh:mm:ss] - - - - - 1335.312 - - - - - - - - invoque(onAppStart): java.lang.reflect.InvocationTargetException|at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)|at sun.reflect.NativeMethodAccessorImpl.invoke(|en sun.reflect.DelegatingMethodAccessorImpl.invoke(|en java.lang.reflect.Method.invoke(|en com.wowza.wms.module. FunciónMódulo.invoke(FunciónMó|

Why:Any module method can cause this error, and the name of the method is provided in the first part of the message:get together(moduleMethodName)🇧🇷 The error occurs when a module method throws an exception that is not caught or handled in the method. The exception is thrown for built-in controllers that call the module's methods.

Uncaught exceptions can cause memory leaks or make Wowza Streaming Engine unstable because instructions that normally occur after the exception occurs will not be executed.

To find the nature of the error:

  1. Capture and log the original error to see what is causing it. The following example shows how to detect and log the error. The error message will move fromget togethermethod for themodulemethod.
    public void onAppStart(IApplicationInstance appInstance){ try { do something(); } catch(Exception e) { getLogger().error("MyModule.onAppStart exception thrown: " + e, e); } finally { sorted(); 🇧🇷
  2. The cause of the error should be apparent from the logged exception. Use this information to resolve the error.

Messages for Wowza nDVR

comment server WARN DvrApplicationStoreManagerBase.removeStream() stream foo does not exist on this DVR.

Why:This is a valid warning if:

  • A player requested fragments of foo, but foo no longer exists because the user deleted it.
  • oFileStrategyproperty is defined asRemovenoApplication.xml.
comment server WARN The current time the DVR attempted to rewind. New ignored time. Old Time = 422310. New Server Comment Time = 0.WARN - DvrPacketHandler.handlePacket[myApplication/_definst_/]: Out of Service Time Code [audio]: 8166079375: 8166079384

Why:There is a problem with the encoder sending packets with odd packet times. nDVR reports the problem but does not fix it.

WARN LiveStreamDvrRecorder.endChunk[myApplication/_definst_/myStream]: recalculating duration by conjecture. Also -601. Now it's

Why:This is a built-in protection in Wowza nDVR. If Wowza Streaming Engine detects an invalid chunk, it will try to fix it by recalculating if the clock has been reset. If you can't fix it, the part is thrown away.

WARN DvrPacketHandler.handleHolder(): Ignoring the handle that cannot be realigned. Holder: {DvrPacketHolder: type:V pt:3332574 utc:1335872445912 dur:1230 (KEY, ) codec:7 numPackets:0 dataLen:18513 enc.n:0 pkt:{{DvrAMFPacket: size:18513, type:9, src :1, seq:0, abs timecode: 3332574, timecode:1230, utcTc:1335872445912}}}

Why:This is a built-in protection in Wowza nDVR. This warning message reports that the block could not be realigned.

WARN DvrPacketHandler.handlePacket[myApplication/_definst_/myStream]: Releasing packet with excessive duration: {DvrAMFPacket: size:6785, type:9, src:32185, seq:126, absTimecode:35557077, timecode:131362, utcTc:113478970};

Why:This is a built-in protection in Wowza nDVR. Wowza nDVR expects incoming audio and video to be aligned. When the audio and video are misaligned beyond the allowable tolerance, you will see this warning message in the logs. Indicates dropped packets and a problematic source flow. To seedvrAllowableAVPacketDeltafor more information on compensation for misalignment problems.

Comentario del servidor WARN myStream[1]: /usr/local/WowzaStreamingEngine/content/myStream (No existe tal archivo o directorio)

Why:oflow typethe value is defined asPatterninstead ofVivanoApplication.xmlFile, Archive. Wowza nDVR only supports live streaming. This message indicates that Wowza Streaming Engine is looking for a VOD file in the content directory. Change theCurrents\Type of currentproperty forViva.

Comentario del servidor WARN ApplicationInstance.setdvrList[dvr/_definst_]: dvr inválido: dvrrecoder

Why:'dvrrecorder' is misspelled in[install directory]\conf\[application name]\Application.xml🇧🇷 Take a good look at the last word of the message.

ERROR server comment LiveStreamDvrRecorderBase.initProperties[myApplication/_definst_/myStream]: DVR/Store 'foo' is not a known DVR store. The DVR cannot record.

Why:'foo' is not a valid DVR storage. put theDVR/Lojaproperty fordvr file storageeither single server or origin. If you are going to embroider, leave it blank.

ERROR server comment LiveStreamDvrRecorderBase.initProperties[myApplication/_definst_/myStream]: DVR/Store not defined in Application.xml. The DVR cannot record.

Why:No value is specified for theDVR/Lojaproperty as expected. put theDVR/Lojaproperty fordvr file storage.

Server Comment ERROR LiveStreamDvrRecorderBase.initProperties[myApplication/_definst_/myStream]: DVR/StorageDir not defined in Application.xml. The DVR cannot record.

Why:No value is specified for theDVR/StorageAddrproperty as expected. The default is<Storage Dir>${com.wowza.wms.context.VHostConfigHome}/dvr</Storage Dir>.

Server Comment WARN DvrStreamStoreBase.startRecording[myApplication/_definst_/myStream/myStream_0]: Attempt to start recording of stream that cannot be recorded.

Why:see anotherDVR/Lojaproperty errors Usually one of them precedes this warning message.

Server Comment ERROR DvrStreamStoreBase.storeChunks[DVR/_definst_/]: Skipping chunk. The A/V packet times differ by 3025ms, more than the 2000ms allowed. aHour=3749903889 vHour=3749906914

Why:This type of registration error indicates an audio/video alignment problem. Due to this alignment problem, the blocks are not written and the recording is degraded. The best way to fix this is upstream from Wowza nDVR (usually in the encoding process). While it is strongly recommended that you correct any audio/video alignment issues before recording, there are nDVR properties that you can configure inApplication.xmlto try to compensate for this problem. Note that these properties do not fix the alignment issue, but they may help to fix it. To seedvrPacketSortTimemidvrAllowableAVPacketDelta.

Feedback Server WARN 200 LiveStreamDvrRecorder.reportCodecInformation[myApplication/_definst_/myStream][avc1.77.31]: H.264 (Video may not play on older iPhone and iPod touch devices where Main/Level 3.1 or lower is required ) Video Information: : { MediaCodecInfoVideo: codec: H264, profile: 77, level: 4.1, frame size: 320x240, screen size: 320x240, frame rate: 29.970000}

Why:This notice is to inform you that depending on the streaming code, the video may not play on older Apple iOS devices. Consult the Apple documentation for your desired playback device to determine the supported codecs.

(Video) Set Up and Configure an SSL/TLS Certificate for Wowza Streaming Engine

servidor de comentarios ERROR 500 - DvrStreamStoreBase.storeChunks[myApplication/_definst_/myStream]: AudioDuration=30624 > 20000 ms. Omitiendo server chunks.comment ERROR 500 - DvrStreamStoreBase.storeChunks[myApplication/_definst_/myStream] : VideoDuration=30600 > 20000 ms. Saltar trozos.

Why:This occurs when the duration of the block exceeds the defined value. To seedvrAudioOnlyChunkTargetDuration.

WARN Server Comment DvrPacketHandler.handlePacket[liveDVR/_definst_/myStream]: Out of Service Time Code [video]: 71500:71580

Why:This usually indicates an encoder problem. It can also be a problem when the CPU or GPU utilization of the computer is maxed out. To debug, seeDebugging AAC or MP3 timecode issues with the Apple HLS package in Wowza Streaming Engine🇧🇷 try to useMediaCaster Stream Monitorto monitor the flows and reset them if they become faulty. If you see this message immediately after publishing the stream before packaging begins, you can ignore it.

Server Comment WARN HTTPStreamerAdapterCupertinoStreamer.onISMVData: application context not loaded [live/ngrp:myStream_all]: live/_definst_

Why:This message appears when the application name or URL is invalid. Your app name may be different from the app name given by default. Check the URL.

WARN Server Comment - Missing Function: DVRSubscribe WARN Server Comment - Missing Function: DVRGetStreamInfo

Why:Wowza nDVR supports playback via any HTTP protocol supported by Wowza Streaming Engine. These warnings occur when you try to use the DVR with an unsupported protocol.

messages to transcoder

WARN Server Comment TranscoderWorkerVideoDecoder.handlePacketVideo[_defaultVHost_:AppName/_definst_/StreamName: decodeIterations:565]: Video decoder pending frame count[198] is greater than threshold[150], restarting

Why:The transcoder cannot decode the stream fast enough. This is usually due to a lack of CPU or GPU resources, but it can also be related to font encoding.

WARN Server Comment LiveStreamTranscoder.isTranscoderAvailable: Transcoder is not available for your platform: platform: null architecture: 32

Why:The transcoder requires a 64-bit platform. This warning occurs if Wowza Streaming Engine is not installed on a 64-bit operating system or if you have an older version of Java installed on your computer. To resolve the Java version issue, seeInstall and troubleshoot Java manually on Wowza Streaming Engine.

JNI WARN Server Comment:AudioEncoderAAC.initialize[_defaultVHost_:myApplication/_definst_/myStream:360p]: Bit rate too high for sample rate. Bit rate adjusted from 128,000 to 48,000

Why:The input sample rate is too low to support the selected bit rate for transcoding. If the input sample rate is 22.05 KHz, 24 KHz, or 32 KHz, you are restricted to a 48 Kbps audio stream. Try using a 44.1 KHz sample rate in the source stream being ingested , or lower the audio bitrate in the encoding preset by adjusting the transcode template.

Comentario del servidor WARN ApplicationInstance.setLiveStreamTranscoderList[myApplication/_definst_]: LiveStreamTranscoder no es válido: transcoder

Why:The transcoder did not start correctly and there are other errors in the registry that indicate a faulty installation or permissions issue. Before reinstalling make a backup[install directory]\conffiles for reference when reconfiguring. Another cause could be that "transcoder" is misspelled[install directory]\conf\[application name]\Application.xml🇧🇷 Take a good look at the last word of the message.

Comentario del servidor WARN[myApplication/_definst_/myStream]: el grupo de nombres no se pudo resolver: myStream_all Reason:[bitrateMissing:true videoCodecIdMissing:true audioCodecIdMissing:false sizeMissing:true]Error del codificador.

Why:The expected data stream is not being sent to the Wowza Streaming Engine. Check the input source.

Comentario del servidor WARN HTTPStreamerCupertinoIndexPlaylist.indexFile[myApplication/_definst_/ngrp:myStream_all]: MediaList está vacío.

Why:There are several causes that can generate this error:

  • Malformed URL or an error in the transcoder template. Check that the value of<Group of Stream Names>/<Stream Name>(no<Group of stream names>/<Name>), is specified as the broadcast group name in the URL. In this example, the name of the source stream ismy streamand the problem is that the value of<Group of Stream Names>/<Stream Name>It is not${SourceStreamName}_all.
  • o<Encode>/<Name>It's in<Sequence Name Group>/<Members>/<Member>/<Encoding Name>are not the same In the sample template, you will see the coding block<Name>360p</Name>has a matching sequence name group block member name (<EncodeName>360p</EncodeName>).
  • The transcoder model that was loaded was not as expected, so the stream name specified in the URL is incorrect. Wowza's drive motor uses the first model listed onTranscoder/ModelsnoApplication.xml🇧🇷 Review the log to validate the model name being loaded.
  • Other errors that indicate a problem with the resulting stream, such as no audio.
WARN 200 - TranscoderStreamNameGroup.validateMembers[myApplication/_definst_/myStream]: StreamNameGroup[160p] Invalid audio codec for namegroup: UNKNOWN (unknown)

Why:The source has no audio.

WARN 200 - TranscoderStreamNameGroup.addInternal[myApplication/_definst_/myStream]: namegroup in aggregate, is empty: myStream_all

Why:The stream name group was not created because the transcoder cannot transcode the stream. Make sure the source stream uses supported codecs (seeSupported video and audio formats🇧🇷 Also, make sure theEnableproperty value for all<Encode>the blocks in the model file are defined asreal.

feedback server INFO 200 - TranscodingSession.updateBehindFilter[myApplication/_definst_:myStream]: video behind filter state change. New State: Server SKIP1FRAMEcomment INFO 200 - TranscodingSession.updateBehindFilter[myApplication/_definst_:myStream]: Video behind filter state change. New State: Server SKIP2FRAMEcomment INFO 200 - TranscodingSession.updateBehindFilter[myApplication/_definst_:myStream]: Video behind filter state change. New state: ALLFRAMESON

Why:These INFO messages indicate that the Wowza Streaming Engine is overloaded and cannot process packets in time. Typically occurs when CPU or GPU utilization for acceleration is at full capacity or exceeds a workable threshold. Make sure Wowza Streaming Engine is tuned in. To seeTune Wowza Streaming Engine for optimal performancemiWowza Streaming Engine Transcoder Performance Comparison.

WARN server comment 200 CupertinoPacketHandler.handlePacket[myApplication/_definst_/myStream]: Time code for the request [video]: 27:25191 WARN server comment 200 CupertinoPacketHandler.resetStream[myApplication/_definst_/myStream][0:11]: Timecodes rewind in time.

Why:This usually indicates an encoder problem. It can also be a problem when the CPU or GPU utilization of the computer is maxed out. To debug, seeDebugging AAC or MP3 timecode issues with the Apple HLS package in Wowza Streaming Engine🇧🇷 try to useMediaCaster Stream Monitorto monitor the flows and reset them if they become faulty. If you see this message immediately after publishing the stream before packaging begins, you can ignore it.

servidor de comentarios ERROR 500 - MediaReaderFactory.getInstance: java.lang.ClassCastException: no se puede convertir a

Why:The applicationflow typeit is not set to one of the live types. This causes the wrong stream classes to be called.

Server Comment WARN - Missing function: createStream

Why:This probably means that theApplication.xmlthe file is malformed. Start over with a fresh copy of[install directory]/confpasta.

Messages for Wowza DRM

Feedback Server WARN 200 - ModuleDRMEZDRM.getPlayreadyLicense[myApplication/_definst_]: EZDRM content key is not defined. Feedback Server WARN 200 - ModuleDRMEZDRM.onHTTPSmoothStreamingPlayReadyCreateVOD[myApplication/_definst_/sample.mp4]: Key request failed. ifFailFakeKey:false

Why:If you unexpectedly see this type of message onwowza*_acceso.log, make sure the EZDRM username and password information is set correctlyApplication.xml.

ERROR server comment: PlayReadyEncryptor.initKey: Illegal key size or default parameters

Why:Microsoft PlayReady encryption keys must be 128 bits (16 bytes). This message appears when the key length is not met. Wowza only supports 128-bit key lengths.

ERRORservercomment2013-08-0614:03:07-----290.512--------BuyDRMUtils.httpRequest[send]: connection expired

Why:A "connection timeout" suggests that Wowza Streaming Engine is trying to connect and cannot. BuyDRM connects from the server to a web service using a specific URL. Confirm that all inbound and outbound firewall rules at the server and network level allow traffic on secure ports.

Feedback Server WARN 200 - ModuleDRMBuyDRM.onHTTPPCupertinoEncryptionKeyVODChunk[buydrm/_definst_/sample.mp4]: Lookup returned UNKNOWN status

Why:Wowza Streaming Engine cannot find thecomprardrmstreammap.txtmap file. When you add properties toApplication.xmlfile to configure the BuyDRM module, thedrmBuyDRMStreamNameMapFileThe property specifies the location of the map file and the default value is[install directory]/conf/buydrmstreammap.txt🇧🇷 For more information on how to configure the BuyDRM module for use with your streaming apps,Use BuyDRM KeyOS DRM com Wowza Streaming Engine.

'); $('.hg-comment-post textarea').keyup(function () { var tlength = $(this).val().length; $(this).val($(this).val().substring (0, maxchars)); var tlength = $(this).val().length; rest = maxchars - parseInt(tlength); $('#remain').text(remain); }); });

(Video) How to Install Wowza Streaming Engine and Run Your First Live Video Stream


1. Connect an RTMP Encoder to Wowza Streaming Engine
2. Live Streaming with Multilingual Audio and Captions Using Wowza Streaming Engine
3. Setup Wowza w Audio
(Andrew Wall)
4. Wowza Streaming Engine REST API
5. Live streaming problems: Troubleshooting tips and fixes
(Epiphan Video)
6. Wowza
(Google Cloud Tech)
Top Articles
Latest Posts
Article information

Author: Melvina Ondricka

Last Updated: 15/04/2023

Views: 5281

Rating: 4.8 / 5 (68 voted)

Reviews: 91% of readers found this page helpful

Author information

Name: Melvina Ondricka

Birthday: 2000-12-23

Address: Suite 382 139 Shaniqua Locks, Paulaborough, UT 90498

Phone: +636383657021

Job: Dynamic Government Specialist

Hobby: Kite flying, Watching movies, Knitting, Model building, Reading, Wood carving, Paintball

Introduction: My name is Melvina Ondricka, I am a helpful, fancy, friendly, innocent, outstanding, courageous, thoughtful person who loves writing and wants to share my knowledge and understanding with you.