Hi ALL,
I recently withed from CentOS 3 X server to CentOS 4.5. It works fine other than printers.
there are many printers connected to it. We have configured the commnad
printconf
queue type is Networked UNIX (LPD)
Some times, we will be able to print , But, some times, We will NOT be able to print.
We can ping its ip address. Even, when we can't print, We can ping its ip address.
When we check logs , we see something like this.
[Job 888] Unable to connect to printer; will retry in 30 seconds...: Connection timed out
Then, What we do is , We go to application, system setting, printing
and when we get the window, We click apply button, Then, again, We will be able to print.
Could u pls let me know why?
But, When We used CentOS 3X, it worked fine. No problem at all.
here are rpms installed on CentOS 3X
[root@lwlsvr_old root]# rpm -qa |grep cups cups-1.1.17-13.3.32 cups-libs-1.1.17-13.3.32
[root@lwlsvr_old root]# rpm -qa |grep samba redhat-config-samba-1.0.16-5 samba-common-3.0.9-1.3E.5 samba-3.0.9-1.3E.5 samba-swat-3.0.9-1.3E.5 samba-client-3.0.9-1.3E.5
But, on CentOS 4.5 , We get issues.
here are rpms installed on CentOS 4.5
[root@lwlsvr ~]# rpm -qa |grep cups hal-cups-utils-0.5.2-8 libgnomecups-0.1.12-5 cups-1.1.22-0.rc1.9.20 cups-libs-1.1.22-0.rc1.9.20
[root@lwlsvr ~]# rpm -qa |grep samba system-config-samba-1.2.21-1.el4.1 samba-common-3.0.10-1.4E.11 samba-3.0.10-1.4E.11 samba-client-3.0.10-1.4E.11
Hope to hear form you.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Indunil Jayasooriya Sent: Thursday, December 18, 2008 2:42 AM To: CentOS mailing list Subject: [CentOS] Unable to connect to printer;will retry in 30 seconds...: Connection timed out
Hi ALL,
I recently withed from CentOS 3 X server to CentOS 4.5. It works fine other than printers.
there are many printers connected to it. We have configured the commnad
printconf
queue type is Networked UNIX (LPD)
Some times, we will be able to print , But, some times, We will NOT be able to print.
We can ping its ip address. Even, when we can't print, We can ping its ip address.
When we check logs , we see something like this.
[Job 888] Unable to connect to printer; will retry in 30 seconds...: Connection timed out
Then, What we do is , We go to application, system setting, printing
and when we get the window, We click apply button, Then, again, We will be able to print.
Could u pls let me know why?
But, When We used CentOS 3X, it worked fine. No problem at all.
here are rpms installed on CentOS 3X
[root@lwlsvr_old root]# rpm -qa |grep cups cups-1.1.17-13.3.32 cups-libs-1.1.17-13.3.32
[root@lwlsvr_old root]# rpm -qa |grep samba redhat-config-samba-1.0.16-5 samba-common-3.0.9-1.3E.5 samba-3.0.9-1.3E.5 samba-swat-3.0.9-1.3E.5 samba-client-3.0.9-1.3E.5
But, on CentOS 4.5 , We get issues.
here are rpms installed on CentOS 4.5
[root@lwlsvr ~]# rpm -qa |grep cups hal-cups-utils-0.5.2-8 libgnomecups-0.1.12-5 cups-1.1.22-0.rc1.9.20 cups-libs-1.1.22-0.rc1.9.20
[root@lwlsvr ~]# rpm -qa |grep samba system-config-samba-1.2.21-1.el4.1 samba-common-3.0.10-1.4E.11 samba-3.0.10-1.4E.11 samba-client-3.0.10-1.4E.11
------------------------------- You Hit the Apply Button But did you bother to make it Default Printer?
JohnStanley
On Wed, Dec 17, 2008 at 11:42 PM, Indunil Jayasooriya indunil75@gmail.com wrote:
Hi ALL,
When we check logs , we see something like this.
[Job 888] Unable to connect to printer; will retry in 30 seconds...: Connection timed out
Then, What we do is , We go to application, system setting, printing
and when we get the window, We click apply button, Then, again, We will be able to print.
Could u pls let me know why?
I can't tell you why, but I can expound on this a little.
I run CentOS on my desktop at home, x86_64. I started on 4.4 and am now running 5.2. During most of this time, I had a Minolta PagePro 1100 printer with parallel (lp0) interface that worked fine - except that every once in a great while, I would get this error, and there was NO way to clear it except to reboot.
ABout a month ago, that printer gave up the ghost (ok, the second drum wore out), so I replaced it with a Brother HL-2140 with a USB interface. I noticed that this problem occurs every time I boot my vmware Windows VM if the printer is attached to the VM, and once, recently, even when it wasn't. (I wonder if this is related to the previous issue on the Minolta....) What usually clears this is to empty the queue, go into the System->Administration->Printer applet (or run system-config-printer as root), disable the printer, cycle power on the printer, then re-enable it, Then it works fine.
Interesting points:
1) Only seems to happen when vmware is involved, most often if the printer is accessible to the vmware VM (usually I have this disabled, for obvious reasons).
2) Disconnecting the USB cable and plugging it back in has no effect - I have to cycle the power on the printer, and only after it has been disabled.
3) This whole process MUST take at least 30 seconds because if I do it too fast, it doesn't work. This may be related to the timeout issue.
I strongly suspect that there is a bug somewhere in the printer system (CUPS maybe?) such that, once a printer gets out of sync (like this), it requires a reset to fix it. With the parallel printer, I had to reset the system. With the USB printer, I can reset the printer, probably because the underlying OS layers are designed to handle USB devices going on and off line more easily that the parallel device(s).
Given the issue I have seen with vmware, I wonder if the issue in your situation has to do with passing control of the printer around on your network. I know that sort of thing _should_ not happen, but reality has a nasty way of intruding on our needs-and-expectations-based world.
Perhaps someone better informed on the details inside can comment....
HTH
mhr
Indunil Jayasooriya wrote:
Hi ALL,
I recently withed from CentOS 3 X server to CentOS 4.5. It works fine other than printers.
there are many printers connected to it. We have configured the commnad
printconf
queue type is Networked UNIX (LPD)
Some times, we will be able to print , But, some times, We will NOT be able to print.
We can ping its ip address. Even, when we can't print, We can ping its ip address.
When we check logs , we see something like this.
[Job 888] Unable to connect to printer; will retry in 30 seconds...: Connection timed out
snip
Hope to hear form you.
We have a CentOS 4.x server at a hosting facility that currently has 73 printers defined on various protocols (socket, ipp, lpd) which can see extensive delays in print jobs. We are seeing the same error in our logs. As a work around for this issue you can do a cupsdisable then a cupsenable for the effected printer which should clear the delay and start it working again, provided that you can ping the printer and the printer itself is not causing the problem. If that does not fix it try doing a service cups restart.
Mark
Hi,
Thanks evryone for giving your support. I downlaoded cups rpm from Centos 4.7 and updated on CentOS 4.5 . But, problem still exists.
Now, May I know Can I download cups from Cent OS 3.6 and install on CentOS 4.5?
The reason for that is , On Cent OS 3.6, it worked perfectly.
Hope to hear from you.
---------- Forwarded message ---------- From: Mark Snyder mark@jmktdis.com Date: Fri, Dec 19, 2008 at 1:38 AM Subject: Re: [CentOS] Unable to connect to printer; will retry in 30 seconds...: Connection timed out To: CentOS mailing list centos@centos.org
Indunil Jayasooriya wrote:
Hi ALL,
I recently withed from CentOS 3 X server to CentOS 4.5. It works fine other than printers.
there are many printers connected to it. We have configured the commnad
printconf
queue type is Networked UNIX (LPD)
Some times, we will be able to print , But, some times, We will NOT be able to print.
We can ping its ip address. Even, when we can't print, We can ping its ip address.
When we check logs , we see something like this.
[Job 888] Unable to connect to printer; will retry in 30 seconds...: Connection timed out
snip
Hope to hear form you.
We have a CentOS 4.x server at a hosting facility that currently has 73 printers defined on various protocols (socket, ipp, lpd) which can see extensive delays in print jobs. We are seeing the same error in our logs. As a work around for this issue you can do a cupsdisable then a cupsenable for the effected printer which should clear the delay and start it working again, provided that you can ping the printer and the printer itself is not causing the problem. If that does not fix it try doing a service cups restart.
Mark
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Indunil Jayasooriya -
John -
Mark Snyder -
MHR