Frequently Asked Questions

Red5 Pro server logging is generally set to INFO or WARN with a release, but you can increase logging levels to get more details towards troubleshooting problems. CAUTION: higher logging levels can reduce server performance. If you are debugging your production environment, you may also want to set a rolling log policy to ensure that your disk doesn’t fill. Note that logging is directed to {red5pro}/log/red5.log file by default.

Logging levels are set in the {red5pro}/conf/logback.xml file.

If you want to update logging across the board, then you can change the root level from INFO to debug

  <root level="INFO">

    <appender-ref ref="CONSOLE"/>

    <appender-ref ref="FILE"/>

  </root>

to

  <root level="DEBUG">

    <appender-ref ref="CONSOLE"/>

    <appender-ref ref="FILE"/>

  </root>

Most other loggers in this file have descriptions. So, for example, if you were having issues with your Stream Manager, you might want to change 

  <!-- Streammanager debugging -->

   <logger name="com.red5pro.services.streammanager" level="WARN" />

to

  <!-- Streammanager debugging -->

   <logger name="com.red5pro.services.streammanager" level="DEBUG" />

And there are multiple points where you can increase logging for WebRTC issues.

  <!-- WebRTC entry point -->

  <logger name="com.red5pro.webrtc.websocket.listener.JSONDataListener" level="WARN"/>

<!-- RTC base connection -->

  <logger name="com.red5pro.webrtc.RTCConnection" level="WARN"/>




  <!-- RTC publisher transformer  -->

  <logger name="com.red5pro.webrtc.stream.RTCSourceStream" level="WARN"/>




  <!-- RTC subscriber Side stream performing transform to webrtc format-->

  <logger name="com.red5pro.webrtc.stream.FlashToRTCTransformerStream" level="WARN"/>




  <!-- SideStream consumer routes packets to socket-->

  <logger name="com.red5pro.webrtc.stream.RTCBroadcastStream" level="WARN"/>




  <!-- Core WebRTC related loggers -->

  <logger name="javax.media" level="WARN"/>

  <logger name="net.sf.fmj" level="WARN"/>




  <logger name="org.ice4j" level="WARN"/>




  <logger name="org.jitsi" level="WARN"/>




  <logger name="com.red5pro.jmfext.protocol.rtc" level="WARN"/>

  <logger name="com.red5pro.media.transform.codec.LibraryLoader" level="WARN"/>

  <logger name="com.red5pro.webrtc.util.CandidateParser" level="WARN"/>

  <logger name="com.red5pro.webrtc.service" level="WARN"/>

More complete logging information will help support troubleshoot your issues as well.

FYI: logging levels from least to most verbose:

• OFF
• ERROR
• WARN
• INFO
• DEBUG
• TRACE