Cups-1.3.7-32.el5_11.x86_64 May Have A Problem

Home » CentOS » Cups-1.3.7-32.el5_11.x86_64 May Have A Problem
CentOS 2 Comments

Everyone,

I have a problem I have been chasing for about three weeks and only occurred after cups was updated with cups-1.6.3-22.el7. I would be interested as to whether any one else has had this problem, and would entertain suggestions as to how I can debug the problem.

My CentOS 5 server is a gateway as well as a cups print server that has been in place for 8 years and has continued to perform exceptionally well.

My CentOS 7 server is a mail server and archive file server that is in the same network as my CentOS 5 server described above. I have cups active on this server, which communicates to the CentOS 5 server described above as well as another remote CentOS 5 cups print server and another remote CentOS 6 cups print server. Each of the latter two print servers are on different networks than the CentOS 7 server that has the problem.

The problem that has been occurring for the last three weeks appears to be related to the CentOS 7 server or communication failure between it and the CentOS 5 print server in the same network. What happens is that when the CentOS 7 archive server receives a command to print an archived file on one of the printers inside its own network it appears to send several print commands to the CentOS 5 server which causes the file to be printed several times. What happens is that the users eventually turn off the printer to keep the file from being printed dozens of times, and eventually the cups print queue on the CentOS 5 server becomes full and all the printers in that network become unreachable with print commands. It is interesting that the remote print servers appear to function normally during this time.

The only way I have figured out to remedy the problem is the use the
“cancel -u user” command on the CentOS 5 server to get rid of the command on the CentOS 5 server and to use cancel lpt2-xxxxx on the Centso 7 server to get rid of the command on the archive server. When I
evaluate the logs, I am either blind to the problem or am not seeing much I can piece together.

Both machines have all updates and are listed as :

Gateway and Cups Print Server :
CentOS release 5.11 (Final)
with 2.6.18-407.el5.CentOS.plusxen kernel with cups-1.3.7-32.el5_11.x86_64

Mail server and Archive File server :
CentOS Linux release 7.2.1511 (Core)
with 3.10.0-327.4.4.el7.x86_64 kernel
with cups-1.6.3-22.el7.x86_64

If any of you have ideas, would sure appreciate your help.

Greg Ennis

2 thoughts on - Cups-1.3.7-32.el5_11.x86_64 May Have A Problem

  • Everyone,

    I have a problem I have been chasing for about three weeks and only occurred after cups was updated with cups-1.6.3-22.el7.  I would be interested as to whether any one else has had this problem, and would entertain suggestions as to how I can debug the problem.

    My CentOS 5 server is a gateway as well as a cups print server that has been in place for 8 years and has continued to perform exceptionally well.

    My CentOS 7 server is a mail server and archive file server that is in the same network as my CentOS 5 server described above.  I have cups active on this server, which communicates to the CentOS 5 server described above as well as another remote CentOS 5 cups print server and another remote CentOS 6 cups print server.  Each of the latter two print servers are on different networks than the CentOS 7 server that has the problem.

    The problem that has been occurring for the last three weeks appears to be related to the CentOS 7 server or communication failure between it and the CentOS 5 print server in the same network.  What happens is that when the CentOS 7 archive server receives a command to print an archived file on one of the printers inside its own network it appears to send several print commands to the CentOS 5 server which causes the file to be printed several times.  What happens is that the users eventually turn off the printer to keep the file from being printed dozens of times, and eventually the cups print queue on the CentOS 5 server becomes full and all the printers in that network become unreachable with print commands.  It is interesting that the remote print servers appear to function normally during this time.

    The only way I have figured out to remedy the problem is the use the
    “cancel -u user” command on the CentOS 5 server to get rid of the command on the CentOS 5 server and to use cancel lpt2-xxxxx on the Centso 7 server to get rid of the command on the archive server.  When I
    evaluate the logs, I am either blind to the problem or am not seeing much I can piece together.   

    Both machines have all updates and are listed as :

    Gateway and Cups Print Server :
    CentOS release 5.11 (Final)
     with 2.6.18-407.el5.CentOS.plusxen kernel
     with cups-1.3.7-32.el5_11.x86_64

    Mail server and Archive File server :
    CentOS Linux release 7.2.1511 (Core)
      with 3.10.0-327.4.4.el7.x86_64 kernel
      with cups-1.6.3-22.el7.x86_64

    If any of you have ideas, would sure appreciate your help.

    Greg Ennis

    ———————————————————————–

    Unfortunately, I am still contending with this problem.  It appears that when the cups-1.6.3-22.el7.x86_64 sends a file to the server that has the printers defined which uses cups-1.3.7-32.el5_11.x86_64 the cups-1.6.3-22.el7.x86_64 continues to resend the file over and over again.  I have the logs set to ‘DEBUG’, but the Logs do not tell me much other than the file is resent in the page log file. The entries below were duplicated about 250 times. 

    lpt2 mail 3621 [21/Jan/2016:23:00:24 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:25 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:26 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:28 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:31 -0600] total 0 – localhost smile.pr.d4UBof.o –

    Any one have any ideas how I could debug this

    Greg

  • Everyone,

    I have a problem I have been chasing for about three weeks and only occurred after cups was updated with cups-1.6.3-22.el7.  I would be interested as to whether any one else has had this problem, and would entertain suggestions as to how I can debug the problem.

    My CentOS 5 server is a gateway as well as a cups print server that has been in place for 8 years and has continued to perform exceptionally well.

    My CentOS 7 server is a mail server and archive file server that is in the same network as my CentOS 5 server described above.  I have cups active on this server, which communicates to the CentOS 5 server described above as well as another remote CentOS 5 cups print server and another remote CentOS 6 cups print server.  Each of the latter two print servers are on different networks than the CentOS 7 server that has the problem.

    The problem that has been occurring for the last three weeks appears to be related to the CentOS 7 server or communication failure between it and the CentOS 5 print server in the same network.  What happens is that when the CentOS 7 archive server receives a command to print an archived file on one of the printers inside its own network it appears to send several print commands to the CentOS 5 server which causes the file to be printed several times.  What happens is that the users eventually turn off the printer to keep the file from being printed dozens of times, and eventually the cups print queue on the CentOS 5 server becomes full and all the printers in that network become unreachable with print commands.  It is interesting that the remote print servers appear to function normally during this time.

    The only way I have figured out to remedy the problem is the use the
    “cancel -u user” command on the CentOS 5 server to get rid of the command on the CentOS 5 server and to use cancel lpt2-xxxxx on the Centso 7 server to get rid of the command on the archive server.  When I
    evaluate the logs, I am either blind to the problem or am not seeing much I can piece together.   

    Both machines have all updates and are listed as :

    Gateway and Cups Print Server :
    CentOS release 5.11 (Final)
     with 2.6.18-407.el5.CentOS.plusxen kernel
     with cups-1.3.7-32.el5_11.x86_64

    Mail server and Archive File server :
    CentOS Linux release 7.2.1511 (Core)
      with 3.10.0-327.4.4.el7.x86_64 kernel
      with cups-1.6.3-22.el7.x86_64

    If any of you have ideas, would sure appreciate your help.

    Greg Ennis

    ———————————————————————–

    Unfortunately, I am still contending with this problem.  It appears that when the cups-1.6.3-22.el7.x86_64 sends a file to the server that has the printers defined which uses cups-1.3.7-32.el5_11.x86_64 the cups-1.6.3-22.el7.x86_64 continues to resend the file over and over again.  I have the logs set to ‘DEBUG’, but the Logs do not tell me much other than the file is resent in the page log file. The entries below were duplicated about 250 times. 

    lpt2 mail 3621 [21/Jan/2016:23:00:24 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:25 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:26 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:28 -0600] total 0 – localhost smile.pr.d4UBof.o – –

    lpt2 mail 3621 [21/Jan/2016:23:00:31 -0600] total 0 – localhost smile.pr.d4UBof.o –

    Any one have any ideas how I could debug this

    Greg

    ———————————————————————-
    Everyone,

    I have created a bug report on this problem.

    https://bugs.CentOS.org/view.php?id=10226

    Greg