From time to time, PaperCut Technical Support will request additional logs from the CUPS printing environment found on many Linux servers, clients and Mac environments. This will aid PaperCut in diagnosing issues that you may have. This KB article is best used in conjunction with the HowToEnableDebugInThePrintProvider article.
CUPS creates a few log files in the default logs directory (normally /var/log/cups/ for Ubuntu, Debian and macOS). We will want to look at error_log primarily. This is a file where CUPS writes information about what it is doing. However, for this file to be useful to us, we have to enable Debug Logging in CUPS first.
To modify these settings you will likely need root access in a shell or terminal. Once you’ve opened a shell or terminal, you can then elevate yourself to root by “sudo’ing to it” with:
“sudo su -”
This should work on all modern Linux operating systems as well as macOS.
Debian / Ubuntu
Enabling and disabling CUPS debug logging is done via cupsctl
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.