How to Enable Debug in Lexmark Devices

KB Home   |   How to Enable Debug in Lexmark Devices

Main.LexmarkDebug History

Hide minor edits - Show changes to output

June 23, 2011, at 07:57 AM by 202.129.124.120 -
Changed lines 17-26 from:
'''5.''' Now perform the problem action.  Try to select a situation that is likely to ''cause'' the issue being investigated such as a copy off the glass or a reboot.

'''6.''' Record the approximate time of the problem and/or the name of the user logging in.  This will help the developers match up log entries with your test activity.  Additional information such as what was observed or what was expected would also be useful.

'''7.''' Go back to the SE menu as above: [@http://<device-ip>/se@]

'''8.''' Click "Embedded Solutions"

'''9.''' Click "Log File". Copy & paste the text into an email to PaperCut support.
to:
'''5.''' Reboot the device.

'''6.''' Now perform the problem action.  Try to select a situation that is likely to ''cause'' the issue being investigated such as
a copy off the glass or a reboot.

'''7.''' Record the approximate time of the problem and/or the name of the user logging in.  This will help the developers match up log entries with your test activity.  Additional information such as what was observed or what was expected would also be useful.

'''8.''' Go back to the SE menu as above: [@http://<device-ip>/se@]

'''9.''' Click "Embedded Solutions"

'''10.''' Click "Log File". Copy & paste the text into an email to PaperCut support.
April 07, 2010, at 01:04 AM by 202.129.124.120 -
Changed lines 13-14 from:
'''3.''' Click "Set Loggin Level"
to:
'''3.''' Click "Set Logging Level"
April 07, 2010, at 12:06 AM by 202.129.124.120 -
Changed line 9 from:
'''1.''' Access the "SE" menu by using a browser going to the URL: [@http://<device-ip>/se@], where <device-ip> is the IP address of the Lexmark device. Note the ending "/se" attached to the URL.
to:
'''1.''' Access the "SE" menu by using a web browser to go to the URL: [@http://<device-ip>/se@], where <device-ip> is the IP address of the Lexmark device. Note the ending "/se" attached to the URL.
April 06, 2010, at 11:59 PM by 202.129.124.120 -
Changed lines 13-16 from:
'''3.''' Click "Log Level"

'''4.''' Click "Yes" and "Submit" and "Back".
to:
'''3.''' Click "Set Loggin Level"

'''4.''' Click "Yes" and "Submit".
April 06, 2010, at 11:58 PM by 202.129.124.120 -
Changed lines 1-2 from:
(:title How to Enable Debug in the Print Provider :)
to:
(:title How to Enable Debug in Lexmark Devices :)
Changed lines 5-13 from:
The '''enable debug''' option causes PaperCut to produce a detailed text log of activity.  The log allows our developers to inspect the internal workings of the PaperCut application and pinpoint the cause of problems.  Enabling debugging is only usually required if requested by the PaperCut Support team.

The ''Print Provider'' is the component in PaperCut n-tiered architecture that interfaces with the print queues.  It is the layer closest to the printers and hence debug here can help diagnose monitoring related problems.

!!To enable debug in PaperCut Print Provider:

'''1.''' Open the file:
->[@[app-path]/providers/print/[platform]/print-provider.conf@]
->in a text editor
.
to:
The '''debug''' option causes a Lexmark device to produce a detailed text log of activity.  The log allows our developers to inspect the internal workings of the PaperCut application and pinpoint the cause of problems.  Enabling debugging is only usually required if requested by the PaperCut Support team.

!!To enable debug in Lexmark devices:

'''1.''' Access the "SE" menu by using a browser going to the URL: [@http://<device-ip>/se@], where <device-ip> is
the IP address of the Lexmark device. Note the ending "/se" attached to the URL.
Changed lines 11-32 from:
'''2.''' Under the line [@#debug=on@] add the line:
->[@debug=on@]
-->or

->[@debug=snapshot@] (if directed by support)
Or simply remove the [@#@] comment from
the existing line.

'''3.''' Save the file.
 
'''4.''' Some components may need to be restarted before debug logging is enabled.
* '''If running Windows''': restart the ''PaperCut Print Provider'' Service under '''Control Panel -> Administrative Tools -> Services'''.
* '''If running Novell iPrint''': restart the ''Print Manager'' from iManager.
* No restarts are required on Mac or Linux CUPS.

'''5.''' Print a few test documents from a network workstation, or perform the problem action
.  Try to select a situation that is likely to ''cause'' the issue being investigated.

'''6.''' Record the approximate time of the problem and/or the name of any printed documents (or the time you performed the test action).  This will help the developers match up log entries with your test activity.  Additional information such as what was observed or what was expected would also be useful.
 
'''7.''' Zip and email the file:

            @@[app-path]/providers/print/[platform]/print-provider.log@@


to:
'''2.''' Click "Embedded Solutions" near the bottom.

'''3.''' Click "Log Level"

'''4.''' Click "Yes" and "Submit" and "Back".

'''5.''' Now perform
the problem actionTry to select a situation that is likely to ''cause'' the issue being investigated such as a copy off the glass or a reboot.

'''6.''' Record the approximate time of the problem and/or the name of the user logging in.  This will help the developers match up log entries with your test activity.  Additional information such as what was observed or what was expected would also be useful.

'''7.''' Go back
to the SE menu as above: [@http://<device-ip>/se@]

'''8.''' Click "Embedded Solutions"

'''9.''' Click "Log File". Copy & paste the text into an email to PaperCut support.
Deleted lines 28-31:
->'''Note:''' if the files are large, please place in a zip archive before sending.

'''8.''' Disable logging by reversing step 2.

April 06, 2010, at 11:47 PM by 202.129.124.120 -
Added lines 1-44:
(:title How to Enable Debug in the Print Provider :)

''Please also see [[ReportingProblems|+]]''

The '''enable debug''' option causes PaperCut to produce a detailed text log of activity.  The log allows our developers to inspect the internal workings of the PaperCut application and pinpoint the cause of problems.  Enabling debugging is only usually required if requested by the PaperCut Support team.

The ''Print Provider'' is the component in PaperCut n-tiered architecture that interfaces with the print queues.  It is the layer closest to the printers and hence debug here can help diagnose monitoring related problems.

!!To enable debug in PaperCut Print Provider:

'''1.''' Open the file:
->[@[app-path]/providers/print/[platform]/print-provider.conf@]
->in a text editor.
 
'''2.''' Under the line [@#debug=on@] add the line:
->[@debug=on@]
-->or
->[@debug=snapshot@] (if directed by support)
Or simply remove the [@#@] comment from the existing line.
 
'''3.''' Save the file.
 
'''4.''' Some components may need to be restarted before debug logging is enabled.
* '''If running Windows''': restart the ''PaperCut Print Provider'' Service under '''Control Panel -> Administrative Tools -> Services'''. 
* '''If running Novell iPrint''': restart the ''Print Manager'' from iManager.
* No restarts are required on Mac or Linux CUPS.

'''5.''' Print a few test documents from a network workstation, or perform the problem action.  Try to select a situation that is likely to ''cause'' the issue being investigated.

'''6.''' Record the approximate time of the problem and/or the name of any printed documents (or the time you performed the test action).  This will help the developers match up log entries with your test activity.  Additional information such as what was observed or what was expected would also be useful.
 
'''7.''' Zip and email the file:

            @@[app-path]/providers/print/[platform]/print-provider.log@@


->Include an explanation of the steps taken, along with any other other information requested by the PaperCut Developers.

->'''Note:''' if the files are large, please place in a zip archive before sending.

'''8.''' Disable logging by reversing step 2.

----
''Categories:'' [[Category.Debugging|+]], [[Category.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.

Article last modified on June 23, 2011, at 07:57 AM
Printable View   |   Article History   |   Edit Article