Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

DCED/RPCD cannot be started

Nisar Ahmad
Regular Advisor

DCED/RPCD cannot be started

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
8 REPLIES
Sridhar Bhaskarla
Honored Contributor

Re: DCED/RPCD cannot be started

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
You may be disappointed if you fail, but you are doomed if you don't try
Uday_S_Ankolekar
Honored Contributor

Re: DCED/RPCD cannot be started

Did you try

/sbin/init.d/Rpcd start ??


-USA..
Good Luck..
Nisar Ahmad
Regular Advisor

Re: DCED/RPCD cannot be started

Hi Uday

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

Thanks

Nisar
Uday_S_Ankolekar
Honored Contributor

Re: DCED/RPCD cannot be started

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

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

-USA..
Good Luck..
Nisar Ahmad
Regular Advisor

Re: DCED/RPCD cannot be started

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
T G Manikandan
Honored Contributor

Re: DCED/RPCD cannot be started

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

Ian Timms
Advisor

Re: DCED/RPCD cannot be started


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?

Alex Glennie
Honored Contributor

Re: DCED/RPCD cannot be started

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