PaperCut has special debug options which cause PaperCut to produce a detailed text log of activity. The log allows our developers to inspect the internal workings of the PaperCut application and pinpoint the cause of problems. Enabling debug logging is only usually required or requested by the PaperCut Support team.
Introduced in PaperCut version 15.0, the Site Server is an optional component which can be deployed to provide resiliency for a distributed deployment. In short, Site Servers can be deployed for each geographically disparate location (with appropriate licensing), each of which is then configured to synchronise with your primary Application Server over a WAN connection. In the event that the Application Server becomes unavailable, be it due to system failure or the WAN link going down, a Site Server will step up to maintain the majority of application services for local users. You can read more about Site Servers here in our online User Manual.
At this stage, the decision has been made that Site Servers will perform debug level logging by default. Debug therefore presently does not need to be manually enabled in order to begin capturing debug level log events. However, these log files will need to be collected manually.
In order to collect debug logs from a Site Server, start by logging on to the machine, opening a file browser, and navigating to the following location, where “[site-path]” is the local PaperCut installation directory:
Identify every file in this directory with a name that begins with “server.log” or “service.log”, e.g.:
… and so on. Make a copy of all these files, and bundle them together into a zip file, ready to be provided to our support team. If in doubt, simply zip up the entire contents of the “logs” directory! These files will probably be too large to email, so ask us to provide you with a link you can use to upload the zip archive to us directly.
Note that if debug logging is required for the Print Provider which runs locally on the Site Server, this will still need to be enabled separately, in the same fashion as for Print Providers running on the Application Server or any Secondary Servers. The instructions for enabling debug for the Print Provider can be found here.
Categories: Debugging, Troubleshooting
Keywords: debug, logging, site, zono