FileWave Log File Locations
The following lists the locations of log files, as well as some additional files used by FileWave across the FileWave family of products
FileWave Admin
FileWave Admin Logs
| Details | File | Location |
| FileWave Admin Log Logs all FileWave Admin Connection Activity |
FileWaveAdmin.log, FileWaveAdmin.log.* | macOS~/Library/Application Support/FileWave/FileWaveAdmin.logWindows C:\ProgramData\FileWave\FileWaveAdmin.log |
| Client Logs Retrieved Client Logs |
ClientLog_$IP_$Port_$date.log | macOS~/Library/Application Support/FileWave/Client Logs/Windows C:\ProgramData\FileWave\Client Logs\ |
| Server Logs Retrieved Server Logs FileWave Admin > Server > Get Logfile |
fwxserver_$timestamp.log | macOS~/Library/Application Support/FileWave/Server Logs/Windows C:\ProgramData\FileWave\Server Logs\ |
FileWave Admin Files
| Details | File | Location |
| FileWave Admin Settings Settings for the local FileWave Admin App |
macOS
Windows
|
macOS~/Library/Preferences/Windows HKCU\Software\FileWave\FileWave Admin |
| Exported Views Views saved from FileWave Admin: * Views > Export Current View |
Filesets Export ($date).txt | macOS~/Library/Application Support/FileWave/ExportsWindows C:\ProgramData\FileWave\Exports |
FileWave Booster
Booster Logs
| Details | File | Location |
| Booster Log Global Booster activity |
fwbooster.log | macOS/Linux/private/var/log/fwbooster.logWindows C:\ProgramData\FileWave\FWBooster\fwbooster.log |
| NATS NATS Booster Logs |
macOS/Linux
Windows
|
macOS/Linux/private/var/log/Windows C:\ProgramData\FileWave\FWBooster\NATS\nats-booster.log |
| Discovery Log Only exists when discovery configured and run |
macOS/Linux
|
macOS/Linux/private/var/log/fwdiscovery.log |
FileWave Client
FileWave Client Logs
| Details | File | Location |
| Client Logs Global Client activity |
fwcld.log | macOS/var/log/fwcld.logWindows C:\ProgramData\FileWave\FWClient\fwcld.log |
| Kiosk Logs Kiosk application activity |
FWGUI.log | macOS~/Library/Application\ Support/FileWave/FWGUI.logWindows C:\ProgramData\FileWave\FWGUI.log |
| Fileset Script Logs Logs generated by Fileset scripts |
macOS $Fileset_ID/$script_name_from_fileset.log Windows $Fileset_ID\$script_name_from_fileset.log |
macOS/var/log/fwcld/Windows C:\ProgramData\FileWave\log\fwcld\ |
| Custom Field Logs Logs generated by Custom Fields |
custom_field_script.$script_type.log
|
macOS/var/log/fwcld/1/Windows C:\ProgramData\FileWave\log\fwcld\1\ |
| Fileset Blocker Script Logs Logs generated by Blocker Scripts |
blocker_script.$script_type.log
|
macOS/var/log/fwcld/1/Windows C:\ProgramData\FileWave\log\fwcld\1\ |
| Installer (PKG / MSI) Logs Logs generated from PKG/MSI Filesets |
$Fileset_ID.log | macOS/usr/local/etc/FileWaveInstallerLogfiles/Windows C:\ProgramData\FileWave\FileWaveInstallerLogfiles\ |
FileWave Client Files
| Details | File | Location |
| FileWave Client Settings Settings for the FileWave Client |
macOS
Windows
|
macOS/usr/local/etc/Windows HKLM\SOFTWARE\Wow6432Node\Filewave\WinClient |
| FileWave Client Preferences Preference file containing unique client details |
macOS
Windows
|
macOS/Library/Preferences/Windows C:\ProgramData\FileWave\ |
| FileWave Client Certificate Unique certificate & key per client |
|
macOS/var/FileWave/Windows C:\ProgramData\FileWave\FWClient\ |
| Trust Store Store for self-signed certificates |
*.crt | macOS/private/var/FileWave/trust_storeWindows C:\ProgramData\FileWave\FWClient\trust_store |
Cells highlighted in blue indicate files that are unique per client. These files should not be included when copying or migrating clients from one machine to another. To de-personalise a device, without removing the FileWave Client, some files would require editing, whilst others would need to be removed. If it was felt this was a requirement, consider contacting support to assist with this process.
FileWave Imaging Server (IVS)
IVS Logs
| Details | File | Location |
| Django Imaging Server Logs Django logs for requests regarding Serial numbers, names etc. made by netbooted clients |
filewave_imaging_server*.log | /imaging/logs/ |
| Windows Image Upload Logs Captured Windows image uploads |
fwadmin.log | /imaging/logs/fwadmin.log |
| Windows Image Upload Logs Captured Windows image uploads |
fwadmin-dlog.log | /var/log/fwadmin-dlog.log |
| Messages Logs Netboot/PXE Queries & Responses,TFTP transfers, NFS Mounts |
dnsmasq Log |
CentoS
Debian
|
| Apache Imaging Server Logs Apache logs for requests regarding Serial numbers, names etc. made by netbooted clients |
netboot_*.log | /imaging/logs/ |
| Client Imaging Logs Client logs - indicating progress of imaging operation of netbooted clients |
$Serial/$Mac-$Date | /imaging/logs/ |
| FileWave Client Log IVS FileWave Client Log |
fwcld.log | /var/log/fwcld.log |
FileWave Server
FileWave Server Logs
| Details | File | Location |
| Apache Logs Server Apache logs |
|
/usr/local/filewave/apache/logs/ |
| Apache Exporter Logs Server Apache Exporter Logs |
|
/usr/local/filewave/log/ |
| Alert Manager Logs Server Alert Manager logs |
|
/usr/local/filewave/log/ |
| FileWave Admin Audit Logs Audit logs from FileWave Admin |
audit.log | /usr/local/filewave/log/audit.log |
|
FileWave Admin Audit Logs Audit logs from FileWave Admin |
fwaaudit-[date].txt |
/private/var/log/FWAdmin Audit/ |
|
FileWave Dotenv file
Environment variable like configs across services. |
*.env | /usr/local/etc/filewave/.env |
| Django Logs Server Django logs |
|
/usr/local/filewave/log/ |
| LDAP Logs Logs from LDAP |
fwldap.log, fwldap.log.* | /private/var/log/ |
| Software Update Logs Software Update logs |
fwsu.log | /private/var/log/fwsu.log |
| FWX Process Logs Various fwx process logs |
|
/private/var/log/ |
| Migration Logs Server migration logs |
fwxserver-migration-* | /var/log/fwxserver-migration-* |
| Grafana Logs |
|
/usr/local/filewave/log/ |
| Installer Logs Linux installer logs |
install.log | /private/var/log/install.log |
| mtail Logs Server mtail logs |
|
/usr/local/filewave/log/ |
| NATS Logs NATS logs |
|
/usr/local/filewave/log/ |
| Web Admin Logs |
|
/usr/local/filewave/log/ |
| Postgres Exporter Logs |
|
/usr/local/filewave/log/ |
| Postgres Database Logs | postgresql-$day.log | /usr/local/filewave/fwxserver/DB/pg_data/pg_log/*.log |
| Prometheus Logs |
|
/usr/local/filewave/log/ |
| FileWave Server Logs | request_errors.log | /usr/local/filewave/log/ |
| SQL Logs | sql.log | /usr/local/filewave/log/ |
| Update Controller Logs Removed in FileWave 14.10 |
|
/usr/local/filewave/log/ |
| Client Monitor | client-monitor.log | /usr/local/filewave/log/ |
| FileWave Log Messages | task_executor.log | /usr/local/filewave/log/ |
| Scheduler Log Messages | huey.log | /usr/local/filewave/log/ |
Additional Logging
All of the above will default to standard log level. There are 3 levels of logging available:
-
10 – Standard Log Level
-
99 – Debug Log Level
-
101 – Trace Log Level
The level of logging may be set as per our guide:
5 Comments
on my RedHat server (not sure if RedHat is a variable or not), while NATS Booster Logs are located in same directory, they are not listed as:
instead, the there is no wildcard before nats; there should be a wildcard after the word log to capture the full range:
example: nats-booster.err.log nats-booster.err.log.1 nats-booster.err.log.10 nats-booster.err.log.2 nats-booster.err.log.3 nats-booster.err.log.4 nats-booster.err.log.5 nats-booster.err.log.6 nats-booster.err.log.7 nats-booster.err.log.8 nats-booster.err.log.9 nats-booster.log nats-booster.out.log node_exporter.err.log node_exporter.out.log
belatedly, I realize that the wildcard before the filename may be representing the pathname, but placing the wildcard there is confusing, especially with additional logs being created (so wildcards are also needed with some files after the filename).
the separation of filenames from the pathnames may be a good choice in some scenarios, though, one scenario where it is problematic is when a FileWave admin needs to combine both pathnames and filenames together in order to present a unified list of logs that need to be sent to a log server. not knowing the reasons for separating the two elements, I wish I could offer an alternative solution that could possibly work.
In reply to #2
Thanks Sean for these 2 notes. I see what you mean. Will take a look at this.
In reply to #3
Wasn't suppose to be wildcards. An issue from the import from the old KB; they should all be bullet points. Fixed.
In reply to #4
Thanks! :-)