Media Flow Controller Logs : FMSEdge Log (fmsedgelog)

FMSEdge Log (fmsedgelog)
FMSEdge Log is used for diagnostic purposes and displays transactions to the FMS edge server; for example, “Connection rejected by server,” “Edge disconnected from core,” “Listener started for clients.” This log is generated by the FMS server (must be installed, see “Installing and Using Flash Media Server (FMS) in Media Flow Controller” on page 99). This log is written to /nkn/adobe/fms/logs/edge.<nn>.log, by default (you can access this using application fms shell). See fmsedgelog for CLI details. See “Configuring Service Logs” on page 132 for implementation details.
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 for descriptions of all message ID.
x-ctx—Event dependent context information
Example:
2010-05-27 09:57:23 13826 (i)2581173 Host: QA10 IPv4: 127.0.0.1 -
2010-05-27 09:57:23 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4 -
2010-05-27 09:57:23 13826 (i)2581252 Registering core (13829). -
2010-05-27 09:57:24 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) : 1935/v4 -
2010-05-27 09:57:24 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) : 8888/v4 -
2010-05-27 09:58:29 13826 (i)2581252 Registering core (14959). -
2010-05-27 10:28:34 13826 (i)2581250 Edge disconnected from core (14959).
 

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.