RPC: Rpcbind failure

[Pauline Patricia]

Update syslog file..

[Pauline Patricia]

Hi,

after i make changes in the /etc/nsswitch.conf in ignite client, I tried to mount the nfs share in client.

the following error msg.

wfdb:root-/tmp>mount -F nfs ignite:/var/opt/ignite/clients /tmp/directory1/
nfs mount: get_fh: ignite:: RPC: Unknown host
wfdb:root-/tmp>

[Horia Chirculescu]

Seems that you have a configuration problem related to rpcbind

Feb 17 13:30:38 ignitsvr rpcbind: init_transport: udp: cannot bind: address in use

Seems that rpcbind it is called again and this conflicts with the previous call (rpcbind allready running).

[Horia Chirculescu]

In this case, I would start rpcbind on debug mode (kill the daemon first, of course!) rpcbind -d, see:

man 1M rpcbind

And see what messages I get from this daemon.

Horia.

[Johnson Punniyalingam]

from the Ignite Client

Example :-

# ps -ef |grep rpc
root 725 1 0 Jul 28 ? 0:01 /usr/sbin/rpcbind
root 767 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.lockd
root 761 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.statd
root 1154 1 0 Jul 28 ? 12:05 /opt/dce/sbin/rpcd
root 1646 1 0 Jul 28 ? 0:00 /usr/sbin/rpc.mountd
root 4568 3369 1 18:00:43 ttyp2 0:00 grep rpc

# kill -9 725 1154 (.....to permanently kill the Process ID for "rpcbind" and "rpcd" daemons)

# /sbin/rc2.d/S590Rpcd start (.....to restart the "rpcd" daemon)

# /usr/sbin/rpcbind (.....to restart the "rpcbind" daemon)

# ps -ef |grep rpc (.....both daemons should be showing the current time)

[Pauline Patricia]

Hi,

I did the following

wfdb:root-/>ps -ef |grep rpc
root 3890 1 0 Feb 15 ? 0:00 /usr/sbin/rpc.lockd
root 3884 1 0 Feb 15 ? 0:00 /usr/sbin/rpc.statd
root 7072 1 0 Feb 15 ? 0:01 /opt/dce/sbin/rpcd
root 28606 1 0 Feb 16 ? 0:00 /usr/sbin/rpc.mountd
root 3847 1 0 Feb 15 ? 0:00 /usr/sbin/rpcbind
root 10148 10132 1 08:21:00 pts/0 0:00 grep rpc
wfdb:root-/>
wfdb:root-/>kill -9 3847 7072
wfdb:root-/>sbin/rc2.d/S590Rpcd start
starting the DCE RPC Daemon
/opt/dce/sbin/rpcd
wfdb:root-/>/usr/sbin/rpcbind
wfdb:root-/>ps -ef |grep rpc
root 3890 1 0 Feb 15 ? 0:00 /usr/sbin/rpc.lockd
root 3884 1 0 Feb 15 ? 0:00 /usr/sbin/rpc.statd
root 10220 1 0 08:21:50 ? 0:00 /usr/sbin/rpcbind
root 28606 1 0 Feb 16 ? 0:00 /usr/sbin/rpc.mountd
root 10226 10132 0 08:21:55 pts/0 0:00 grep rpc
root 10218 1 0 08:21:39 ? 0:00 /opt/dce/sbin/rpcd

Even then I get the same error msg:

wfdb:root-/>mount -F nfs ignitsvr:/var/opt/ignite/clients /tmp/directory1/
nfs mount: get_fh: ignitsvr:: RPC: Rpcbind failure - RPC: Timed out

I have done hardening using Bastille Security Hardening Tool. Does this really cause any restriction in my server related to RPC. Please advise

[Johnson Punniyalingam]

>> I have done hardening using Bastille Security Hardening Tool. Does this really cause any restriction in my server related to RPC. Please advise <<<

Yes. YES. YEs

[Pauline Patricia]

Could you pls tell me at what point the restriction would have occured.

[Johnson Punniyalingam]

Can you look for "rpc" in below "files"

# grep -i rpc /etc/services

# grep -i rpc /etc/inetd.conf

[Pauline Patricia]

