Cups and print server slowing down entire system
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I am a sysadmin, and my computers run Debian Jessie. (I know, I'm working on updating soon.) When I try to print to a network printer, sometimes it works flawlessly. Other times, however, the program I'm printing from will gray out and the print dialog will take forever to come up. All the programs on the computer will hang. At times like these, running lpstat -t will hang as well. Furthermore, after a print job is completed, lpstat -t will show, indefinitely:
Printer printername is idle. Enabled since datetime.
Waiting for printer to finish.
The printer usually accepts more jobs anyway.
Restarting CUPS will usually temporarily fix all of these problems, but I have been unable to identify the source. What can I do to fix this?
Update:
Looking in my log files, I see cupsd is not idle any more, canceling shutdown over and over.
debian cups printer
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
asked Oct 20 '17 at 17:29
Academiphile
108113
add a comment |Â
up vote
2
down vote
favorite
I am a sysadmin, and my computers run Debian Jessie. (I know, I'm working on updating soon.) When I try to print to a network printer, sometimes it works flawlessly. Other times, however, the program I'm printing from will gray out and the print dialog will take forever to come up. All the programs on the computer will hang. At times like these, running lpstat -t will hang as well. Furthermore, after a print job is completed, lpstat -t will show, indefinitely:
Printer printername is idle. Enabled since datetime.
Waiting for printer to finish.
The printer usually accepts more jobs anyway.
Restarting CUPS will usually temporarily fix all of these problems, but I have been unable to identify the source. What can I do to fix this?
Update:
Looking in my log files, I see cupsd is not idle any more, canceling shutdown over and over.
debian cups printer
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
asked Oct 20 '17 at 17:29
Academiphile
108113
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
Problem can in router also,rebootyour router.
– Arpit Agarwal
Oct 28 '17 at 19:49
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am a sysadmin, and my computers run Debian Jessie. (I know, I'm working on updating soon.) When I try to print to a network printer, sometimes it works flawlessly. Other times, however, the program I'm printing from will gray out and the print dialog will take forever to come up. All the programs on the computer will hang. At times like these, running lpstat -t will hang as well. Furthermore, after a print job is completed, lpstat -t will show, indefinitely:
Printer printername is idle. Enabled since datetime.
Waiting for printer to finish.
The printer usually accepts more jobs anyway.
Restarting CUPS will usually temporarily fix all of these problems, but I have been unable to identify the source. What can I do to fix this?
Update:
Looking in my log files, I see cupsd is not idle any more, canceling shutdown over and over.
debian cups printer
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
asked Oct 20 '17 at 17:29
Academiphile
108113
I am a sysadmin, and my computers run Debian Jessie. (I know, I'm working on updating soon.) When I try to print to a network printer, sometimes it works flawlessly. Other times, however, the program I'm printing from will gray out and the print dialog will take forever to come up. All the programs on the computer will hang. At times like these, running lpstat -t will hang as well. Furthermore, after a print job is completed, lpstat -t will show, indefinitely:
Printer printername is idle. Enabled since datetime.
Waiting for printer to finish.
The printer usually accepts more jobs anyway.
Restarting CUPS will usually temporarily fix all of these problems, but I have been unable to identify the source. What can I do to fix this?
Update:
Looking in my log files, I see cupsd is not idle any more, canceling shutdown over and over.
debian cups printer
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
asked Oct 20 '17 at 17:29
Academiphile
108113
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
edited Oct 30 '17 at 20:00
CoreyJJohnson
886
886
asked Oct 20 '17 at 17:29
Academiphile
108113
asked Oct 20 '17 at 17:29
Academiphile
108113
asked Oct 20 '17 at 17:29
Academiphile
108113
108113
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
Problem can in router also,rebootyour router.
– Arpit Agarwal
Oct 28 '17 at 19:49
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28
add a comment |Â
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
Problem can in router also,rebootyour router.
– Arpit Agarwal
Oct 28 '17 at 19:49
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
Problem can in router also,
reboot your router.– Arpit Agarwal
Oct 28 '17 at 19:49
Problem can in router also,
reboot your router.– Arpit Agarwal
Oct 28 '17 at 19:49
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399390%2fcups-and-print-server-slowing-down-entire-system%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I can guess your network printer was not enough memory. How large file did you send to the network printer?You should check your network speed before you did network printing.
– supriady
Oct 26 '17 at 3:04
I have many network printers, and this problem only began recently.
– Academiphile
Oct 26 '17 at 3:04
When you said this problem only began recently. You should check your network. Maybe your network got a problem recently too. Maybe Someone sent a large file to network printer. Did you change anything on CUPS and print server recently?
– supriady
Oct 27 '17 at 4:10
Problem can in router also,
rebootyour router.– Arpit Agarwal
Oct 28 '17 at 19:49
What does localhost:631 say? I think that web server is the most reliable interface to CUPS.
– Alexander
Oct 31 '17 at 9:28