Skip to main content
R
rsikoramelo
Participant
May 6, 2009
Question

FMS taking over my processor

  • May 6, 2009
  • 2 replies
  • 3119 views

Hi, for some reason, my Flashmedia3_5_Int_Strm_ALP, after each 24h starts eating my cpu, and my server load rises from 0.10 to 3.50.

All I could find in fms logs is:

2009-05-06    12:40:17    15224    (e)2581395    Failed to signal process condition: errno(43).    -
2009-05-06    12:44:22    4417    (i)2581247    Core (4417) disconnected from edge.    -
2009-05-06    12:45:18    15224    (e)2581395    Failed to signal process condition: errno(22).    -

Couldn't find anything out there. Any good soul can help me at least to understand these error messages.

I'm using Debian Linux 4.0

Thanks

    This topic has been closed for replies.

    2 replies

    T
    techeye
    Participating Frequently
    May 8, 2009

    errno 43 = EIDRM /* identifier removed */

    errno 22 = EINVAL /* invalid argument */

    Can you provide any more info?

    What kernel version is it?  What type of features are you using on the server?  Live? SSAS?  What is the load like?

    A tech note releated to process conditions:

    http://kb2.adobe.com/cps/407/kb407245.html

    R
    rsikorameloAuthor
    Participant
    May 9, 2009

    I did read that tech note, but looks my problem is a bit different, I'm not having issues to create a new process.

    BTW that's my kernel: 2.6.18-5-686-bigmem

    2Gb RAM, it's a quad core server, with load avg around 0.2.

    I do not have more than 10 concurrent connections ot given time on FMS (I'm even using the development-free version yet).

    My application is very simple. It's an audio recorder with RECORD/STOP/PLAY option where the play is just to check what was recorded, the following plays aren't being streamed by FMS.

    That's all I'm using.

    Since I was using the limited version, I was dropping idle connections each 60seconds.

    Thanks, lemme know if u need more information.

    C
    csabyka
    Participant
    May 8, 2009

    same as me. I take question about that problem in adobe support, but no answer. In this case (when this error will usually)

    My solution is stopping fms, empty temp dir, and start fms again.

    R
    rsikorameloAuthor
    Participant
    May 8, 2009

    Yeah, I had to switch back to red5, what's very frustrating.

    At least I hadn't spent some bucks on FMS yet, gonna wait some answers and do more tests before I change again.

    Lemme know if u find an answer to this issue.

    regards

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