Choose your language

Choose your login


Troubleshooting the PaperCut Print Deploy Cloner

This page applies to:

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

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

IssueSome of the print queues in my reference computer did not get cloned (Windows)
CauseThe Windows cloner tool excludes some printers when cloning for various reasons.
Log file lines to look out for2019-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.
IssueI can’t see any of the print queues I just cloned.
CauseThe cloner tool failed to connect to the Application Server to upload print queues.
Log file lines to look out for2019-07-19-14:40:30 ERROR main.go:131 failed to initialise uploader: server not reachable: dial tcp 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 dial tcp 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 error: HTTPRetryClient: request cancelled

In 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\

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)
IssueI receive an error message about otool and developer path?
CauseThe cloner tool requires a working version of the `otool` library on macOS.
Cloner console lines to look out forFailed 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.
IssueError when running cloner on macOS says "Too many open files"
CauseMac and Linux operating systems have a limit to the number of allowed files open at any given time.
Cloner console lines to look out forFailed 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.

Problem with a specific print driver

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

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