Asset ID:	1-72-1012320.1
Update Date:	2010-06-29
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1012320.1 :   Sun Fire[TM] 12K/15K/20K/25K: Domain reports "sun-dr/tcp: bind: Address already in use"  


PreviouslyPublishedAs
217002

Applies to:

Sun Enterprise 10000 Server
Sun Fire 12K Server
Sun Fire 15K Server
Sun Fire E20K Server
Sun Fire E25K Server
All Platforms
***Checked for relevance on 29-Jun-2010***

Symptoms

The following message is reported in the /var/adm/messages file of a 12k/15k domain:

inetd[3008]: [ID 161378 daemon.error] sun-dr/tcp: bind: Address already in use

Cause

The error message indicates that inetd is unable to bind to a port, because something else is using the port. If you look at the /etc/inet/services file, you will see that sun-dr uses port 665:

sun-dr 665/tcp # Remote Dynamic Reconfiguration

From the dcs man page:

"The Domain Configuration Server (DCS) is a daemon process
that runs on Sun servers that support remote Dynamic Recon-
figuration (DR) clients. It is started by inetd(1M) when the
first DR request is received from a client connecting to the
network service sun-dr."

dcs will be started when a DR operation is initiated, but it will not exit when
the DR operation is complete. If inetd is restarted when dcs is still running,
inetd will not be able to bind to port 665.

To determine if this is the cause of the "sun-dr/tcp: bind: Address already in
use" messages you are seeing, look at ps -ef output.

* First, if the dcs process is running, look at the time stamp in the ps output.
In the following example, dcs was started on January 19th:

# ps -ef | grep dcs
root 12328 1 0 Jan 19 ? 0:00 dcs

* Next, look for inetd. This output shows that inetd was restarted on the 27th:

# ps -ef | grep inetd
root 3178 1 0 Jan 27 ? 0:12 /usr/sbin/inetd -s

The error messages from inetd began on January 27th, after inetd was restarted.
Because inetd was restarted on the 27th, it is unable to bind to port 665
because dcs is still holding the port.

Solution

To resolve the problem, kill the dcs process and restart inetd. The error messages will stop, and dcs will be started automatically when a DR operation is performed in the future. There is no need to restart dcs manually.





Attachments

This solution has no attachment