Known Issues with PaperCut on Novell OES Linux iPrint

KB Home   |   Known Issues with PaperCut on Novell OES Linux iPrint

Main.KnownIssuesOnOESLinuxiPrint History

Hide minor edits - Show changes to output

March 27, 2019, at 04:36 AM by Mel Zouzoulas - Updated to mention the support web form
Changed lines 423-424 from:
* '''Update 14th April 2009''' - The Novell iPrint team have released a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
* '''Update 17th June 2009
''' -  The Novell iPrint team have again supplied us with a new set of patches.  Again we are able to supply on request.  Please email support@papercut.com for more information and details on how to access patch!
to:
* '''Update 14th April 2009''' - The Novell iPrint team have released a patch, however it is yet to make it out via official channels.  Please reach out via (http://support.papercut.com) for more information and details on how to access the "unofficial" patch!
*
'''Update 17th June 2009''' -  The Novell iPrint team have again supplied us with a new set of patches.  Again we are able to supply on request.  Please reach out via (http://support.papercut.com) for more information and details on how to access patch!
December 10, 2018, at 07:05 AM by TimG - Updated to new format
Changed lines 5-100 from:
!!PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018

From PaperCut 18.2.3, the novell-print-provider was built on an OES 2018 machine which made it incompatible for older versions of iPrint and SLES (such as any of the existing iPrint appliances). This was due to a glibc incompatibility between versions of SLES. PaperCut's novell-print-provider will be fixed in 18.2.6 and a hotfix for an earlier release can be provided on request.

!!PaperCut Application Server fails to start on OES 2018

OES 2018 has moved to use ''systemd'' and as part of ''systemd'', PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the ''papercut'' group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the ''papercut'' group to be created.

!!Novell iPrint does not support the restart of held print jobs

If ipsmd is restarted then any held jobs remain in held/pending state in the iPrint queue. They are not reheld by PaperCut. The jobs will show in the iPrint queue but not in PaperCut.

!!PaperCut's iPrint Print Provider does not support Email to Print or Google Cloud Print

Currently, PaperCut's iPrint accounting agent (Print Provider) does not support processing of "spooled jobs" which are a queue of jobs to print which PaperCut uses for Email to Print and Google Cloud Print.

!!Print jobs fail to appear in the jobs pending release list

In some situations, jobs sent to a hold and release queue will fail to show up in the jobs pending release list. The PaperCut print provider service will get the pre-notification message which should be followed relatively immediately by the Novell print provider stating it created the job. However, the job-create message eludes the PaperCut print provider for some reason.

As it turns out, these are symptoms of the workstation's remote renderer not communicating correctly with the iPrint Appliance. To confirm this, launch the spool file directory on the iPrint Appliance and check whether job submission generates only a PDF file without its spool file counterpart. If the spool file is missing, please re-install the remote render software on the affected workstation. A customer report confirmed that re-installing the remote renderer restored full communication to the iPrint Appliance and correctly generated the job's corresponding PDF and spool files.

!! Slow printing from MS Office when iPrint queues contain many jobs.

When using PaperCut with hold/release queues or find-me printing, the iPrint queues may contain many jobs awaiting release.  When printing from Microsoft Office (e.g. Microsoft Word) the application queries the status of all the print jobs in the queue.  Novell iPrint takes a long time to respond to these queries resulting in slowness in the MS Office print dialogs from appearing.

This affects all versions of iPrint up to and including OES 6.3 [=SP3=].

Novell are aware of the issue and have raised an internal bug (#700160).

As of 2nd December 2011, Novell have notified us they have a fix in testing for this problem.  If you would like access to this fix, please contact Novell Support and reference the bug #700160.

This fix is expected to be included in upcoming Novell iPrint releases.

!!Special "debug" versions of iPrint will not work with PaperCut
In some situations Novell support engineers will install a special debug version of iPrint.  Debug versions of iPrint are not compatible with the autoload command provided by PaperCut.  The main behaviour observed is that the iPrint ipsmd services will not start after [@papercut@] is added to the ''autoload'' command.

To run PaperCut with a debug version of iPrint, PaperCut needs to be recompiled with special debug flags against the matching debug version.  If you're working with the Novell support team to diagnose an issue and PaperCut needs to be enabled during this diagnostic, please contact our support team.  We'll look into the possibility of supplying a matching compatible debug version of PaperCut.

!!Warning to customers running HP `ToolboxFX status tool
Some large sites running PaperCut on Novell OES Linux has seen high iPrint (ipsmd) CPU usage if network has HP printers are the HP `ToolboxFX status tool has been deployed along with the driver.  It seems like this tool excessively "pings" the printer for status information and does not scale well across large networks.  The solution is to deploy the standard network driver only (no extra tools).

!!Cluster resource script configuration
Sites running PaperCut on an OES Cluster who are upgrading to version 10.5+ may need to update their cluster resource scripts after upgrade. The installer should warn you. To summarize, change the line:
    exit_on_error /etc/init.d/papercutcups start
To
    exit_on_error /etc/init.d/papercut-event-monitor start
[-(This service was renamed as it now does more than just CUPS management - it also does server connection monitoring for the new event resend feature.)-]


!!Crash bug in iPrint (ipsmd) on `OES2 Linux `SP2

The default iPrint that ships with `OES2 Linux `SP2 contains a bug where after enabling PaperCut via the ''Accounting autoload command'' iPrint may crash after receiving a print job.

!!!Symptoms:
* Jobs do not print after enabling PaperCut on the printer
* Errors may appear in the iPrint logs (ipsmd.log)


!!!Known Workarounds:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture. (the version should be novell-iprint-server-6.2.20100414-0.4 or later)

!!Rare crash bug in iPrint (ipsmd) on `OES2 Linux `SP1

The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator canceling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.

!!!Symptoms:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716 (0x506D0012)
* Errors may appear in the iPrint logs (ipsmd.log)
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process (this is because the parent process has died and left us in a zombie/orphaned state as explained [[http://en.wikipedia.org/wiki/Zombie_process|here]]).

!!!Known Workarounds:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]]

!!User identity security problem

Some PaperCut sites have reported an issue where the wrong username being logged against jobs in PaperCut. This issue was tracked down an iPrint bug where the iPrint client software is not correctly flushing the iPrint client cache.  Novell have a guide on how to 'resolve' the issue (clear iPrint's cache on logout) TID 7005753 .  We hope an official fix will be available soon.

!!!Symptoms:
* Jobs are identified in PaperCut under the wrong username.

!!!Known Workarounds:
* See Novell TID 7005753.

!! NWUSERNAME is no longer available in Windows 7 and Windows Vista

!!! Symptoms:
* Logon scripts that utilize the NWUSERNAME variable no longer work properly.
* PaperCut's User Client is reporting the wrong username.

!!! Workarounds:
* Use the following command to set the variable:
 
--> SET NWUSERNAME = "%CN"

More information is available from the [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7006517&sliceId=1&docTypeID=DT_TID_1_1&dialogID=230670142&stateId=0%200%20230668540|Novell website]].
to:
PaperCut is fully committed to helping customers and partners make the best use of our technology.  A key part of that is transparency and full disclosure of issues that may affect how well the solution works for you.  Unfortunately, with complex modern technology (often supplied by different organizations) there is no way to address all problems and issues immediately but keep checking back to see if we have fixed something.  If something is causing you particular concern please contact [[https://www.papercut.com/contact/|support]].

Changed lines 9-52 from:
!!General Discussion/Comments (History)

* '''Update 14th April 2009''' - The Novell iPrint team have released a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
* '''Update 17th June 2009''' -  The Novell iPrint team have again supplied us with a new set of patches.  Again we are able to supply on request.  Please email support@papercut.com for more information and details on how to access patch!
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  The following hotfix may be applied to existing 9.x installs:

      su - papercut
      cd ~
      tar -zcf pre-fix-backup.tgz providers/print/linux-*
      wget https://www.papercut.com/anonftp/pub/pcng/previews/novell-oes-hotfix-2009-06-24.tgz
      tar -zxf novell-oes-hotfix-2009-06-24.tgz
      su - root
      /home/papercut/providers/print/linux-x64/roottasks

->Then restart The iPrint Print Manager or simply restart the server to apply.

* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 

* '''Update 14th August 2009''' - Novell have decided to make the 20090731-1 available as an official patch.  That's the version we've tested in house with great promise.  Should be available in the next few days. I'll post an update here.

* '''Update 11th September 2009''' - Hooray!  Looks like we've finally found and fixed the remaining race-condition related bugs.  We've put some additional synchronization logic in our code and also the iPrint team has done the same.  We were seeing some issues on customer sites running on some very fast multi-processor systems and the latest round of fixes has addressed these issues.  Novell are going to make the update available as an official update/hotfix soon.  If you're running on a fast multi-core/processor system and need access to the fix now, please email us at support.

* '''Update October 2009''' - Latest 9.6 release of PaperCut with latest iPrint patches have proved to be very stable with no issues reported on the high volume sites.  We've also now got PaperCut running on clustered iPrint servers.  Official cluster setup documentation will be incorporated into the 9.7 release.  If you require early access to cluster support, please email us at support.

* '''Update October 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.  More information here under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1&dialogID=103124059&stateId=1%200%2057898768|TID 7004872]].

* '''Update 28th October  2009''' - PaperCut now works on [=OES=] Linux clusters.  9.7 will include official setup documentation however if you require early access, please email us at support.

* '''Update November 2009''' - There seems to be a regression [=OES2=] [=SP2=].  After upgrading, some customers have reported that the iPrint server crashes.  We're working with Novell to resolve this issue.  In the meantime we recommend sticking to [=SP1=] and delaying any upgrade.

* '''Update December 2009''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  Customer's running `SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch available, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

* '''15th January 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now available under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].

* '''24th April 2010''' - Novell have issued another iPrint update under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  I added some extra locking and rate-limiting to our code a while back to work around the problems this update fixes so it was rare for live sites to see this problem under normal load.  I still however recommend the update.

* '''29th September 2010''' - Added new iPrint issue related to user identity issue discussed in [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005753|TID 7005753]].

* '''21st February 2011''' - Updated website to indicate support for Novell [=OES2=] Linux [=SP3=] after internal testing and no reported problems.

* '''15th March 2012''' - Fixed possible crashing in PaperCut with handling of long document names (around 1K and larger) when debug logging is used. This will be incorporated into the upcoming release of PaperCut 12.2.


The PaperCut development team working on the [[https://www.papercut.com/|print control solution for Novell iPrint]] will continue to post updates here as they become available.
to:

(:comment ***** Issues Table - use class=resolved or class=unresolved on the Status cells to alter the text colour **************************************************** :)

(:table border=1 width=100% cellspacing=5 class=issues :)

(:cellnr :)
'''Issue ID'''
(:cell :)
'''Description'''
(:cell :)
'''Reported in'''
(:cell :)
'''Status'''
(:cell :)
'''Resolved in'''
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
PC-14440
(:cell class=description :)
PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018.
\\
[[#iPC-14440| More info...]]
(:cell :)
18.2.3
(:cell class=resolved :)
Resolved
(:cell :)
18.2.6
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
PC-13510
(:cell class=description :)
PaperCut Application Server fails to start on OES 2018.
\\
[[#iPC-13510| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
18.3.2
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
PC-9026
(:cell class=description :)
Novell iPrint does not support the restart of held print jobs.
\\
[[#iPC-9026| More info...]]
(:cell :)
All
(:cell class=unresolved :)
Open
(:cell :)
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
PC-11612
(:cell class=description :)
PaperCut’s iPrint Print Provider does not support Email to Print or Google Cloud Print.
\\
[[#iPC-11612| More info...]]
(:cell :)
All
(:cell class=unresolved :)
Open
(:cell :)
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45952
(:cell class=description :)
Print jobs fail to appear in the jobs pending release list.
\\
[[#iU-45952| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Workaround
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45951
(:cell class=description :)
Slow printing from MS Office when iPrint queues contain many jobs.
\\
[[#iU-45951| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
2011 OES\\
update
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45950
(:cell class=description :)
Special “debug” versions of iPrint will not work with PaperCut.
\\
[[#iU-45950| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Workaround
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45949
(:cell class=description :)
Warning to customers running HP ToolboxFX status tool.
\\
[[#iU-45949| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Workaround
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45948
(:cell class=description :)
Cluster resource script configuration.
\\
[[#iU-45948| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Workaround
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45947
(:cell class=description :)
Crash bug in iPrint (ipsmd) on OES2 Linux SP2.
\\
[[#iU-45947| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Updated\\
iPrint build
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45946
(:cell class=description :)
Rare crash bug in iPrint (ipsmd) on OES2 Linux SP1
\\
[[#iU-45946| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Updated\\
iPrint build
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45945
(:cell class=description :)
User identity security problem
\\
[[#iU-45945| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Updated\\
iPrint build
(:comment ******************************  New Issue Row  **************************************************** :)
(:cellnr :)
U-45944
(:cell class=description :)
NWUSERNAME is no longer available in Windows 7 and Windows Vista
\\
[[#iU-45944| More info...]]
(:cell :)
All
(:cell class=resolved :)
Resolved
(:cell :)
Workaround
(:tableend:)

\\

Other known issues, not specific to the Toshiba Embedded solution are covered in:
* [[KnownIssues|Known issues with PaperCut NG and MF]]



Changed lines 206-220 from:
''Categories:'' [[Category.Novell|+]], [[Category.KnownIssues|+]]
to:



[[#iPC-14440]]

\\
\\

!!!PC-14440: PaperCut NG/MF 18
.2.3 for iPrint does not work on anything other than OES 2018

From PaperCut 18.2.3, the novell-print-provider was built on an OES 2018 machine which made it incompatible for older versions of iPrint and SLES (such as any of the existing iPrint appliances). This was due to a glibc incompatibility between versions of SLES. PaperCut’s novell-print-provider will be fixed in 18.2.6 and a hotfix for an earlier release can be provided on request.

Note: Fixed in 18.2.6

Added lines 222-471:

[[#iPC-13510]]

\\
\\

!!!PC-13510: PaperCut Application Server fails to start on OES 2018

OES 2018 has moved to use systemd and as part of systemd, PaperCut runs the Application Server as the group “papercut”. The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the papercut group needs to be added to the system. On other Linux systems, the PaperCut instructions cause the papercut group to be created.

Note: Fixed in the documentation with 18.3.2

----

[[#iPC-9026]]

\\
\\

!!!PC-9026: Novell iPrint does not support the restart of held print jobs

If ipsmd is restarted then any held jobs remain in held/pending state in the iPrint queue. They are not reheld by PaperCut. The jobs will show in the iPrint queue but not in PaperCut.

----

[[#iPC-11612]]

\\
\\

!!!PC-11612: PaperCut’s iPrint Print Provider does not support Email to Print or Google Cloud Print

Currently, PaperCut’s iPrint accounting agent (Print Provider) does not support processing of “spooled jobs” which are a queue of jobs to print which PaperCut uses for Email to Print and Google Cloud Print.


----

[[#iU-45952]]

\\
\\

!!!U-45952: Print jobs fail to appear in the jobs pending release list

In some situations, jobs sent to a hold and release queue will fail to show up in the jobs pending release list. The PaperCut print provider service will get the pre-notification message which should be followed relatively immediately by the Novell print provider stating it created the job. However, the job-create message eludes the PaperCut print provider for some reason.

As it turns out, these are symptoms of the workstation’s remote renderer not communicating correctly with the iPrint Appliance. To confirm this, launch the spool file directory on the iPrint Appliance and check whether job submission generates only a PDF file without its spool file counterpart. If the spool file is missing, please re-install the remote render software on the affected workstation. A customer report confirmed that re-installing the remote renderer restored full communication to the iPrint Appliance and correctly generated the job’s corresponding PDF and spool files.


----

[[#iU-45951]]

\\
\\

!!!U-45951: Slow printing from MS Office when iPrint queues contain many jobs.

When using PaperCut with hold/release queues or find-me printing, the iPrint queues may contain many jobs awaiting release. When printing from Microsoft Office (e.g. Microsoft Word) the application queries the status of all the print jobs in the queue. Novell iPrint takes a long time to respond to these queries resulting in slowness in the MS Office print dialogs from appearing.

This affects all versions of iPrint up to and including OES 6.3 SP3.

Novell are aware of the issue and have raised an internal bug (#700160).

As of 2nd December 2011, Novell have notified us they have a fix in testing for this problem. If you would like access to this fix, please contact Novell Support and reference the bug #700160.

This fix is expected to be included in upcoming Novell iPrint releases.


----

[[#iU-45950]]

\\
\\

!!!U-45950: Special “debug” versions of iPrint will not work with PaperCut

In some situations Novell support engineers will install a special debug version of iPrint. Debug versions of iPrint are not compatible with the autoload command provided by PaperCut. The main behaviour observed is that the iPrint ipsmd services will not start after @@papercut@@ is added to the autoload command.

To run PaperCut with a debug version of iPrint, PaperCut needs to be recompiled with special debug flags against the matching debug version. If you’re working with the Novell support team to diagnose an issue and PaperCut needs to be enabled during this diagnostic, please contact our support team. We’ll look into the possibility of supplying a matching compatible debug version of PaperCut.


----

[[#iU-45949]]

\\
\\

!!!U-45949: Warning to customers running HP ToolboxFX status tool

Some large sites running PaperCut on Novell OES Linux has seen high iPrint (ipsmd) CPU usage if network has HP printers are the HP ToolboxFX status tool has been deployed along with the driver. It seems like this tool excessively “pings” the printer for status information and does not scale well across large networks. The solution is to deploy the standard network driver only (no extra tools).


----

[[#iU-45948]]

\\
\\

!!!U-45948: Cluster resource script configuration

Sites running PaperCut on an OES Cluster who are upgrading to version 10.5+ may need to update their cluster resource scripts after upgrade. The installer should warn you. To summarize, change the line:

From:
  @@exit_on_error /etc/init.d/papercutcups start@@

To:
  @@exit_on_error /etc/init.d/papercut-event-monitor start@@

(This service was renamed as it now does more than just CUPS management - it also does server connection monitoring for the new event resend feature.)


----

[[#iU-45947]]

\\
\\

!!!U-45947: Crash bug in iPrint (ipsmd) on OES2 Linux SP2


'''Symptoms''':
* Jobs do not print after enabling PaperCut on the printer
* Errors may appear in the iPrint logs (ipsmd.log)


'''Known Workarounds''':
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture. (the version should be novell-iprint-server-6.2.20100414-0.4 or later)


----

[[#iU-45946]]

\\
\\

!!!U-45946: Rare crash bug in iPrint (ipsmd) on OES2 Linux SP1

The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator canceling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.

'''Symptoms''':
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716 (0x506D0012)
* Errors may appear in the iPrint logs (ipsmd.log)
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process (this is because the parent process has died and left us in a zombie/orphaned state as explained [[http://en.wikipedia.org/wiki/Zombie_process|here]]).

'''Known Workarounds''':
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]]


----

[[#iU-45945]]

\\
\\

!!!U-45945: User identity security problem

Some PaperCut sites have reported an issue where the wrong username being logged against jobs in PaperCut. This issue was tracked down an iPrint bug where the iPrint client software is not correctly flushing the iPrint client cache.  Novell have a guide on how to 'resolve' the issue (clear iPrint's cache on logout) TID 7005753 .  We hope an official fix will be available soon.

'''Symptoms''':
* Jobs are identified in PaperCut under the wrong username.

'''Known Workarounds''':
* See Novell TID 7005753.



----

[[#iU-45944]]

\\
\\

!!!U-45944: User identity security problem

'''Symptoms''':
* Logon scripts that utilize the NWUSERNAME variable no longer work properly.
* PaperCut's User Client is reporting the wrong username.

'''Workarounds''':
* Use the following command to set the variable:
 
--> SET NWUSERNAME = "%CN"

More information is available from the [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7006517&sliceId=1&docTypeID=DT_TID_1_1&dialogID=230670142&stateId=0%200%20230668540|Novell website]].

\\
\\
\\


----
!!General Discussion/Comments (History)

* '''Update 14th April 2009''' - The Novell iPrint team have released a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
* '''Update 17th June 2009''' -  The Novell iPrint team have again supplied us with a new set of patches.  Again we are able to supply on request.  Please email support@papercut.com for more information and details on how to access patch!
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  The following hotfix may be applied to existing 9.x installs:

      su - papercut
      cd ~
      tar -zcf pre-fix-backup.tgz providers/print/linux-*
      wget https://www.papercut.com/anonftp/pub/pcng/previews/novell-oes-hotfix-2009-06-24.tgz
      tar -zxf novell-oes-hotfix-2009-06-24.tgz
      su - root
      /home/papercut/providers/print/linux-x64/roottasks

->Then restart The iPrint Print Manager or simply restart the server to apply.

* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 

* '''Update 14th August 2009''' - Novell have decided to make the 20090731-1 available as an official patch.  That's the version we've tested in house with great promise.  Should be available in the next few days. I'll post an update here.

* '''Update 11th September 2009''' - Hooray!  Looks like we've finally found and fixed the remaining race-condition related bugs.  We've put some additional synchronization logic in our code and also the iPrint team has done the same.  We were seeing some issues on customer sites running on some very fast multi-processor systems and the latest round of fixes has addressed these issues.  Novell are going to make the update available as an official update/hotfix soon.  If you're running on a fast multi-core/processor system and need access to the fix now, please email us at support.

* '''Update October 2009''' - Latest 9.6 release of PaperCut with latest iPrint patches have proved to be very stable with no issues reported on the high volume sites.  We've also now got PaperCut running on clustered iPrint servers.  Official cluster setup documentation will be incorporated into the 9.7 release.  If you require early access to cluster support, please email us at support.

* '''Update October 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.  More information here under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1&dialogID=103124059&stateId=1%200%2057898768|TID 7004872]].

* '''Update 28th October  2009''' - PaperCut now works on [=OES=] Linux clusters.  9.7 will include official setup documentation however if you require early access, please email us at support.

* '''Update November 2009''' - There seems to be a regression [=OES2=] [=SP2=].  After upgrading, some customers have reported that the iPrint server crashes.  We're working with Novell to resolve this issue.  In the meantime we recommend sticking to [=SP1=] and delaying any upgrade.

* '''Update December 2009''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  Customer's running `SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch available, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

* '''15th January 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now available under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].

* '''24th April 2010''' - Novell have issued another iPrint update under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  I added some extra locking and rate-limiting to our code a while back to work around the problems this update fixes so it was rare for live sites to see this problem under normal load.  I still however recommend the update.

* '''29th September 2010''' - Added new iPrint issue related to user identity issue discussed in [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005753|TID 7005753]].

* '''21st February 2011''' - Updated website to indicate support for Novell [=OES2=] Linux [=SP3=] after internal testing and no reported problems.

* '''15th March 2012''' - Fixed possible crashing in PaperCut with handling of long document names (around 1K and larger) when debug logging is used. This will be incorporated into the upcoming release of PaperCut 12.2.


The PaperCut development team working on the [[https://www.papercut.com/|print control solution for Novell iPrint]] will continue to post updates here as they become available.


----
''Categories:'' [[Category.Novell|+]], [[Category.KnownIssues|+]]
----

Added lines 12-15:

!!Novell iPrint does not support the restart of held print jobs

If ipsmd is restarted then any held jobs remain in held/pending state in the iPrint queue. They are not reheld by PaperCut. The jobs will show in the iPrint queue but not in PaperCut.
October 17, 2018, at 07:56 PM by Aaron Pouliot - Added category - Known Issues
Changed line 143 from:
''Categories:'' [[Category.Novell|+]]
to:
''Categories:'' [[Category.Novell|+]], [[Category.KnownIssues|+]]
Changed line 7 from:
From PaperCut 18.2.3, the novell-print-provider was built on an OES 2018 machine which made it incompatible for older versions of iPrint and SLES (such as any of the existing iPrint appliances). This was due to a glibc incompatibility between versions of SLES. PaperCut's novell-print-provider will be fixed in 18.2.6.
to:
From PaperCut 18.2.3, the novell-print-provider was built on an OES 2018 machine which made it incompatible for older versions of iPrint and SLES (such as any of the existing iPrint appliances). This was due to a glibc incompatibility between versions of SLES. PaperCut's novell-print-provider will be fixed in 18.2.6 and a hotfix for an earlier release can be provided on request.
Changed line 5 from:
!!!PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018
to:
!!PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018
September 24, 2018, at 01:38 AM by Tim Shimmin - Add info about issue with iPrint agent on 18.2.3 and above.
Added lines 4-7:

!!!PaperCut NG/MF 18.2.3 for iPrint does not work on anything other than OES 2018

From PaperCut 18.2.3, the novell-print-provider was built on an OES 2018 machine which made it incompatible for older versions of iPrint and SLES (such as any of the existing iPrint appliances). This was due to a glibc incompatibility between versions of SLES. PaperCut's novell-print-provider will be fixed in 18.2.6.
March 28, 2018, at 11:33 PM by Tim Shimmin - mention that we don't support GCP or email-to-print on Novell
Added lines 8-11:

!!PaperCut's iPrint Print Provider does not support Email to Print or Google Cloud Print

Currently, PaperCut's iPrint accounting agent (Print Provider) does not support processing of "spooled jobs" which are a queue of jobs to print which PaperCut uses for Email to Print and Google Cloud Print.
March 28, 2018, at 04:23 AM by Tim Shimmin -
Changed line 7 from:
OES 2018 has moved to use ''systemd'' and as part of ''systemd'' PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the ''papercut'' group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the ''papercut'' group to be created.
to:
OES 2018 has moved to use ''systemd'' and as part of ''systemd'', PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the ''papercut'' group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the ''papercut'' group to be created.
March 28, 2018, at 04:22 AM by Tim Shimmin -
Changed lines 5-7 from:
!!PaperCut Application Server fails to start with OES 2018

OES 2018 has moved to systemd and as part of systemd PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the "papercut" group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the "papercut" group to be created.
to:
!!PaperCut Application Server fails to start on OES 2018

OES 2018 has moved to use ''systemd'' and as part of ''systemd'' PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the ''papercut'' group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the ''papercut'' group to be created.
March 28, 2018, at 01:42 AM by Tim Shimmin - Talk about issue on OES 2018
Added lines 4-7:

!!PaperCut Application Server fails to start with OES 2018

OES 2018 has moved to systemd and as part of systemd PaperCut runs the Application Server as the group "papercut". The group that is used for running the services is specified in /etc/systemd/system/pc-app-server.service. This file either needs to be modified to refer to an existing group or the "papercut" group needs to be added to the system. On other Linux systems, the PaperCut  instructions cause the "papercut" group to be created.
December 15, 2017, at 01:36 AM by Arturo - added remote render Iprint appliance communication issues
Added lines 4-9:

!!Print jobs fail to appear in the jobs pending release list

In some situations, jobs sent to a hold and release queue will fail to show up in the jobs pending release list. The PaperCut print provider service will get the pre-notification message which should be followed relatively immediately by the Novell print provider stating it created the job. However, the job-create message eludes the PaperCut print provider for some reason.

As it turns out, these are symptoms of the workstation's remote renderer not communicating correctly with the iPrint Appliance. To confirm this, launch the spool file directory on the iPrint Appliance and check whether job submission generates only a PDF file without its spool file counterpart. If the spool file is missing, please re-install the remote render software on the affected workstation. A customer report confirmed that re-installing the remote renderer restored full communication to the iPrint Appliance and correctly generated the job's corresponding PDF and spool files.
Changed lines 3-4 from:
This page lists known issues or bugs with PaperCut (print control/quotas) on [[https://www.papercut.com/news/papercut-on-novell-oes-linux-iprint/|Novell OES Linux]].
to:
This page lists known issues or bugs with PaperCut (print control/quotas) on Novell OES Linux.
March 15, 2012, at 06:37 AM by tim - add info about v_copy bug with long document names
Changed lines 120-122 from:
to:
* '''15th March 2012''' - Fixed possible crashing in PaperCut with handling of long document names (around 1K and larger) when debug logging is used. This will be incorporated into the upcoming release of PaperCut 12.2.

Changed lines 18-19 from:
In some situations Novell support engineers will install a special debug version of iPrint.  Debug versions of iPrint are not compatible with the autoload command provided by PaperCut.  The main behaviour observed is that the iPrint ipsmd services will not start after [@papercut@} is added to the ''autoload'' command.
to:
In some situations Novell support engineers will install a special debug version of iPrint.  Debug versions of iPrint are not compatible with the autoload command provided by PaperCut.  The main behaviour observed is that the iPrint ipsmd services will not start after [@papercut@] is added to the ''autoload'' command.
January 29, 2012, at 10:56 PM by 202.129.124.120 -
Changed lines 17-18 from:

to:
!!Special "debug" versions of iPrint will not work with PaperCut
In some situations Novell support engineers will install a special debug version of iPrint.  Debug versions of iPrint are not compatible with the autoload command provided by PaperCut.  The main behaviour observed is that the iPrint ipsmd services will not start after [@papercut@} is added to the ''autoload'' command.

To run PaperCut with a debug version of iPrint, PaperCut needs to be recompiled with special debug flags against the matching debug version.  If you're working with the Novell support team to diagnose an issue and PaperCut needs to be enabled during this diagnostic, please contact our support team.  We'll look into the possibility of supplying a matching compatible debug version of PaperCut.

Changed lines 115-117 from:
* '''21st February 2011''' - Updated website to indicate support for Novell OES2 Linux SP3 after internal testing and no reported problems.

to:
* '''21st February 2011''' - Updated website to indicate support for Novell [=OES2=] Linux [=SP3=] after internal testing and no reported problems.

Added lines 5-18:
!! Slow printing from MS Office when iPrint queues contain many jobs.

When using PaperCut with hold/release queues or find-me printing, the iPrint queues may contain many jobs awaiting release.  When printing from Microsoft Office (e.g. Microsoft Word) the application queries the status of all the print jobs in the queue.  Novell iPrint takes a long time to respond to these queries resulting in slowness in the MS Office print dialogs from appearing.

This affects all versions of iPrint up to and including OES 6.3 [=SP3=].

Novell are aware of the issue and have raised an internal bug (#700160).

As of 2nd December 2011, Novell have notified us they have a fix in testing for this problem.  If you would like access to this fix, please contact Novell Support and reference the bug #700160.

This fix is expected to be included in upcoming Novell iPrint releases.


May 09, 2011, at 05:33 AM by 202.129.124.120 -
Added lines 50-61:
!! NWUSERNAME is no longer available in Windows 7 and Windows Vista

!!! Symptoms:
* Logon scripts that utilize the NWUSERNAME variable no longer work properly.
* PaperCut's User Client is reporting the wrong username.

!!! Workarounds:
* Use the following command to set the variable:
 
--> SET NWUSERNAME = "%CN"

More information is available from the [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7006517&sliceId=1&docTypeID=DT_TID_1_1&dialogID=230670142&stateId=0%200%20230668540|Novell website]].
Changed lines 89-90 from:

to:
* '''21st February 2011''' - Updated website to indicate support for Novell OES2 Linux SP3 after internal testing and no reported problems.

Changed lines 5-7 from:
!!Warning to customers running HP ToolboxFX status tool
Some large sites running PaperCut on Novell OES Linux has seen high iPrint (ipsmd) CPU usage if network has HP printers are the HP ToolboxFX status tool has been deployed along with the driver.  It seems like this tool excessively "pings" the printer for status information and does not scale well across large networks.  The solution is to deploy the standard network driver only (no extra tools).
to:
!!Warning to customers running HP `ToolboxFX status tool
Some large sites running PaperCut on Novell OES Linux has seen high iPrint (ipsmd) CPU usage if network has HP printers are the HP `ToolboxFX status tool has been deployed along with the driver.  It seems like this tool excessively "pings" the printer for status information and does not scale well across large networks.  The solution is to deploy the standard network driver only (no extra tools).
Added lines 5-7:
!!Warning to customers running HP ToolboxFX status tool
Some large sites running PaperCut on Novell OES Linux has seen high iPrint (ipsmd) CPU usage if network has HP printers are the HP ToolboxFX status tool has been deployed along with the driver.  It seems like this tool excessively "pings" the printer for status information and does not scale well across large networks.  The solution is to deploy the standard network driver only (no extra tools).

Changed line 88 from:
The PaperCut development team will continue to post updates here as they become available.
to:
The PaperCut development team working on the [[https://www.papercut.com/|print control solution for Novell iPrint]] will continue to post updates here as they become available.
October 16, 2010, at 08:22 PM by Rick - typos, added link to last Novell TID
Changed lines 27-28 from:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator canceling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Changed lines 66-69 from:
* '''Update 14th August 2009''' - Novell have decided to make the 20090731-1 avaliable as an official patch.  That's the version we've tested in house with great promise.  Should be avaliable in the next few days. I'll post an update here.

* '''Update 11th September 2009''' - Hooray!  Looks like we've finally found and fixed the remaining race-condition related bugs.  We've put some additional synchronization logic in our code and also the iPrint team has done the same.  We were seeing some issues on customer sites running on some very fast multi-processor systems and the latest round of fixes has addressed these issues.  Novell are going to make the update avaliable as an official update/hotfix soon.  If you're running on a fast multi-core/processor system and need access to the fix now, please email us at support.
to:
* '''Update 14th August 2009''' - Novell have decided to make the 20090731-1 available as an official patch.  That's the version we've tested in house with great promise.  Should be available in the next few days. I'll post an update here.

* '''Update 11th September 2009''' - Hooray!  Looks like we've finally found and fixed the remaining race-condition related bugs.  We've put some additional synchronization logic in our code and also the iPrint team has done the same.  We were seeing some issues on customer sites running on some very fast multi-processor systems and the latest round of fixes has addressed these issues.  Novell are going to make the update available as an official update/hotfix soon.  If you're running on a fast multi-core/processor system and need access to the fix now, please email us at support.
Changed lines 78-81 from:
* '''Update December 2009''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  Customer's running `SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch avaliable, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

* '''15th January 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now avaliable under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].
to:
* '''Update December 2009''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  Customer's running `SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch available, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

* '''15th January 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now available under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].
Changed lines 84-87 from:
* '''29th September 2010''' - Added new iPrint issue related to user identity issued discussed in Novell TID 7005753.


to:
* '''29th September 2010''' - Added new iPrint issue related to user identity issue discussed in [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005753|TID 7005753]].


September 29, 2010, at 12:20 PM by 218.214.136.115 -
Changed lines 84-87 from:
to:
* '''29th September 2010''' - Added new iPrint issue related to user identity issued discussed in Novell TID 7005753.


September 29, 2010, at 12:18 PM by 218.214.136.115 -
Changed lines 37-39 from:


to:
!!User identity security problem

Some PaperCut sites have reported an issue where the wrong username being logged against jobs in PaperCut. This issue was tracked down an iPrint bug where the iPrint client software is not correctly flushing the iPrint client cache.  Novell have a guide on how to 'resolve' the issue (clear iPrint's cache on logout) TID 7005753 .  We hope an official fix will be available soon.

!!!Symptoms:
* Jobs are identified in PaperCut under the wrong username.

!!!Known Workarounds:
* See Novell TID 7005753.

September 08, 2010, at 11:13 AM by 218.214.136.115 -
Deleted line 78:
Added lines 80-81:
''Categories:'' [[Category.Novell|+]]
----
Changed line 9 from:
   exit_on_error /etc/init.d/papercut-event-monitor
to:
   exit_on_error /etc/init.d/papercut-event-monitor start
Added lines 5-12:
!!Cluster resource script configuration
Sites running PaperCut on an OES Cluster who are upgrading to version 10.5+ may need to update their cluster resource scripts after upgrade. The installer should warn you. To summarize, change the line:
    exit_on_error /etc/init.d/papercutcups start
To
    exit_on_error /etc/init.d/papercut-event-monitor
[-(This service was renamed as it now does more than just CUPS management - it also does server connection monitoring for the new event resend feature.)-]

Changed lines 3-4 from:
This page lists known issues or bugs with PaperCut on [[https://www.papercut.com/news/papercut-on-novell-oes-linux-iprint/|Novell OES Linux]].
to:
This page lists known issues or bugs with PaperCut (print control/quotas) on [[https://www.papercut.com/news/papercut-on-novell-oes-linux-iprint/|Novell OES Linux]].
Changed lines 15-16 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture. (the version should be novell-iprint-server-6.2.20100414-0.4)
to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture. (the version should be novell-iprint-server-6.2.20100414-0.4 or later)
April 28, 2010, at 04:19 AM by 202.129.124.120 -
Changed lines 15-16 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture.
to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture. (the version should be novell-iprint-server-6.2.20100414-0.4)
April 28, 2010, at 04:18 AM by 202.129.124.120 -
Changed lines 5-10 from:
-->''Did you [[https://www.papercut.com/blog/chris/2010/04/20/novell-brainshare/|see us]] at [[http://www.novell.com/brainshare/|BrainShare]]?''

!!Rare crash bug in
iPrint (ipsmd) on `OES2 Linux `SP1

The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often
.
to:
!!Crash bug in iPrint (ipsmd) on `OES2 Linux `SP2

The default
iPrint that ships with `OES2 Linux `SP2 contains a bug where after enabling PaperCut via the ''Accounting autoload command'' iPrint may crash after receiving a print job.
Changed line 10 from:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716 (0x506D0012)
to:
* Jobs do not print after enabling PaperCut on the printer
Changed lines 12-13 from:
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process (this is because the parent process has died and left us in a zombie/orphaned state as explained [[http://en.wikipedia.org/wiki/Zombie_process|here]]).
to:

Added lines 15-26:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  Ensure the update is suitable for `OES2 `SP2 and your architecture.

!!Rare crash bug in iPrint (ipsmd) on `OES2 Linux `SP1

The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.

!!!Symptoms:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716 (0x506D0012)
* Errors may appear in the iPrint logs (ipsmd.log)
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process (this is because the parent process has died and left us in a zombie/orphaned state as explained [[http://en.wikipedia.org/wiki/Zombie_process|here]]).

!!!Known Workarounds:
Changed lines 29-41 from:
!!Crash bug in iPrint (ipsmd) on `OES2 Linux `SP2

The default iPrint that ships with `OES2 Linux `SP2 contains a bug where after enabling PaperCut via the ''Accounting autoload command'' iPrint may crash after receiving a print job.

!!!Symptoms:
* Jobs do not print after enabling PaperCut on the printer
* Errors may appear in the iPrint logs (ipsmd.log)


!!!Known Workarounds:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for `OES2 `SP2 and your architecture.  The latest version we've stress tested with success is 6.2.20091222 .


to:


Changed lines 67-69 from:
to:
* '''24th April 2010''' - Novell have issued another iPrint update under  [[http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7005723&sliceId=1&docTypeID=DT_TID_1_1&dialogID=137913476&stateId=0%200%20137911365|TID 7005723]].  I added some extra locking and rate-limiting to our code a while back to work around the problems this update fixes so it was rare for live sites to see this problem under normal load.  I still however recommend the update.

Changed lines 49-51 from:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1 begin_of_the_skype_highlighting              20090731-1      end_of_the_skype_highlighting begin_of_the_skype_highlighting              20090731-1      end_of_the_skype_highlighting).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 

to:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users.
Deleted line 52:
Changed lines 9-10 from:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerate" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Changed lines 5-6 from:
-->''Are you going to [[http://www.novell.com/brainshare/|Brainshare]]?  Of so, come and visit PaperCut at booth 1012!''
to:
-->''Did you [[https://www.papercut.com/blog/chris/2010/04/20/novell-brainshare/|see us]] at [[http://www.novell.com/brainshare/|BrainShare]]?''
Added lines 5-6:
-->''Are you going to [[http://www.novell.com/brainshare/|Brainshare]]?  Of so, come and visit PaperCut at booth 1012!''
Changed lines 27-29 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for OES2 SP2 and your architecture.  The latest version we've stress tested with success is 6.2.20091222 .

to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for `OES2 `SP2 and your architecture.  The latest version we've stress tested with success is 6.2.20091222 .

Changed lines 47-49 from:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 

to:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1 begin_of_the_skype_highlighting              20090731-1      end_of_the_skype_highlighting begin_of_the_skype_highlighting              20090731-1      end_of_the_skype_highlighting).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 

Changed lines 65-67 from:
* '''15th Januaray 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now avaliable under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].

to:
* '''15th January 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now avaliable under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].

Changed lines 65-67 from:
to:
* '''15th Januaray 2010''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  It's now avaliable under official support channels via [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].

Changed lines 27-29 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for OES2 SP2.  The latest version we've stress tested with success is 6.2.20091222 .

to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for OES2 SP2 and your architecture.  The latest version we've stress tested with success is 6.2.20091222 .

Changed lines 15-16 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.   The last known version to work successfully is 6.1.20091218.
to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]]
Changed lines 27-29 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.  The latest version we've stress tested with success is 6.2.20091222 .

to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut.  It's filed under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1|TID 7004872]].  Ensure the update is suitable for OES2 SP2.  The latest version we've stress tested with success is 6.2.20091222 .

Changed lines 15-16 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.
to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.  The last known version to work successfully is 6.1.20091218.
Changed lines 27-29 from:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.

to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.  The latest version we've stress tested with success is 6.2.20091222 .

Changed lines 5-6 from:
!!Rare crash bug in iPrint (ipsmd) on OES2 Linux `SP1
to:
!!Rare crash bug in iPrint (ipsmd) on `OES2 Linux `SP1
Changed lines 17-18 from:
!!Crash bug in iPrint (ipsmd) on OES2 Linux `SP2
to:
!!Crash bug in iPrint (ipsmd) on `OES2 Linux `SP2
Changed lines 5-6 from:
!!Feb 2009: Known Bug crash bug in iPrint (ipsmd)
to:
!!Rare crash bug in iPrint (ipsmd) on OES2 Linux `SP1
Changed lines 15-16 from:
* Temporarily setting all users to "unrestricted" will ensure that jobs are never denied and avoid the problematic cancel operation.  This however does mean that users can run their accounts below zero.
to:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.

!!Crash bug in iPrint (ipsmd) on OES2 Linux `SP2

The default iPrint that ships with `OES2 Linux `SP2 contains a bug where after enabling PaperCut via the ''Accounting autoload command'' iPrint may crash after receiving a print job.

!!!Symptoms:
* Jobs do not print after enabling PaperCut on the printer
* Errors may appear in the iPrint logs (ipsmd.log)


!!!Known Workarounds:
* Contact Novell support and ask for the latest iprint update compatible with PaperCut (The iPrint support team knows who we are as many sites request this every week!).  Ask for the version for your OES Services Pack.


----
!!General Discussion/Comments (History)

Changed lines 47-49 from:
* '''Update December 2009''' - Novell have issued a hotfix for the regression in OES2 SP2 (listed as bug 555918).  Customer's running SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch avaliable, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

to:
* '''Update December 2009''' - Novell have issued a hotfix for the regression in `OES2 `SP2 (listed as bug 555918).  Customer's running `SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch avaliable, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

Changed lines 47-48 from:

to:
* '''Update December 2009''' - Novell have issued a hotfix for the regression in OES2 SP2 (listed as bug 555918).  Customer's running SP2 should ensure they are running version 6.2.20091222 or higher.  We have this patch avaliable, however in line with Novell's support procedure, please contact Novell to obtain this patch through official channels.

Changed lines 43-48 from:
* '''Update 28th October  2009''' - PaperCut now works on OES Linux clusters.  9.7 will include official setup documentation however if you require early access, please email us at support.

* '''Update November 2009''' - There seems to be a regression OES2 SP2.  After upgrading, some customers have reported that the iPrint server crashes.  We're working with Novell to resolve this issue.  In the meantime we recommend sticking to SP1 and delaying any upgrade.


to:
* '''Update 28th October  2009''' - PaperCut now works on [=OES=] Linux clusters.  9.7 will include official setup documentation however if you require early access, please email us at support.

* '''Update November 2009''' - There seems to be a regression [=OES2=] [=SP2=].  After upgrading, some customers have reported that the iPrint server crashes.  We're working with Novell to resolve this issue.  In the meantime we recommend sticking to [=SP1=] and delaying any upgrade.


Changed lines 45-48 from:



to:
* '''Update November 2009''' - There seems to be a regression OES2 SP2.  After upgrading, some customers have reported that the iPrint server crashes.  We're working with Novell to resolve this issue.  In the meantime we recommend sticking to SP1 and delaying any upgrade.


Changed lines 41-42 from:
* '''Update October 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.  More information [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1&dialogID=103124059&stateId=1%200%2057898768|here under TID 7004872]].
to:
* '''Update October 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.  More information here under [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1&dialogID=103124059&stateId=1%200%2057898768|TID 7004872]].
Added lines 41-42:
* '''Update October 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.  More information [[http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7004872&sliceId=1&docTypeID=DT_TID_1_1&dialogID=103124059&stateId=1%200%2057898768|here under TID 7004872]].
Changed lines 45-48 from:
* '''Update November 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.


to:



Changed lines 41-42 from:

to:
* '''Update 28th October  2009''' - PaperCut now works on OES Linux clusters.  9.7 will include official setup documentation however if you require early access, please email us at support.

* '''Update November 2009''' - We've had a few of the larger sites sites report slow printing performance after applying one of the Novell patches provided to address stability issues above.  If you're seeing slow printing, please email support and we can supply a newer patch that addresses this.


Changed lines 39-42 from:
to:
* '''Update October 2009''' - Latest 9.6 release of PaperCut with latest iPrint patches have proved to be very stable with no issues reported on the high volume sites.  We've also now got PaperCut running on clustered iPrint servers.  Official cluster setup documentation will be incorporated into the 9.7 release.  If you require early access to cluster support, please email us at support.


Added lines 36-39:

* '''Update 11th September 2009''' - Hooray!  Looks like we've finally found and fixed the remaining race-condition related bugs.  We've put some additional synchronization logic in our code and also the iPrint team has done the same.  We were seeing some issues on customer sites running on some very fast multi-processor systems and the latest round of fixes has addressed these issues.  Novell are going to make the update avaliable as an official update/hotfix soon.  If you're running on a fast multi-core/processor system and need access to the fix now, please email us at support.

Added lines 33-35:

* '''Update 14th August 2009''' - Novell have decided to make the 20090731-1 avaliable as an official patch.  That's the version we've tested in house with great promise.  Should be avaliable in the next few days. I'll post an update here.

Changed line 17 from:
* '''Update 14th April 2009''' - The Novell iPrint team have release a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
to:
* '''Update 14th April 2009''' - The Novell iPrint team have released a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
Changed lines 31-32 from:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make avaliable to PaperCut users. 
to:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make available to PaperCut users. 
Changed lines 35-36 from:

[-keywords: zombie process, oes linux, novell iprint, crash dumb -]
to:
----
[-
keywords: zombie process, oes linux, novell iprint, crash dump-]
Added lines 31-32:
* '''Update 4th August 2009''' - We've been working with the iPrint team to QA a recent iPrint build (20090731-1).  This version shows lots of promise. We've run thousands of jobs through via our automated testing procedures and have not had any crashes.  We're working with Novell to make this an official release that we can make avaliable to PaperCut users. 
Changed line 9 from:
Symptoms:
to:
!!!Symptoms:
Changed line 14 from:
Known Workarounds:
to:
!!!Known Workarounds:
Changed lines 19-20 from:
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  The follow hotfix may be applied to existing 9.4 installs:
to:
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  The following hotfix may be applied to existing 9.x installs:
Changed lines 19-20 from:
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  We can arrange early access to this build as required.
to:
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  The follow hotfix may be applied to existing 9.4 installs:

      su - papercut
      cd ~
      tar -zcf pre-fix-backup.tgz providers/print/linux-*
      wget https://www.papercut.com/anonftp/pub/pcng/previews/novell-oes-hotfix-2009-06-24.tgz
      tar -zxf novell-oes-hotfix-2009-06-24.tgz
      su - root
      /home/papercut/providers/print/linux-x64/roottasks

->Then restart The iPrint Print Manager or simply restart the server to apply
.
Added line 16:
Changed lines 19-20 from:
to:
* '''Update 23rd June 2009''' - The next release of PaperCut (version 9.5) will have a number of changes that we hope will reduce the probability of the iPrint bug occurring (e.g. thread synchronization changes).  We can arrange early access to this build as required.
Changed lines 17-18 from:
to:
* '''Update 17th June 2009''' -  The Novell iPrint team have again supplied us with a new set of patches.  Again we are able to supply on request.  Please email support@papercut.com for more information and details on how to access patch!
Changed lines 7-8 from:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a [[https://www.papercut.com/solutions/printer-control-for-education/|print control]] application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Changed lines 16-17 from:
* '''Update 14th April 2009''' - The Novell iPrint team have release a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and information on how to access the "unofficial" patch!
to:
* '''Update 14th April 2009''' - The Novell iPrint team have release a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and details on how to access the "unofficial" patch!
Changed lines 16-18 from:
* Ask your Novell support contact for access to the latest development builds of iPrint (and/or hotfix).
* Be patient and put up with it until an official update is out :-)

to:
* '''Update 14th April 2009''' - The Novell iPrint team have release a patch, however it is yet to make it out via official channels.  Please email support@papercut.com for more information and information on how to access the "unofficial" patch!
Changed lines 12-13 from:
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process
to:
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process (this is because the parent process has died and left us in a zombie/orphaned state as explained [[http://en.wikipedia.org/wiki/Zombie_process|here]]).
Changed line 16 from:
* Ask Novell for access to the latest development builds of iPrint (and/or hotfix).
to:
* Ask your Novell support contact for access to the latest development builds of iPrint (and/or hotfix).
Changed lines 17-20 from:

The PaperCut development team will continue to post updates here as they become avaliable.

to:
* Be patient and put up with it until an official update is out :-)

The PaperCut development team will continue to post updates here as they become available
.

Changed lines 12-13 from:
* The [@papercut@} accounting autoload command may be listed as a [@<defunct>@] process
to:
* The [@papercut@] accounting autoload command may be listed as a [@<defunct>@] process
Changed lines 12-13 from:
* PaperCut may be listed as a [@<defunct>@] process
to:
* The [@papercut@} accounting autoload command may be listed as a [@<defunct>@] process
Changed lines 7-8 from:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel job" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Changed lines 3-4 from:
This page lists known issues or bugs with PaperCut on Novell OES Linux.
to:
This page lists known issues or bugs with PaperCut on [[https://www.papercut.com/news/papercut-on-novell-oes-linux-iprint/|Novell OES Linux]].
Changed line 15 from:
* Temporarily setting all users to "unrestricted" will ensure that jobs are never denied.  This however does mean that users can run their accounts below zero.
to:
* Temporarily setting all users to "unrestricted" will ensure that jobs are never denied and avoid the problematic cancel operation.  This however does mean that users can run their accounts below zero.
Changed line 10 from:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716
to:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716 (0x506D0012)
Changed lines 5-6 from:
!!Known Bug crash bug in iPrint (ipsmd)
to:
!!Feb 2009: Known Bug crash bug in iPrint (ipsmd)
Changed lines 7-8 from:
The default iPrint that ships with 'OES2 Linux 'SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with `OES2 Linux `SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Changed lines 15-17 from:
 * Temporarily setting all users to "unrestricted" will ensure that jobs are never denied.  This however does mean that users can run their accounts below zero.
 * Ask Novell for access to the latest development builds of iPrint (and/or hotfix).
to:
* Temporarily setting all users to "unrestricted" will ensure that jobs are never denied.  This however does mean that users can run their accounts below zero.
* Ask Novell for access to the latest development builds of iPrint (and/or hotfix).
Changed lines 9-13 from:
Symptons:
 * Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716
 * Errors may appear in the iPrint logs (ipsmd.log)
 * PaperCut may be listed as a [@<defunct>@] process
to:
Symptoms:
* Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716
* Errors may appear in the iPrint logs (ipsmd.log)
* PaperCut may be listed as a [@<defunct>@] process
Changed lines 7-8 from:
The default iPrint that ships with OES2 Linux SP1 contains a bug where canceling a job may occassionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
to:
The default iPrint that ships with 'OES2 Linux 'SP1 contains a bug where canceling a job may occasionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.
Added lines 1-21:
(:title Known Issues with PaperCut on Novell OES Linux iPrint:)

This page lists known issues or bugs with PaperCut on Novell OES Linux.

!!Known Bug crash bug in iPrint (ipsmd)

The default iPrint that ships with OES2 Linux SP1 contains a bug where canceling a job may occassionally crash ipsmd.  This is a bug in iPrint, however the introduction of PaperCut may "exaggerated" it. On a normal network, the "cancel" operation would only be used occasionally - say by an administrator cancelling a job to unblock a jammed print queue. PaperCut being a print control application however cancels jobs from time to time as part of standard operation - e.g. a user running out of quota.  The fact that the cancel operation is called more often causes this bug to surface more often.

Symptons:
 * Errors may appear in PaperCut's print-provider.log - Unable to cancel job error number: 1349320716
 * Errors may appear in the iPrint logs (ipsmd.log)
 * PaperCut may be listed as a [@<defunct>@] process

Known Workarounds:
 * Temporarily setting all users to "unrestricted" will ensure that jobs are never denied.  This however does mean that users can run their accounts below zero.
 * Ask Novell for access to the latest development builds of iPrint (and/or hotfix).

The PaperCut development team will continue to post updates here as they become avaliable.


[-keywords: zombie process, oes linux, novell iprint, crash dumb -]

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 March 27, 2019, at 04:36 AM
Printable View   |   Article History   |   Edit Article