FAMT Daemon crashes frequently - restarting Daemon does not start logging

  • 7012528
  • 31-May-2013
  • 05-Feb-2014

Environment

Novell Filr 1.0

Situation

  • The FAMT Daemon crashes.
  • FAMT is not logging.
  • Uploading files in numerous Active Directory users' home directories, causes FAMT to crash.
  • Attempting to sync Filr with an Active Directory Net Folder via CIFS causes FAMT to crash.
  • "I/O error: Connection refused" when downloading from a Filr Net Folder

Resolution

There are various fixes being investigated and are hoped to be available in the near future.

Workaround:
1)  There are three commands needed to get the FAMT Daemon up and going, along with the logs working, in the following order:
  1. rcnovell-famtd start (used to start the FAMT Daemon)
  2. /usr/bin/killall -HUP syslog-ng (used to restart the logging after the FAMT Daemon is running)
  3. /opt/novell/filr/bin/famtconfig -s loglevel=4 (optional, used to change the loglevel to 4 or another desired level)
2) Ganglia can be enabled to monitor and restart FAMT, if it goes down.  Logging should automatically restart when Ganglia does the restart.  To enable the Ganglia module:
  1. rename the configuration file found at /etc/opt/novell/ganglia/monitor/conf.d/filrfamtd.pyoff to filrfamtd.pyconf.
  2. After making the change, restart ganglia:
    1. /etc/init.d/novell-gmond restart
    2. /etc/init.d/novell-gmetad restart


Status

Reported to Engineering

Feedback service temporarily unavailable. For content questions or problems, please contact Support.