How to create AUA debug logs

This article describes how you can create the Automatic Update Agent (AUA) debug logs.

On Windows

  1. Go to [F-Secure Installation Path]\FSAUA\Program.
  2. Locate the fsaua.cfg file. If the file does not exist, create an empty file by using a text editor and save it as fsaua.cfg.
  3. Open fsaua.cfg by using a text editor, and add in the following lines:
  4. Restart the FSAUA service (for PMS) or the FSMA service (for CS/PSB/Server Security).
  5. Upon restart, a new file named fsaua.dbg is created under the path:
    C:\Documents and settings\all users\Application Data\F-Secure\logs\fsaua
    (Windows XP or 2003)
  6. Generate a new FSDIAG file.

Note: In a Policy Manager installation, fsaua.cfg already exists. You only need to modify the value of debug_level to

and restart the FSAUA service. The logs for AUA standard and debug are automatically fetched by FSDIAG.
On Linux
  1. Edit /etc/opt/f-secure/fsaua/fsaua_config with the following entries:
  2. Restart the FSAUA service:
    /etc/init.d/fsaua restart
  3. Generate a new FSDIAG file.
On Mac
  1. Make sure you are logged in with administrator rights. Open Terminal, and type in the following commands:
    1. Save a backup of AUA launchd plist:
      cp /Library/LaunchDaemons/com.f-secure.aua.plist ~/Desktop
    2. Turn off AUA. Note: The GUI will crash at this point but this is to be expected:
      sudo launchctl unload /Library/LaunchDaemons/com.f-secure.aua.plist
    3. Enable the AUA debug logging. The log will be saved to /tmp/fsaua-err.log. This file is deleted upon reboot:
      sudo defaults write /Library/LaunchDaemons/com.f-secure.aua.plist ProgramArguments -array-add -d 99
      sudo defaults write /Library/LaunchDaemons/com.f-secure.aua.plist StandardErrorPath /tmp/fsaua-err.log
    4. Start AUA:
      sudo launchctl load /Library/LaunchDaemons/com.f-secure.aua.plist
    5. Relaunch the UI by double-clicking the app icon in Finder or Launch Pad.