Bug 132318
Summary: | BrowsePoll fails after 5 minutes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Kevin Otte <kotte> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | imcguire, jdreese, mike.whitney, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:18:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kevin Otte
2004-09-10 20:57:23 UTC
an strace -p against the cups-polld process indicates that when it is done retrieving the printer list, it goes into a nanosleep({2147483647,0},...), or a 68 year wait, as opposed to the 30 second wait it is supposed to go into. The problem also exists in cups-1.1.17-13.3.13. The problem manifests itself when BrowseInterval < number_of_printers. Norm is looking at this but he needs the broken cups.conf and the mechanism being used to monitor the printer list? (he is using printtool) The cups.conf is unmodified from its packaged state. I am just using an lpstat -a and also tail -f'ing the contents of /var/log/cups/error_log. Kevin: could you possibly provide the full strace output? Thanks. I have stumbled over this problem on our systems as well. We are currently using the workaround of increasing BrowseInterval to be greater than the number of printers discovered on thet browse source. As a useful debugging tip, you can kick the cups-polld out of its 68 year wait by sending it a SIGSTOP followed by a SIGCONT. I can get an strace of a full poll cycle this way, but haven't figured out how to strace from the beginning when it's fired off from cupsd. Mike: do you still see this problem? This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |