Highlighted
Regular Contributor.
Regular Contributor.
1757 views

iPrint Very Unreliable

We've run iPrint in our tree using SLES 11 SP3/OES11 sp2 and now iPrint Appliance 1.1. We're in a school district with approximately 3000 Macs and a handful of Windows XP and 7 machines. We use a single iPrint server consisting of about 200 printers with around 180 HP printers and 20 Xerox machines. We have drivers for Mac, XP and 7.

We've run into problems on both server platforms. From time to time, our iPrint server stops processing requests, the psmstatus page becomes unresponsive and I have to reload the driver store, print manager, and Apache, sometimes several times over before it starts processing requests. Lately, the problem has been worse and we've called support in the past and the only thing they were able to do was disassociate the drivers from the printers and that seems to at least let the print jobs process more reliably. That's obviously not a long term solution. I'm not sure if the problem is the number of requests to the print server, the types of jobs being sent, etc.

The print manager seems to restart on its own a lot but most of the time this doesn't cause a problem. Has anyone encountered this type of unreliability and it lasts for long periods of time? We have to get this issue fixed or my organization is going to request a different printing solution as this has been far too unreliable. We do have a few deleted printers that a few of our clients still have installed, but that's not that many. We've made sure our clients have the newest iPrint clients installed. I've also attached a screen shot of the load strings our printer agents use. Anyone else run into these kinds of issues?
0 Likes
6 Replies
Highlighted
Absent Member.
Absent Member.

Re: iPrint Very Unreliable

On 09/18/2016 11:26 PM, alcockb wrote:
>
> We've run iPrint in our tree using SLES 11 SP3/OES11 sp2 and now iPrint
> Appliance 1.1. We're in a school district with approximately 3000 Macs
> and a handful of Windows XP and 7 machines. We use a single iPrint
> server consisting of about 200 printers with around 180 HP printers and
> 20 Xerox machines. We have drivers for Mac, XP and 7.
>
> We've run into problems on both server platforms. From time to time,
> our iPrint server stops processing requests, the psmstatus page becomes
> unresponsive and I have to reload the driver store, print manager, and
> Apache, sometimes several times over before it starts processing
> requests. Lately, the problem has been worse and we've called support
> in the past and the only thing they were able to do was disassociate the
> drivers from the printers and that seems to at least let the print jobs
> process more reliably. That's obviously not a long term solution. I'm
> not sure if the problem is the number of requests to the print server,
> the types of jobs being sent, etc.
>
> The print manager seems to restart on its own a lot but most of the time
> this doesn't cause a problem. Has anyone encountered this type of
> unreliability and it lasts for long periods of time? We have to get
> this issue fixed or my organization is going to request a different
> printing solution as this has been far too unreliable. We do have a few
> deleted printers that a few of our clients still have installed, but
> that's not that many. We've made sure our clients have the newest
> iPrint clients installed. I've also attached a screen shot of the load
> strings our printer agents use. Anyone else run into these kinds of
> issues?
>
>
> +----------------------------------------------------------------------+
> |Filename: Screen Shot 2016-09-01 at 3.20.55 PM.png |
> |Download: https://forums.novell.com/attachment.php?attachmentid=5606 |
> +----------------------------------------------------------------------+
>


Other way around. I see single printer managers with 3000+ printers
performing very good.

1. Restart other print manager is an auto defense mechanism to protect
the database again corruption. Too many time it may point to a problem
already on the database. A recover of the database may help

2. The symptom looks like an apache/resources one. Without more info
about your hardware and with no logs to check when issue is present, i
can just advise to change apache from the default prefork to worker.
tid7013441

3. Your screenshot shows that PRINTERNAME is using other than the
default passthrough. Not sure why as this is only a specific requirement
with particular printers, not sure that you need it with HP or Xerox and
it should only be used if printer vendor advise it to do so. see:

https://www.novell.com/support/kb/doc.php?id=3604883

If you still have this issue, i'll ope nan SR, take the lgo files
support will ask at the moment problem arise and they will be able to
help you further.


0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Re: iPrint Very Unreliable

