Description of problem: In a networked environment, remote printers are not listed by CUPS because rpcbind is listening on 0.0.0.0:631. Trying to print anything from a GUI application or running system-config-printer shows no network printers. Restarting CUPS has no effect. The only solution is to stop CUPS and rpcbind, start CUPS and then restart rpcbind. Not sure if this is actually a cups problem, but since the result is that you can't print, I thought we could start there. Version-Release number of selected component (if applicable): # rpm -q cups portreserve rpcbind cups-1.3.9-6.fc10.i386 portreserve-0.0.3-2.fc10.i386 rpcbind-0.1.7-1.fc10.i386 How reproducible: Not reproducible yet. Has occurred twice in the last week. Steps to Reproduce: 1. Reboot system. 2. Try to print something to a network printer. Actual results: No network printers shown. The command "netstat -l -n -p | grep 631" shows: # netstat -l -n -p | grep 631 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 3091/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 2580/rpcbind udp 0 0 :::631 :::* 2580/rpcbind Expected results: Network printers should be shown. Additional info: Will attach /var/log/cups/*_log, /etc/cups/cupsd.conf. Please let me know if anything else will help.
Created attachment 333107 [details] CUPS Access Log
Created attachment 333108 [details] CUPS Error Log
Created attachment 333111 [details] /var/log/boot.log Boot log. Note that portreserve starts _after_ rpcbind: Starting rpcbind: [ OK ] Starting NFS statd: [ OK ] Starting RPC idmapd: [ OK ] Starting system message bus: [ OK ] Starting acpi daemon: [ OK ] Starting HAL daemon: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] Loading autofs4: [ OK ] Starting automount: [ OK ] Starting portreserve: [ OK ] Could this be the problem?
OK. This is weird... /etc/rc.d/init.d/portreserve contains: #!/bin/sh # # portreserve This script starts and stops the TCP port reserver # Originally written by Tim Waugh from Red Hat # Adapted to Debian by Javier Fernandez-Sanguino # # chkconfig: 2345 11 89 # description: TCP port reservation utility # ### BEGIN INIT INFO # Provides: portreserve # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 0 6 # Short-Description: Port reservation utility # Description: Portreserve is a TCP port reservation utility # that can be use to prevent RPC services from # picking up well-known reserved ports. ### END INIT INFO but /etc/rc.d/rc{2,3,4,5}.d/*portreserve contains: # ls /etc/rc.d/rc{2,3,4,5}.d/*portreserve /etc/rc.d/rc2.d/S28portreserve /etc/rc.d/rc4.d/S28portreserve /etc/rc.d/rc3.d/S28portreserve /etc/rc.d/rc5.d/S28portreserve That's not right, is it?
No, it's not. I had this on my system as well, but running 'chkconfig --add portreserve' (trying to diagnose it) fixed the priorities back to S11 and K89. I can't see anything wrong with the LSB header, and all the required-start dependencies seem to resolve correctly with the suggested priorities: portreserve: 11 required-start: $network | V network: 10 provides: $network should-start: iptables ip6tables | V iptables: 08 ip6tables: 08 The only thing that seems to be not as it should be is that the cups initscript ought to have 'Should-Start: portreserve' -- but this is no reason for portreserve's start priority to be set as high as 28! Changing component to chkconfig as it seems to have miscalculated the start/kill priorities.
NetworkManager (which provides $network for him) started at 27; chkconfig's doing the right thing.
Ah, I should have seen that from comment #4, sorry. Hmm, seems like portreserve doesn't need to require $network after all then. Will change.
portreserve-0.0.4-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/portreserve-0.0.4-1.fc10
portreserve-0.0.4-1.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update portreserve'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2104
portreserve-0.0.4-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.