Log Locations - 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.

Applications keep several days of logs. Each log file has the name of your instance (the product name, like Zulu or MirrorSync, by default) and a date in its name. We will often ask you to send us logs from the date when the issue last occurred.

MirrorSync 7.1 and later run in their own service, "360Works Jakarta", and write their logs to the JakartaApplications folder. Other 360Works web applications, and MirrorSync 7.0 and earlier, run in the "360Works" service and share the Applications folder. SuperContainer keeps its logs in a different place. See SuperContainer log locations.

Default log locations are as follows:

OSX

MirrorSync 7.1 and later:
Macintosh HD/Library/360Works/JakartaApplications/logs

Other web applications, and MirrorSync 7.0 and earlier:
Macintosh HD/Library/360Works/Applications/logs

Windows

MirrorSync 7.1 and later:
C:\Program Files\360Works\JakartaApplications\logs

Other web applications, and MirrorSync 7.0 and earlier:
C:\Program Files\360Works\Applications\logs

Linux

MirrorSync 7.1 and later:
/var/lib/360works/JakartaApplications/logs

Other web applications, and MirrorSync 7.0 and earlier:
/var/log/tomcat9
OR
/var/lib/tomcat9/webapps/logs

Service logs (MirrorSync 7.1 and later)

If MirrorSync does not start at all, the "360Works Jakarta" service writes its own logs here:

Mac: Macintosh HD/Library/360Works/JakartaInternal/Logs
Windows: C:\Program Files\360Works\JakartaInternal\Logs
Linux: /var/lib/360works/JakartaInternal/Logs