wfdb:root-/>grep -i rpc /etc/services
portmap 111/tcp sunrpc # SUN Remote Procedure Call
portmap 111/udp sunrpc #
courier 530/tcp rpc #
p7_c33upd 8545/tcp #TSD acceSS7 configuration update RPC server
p7_c33 8546/tcp #TSD acceSS7 configuration RPC server
p7_c32 8547/tcp #TSD acceSS7 communications status RPC server
p7_c35 8548/tcp #TSD acceSS7 communications configuration RPC server
p7_g06 8549/tcp #TSD acceSS7 application version registration RPC server
p7_e30 8550/tcp #TSD acceSS7 event manager RPC server
SrpCentralDaemon 6179/tcp # acceSS7 Statistics Central Server query daemon
wfdb:root-/>grep -i rpc /etc/inetd.conf
# rpc services, registered by inetd with portmap
# WARNING: The rpc.mountd should now be started from a startup script.
# Please enable the mountd startup script to start rpc.mountd.
rpc stream tcp nowait root /usr/sbin/rpc.rexd 100017 1 rpc.rexd
rpc dgram udp wait root /usr/lib/netsvc/rstat/rpc.rstatd 100001 2-4 rpc.rstatd
rpc dgram udp wait root /usr/lib/netsvc/rusers/rpc.rusersd 100002 1-2 rpc.rusersd
rpc dgram udp wait root /usr/lib/netsvc/rwall/rpc.rwalld 100008 1 rpc.rwalld
rpc dgram udp wait root /usr/sbin/rpc.rquotad 100011 1 rpc.rquotad
rpc dgram udp wait root /usr/lib/netsvc/spray/rpc.sprayd 100012 1 rpc.sprayd
rpc xti tlcotsod wait root /usr/lib/gss/gssd 100234 1 gssd
rpc xti tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1 /usr/dt/bin/rpc.ttdbserver
rpc dgram udp wait root /usr/dt/bin/rpc.cmsd 100068 2-5 rpc.cmsd
wfdb:root-/>

[Johnson Punniyalingam]

Sorry, I have never used "Bastille" to handern servers.

But You can look below -> Doc's which give clear picture and you can proceed further.

Once you use "Bastille" -> Hardern server
Bastille can create a very basic firewall configuration

Check this out.
http://docs.hp.com/en/B2355-90950/apbs01.html

[Pauline Patricia]

I had a look in to the doc which you had given and I found that remshd services was disbled in my Ignite server and client which is actually required for Ignition.

I enabled remshd services in my server and client. Now I get different msg.

ERROR: Cannot retrieve Ignite-UX version from server "ignitsvr".

Could you please help me out. Am really struggling with this issue for past five days.

[R.K. #]

Hi Patricia,

May be issue is with tftp. Ignite sometimes uses tftp to pull certain files.

Check if tftp is working properly:

/etc/services and /etc/inetd.conf --> tftp must be enabled and registered

Then try tftp:
# tftp ignitsvr
tftp> get

See, if you get any error.

[Pauline Patricia]

Tftp is already running in server and client.

From Ignite client I tried to get some files available in ignite server. I get the following error msg.

wfdb:root-/>tftp ignitsvr
tftp> get ignitsvr:/tmp/unload.log /tmp/unload.log
Error code 2: Access violation
Error code 2: Access violation
Error code 2: Access violation
tftp>

[Johnson Punniyalingam]

>>From Ignite client I tried to get some files available in ignite server. I get the following error msg.<<

Check your folder permissions ????

man tftpd:
In this case access is restricted to files whose names
are prefixed by the one of the given directories.

[Johnson Punniyalingam]

Symptom:
File transfer fails with Access Violation, Permission Denied, or TFTP Error Code 2 message.

Cause:
tftpd does not have permission to read the file.

http://docs.hp.com/en/B2355-90147/ch05s08.html#cdbchjdd

Its been hard-time for you "going through" lot of trouble shootings, You know why ? You Subject Started with "RPC:- Rpcbind" failure

slowly slowly, you are posting .. that my "Server is harden" -> Sounds to me we are all shooting in >>Dark<< -... :( if you would have clear description of your problem. It would be help full for others . help and advice you accordingly

[Horia Chirculescu]

Hello Pauline,

You should take a look at the ports that IGNITE is using. Then be sure that ALL those ports are opened on the ignitsvr and on the server trying to mount the NFS volume(/IGNITE) your using bastille.

http://docs.hp.com/en/5992-6584/5992-6584.pdf

Horia.

[Horia Chirculescu]

Read

8.1 Ignite-UX Server Ports

Horia.

[R.K. #]

Hello,

Make changes in inetd.conf and enable logging:

# grep ^tftp /etc/inetd.conf
tftp dgram udp wait root /usr/lbin/tftpd -l tftpd

Now, start do tftp transfer from command line and check for tftpd messages in /var/adm/syslog/syslog.log

Also check if UDP port is enabled in the firewall.