Knowledge Base

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.

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)

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

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:

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
• Version of PaperCut installed

Categories: Novell, Debugging, Troubleshooting

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

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.