Mysterious;2439656 wrote:
On 09/18/2016 11:26 PM, alcockb wrote:
>
> We've run iPrint in our tree using SLES 11 SP3/OES11 sp2 and now iPrint
> Appliance 1.1. We're in a school district with approximately 3000 Macs
> and a handful of Windows XP and 7 machines. We use a single iPrint
> server consisting of about 200 printers with around 180 HP printers and
> 20 Xerox machines. We have drivers for Mac, XP and 7.
>
> We've run into problems on both server platforms. From time to time,
> our iPrint server stops processing requests, the psmstatus page becomes
> unresponsive and I have to reload the driver store, print manager, and
> Apache, sometimes several times over before it starts processing
> requests. Lately, the problem has been worse and we've called support
> in the past and the only thing they were able to do was disassociate the
> drivers from the printers and that seems to at least let the print jobs
> process more reliably. That's obviously not a long term solution. I'm
> not sure if the problem is the number of requests to the print server,
> the types of jobs being sent, etc.
>
> The print manager seems to restart on its own a lot but most of the time
> this doesn't cause a problem. Has anyone encountered this type of
> unreliability and it lasts for long periods of time? We have to get
> this issue fixed or my organization is going to request a different
> printing solution as this has been far too unreliable. We do have a few
> deleted printers that a few of our clients still have installed, but
> that's not that many. We've made sure our clients have the newest
> iPrint clients installed. I've also attached a screen shot of the load
> strings our printer agents use. Anyone else run into these kinds of
> issues?
>
>
> +----------------------------------------------------------------------+
> |Filename: Screen Shot 2016-09-01 at 3.20.55 PM.png |
> |Download: https://forums.novell.com/attachment.php?attachmentid=5606 |
> +----------------------------------------------------------------------+
>


Other way around. I see single printer managers with 3000+ printers
performing very good.

1. Restart other print manager is an auto defense mechanism to protect
the database again corruption. Too many time it may point to a problem
already on the database. A recover of the database may help

2. The symptom looks like an apache/resources one. Without more info
about your hardware and with no logs to check when issue is present, i
can just advise to change apache from the default prefork to worker.
tid7013441

3. Your screenshot shows that PRINTERNAME is using other than the
default passthrough. Not sure why as this is only a specific requirement
with particular printers, not sure that you need it with HP or Xerox and
it should only be used if printer vendor advise it to do so. see:

https://www.novell.com/support/kb/doc.php?id=3604883

If you still have this issue, i'll ope nan SR, take the lgo files
support will ask at the moment problem arise and they will be able to
help you further.


We're only running roughly 200+ printers, so compared to 3000 on a single server, it shouldn't be a problem. On organizations running 3000 printers on a single iPrint server, how do they have it configured?

We have roughly 3000 Macs that use this print server, so I did finally open up an SR. I did change the load strings on all of the printers to Passthrough, although the problem still occurred. The support engineer did have me run through a Apache server-tuning thread to raise the keep alive requests and the alive timeout, as well as, increase the max clients for the Apache worker thread, which is also in the same server tuning file. It seems to be more stable, but we still won't know for a while.
0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Re: iPrint Very Unreliable

Also, is it common in the PSMStatus for the iPrint Manager to restart every few days?
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: iPrint Very Unreliable

alcockb;2440112 wrote:
Also, is it common in the PSMStatus for the iPrint Manager to restart every few days?


If you're referring to the PSMStatus page, where you scroll to the bottom and click:
Advanced iPrint Manager information

and then on that new page, scroll down to the "uptime",

I'd say "No", that is not normal. We have 200+ printers on a single manager on OES11 SP2 (not the iPrint appliance) and it's been up for 164 days.
0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Re: iPrint Very Unreliable

kjhurni;2440123 wrote:
If you're referring to the PSMStatus page, where you scroll to the bottom and click:
Advanced iPrint Manager information

and then on that new page, scroll down to the "uptime",

I'd say "No", that is not normal. We have 200+ printers on a single manager on OES11 SP2 (not the iPrint appliance) and it's been up for 164 days.


Ours restarts every few days or sometimes more than once a day. I'm not sure what to do at this point. I'm trying to track workstations that still have printers installed that don't exist anymore, but our ndpsmmon.log keeps showing a lot of generic errors like this one:

09/23/2016 02:27:59 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:59 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:59 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:58 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:58 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:57 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)
09/23/2016 02:27:57 PM, Operation Shutdown Printer Agent:,
Error: 506D0030 - insufficient rights,
User Name, Not Bound,
Address, unknown,
Object Name: unknown
(Client Interface)

I can't find anything based on that information.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: iPrint Very Unreliable

This is just a guess on my part:

Either some form of memory leak or possibly a bad printer agent is causing it to restart.

I'm not sure if there's a way to obtain a debug log or core file (assuming Linux/OES here).

I know some of our regional offices have high memory utilization with the iPrint manager (it doesn't restart, but it chews up the virtual memory/SWAP on OES).
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.