Server Freeze with FMS!

[MeenXo]

Hello everyone,

I have created a voice chat with the communication components with Flash MX. I
am running FMS on Windows 2003 Standard Ed Dual Pentium 4 1GB Ram on a T1
Shared line. Every once in a while the server freezes and the only way to
restart is using the Reset button on the server. I know the problem is coming
from FMS because I uninstalled FMS and my server was fine. I checked the CPU
usage and it seems fine. I dont know how else to debug this!

Can someone help me out figure out this problem. Any piece of advice or
information would really help!

Thanks in advance

[FMS_Developer]

Check the mem usage of your FMS service. If it grows fast towards 1 Gb your
server might run out of memory and crash. This might cause the freeze. We
haven't had any instable servers (hardware freezes like you mention) on both
the Linux and Windows platform... This doesn't however mean hardware freezes
aren't possible ofcourse, as your situation shows.

[MeenXo]

Thanks for the reply. Ill keep my eye on the RAM usage and keep everyone who is having the same problem (if any) updated

:)

[MeenXo]

Well I monitored the RAM usage for the past couple of days it ranged from
330-490/2100

So the RAM seems to be fine, I dont know if it gets kicked up all the sudden
then crashes. Is there some type of program I could install to monitor this?
Do you think upgrading RAM will fix the problem?

[Adam Walsworth]

you could use perfmon to monitor ram usage. You should also check out your windows event logs, as well as the fms server logs.

regards,

Adam Walsworth
[url]http://adamwalsworth.com[/url]

[FMS_Developer]

I'm also curious for the logs of the FMS itself ; check the master.00 , core.00
and application.00 logs in the various locations on your hdd. It might show
some errors that you normally don't see.

But, tbh, a real freeze (hardware freeze) which lockups everything, might be
related to bad hardware (or bad drivers). Since FMS doesn't use many drivers
(like the driver of your videocard) I might think it's due to bad ram. If you
are able to change the ram, try to.

Als try to contact Adobe/Macromedia for this problem. They might be interested
in this case.