Skip to main content
Inspiring
December 9, 2011
Answered

URGENT: FMS 3.5 drops streams

  • December 9, 2011
  • 1 reply
  • 2281 views

Hi,

We've had a licensed FMS 3.5.1 running for a long while now (about 3-4 years). Everything was smooth, until a month ago when a new bug was introduced.

The bug is a little bit vague, and I might now have tracked it correctly, so any advices are highly appreciated.

System Specs:

FMS 3.5.1

Fedora 12

http, mysql, php

1 CPU core,

1 GB RAM

The bug: Suddenly when everything is working fine, all streams gets dropped off... no warnings... and sometimes, streams would start having huge latency, then they would drop off.

Approaches used to solve this problem:

1- I monitored the FMS Console, found that the CPU has high spikes (that reach over 75% for long periods)... so I thought its the CPU and I increased 1 CORE to my server... but the problem didn't go away.

2- Using the top command on Fedora to monitor the CPU and/or RAM, I found that the RAM was almost full (and full in many other times), so I increased another 1GB RAM... but still same problem.. and the 2GB RAMs now get almost full in many times.

3- Reverted changes in my software (thinking that this bug might be caused by a software bug)... but problem stays. Then I put the changes back.

4- Looking into the logs: I find that this line is repeated too many times:

Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 109

Not sure what that means... and couldn't find answers on google... so I was hoping I could find some answers here.

This is so critical as the clients are starting to get frustrated for being disconnected and having to reconnect.

Thanks,

Barjawi

This topic has been closed for replies.
Correct answer Nikhil_Kalyan

Hi,

The FMS seem to have some leakage issue on the build you are using. Can you please update the FMS bits to the lates 3.5.7 ? Its a free maintainance upgrade that should be available @ http://www.stage.adobe.com/support/flashmediaserver/downloads_updaters.html

Let us know if the CPU and memory usage got stable with this build . THank you !

1 reply

Nikhil_Kalyan
Nikhil_KalyanCorrect answer
Participating Frequently
December 12, 2011

Hi,

The FMS seem to have some leakage issue on the build you are using. Can you please update the FMS bits to the lates 3.5.7 ? Its a free maintainance upgrade that should be available @ http://www.stage.adobe.com/support/flashmediaserver/downloads_updaters.html

Let us know if the CPU and memory usage got stable with this build . THank you !

BarjawiAuthor
Inspiring
January 3, 2012

Thank you Nikhil again for your helpful replies... as indicated in my other post here, I wasn't able to upgrade my FMS on Fedora. However, after I switched to CentOs, I was able to install the latest FMS 3.5.7 which works like charm.

So I am not sure whether the switch to CentOS is the solution to my problem, or is it the upgrade of FMS to version 3.5.7. But I guess its fine.

I have one other question though... When monitoring the FMS Console, somtimes I notice CPU spike (the cpu usage goes up to %100 for a second then gets back to normal)... I was wondering if you have any advices on tracking this issue and figuring whether it would cause a problem or not... for now, no problems are occuring because of it, however, I just wanted to be more careful this time.

In addition, in the server log (inside FMS Consol) I see this statement a lot:

Tue 03:04:51 PM: Assert failed in /FlashPlayer6_02_FlashCom/shared_tcserver/tcparser.cpp line 129

which I am not sure what it means and not sure how to track it. Everything still working fine though.

Thanks,

Nikhil_Kalyan
Participating Frequently
January 5, 2012

Hi ,

Good to know that things are in place for you. Regarding CPU usage, 100% should not be hit, please make sure you watch CPU both from the FMS admin console as well as the Task Manager stats (of the OS) to make sure it is indeed spiking.

I vaguely remember hitting that assert statement, but would like to know more about the scenario you tried when you got that error.

Thank you !