Date: Sat, 25 Mar 2006 01:07:24 GMT From: Christopher Sean Hilton <chris@vindaloo.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/94920: rpd.statd conflict with cups over tcp and udp ports 631 Message-ID: <200603250107.k2P17OBK005538@www.freebsd.org> Resent-Message-ID: <200603250110.k2P1AFxA031003@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 94920 >Category: misc >Synopsis: rpd.statd conflict with cups over tcp and udp ports 631 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 25 01:10:15 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Christopher Sean Hilton >Release: 5.4-STABLE >Organization: >Environment: FreeBSD endaba.vindaloo.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Thu Jun 9 16:25:22 EDT 2005 chris@endaba:/usr/obj/usr/src/sys/ENDABA i386 >Description: rpc.statd can grap tcp and udp ports 631 on startup before the cups daemon starts. This would normally only cause a problem with printing at random on the affected machine. However, if the network contains a cups server which sends out broadcasts on udp port 631 that will hose up the rpc.statd daemon and eventually cause poor NFS performance or a hang. >How-To-Repeat: I don't know how rpc.statd determine which port it uses. To me it appears random. You will know if you have the problem if cups complains at startup. Something to the effect of "cupsd: Child exited with status 48" Use sockstat -4 | grep 631 to see if rpc.statd (or rpc.lockd perhaps) is on port 631. >Fix: Reboot until rpc.statd doesn't grab port 631. A more permanent fix would be to change the code in rpc.statd (or wherever) to avoid using port 631. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603250107.k2P17OBK005538>