Date: Tue, 01 May 2018 08:55:31 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 227888] random port selection for daemons cause other daemons to fail Message-ID: <bug-227888-99@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 Bug ID: 227888 Summary: random port selection for daemons cause other daemons to fail Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: standards Assignee: standards@FreeBSD.org Reporter: d8zNeCFG@aon.at The issue described here has caused problems for me for a long time. Scenario: - Small home server running lots of services: amd, apache24, ataidle, cupsd, dbus, delegate, dhcpd, dhcpd6, firewall, gateway, hald, hylafax, inetd, ipv6_gateway, kdm4, moused, mpd, mysql, named, nfs_client, nfs_server, nis_client, nis_server, nis_yppasswdd, ntpd, openvpn, postgresql, powerd, rpc_lockd, rpc_statd, rpcbind, rtadvd, rtsold, rwhod, samba_server, sendmail, squid, sshd, syslogd, winbindd, zfs Result: - Rather often (estimated 10% of all reboots) one of the daemons using random port numbers chooses one which is later on required by another daemon which needs a well-known port number to operate - Example today: mountd listens on port 631 which is required by cups, therefore cups does not work - Example from a few days ago: ypbind listens on 873 which is required by inetd configured to spawn rsync Expected result: - Ports should be chosen so as not to cause conflicts Proposed mitigation measure: Revert to using well-known port numbers for standard system daemons like it was done ages ago. -- Martin -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227888-99>