FSAD_ERROR - Config Router

The File System Access process (fsad) is an internal error message. It is logged each time the File System Access process experiences an access error.

The problem related to this syslog message is described in the following sections:

When an FSAD_ERROR event occurs, it logs the action into the syslog. Below are some examples of the message as it would appear in the syslog output:

fsad[3675]: FSAD_ERROR: main: /var is not mounted on disk, some fsad services will not be available
fsad[2382]: FSAD_ERROR: chargingd_mchild_sigchld_cb: mirroring didn't complete successfully
fsad[13837]: FSAD_ERROR: chargingd_mirror_data: incorrect file/dir name
fsad[3549]: FSAD_ERROR: flowc_logfile_upload: No Flow Collector Transfer Log Archive Sites configured 
fsad[18871]: flowc-upload: no URLs specified:

The cause for such a notification may be due to a target file storage device failure or being offline, or the target file/directory not existing, or some other type of file access error. Also, these log messages are normally observed during the process of Control Board initialization.

The following outputs can be examined to help determine the cause of this message:

show log messages
show chassis hardware detail
show system storage

These outputs can be examined to see what events occurred with or just before this log message. For example, if a component was being reset or if the hard drive is not shown as being present in the chassis, this could explain the cause of the message.

If the error keeps repeating, it is recommended to temporarily record a traceoptions file, if possible, to help find the cause. This can be done by adding the following configuration:

services {
  logging {
    traceoptions {
      file fsad;
      flag connections;
      flag all;
    }
  }
}

Follow these troubleshooting steps to help resolve this issue:

Check the log messages and fsad traceoptions outputs to see if there was an event that would result in the FSAD_ERROR message being generated. This could be a Control Board initialization, or hard drive not accessible message, etc. If so, resolving the cause of the other event may also resolve this issue.
Check the chassis hardware and system storage outputs to verify that the file storage hardware is online and that the target root directories exist.
Run the command, file list <path_to_target>, to verify the file/directory exist and that its parent also exists.
Try to reboot the Routing Engine to resolve the issue.
If the issue is still not resolved, open a case with your technical support representative to investigate the issue further.

Related