I updated one node in my two node SuSE10/OES2 iPrint cluster with the latest printmanager and server code rpms that were released last week or so in the channel; these appear to be the public release versions of the November 3 2008 rpms. I had been running the June 13 2008 debug rpms successfully since 1/12/09.

So I fail my iprint resource over to the new node; the /var/log/messages file indicates the services loaded successfully but when I checked the print manager health web page all the printers were "not bound". So I fail back to the other node with older rpms and everything comes up and works good. That is odd thing number 1. An hour or so later I decide to try again and fail over to the newly patched node. Everything loads successfully according to the logs, printer health looks good and printing resumes normally. Then comes odd thing number 2 - four hours later after about 600 jobs I get calls that printing is dead. I check /var/log/messages and find this:

Feb 20 14:11:10 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 11
Feb 20 14:16:22 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 11
Feb 20 14:17:16 iprint2 iprintgw[9558]: Malformed alert response, alertPtr->severity: 0
Feb 20 14:21:34 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 11

Feb 20 14:26:46 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 11
Feb 20 14:26:57 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:27:53 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:28:56 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:29:58 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:31:01 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:32:03 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 14:33:05 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111

this message repeats every minute or so for the next hour and half until finally:

Feb 20 15:29:18 iprint2 iprintgw[9558]: CommWrite failed for printer agent 'FAA-Com-HP4050-143', Error 111
Feb 20 15:31:36 iprint2 iprintgw[9558]: Unloaded with handleReferencedCount at 2 for gwHandle 74

I'm thinking printing stopped at this point - I was notified around 15:44.

I notice my "iprintgw.log" shows these same messages.

That printer was up and I could ping it. A job was in the queue with a printer console message of

tray 2 load
plain letter
for help
press the ? key

Not too alarming

I failed back to the older node and all was good again. And I'm afraid to run on this new code - I am going to revert back to the older rpms once I find the info on how to do that. I had run almost five weeks with the June debug code and almost 80000 print jobs so I am feeling pretty good about that code.

Any thoughts on what may be the problem? I'd like to move the new rpm but I can't have this happen. Thanks for any help!

Wayne Fee
IT Enterprise Systems
Appalachian State University