reporting a bug

I'm running OES2 SP2 AND SP3

I'm seeing this pattern

When any printer is in an error state (paper jam or out of toner) and user sent a job to it which of course will stay in the print queue, I will start to see this error in var/log/messages. PRINTER23 for example would generate the log below every couple minutes until someone service the printer.



May 1 00:41:05 sav-iprint-server iprintgw[24614]: 05/1/12 00:41:05 LprSendControlFile failed for printer agent 'PRINTER23', ccode=-1 Error 11 - Resource temporarily unavailable
May 1 00:45:35 sav-iprint-server iprintgw[24614]: 05/1/12 00:45:35 LprSendControlFile failed for printer agent 'PRINTER23', ccode=-1 Error 11 - Resource temporarily unavailable
May 1 00:54:35 sav-iprint-server iprintgw[24614]: 05/1/12 00:54:35 LprSendControlFile failed for printer agent 'PRINTER23', ccode=-1 Error 11 - Resource temporarily unavailable



However, if you leave the printer with this error for 2 days or more, your print server will eventually crash and auto restart



May 3 09:22:45 WARNING A child process has gone or the iPrint Manager has just experienced a fatal error. It will be restarted by its monitor process.
May 3 09:22:45 INFO Starting print manager process with pid: 25697
May 3 09:23:08 INFO Starting iprintgw process with pid: 25742
May 3 09:23:08 INFO Starting papercut process with pid: 25745
May 3 09:23:10 INFO iPrint Manager 'SAV-IPRINT-MANAGER' has successfully loaded.
May 3 16:44:46 WARNING The monitor process (29911) received signal: 15 from process (24515) running with uid (0).



At this point, the iprint manager status will show "BAD" but everthing is still functioning. It has "BAD" status because the "Client Interface" status gave a crazy amount of Failed operations.


Latest Client Event from printserver/psmstatus/

"Operations that Failed 4238 69663 210040"


The only workaround that fixed the "BAD" status after print manager auto restarted is to stop print manager service and must killall-9 iprintgw and restart the print service


My real problem is this, if you ignore the printer error status and let the iprint manager crash and auto restart and this loop will continue. After serveral auto restarts (around 30-45 days total), I believe it will hang trying to auto restart again and no one can print. This is where I'm at. I shouldn't be watching the logs for printers that are in error states to prevent all the crashing and auto restart of the print manager.


Can any one confirm this? I know you can duplicate this problem easily. You must be in a large environment with lots of printers to experience this problem because chance of printers that left unservice for days. I'm seeing this problem on the latest patches of OES2 SP2, SP3 and i'm pretty sure OES11 since there are not much changes between them for iprint. Thank you.


Phil