Skip to main content
F
Franck_21
Participating Frequently
February 18, 2009
Question

Core is no longer active

  • February 18, 2009
  • 6 replies
  • 6913 views
Good morning,

We've been running FMS3 for a while and traffic is increasing. For some reason all applications (we have only 2) are disappearing and are being reset by the server every 15mn or so.

In the master logs I am seeing:

2009-02-18 01:31:51 1312 (i)2581223 Core (7744) is no longer active. -

2009-02-18 01:31:51 1312 (w)2581256 Core (7744) _defaultRoot_:::: experienced 1 failure! -

2009-02-18 01:32:15 1312 (i)2581221 Core (7988) started, arguments : -adaptor "_defaultRoot_" -vhost -app -inst -tag -conf "D:\Program Files\Adobe\Flash Media Server 3\conf\server.xml" -name "_defaultRoot_::::".



And the event monitor:

Source: FMS (Edge)
* Event Log: Application
* Type: Warning Event
* Event ID: 1213
* Connection rejected by server. Reason : [ Server.Reject ] : Virtual host is not available.

Any idea how to investigate and fix that?

Thanks
Franck

    This topic has been closed for replies.

    6 replies

    A
    Anonymous
    January 19, 2010

    Hi,

    I had that same problem today!

    I tried then to update my FMS to v3.5.3. Which did not help

    After a while I recognized, that the problem was on client-side. Inside a module I did a SharedObject.getRemote() with an invalid NetConnection (null, actually).When I executed it, i got an error message which was something like "Cannot create SharedObject" and at the same time, my server crashed with the above mentionned message written to the log.

    However, this only happened when I re-loaded the module. (so, first a [ModuleLoader-instance].load(), then unload() and then load() again, and - voilà - I hab my error).

    Somehow my previously used SharedObject got re-used and made everything crash.

    Hope this is helpful to someone.

    Bye

    L
    lipingmu
    Participant
    December 30, 2009

    We  are using FMS v3. We have the same "core is no longer active" problem.

    I have 3 questions:

      

    1.) How to find out the maxCores we are using?

    2.) Can we increase the MaxCores? If yes, how to do that?

    3.) Do we have any other option besides this "work around" way?

    Thanks in advance.

    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    January 4, 2010

    @lipingmu

    Each core failure can happen for a distinct reason.  We can and should evaluate what yours is and what's occuring around it.  If you're still seeing this behavior please give me a direct email and we can determine the source of the problem.  awhilloc@adobe.com.  Also please do update to the most recent FMS 3.5.3 as that has many such crash bugs fixed and could be a quick solution to the problem that you're experiencing.

    Asa

    G
    G-Rem44
    Participating Frequently
    April 15, 2009

    Hi,

    I'ver got the same error message, but I doesn't have any information about the source of the problems in the logs... Just :

    2009-02-18 01:31:51 1312 (i)2581223 Core (7744) is no longer active. -

    2009-02-18 01:31:51 1312 (w)2581256 Core (7744) _defaultRoot_:::: experienced 1 failure! -

    I didn't observe any extra RAM consumtion or anything else. The only things I modified is my new FileAdaptor Plug-In.

    Please help !

    A
    Anonymous
    March 3, 2009
    Will do, Franck.
    Asa_-_FMS
    Adobe Employee
    Asa_-_FMS
    Adobe Employee
    March 3, 2009
    Hi Franck

    No I didn't receive your crash dump. Can you let me know the day that you sent it and I'll see if I can pick it up out of my email file filter. If not, we may need to work our an FTP transfer for this information. Please email me directly to work this out - you can reach me at awhilloc at adobe.com
    F
    Franck21
    Participating Frequently
    March 3, 2009
    Hi Asa

    Glad to hear from you. :) My original email was went on March 2nd at 10:38 ECT. I have just sent it again

    Please confirm receipt. My email is webmaster at 21mediacash.com

    Thanks

    Franck
    A
    Anonymous
    March 3, 2009
    Hi Franck,

    Yes, Asa is the right person to e-mail at Adobe. Thanks for taking the time to get him the information.

    Jody
    F
    Franck21
    Participating Frequently
    March 3, 2009
    Hi Jody,

    Do you mind checking with Asa that he got the info as he has not acknowledged receipt of it?

    Thanks

    Franck
    D
    dejanp777
    Inspiring
    February 20, 2009
    Same thing happens to me on my Flash Media Interactive Server, I hope someone could help with this problem.
    On which OS are you running your FMS? I on Linux Centos.
    F
    Franck_21Author
    Participating Frequently
    February 20, 2009
    Win 2003 SP2, 4GB RAM, 4 proc opteron 280

    I have upgraded to FMS 3.0.2.201 and made the following changes:

    SERVER.FLVCACHE_MAXSIZE=2048

    <AutoCloseIdleClients enable="true">
    <MaxIdleTime>180</MaxIdleTime>
    <IdleTime>10</IdleTime>
    <FLVCacheSize>50</FLVCacheSize>

    <MaxFailures>1</MaxFailures>
    <MaxWriteDelay>20</MaxWriteDelay>

    <RuntimeSize>81920</RuntimeSize>

    Will keep u posted.
    F
    Franck_21Author
    Participating Frequently
    February 22, 2009
    Sadly, not much better

    One thing I noticed looking at RAM graphs through our monitoring tool is that we see patterns of RAM usage gradually reaching 50% then crashing down to 20% in line with the core disconnections.

    Also I have noticed that the RAM load as reported by the administration console is twice the load reported in the task manager.

    Any help out there?

    Thanks

    PS: we are streaming large H264 files (hour+ movies at 1024 kb/s)
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices