Skip to main content
November 18, 2009
Question

Assertion Error with Flash Media Interactive Server

  • November 18, 2009
  • 1 reply
  • 1171 views

I'm attempting to install and run FMS on a Red Hat Enterprise Linux system.  At one point, it did function properly, but now it will not stream video at all, and I keep getting a constant stream of errors.  No changes were made to the FMS configuration to make it stop working.  Attempting to load it in console mode results in the following:

-bash-3.2$ ./fmsmaster -console
Adobe Flash Media Server (Master)Console mode.
FMS detected IPv6 protocol stack!
FMS config <NetworkingIPv6 enable=false>
FMS running in IPv4 protocol stack mode!
Host: uberserver IPv4: 127.0.0.1
Server starting...
Edge (13199) started, arguments : -edgeports ":1935,80" -coreports "localhost:19350" -conf "/opt/adobe/fms/conf/Server.xml" -adaptor "_defaultRoot_" -name "_defaultRoot__edge1".
Core (13202) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app "registry" -inst "registry" -tag  -console  -conf "/opt/adobe/fms/conf/Server.xml" -name "_defaultRoot_:_defaultVHost_:registry:registry:".
Server started (/opt/adobe/fms/conf/Server.xml).
Adobe Flash Media Server (Core)Console mode.
FMS detected IPv6 protocol stack!
FMS config <NetworkingIPv6 enable=false>
FMS running in IPv4 protocol stack mode!
Host: uberserver IPv4: 127.0.0.1
Assert failed in /util/TCSysUtil.cpp line 683
Assert failed in /util/TCSysUtil.cpp line 683
Assert failed in /util/TCSysUtil.cpp line 683
Assert failed in /util/TCSysUtil.cpp line 683
Assert failed in /util/TCSysUtil.cpp line 683
Assert failed in /util/TCSysUtil.cpp line 683

The assert errors continue until I terminate the process.

    This topic has been closed for replies.

    1 reply

    Asa_-_FMS
    Adobe Employee
    Adobe Employee
    November 19, 2009

    I can look up this assert for you.  What version of FMS are you running please? 

    Asa

    November 19, 2009

    Interactive v3.5

    Asa_-_FMS
    Adobe Employee
    Adobe Employee
    November 19, 2009

    Need some more info than that, down to the specific build number - that's logged at the beginning of each one of your dianostic log files.  So if you go into your logs directory in the FMS install and open master.00.log or its equivalent as so configured - you'll find in the opening preamble of the log file a detailed version number.

    Asa