Troubleshooting the PaperCut Print Deploy Cloner

Refer to this article for any problems with the Print Deploy Cloner tool.

Print Deploy Cloner logs

Your PaperCut support contact might request that you share the logs from the Print Deploy Cloner tool. These logs are now automatically collected when you share the Diagnostic Bundle from your PaperCut NG or MF server.

These logs can also be collected manually from the reference computer, if you know where to look.

Windows: pc-print-deploy-cloner-<timestamp>.log, stored in the same directory you ran the cloner tool from
macOS: pc-print-deploy-cloner-<timestamp>.log, stored in /tmp

For more details on Print Deploy logging, refer to Finding the Print Deploy logs for troubleshooting .

Cloned Driver Bundles

The zipped bundle for the driver and other files may be requested by your PaperCut support contact for troubleshooting.

The cloner keeps a copy of these files on the reference computer.

Windows: [host]-[os]-[arch]-[epoch].zip, stored in the same directory you ran the cloner tool from
MacOS: [host]-[os]-[arch]-[epoch].zip, stored in /tmp for Mac OS
Linux: [host]-[os]-[arch]-[epoch].zip, stored in /tmp for Linux

Cloner troubleshooting


Issue	Some of the print queues in my reference computer did not get cloned (Windows)
Cause	The Windows cloner tool excludes some printers when cloning for various reasons.
Log file lines to look out for	`2019-07-19-14:11:14 SUPPO cloner_windows.go:182 printer 'Adobe PDF Converter' is not a real one. not cloned`The printer is not a real (for example, Adobe PDF Converter) printer.
	`2019-07-19-14:11:14 SUPPO cloner_windows.go:191 printer 'KONICA MINOLTA Universal PS v3.4' uses a WSD port. not cloned`The printer uses an unsupported port, for example, a WSD port.
	`2019-07-19-14:11:14 ERROR cloner_windows.go:172 printer 'FX L1' has driver 'FX C3450 d' with no inf file. not cloned`The printer driver does not have an INF file. For now, Print Deploy doesn’t support drivers that do not have INF files.Seen with some Fuji Xerox drivers that were installed using the installer. A workaround is to extract the driver package and install the driver using Windows ‘Add Printer’ dialog.


Issue	I can’t see any of the print queues I just cloned.
Cause	The cloner tool failed to connect to the Application Server to upload print queues.
Log file lines to look out for	`2019-07-19-14:40:30 ERROR main.go:131 failed to initialise uploader: server not reachable: dial tcp 10.100.1.1:9174: i/o timeout or 2019-07-19-15:36:18 ERROR main.go:131 failed to initialise uploader: dial tcp: lookup l-ranganathg: no such host`Before the cloner starts, it checks if the server is reachable. In most cases, if there’s no connectivity the cloning will fail at the beginning with this log entry.
	2019-07-19-14:44:27 ERROR uploader.go:114 upload failed on attempt 3 of 3. error: Post https://10.100.1.1:9174/deploy/upload: dial tcp 10.100.1.1:9174: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.``2019-07-19-14:44:27 ERROR uploader.go:122 upload failed after 3 attempts 2019-07-19-14:44:58 ERROR main.go:195 failed to upload package file l-ranganathg-win-amd64-1563511387.zip. error: HTTPRetryClient: request cancelledIn the rare case the connection to the server gets lost after the cloning starts, the cloner will retry three times before giving up.
	`Failed to upload the zip file to the server. File saved to C:\Work\Code\pc-printer-cloner\l-ranganathg-win-amd64-1563511387.zip`If the cloned printer bundle fails to upload, the cloner will write this log entry and also display an error in the terminal (Macs) or command prompt (Windows)


Issue	I receive an error message about otool and developer path?
Cause	The cloner tool requires a working version of the `otool` library on macOS.
Cloner console lines to look out for	`Failed to clone: error while cloning print queues: failed to collect driver-related dynamic link libraries for "print-queue": failed to get a list of depdent files for "/Filename": failed to run /usr/bin/otool, output=xcrun: error: invalid active developer path (/Library/Developer/Com: exit status 1.` To resolve, run `xcode-select --install` in terminal. If the above does not resolve the issue, run `xcode-select --reset` in terminal.


Issue	Error when running cloner on macOS says “Too many open files”
Cause	Mac and Linux operating systems have a limit to the number of allowed files open at any given time.
Cloner console lines to look out for	`Failed to clone: error while cloning print queues: collect drivers: failed to copy driver-related files: failed to copy printer specific files: failed to copy PPD for MY_FAV_PRINTER: failed to copy: : open /dev/null: too many open files. Saving session...`To resolve, open Terminal as administrator and increase the open file limit with the command`sudo launchctl limit maxfiles`Then run the PaperCut Print Deploy Cloner tool again.


Issue	Error when running cloner on Windows says “failed to set up cloner: failed to get host OS info: failed to find command”
Cause	Previous versions of the Print Deploy Cloner prior to August 2024 relied on the Windows Management Instrumentation (WMI) service and would result in this error if the service was not running. The quickest solution is to log into the web interface of the PaperCut server as an admin navigate to the Print Deploy section and download the latest version of the cloner tool for Windows.
Log file lines to look out for	`2024-10-12-23:36:07 ERROR main.go:219 failed to set up cloner: failed to get host OS info: failed to find command`

Problem with a specific print driver

Having trouble with specific print driver? Report it to us using the Print Deploy issue report form .

Print Deploy logs

Still having issues? Check out how to collect the Print Deploy logs for troubleshooting .

Here’s your answer

Did this solve your issue?

Oops!