Latest problems with LPRng

This page is intended to be a place where we can make notes about, and hopefully finally arrive at a solution for, the printer problems currently being experienced within Informatics. There seems to be 2 separate problems

  1. print queues get jammed, lpq includes an error message about looping printcaps. This seems to happen after the /etc/printcap file has been recreated.

  1. print queues get jammed, lpq does not report an error but an examination of status.pr for a stuck queue shows that jobs are being sent to localhost rather than the printer itself (Actual error messages coming as soon as it happens again).

Error 1. cropped up on powell this morning 5/4/07. An examination of /etc/printcap showed no changes from the printcap used by a working print server. Running top showed that roughly 50% of the cpu was being used up on io wait. Stopping slapd resolved this but when slapd was restarted, the io wait load returned and the printing issue was not fixed. Restarting LPRng also cleared the load and did resolve the printing issue.

-- CraigStrachan - 05 Apr 2007

Some random thoughts by Gordon -

When the printcap is recreated what happens to the old one? What is the procedure for stopping/starting/getting lpd to read the new version of the printcap? What if some slow to die process still has the old one open ? Are we sure that the new printcap is exactly the same as the old one? What if the EOF marker isn't there, or the last newline or something?

Edit | Attach | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 12 Apr 2007 - 12:03:41 - GordonReid
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies