Skip to main content
October 17, 2008
Question

FMS stuck on full CPU usage

  • October 17, 2008
  • 1 reply
  • 860 views
Hi,

We are hosting a FMS3 server on a Redhat EL5. The Redhat EL5 is fully patched with Red Hat Network, and the version on the FMS server is FMS3_0_2_r217. We are running the server a few months without any problems so far. There are about 30 vhosts active on the server.

Today the load of the server increased by a lot, and we saw a process called 'fmscore' taking all CPU power (200%). When I restarted the server, the problem returned. When I went to the logs folder I saw the following entries:

-rw-rw---- 1 3188489 Oct 17 11:31 core.00.log
-rw-rw---- 1 10487959 Oct 17 11:30 core.01.log
-rw-rw---- 1 10487978 Oct 17 11:30 core.02.log
-rw-rw---- 1 10486128 Oct 17 11:29 core.03.log
-rw-rw---- 1 10520479 Oct 17 11:11 core.04.log
-rw-rw---- 1 10505753 Oct 17 11:11 core.05.log

You notice the time-stamps are within minutes from each other, and each logfile is 10mb in size. When I opened the logfile, I got the following messages:

2008-10-17 11:30:15 9407 (e)2581279 Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 109 -
2008-10-17 11:30:15 9407 (e)2581279 Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 109 -
2008-10-17 11:30:15 9407 (e)2581279 Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 109 -
2008-10-17 11:30:15 9407 (e)2581279 Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 109 -

This was set about 1000 times per second.

Does anyone know what can be the cause of this behavior, and know what the solution might be to prevent this from happening?

Cheers
Nstuff
    This topic has been closed for replies.

    1 reply

    Participating Frequently
    October 20, 2008
    The server is trying to parse bad data. What are those 30 vhosts doing in their application code?
    December 22, 2008
    Hey I'm facing the same issue. Can you tell me what is your definition of bad data for FMS server. Also is there any problem sending Arraycollection to FMS?
    Participating Frequently
    December 31, 2008
    Bad data is that which cannot be parsed because it is not in the expected format.

    When using an "Arraycollection" this message could be produced by incorrectly mixing AMF0 with AMF3 data types; I would check this first. Another reason for this message is that a variable exceeds the memory limit imposed on the data type.

    Try to identify a minimal test case and report back with what you find.