Skip to main content
_
__BLACKCREEK__
Participant
July 16, 2012
Question

core no longer active

  • July 16, 2012
  • 1 reply
  • 916 views

I am having an issue with my Flash Media Server.  I have an application that works as a video conference system using FMS 4.0.  A few days ago it stopped connecting the two sides.  Rebooting the server fixed the problem, but this has happened before so we know it will come up again.  I was looking at the log files to see if I could find the problem. There wasn't any error messages directly related to the connection issue, but there were lots off errors about memory and core failures.  I posted some of the log lines below.  These are from today so they don't have anything to do with the connection problem, but I am wondering if this is the start of the problem.  Has anyone experienced this or have an idea to what is going on?

2012-07-16 08:41:36 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 08:41:42 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 08:54:10 1484 (i)2581221 Core (5804) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_2" -conf "C:\Program Files\Adobe\Flash Media Server 4\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_2". -

2012-07-16 08:54:13 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:01:09 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:01:09 1484 (i)2581223 Core (5804) is no longer active. -

2012-07-16 09:01:09 1484 (w)2581256 Core (5804) _defaultRoot_:_defaultVHost_:::_2 experienced 1 failure! -

2012-07-16 09:01:19 1484 (i)2581221 Core (5816) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_2" -conf "C:\Program Files\Adobe\Flash Media Server 4\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_2". -

2012-07-16 09:01:21 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:02:05 1484 (i)2581223 Core (5816) is no longer active. -

2012-07-16 09:02:05 1484 (w)2581256 Core (5816) _defaultRoot_:_defaultVHost_:::_2 experienced 1 failure! -

2012-07-16 09:02:05 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:02:13 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:04:16 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:12:30 1484 (i)2581221 Core (5696) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_2" -conf "C:\Program Files\Adobe\Flash Media Server 4\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_2". -

2012-07-16 09:12:31 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:12:46 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:12:46 1484 (i)2581223 Core (5696) is no longer active. -

2012-07-16 09:12:46 1484 (w)2581256 Core (5696) _defaultRoot_:_defaultVHost_:::_2 experienced 1 failure! -

2012-07-16 09:13:17 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:13:21 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:13:28 1484 (w)2581171 System memory load (91) is high. -

2012-07-16 09:31:03 1484 (i)2581221 Core (5436) started, arguments : -adaptor "_defaultRoot_" -vhost "_defaultVHost_" -app  -inst  -tag "_1" -conf "C:\Program Files\Adobe\Flash Media Server 4\conf\server.xml" -name "_defaultRoot_:_defaultVHost_:::_1". -

2012-07-16 09:32:05 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:32:08 1484 (w)2581171 System memory load (94) is high. -

2012-07-16 09:32:09 1484 (i)2581172 System memory load (90) is now below the maximum threshold. -

2012-07-16 09:43:42 1484 (i)2581223 Core (5436) is no longer active. -

2012-07-16 09:43:42 1484 (w)2581256 Core (5436) _defaultRoot_:_defaultVHost_:::_1 experienced 1 failure! -

    This topic has been closed for replies.

    1 reply

    S
    ShivenK
    Inspiring
    July 17, 2012

    Hi,

    It seems that the memory used by the fmscore is increasing. This can happen when the Server memory is low or when the core has been up for days.

    The core is designed to shut down when the memory consumption rises above a threshold. These log messages are indicative of that.

    Can you gather some memory consumption data as well?

    To best counteract this, I recommend that you check the <Distribute numprocs=""></Distribute> setting in Application.xml and set this to split the cores according to your needs.

    Thanks,

    Shiven

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices