Capturing a Novell Spool file

KB Home   |   Capturing a Novell Spool file

Main.CapturingANovellSpoolFile History

Hide minor edits - Show changes to output

November 09, 2012, at 04:26 AM by ian - standardise with other spool file articles
Changed lines 3-5 from:
PaperCut Support may ask you to supply a print-to-file or a spool file. This is a little more difficult on the Novell/Linux platform and involves "capturing" a spool file using one of the following procedures:

to:
PaperCut Support may ask you to supply a spool file. This is a little more difficult on the Novell/Linux platform and involves "capturing" a spool file using one of the following procedures:

Changed lines 28-29 from:
and email to support.
to:
and email to [[mailto:support@papercut.com|PaperCut Support]].
Changed lines 52-53 from:
'''8.''' Email support the spool file that you saved.
to:
'''8.''' Email a zipped copy of the spool file that you saved to [[mailto:support@papercut.com|PaperCut Support]].

See also:

* [[PageCountProblems|+]]
* [[CapturingAWindowsSpoolFile|+]]
* [[MacSpoolFile|+]]
* [[CapturingALinuxSpoolFile|+]]

Changed line 64 from:
[-keywords: novell linux print to file -]
to:
[-keywords: novell linux print to file -]
November 09, 2011, at 07:05 AM by tim - snapshot method shouldn't require stopping the printer
Changed lines 14-19 from:
'''2.''' Temporarily stop the printer, or turn off the printer so that jobs hold in the queue. Print a job, or set of jobs that demonstrates the problem behavior. This printing may be performed from a workstation.

'''3.''' Print a problem document the demonstrates the issue and wait for it to spool.

'''4
.''' As root on the PaperCut server, enter the command:
to:
'''2.''' Print a problem document that demonstrates the issue and wait for it to spool.

'''3.'''
As root on the PaperCut server, enter the command:
Changed lines 22-25 from:
'''5.''' Repeat the 3 and 4 again as required to demonstrate the issue.

'''6.''' Compress the [@*.spl@] files in the root home directory as well as
to:
'''4.''' Repeat the 2 and 3 again as required to demonstrate the issue.

'''5.''' Compress the [@*.spl@] files in the root home directory as well as
Changed lines 6-7 from:
!! Snapshot Method (available in release after 11.4)
to:
!! Snapshot Method (available from release 11.5)
Changed lines 6-7 from:
!! Snapshot Method (available release after 11.4)
to:
!! Snapshot Method (available in release after 11.4)
Changed lines 6-7 from:
!! Snapshot Method
to:
!! Snapshot Method (available release after 11.4)
Changed lines 6-7 from:
!! Automated Script
to:
!! Snapshot Method
Changed line 59 from:
[-keywords: linux print to file -]
to:
[-keywords: novell linux print to file -]
Changed lines 34-35 from:
'''1.''' Enable debug (or leave on snapshot) level logging in the Print Provider layer by adding the line:
to:
'''1.''' Enable debug (or leave on snapshot from above) level logging in the Print Provider layer by adding the line:
Added line 41:
Added line 43:
Added line 45:
Added line 51:
Added line 53:
September 12, 2011, at 01:23 AM by tim - add text about capturing a spool file on Novell
Added lines 1-54:
(:title Capturing a Novell Spool file:)

PaperCut Support may ask you to supply a print-to-file or a spool file. This is a little more difficult on the Novell/Linux platform and involves "capturing" a spool file using one of the following procedures:


!! Automated Script

'''1.''' Enable snapshot level debug logging in the Print Provider layer by adding the line:

->[@debug=snapshot@]

to the file at [@~papercut/providers/print/linux-[arch]/print-provider.conf@]

'''2.''' Temporarily stop the printer, or turn off the printer so that jobs hold in the queue. Print a job, or set of jobs that demonstrates the problem behavior. This printing may be performed from a workstation.

'''3.''' Print a problem document the demonstrates the issue and wait for it to spool.

'''4.''' As root on the PaperCut server, enter the command:

->[@cp /tmp/spool-snapshot.spl ~/10-pages-grayscale.spl@]

->(Note: Replace 10-pages-grayscale.spl with an appropriate name).

'''5.''' Repeat the 3 and 4 again as required to demonstrate the issue.

'''6.''' Compress the [@*.spl@] files in the root home directory as well as

-> [@~papercut/providers/print/linux-[arch]/print-provider.log@]

and email to support.

!! Manual Method

'''1.''' Enable debug (or leave on snapshot) level logging in the Print Provider layer by adding the line:

->[@debug=on@]

to the file at [@~papercut/providers/print/linux-[arch]/print-provider.conf@]

'''2.''' Temporarily pause the printer output, by going to the problem printer in Novell Manage Printer
'''3.''' Click on Pause Output
'''4.''' Issue a print job to the problem printer
'''5.''' Look for lines of the form "Analysis results from spool file..." in

-> [@~papercut/providers/print/linux-[arch]/print-provider.log@]

'''6.''' Using the spool file path that you found in the log file, copy the spool file to somewhere appropriate.
'''7.''' Go back to the Novell Manage Printer page and click on "Resume Output"
'''8.''' Email support the spool file that you saved.

----
''Categories:'' [[Category.Troubleshooting|+]]
----
[-keywords: linux print to file -]

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.

Article last modified on November 09, 2012, at 04:26 AM
Printable View   |   Article History   |   Edit Article