Viewing The Fmsedge Log; Fmsconnector Log / Fuselog - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
fmsedgelog
page 226
fmsedgelog
copy <SCP>
filename <filename>
on-the-hour {disable | enable}
rotate {filesize-MB <integer> | time-interval <integer>}
syslog
The FMSEdge log provides this information:
•
Date—Date of the event
•
Time—Time of the event
•
x- pid—Server process ID
•
x-status—The code is category and message ID (i) information and message id. See
Flash Media Server Diagnostic Log Messages
•
x-ctx—Event dependent context information
Example:
2010-05-27 09:57:23
2010-05-27 09:57:23
localhost:19350/v4
2010-05-27 09:57:23
2010-05-27 09:57:24
1935/v4
2010-05-27 09:57:24
8888/v4
2010-05-27 09:58:29
2010-05-27 10:28:34

Viewing the FMSEdge Log

To view the Media Flow Controller FMSEdge log:
•
Web interface—Media Flow Controller FMSEdge log entries are available for viewing on
the Web interface Logs tab, FMSEdge Log page.
•
CLI—To upload the fmsedgelog, run upload fmsedgelog scp://<URL>. Now you can
access the FMSEdge log at the specified system, move it (if needed) and view its
contents. See

FMSConnector Log / fuselog

The Media Flow Controller FMSConnector Log records RTSP transaction details including
what URIs are accessed and how many bytes are returned by the FUSE module. This log is
generated by Media Flow Controller. See
Flow Controller Service Logs (CLI)" on page 226
for CLI details. See
for implementation details.
13826 (i)2581173
13826 (i)2631174
-
13826 (i)2581252
13826 (i)2631174
-
13826 (i)2631174
-
13826 (i)2581252
13826 (i)2581250
"Terminology" on page 30
Configuring and Using Media Flow Controller Logs and Alarms
"Configuring Media Flow Controller Service Logs (CLI)" on
for descriptions of all message ID.
Host: QA10 IPv4: 127.0.0.1
Listener started ( _defaultRoot__edge1 ) :
Registering core (13829).
Listener started ( _defaultRoot__edge1 ) :
Listener started ( _defaultRoot__edge1 ) :
Registering core (14959).
Edge disconnected from core (14959).
for the scp URL format and requirements.
fuselog for CLI details. See
for implementation details.
-
-
-
"Configuring Media
FMSConnector Log / fuselog 219