Skip to main content
November 20, 2006
Question

FMS 2.0.3 + RHEL4 + NetApp NFS = bork bork bork

  • November 20, 2006
  • 2 replies
  • 359 views
All:

Operating a low traffic FMS (<50 concurrent connections) whose sole task in life is to accept incoming FLV audio streams and record them to disk. The store it places these on is mounted to a NetApp FAS3020C via NFS v2. The disks are a 150 gig fiberchannel raid6 array connected via gigE.

Every 3 weeks or so, the FMS quits being able to write any data to the NFS mount, and the fmsadmin applet reports the CPU as bound at 100%. Logging into the RHEL4 machine hosting FMS (and nothing else) reports cpu load at or near 0.00, and the NFS array functioning normally (can add, remove files to the store from the command line).

Any ideas? The application in question needs shared read-only access to the files that FMS creates, and occasionally purges those files by deleting them from the store (once per day, any files in the app_name/streams directory that is over 8 hours old).

Thanks for the help,
-tom
    This topic has been closed for replies.

    2 replies

    November 24, 2006
    Could you find any useful information about the 'problems' in the logs (core.00 , master.00 and application.00 etc etc ? )

    I'd also suggest to have a look at the configuration parameters in your Application.xml file.

    Check out [MaxTimeOut] (jsengine) [MaxCores] [Lifetime] [RollOver] and [WriteBuffSize] and read the descriptions in the docs, they might be useful for your situation.
    November 30, 2006
    Thanks -- I'll look into it.

    The only glaring error I see is:

    2006-11-24 23:17:10 2799 (i)2581241 Connection to admin received. -
    2006-11-24 23:17:10 2799 (i)2581243 Connection from core 20403 received. -
    2006-11-24 23:17:10 2799 (i)2581244 Connection from core 20403 accepted. -
    2006-11-24 23:17:49 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:18:49 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:19:49 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:20:49 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:21:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:22:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:23:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:24:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:25:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:26:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:27:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -
    2006-11-24 23:28:50 2799 (e)2581279 Assert failed in /server/admin/FCSAdminServer.cpp line 361 -

    This continues until CPU goes crazy. The only thing that corrects it is shutting down the FMS, unmounting the NFS store, remounting, and starting up again. Strange, no?

    I'm thinking that I may just be forced to export the filesystems locally instead of writing to a store. I'm hoping this will help things.

    Thanks!
    -Tom
    November 20, 2006
    I should mention that the fms itself is hosted on local storage, via the usual /opt path. The nfs mount is at the application level -- /opt/macromedia/fms/applications/p_razz in this instance points to /mnt/p_razz where the nfs is locally mounted.