topic Re: DCED/RPCD cannot be started in Operating System - HP-UX

DCED/RPCD cannot be started

Nisar Ahmad — Tue, 28 Jan 2003 23:13:34 GMT

Hi There

I tried to start DCED/RPCD 1.7 on the HP-UX 11.0 but after different tries no succes.

Any clue please

Thanks in advance

Nisar

Re: DCED/RPCD cannot be started

Sridhar Bhaskarla — Tue, 28 Jan 2003 23:33:52 GMT

Hi Nisar,

You will get clues from /var/opt/dce/svc/fatal.log or error.log or warning.log.

Look at them and post the entries here.

It could be most probably the network. Make sure all the configured lan cards are working.

-Sri

Re: DCED/RPCD cannot be started

Uday_S_Ankolekar — Tue, 28 Jan 2003 23:38:00 GMT

Did you try

/sbin/init.d/Rpcd start ??

-USA..

Re: DCED/RPCD cannot be started

Nisar Ahmad — Tue, 28 Jan 2003 23:40:25 GMT

Hi Uday

Yes I tried that and also "# RPCD -c"

Thanks

Nisar

Re: DCED/RPCD cannot be started

Uday_S_Ankolekar — Tue, 28 Jan 2003 23:55:51 GMT

Try..
/opt/dce/sbin/rpcd
If it os not started then

Check for error log in..
/var/opt/dce/svc

-USA..

Re: DCED/RPCD cannot be started

Nisar Ahmad — Wed, 29 Jan 2003 01:33:19 GMT

Hi Uday

I tried as you suggested and it gave following error in fatal.log:

2003-01-29-00:19:14.546+00:00I----- dced FATAL dhd general main.c 719 0x7f7825a0
Cannot use '*all*' protocol sequence, Address already in use

Thanks

Nisar

Re: DCED/RPCD cannot be started

T G Manikandan — Wed, 29 Jan 2003 05:33:12 GMT

The problem is because of 135 port which is used by rpcd is already used by some other process.
From the knowledge base,

//*Fatal.log reports: Cannot use '*all*' protocol sequence, Address already in use.

Rpcd won't start because it needs port 135 and some other process already has it. Locate the failing process by running netstat -an looking for port 135:

# netstat -an | grep 135
tcp 0 0 *.135 *.* LISTEN
udp 0 0 *.135 *.*This netstat shows there is a Listener on port 135. To locate which process ID owns port 135:

# cd /opt/dcelocal/var/rpc/local
# grep 135 */srvr_socks
01351/srvr_socks:/opt/dcelocal/var/rpc/local/s-0/135
01351/srvr_socks:/opt/dcelocal/var/rpc/local/s-3/135
^--------- PIDThe first number in the pathname is the process ID, in this case, 1351. The offending process in this example is perflbd:

*//

# ps -ef |grep 1351

This should give you the process that is already using the port 135

Re: DCED/RPCD cannot be started

Ian Timms — Tue, 25 Mar 2003 12:46:57 GMT

The rpc daemon fails on my HP-UX 11.0 C3000 m/c.
The 'combined' error.log & fatal.log in: /var/opt/dce/svc are attached.

Any ideas?

Re: DCED/RPCD cannot be started

Alex Glennie — Tue, 25 Mar 2003 13:04:16 GMT

yes

a) start a new itrc forums thread for this

b) detail "file core"

c) take a look at http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x9a954a988422d711abdc0090277a778c,00.html