Where to find logs
Plugin Log Locations
FileMaker Client
OS X
/Users/userName/Library/Logs/360Plugin Logs/360Plug-ins_XXXXX.log
NOTE: This Library directory is hidden and can be accessed directly by navigating to "~/Library/" using the Go/Go To Folder... menu item or the ⇧⌘G hotkey.
Windows
C:\Users\<username>\360Works\360Plug-ins_XXXXX.log
Temp Logs
Our plugins also write logs to the temp directory. These are helpful for troubleshooting startup errors. These logs will be named after the plugin and will have random characters appended. For example, Scribe will have temp logs that are named something like:
360Works Scribe_6z69q4.log
Windows
C:\Windows\Temp\360Works Scribe_6z69q4.log
Note: We use the %temp% environment variable for this log location, if the default location has changed please check the newly specified location
OSX
/tmp/360Works Scribe_6z69q4.log
Linux
/tmp/360Works Scribe_6z69q4.log
FileMaker Server
Note:Plugins released after May 2017 will write to a log file called 360Plug-ins_Server.log or 360Plug-ins.Web64.log if you are looking for web publishing plugin logs. The location is the same as below.
OS X
/Library/FileMaker Server/Logs/360Plugin Logs/360Plugins_XXXXX.log
Windows
** Logs are appended to where ever FileMaker Server is installed.** **By default or if no FMS is found they are located here C:/Program Files/FileMaker/FileMakerServer** XP or S2003: C:\Documents and Settings\Default User\My Documents\360Plugin Logs\360Plugins_XXXXX.log Vista or S2008: C:\Users\Default User\Documents\360Plugin Logs\360Plugins_XXXXX.log Windows 7/2008R2 C:\Program Files (x86)\FileMaker\FileMaker Server\Logs Plugins released after 5/9/2017 C:\Program Files\FileMaker\FileMaker Server\Logs\360Plugin Logs\360Plugins_Server.log
Note: The 64 bit version of Windows 7/Windows 2008 R2 runs a 32 bit architecture on top of the 64 bit architecture, and system files that need to run in 32 bit compatibility mode are stored in C:\Windows\SysWoW64 instead of C:\Windows\System32
Linux
/opt/FileMaker/FileMaker Server/Logs/360Plugin Logs
Crash Logs
OS X
If the problem involves a crash, we may also need you to send us a crash log. On Macintosh, the crash file is located here:
FileMaker 7: /Users/yourName/Library/Logs/CrashReporter/FileMaker.crash.log FileMaker 8/9: /Users/yourName/Library/Logs/CrashReporter/FileMaker Pro.crash.log
Windows
On Windows, after a crash, sometimes there will be a Java crashlog file on your desktop called hs_err_pidXXXX.log, where the XXXX is a random number.
Windows crash log locations:
C:\Users\[Some User]\Microsoft\Windows\WER\ReportArchive or C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Old plugin log locations
Older builds of 360Works plugins (usually from before 2013) may write log files separately and to different locations than listed above.
On OS X, the logs are normally in the same directories as those listed above, but separated into plugin-specific logs.
On Windows:
C:\Users\yourUserName\My Documents\nameOfPlugin.log C:\Users\yourUserName\AppData\Local\Temp\nameOfPlugin.log C:\Users\yourUserName\AppData\Local\Temp\360temp.log
Web Applications
Often the best way to send us logs for a web application is to use the browser interface to send the logs. If this feature is not working you may need to send the logs manually. Web Applications that run in the 360Works Service will write logs to the same location (with the exception of SuperContainer) unless you select otherwise during installation. Applications should keep several running days of logs and will have the name of your instance(called the product name like Zulu or MirrorSync by default) and a date in the name of the log file. We will often ask you to send us logs that correspond with the date when the issue last occurred. Default log locations are as follows:
Windows
C:\Program Files\360Works\Applications\logs
Mac
Macintosh HD/Library/360Works/Applications/logs
Linux
/var/lib/tomcat9/webapps/logs
SuperContainer
If you need to get the logs for the SuperContainer Companion plugin, please see the instructions for plugins above. If you need to get the logs for the server component of SuperContainer, they will found at the same level as the "Files" folder. Default locations:
Windows
C:\Users\SuperContainer
Mac
/Users/Shared/SuperContainer
Linux
/var/lib/tomcat9/catalina-<date>.log
Setting up log retention
Our plugins keep one running copy of a log file, and when FileMaker restarts (or the FMS Scripting Engine restarts for plugins on the server), the log file is erased and the plugin writes a new one with the same name. If you want to retain multiple copies of plugin log files, you can enable log retention.
Go to the corresponding location, and create a folder named 360FmKit, if it does not already exist. Then inside that folder, create a file called "retain_logs". You can use the terminal command "touch retain_logs" to create the file in that directory. What this will do is set logs to be retained indefinitely. The location will be the same for both local and server plugins.
Windows
Go to C:\ProgramData\360Works\. Then inside that folder, create a file called "retain_logs". You can use the terminal command "touch retain_logs" to create the file in that directory. What this will do is set logs to be retained indefinitely. The location will be the same for both local and server plugins.
Mac
Go to /Library/Application Support, and create a folder named 360FmKit, if it does not already exist. Then inside that folder, create a file called "retain_logs". You can use the terminal command "touch retain_logs" to create the file in that directory. What this will do is set logs to be retained indefinitely. The location will be the same for both local and server plugins.