Diagnosing issues with Novell iPrint

PaperCut monitors printing on the Novell iPrint server by being configured as the accounting autoload command within iPrint Manager. This allows PaperCut to monitor and track all printing activity on the iPrint server.

If problems occur after enabling PaperCut on the Novell iPrint server (e.g. problems starting iPrint) some diagnosis will be required.

Is printer redirection or Hardware Page Count not working and iPrint 4.2 or above is being used?

If so, then if you if you have a version of PaperCut NG/MF before 22.0.2 then you may need a new novell-print-provider executable from PaperCut Support. If you have PaperCut NG/MF 22.0.2 or above, and you have recently upgraded from an old version of iPrint (e.g. version 3) to iPrint version 4.2 or above, then you may need to rerun the roottasks script located at: ~papercut/providers/print/linux-x64/roottasks.

Check the autoload command is configured correctly

Verify that the autoload command is set to exactly papercut. Ensure that this is entered all as lower-case, and there are no spaces before or after the command.

Ensure that iprint has permission to the PaperCut files

A common cause of problems are caused by iPrint not having permission to access important PaperCut files.

Verify that iprint has permissions as follows:

  • Read access: ~papercut/providers/print/[platform]/print-provider.conf
  • Write access: ~papercut/providers/print/[platform]/print-provider.log*
  • Write access: ~papercut/providers/print/[platform]/*

Check the Novell iPrint logs (ispsmd.log) and system log

If there are problems starting the PaperCut autoload command, this will be reported in the ispmd.log located in:


Check this log for any obvious error messages relating to the papercut autoload command.

Collecting diagnostic information for PaperCut Support

If the above does not help resolve the problem, report the issue to PaperCut support.

It’s generally advisable to first enable debug logging (see here), reproduce the problem and then send the following information to PaperCut support:

Important: The iPrint Manager needs to be restarted!

Zip and send the following log files:

  • /var/opt/novell/log/iprint/ipsmd.log
  • /var/opt/novell/log/iprint/novell-print-provider.log
  • ~papercut/providers/print/[platform]/print-provider.log*

Also send the following information:

  • Description of the problem
  • Version of Novell OES / iPrint (rpm -qa novell-iprint-server)
  • Version of PaperCut installed

Collecting diagnostic information for Novell Support

If we need to further escalate this problem to Novell, then more information will be needed.

Please get the output of the iPrint Information gathering script from your iPrint Server. The script is available from: http://www.novell.com/communities/node/5705/iprint-information-gathering-tool

Turn on debug logging from the health monitor in the Printer Manager. Follow the menus:

Novell Manager → Manager health monitor → Advanced iPrint Manager Information → Debug Options → Debug Screen Options.

Enable all of the options other than “errPause” and get the debug.log

Categories: Troubleshooting Articles, Novell

keywords: novell, iprint, ipsmd, crash, hang, start, restart, oes, troubleshooting