Networker client - Unable to start authentication service
Hello,
# /etc/init.d/networker stop
# rm -rf /nsr
# /etc/init.d/networker start
83401 1313766957 2 0 0 2522863456 11859 0 adsbprd01.adsb.local nsrexecd 284 Warning: The entropy gathering device detected (used to provide random numbers for authentication) may not provide sufficient randomness. This is just an informational warning. Please ensure that a pseudo-random number generator(prngd) is running on this system to avoid this message. 0
# ps -ef | grep nsr
root 11879 11537 0 19:19 pts/0 00:00:00 grep nsr
# cat /nsr/logs/daemon.raw
39078 1313766958 0 0 5 1099794752 11859 0 adsbprd01.adsb.local nsrexecd 14 %s error: %s%s 3 0 6 SYSTEM 49 80 6919 53 Unable to register %ld version %ld on tcp. Aborting.2 2 6 390436 2 1 1 0 0
78109 1313766958 2 0 0 2522863456 11859 0 adsbprd01.adsb.local nsrexecd 38 Unable to start authentication service 0
I could not bring the networker service up. Any help would be highly appreciated.
Entropy part you can ignore. Second part suggest there might be an issue registering with rpc service. Check following:
- selinux is disabled
- check if you have portmap or rpcbind service running (used to be portmap, but RH made recently changes in latest releases.. not sure if that applies to 6.x code or 5.x too).
- do rpcinfo -p localhost... if you have any program starting with 390 registered remove it
- disable nsrauth (since nsrexecd does not run you will need to do this with nsradmin -d /nsr/res/nsrdb command)
- start nsrexecd
- if it still fails, do nsrexecd -D9 > /tmp/nsrexecd.out 2>&1 and check output to get more details
You might have to check if there is any nsrexecd services already running. Also, i suggest you opening a new threas as this thread has been marked as answered and might not get much response.
ble1
6 Operator
•
14354 Posts
•
56186 Points
3527
1
Posted August 19th, 2011 12:00
Entropy part you can ignore. Second part suggest there might be an issue registering with rpc service. Check following:
- selinux is disabled
- check if you have portmap or rpcbind service running (used to be portmap, but RH made recently changes in latest releases.. not sure if that applies to 6.x code or 5.x too).
- do rpcinfo -p localhost... if you have any program starting with 390 registered remove it
- disable nsrauth (since nsrexecd does not run you will need to do this with nsradmin -d /nsr/res/nsrdb command)
- start nsrexecd
- if it still fails, do nsrexecd -D9 > /tmp/nsrexecd.out 2>&1 and check output to get more details