This post is more than 5 years old
34 Posts
0
10977
Start Service Problem
Hello,
I have problem when start the service networker is presenting this error below.
83401 1337258789 2 0 0 1182724688 7646 0 localhost.localdomain 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
thank you.
pn1lDbv3G612259
105 Posts
0
May 17th, 2012 09:00
Hi Gracci,
Looks like the services are already running and you might have trying to restart them again.
Please check if there are any Networker process running on the server.
Also, check if the Networker is using the default ports
Normally portmapper uses port 111. Check if that port is been used by some other process
Thank you
ShivaKiran
pn1lDbv3G612259
105 Posts
0
May 17th, 2012 07:00
Hi,
Please let us know the OS which you are using? Are you using the command line option to restart the services?
Thank you
ShivaKiran
agracci
34 Posts
0
May 17th, 2012 07:00
Hi,
Yes, command line strat service
Linux SAODS1910 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
Client Networker Version: lgtoclnt-7.6.2.1-1
Command: nsrexecd -s saobs1903.dir.svc.accenture.com -D9 &
0 1337266125 2 0 0 1100884288 7977 0 localhost.localdomain nsrexecd 2 %s 1 0 63 Failed to bind to socket for portmapper: Address already in use
75770 1337266125 2 0 0 1100884288 7977 0 localhost.localdomain nsrexecd 42 Failed to start NSR portmapper service: %s 1 24 22 Address already in use
78106 1337266125 2 0 0 1752986192 7977 0 localhost.localdomain nsrexecd 34 Unable to start portmapper service 0
Thank you
Gracci
agracci
34 Posts
0
May 17th, 2012 10:00
Hi Shivakiran,
Thank you for the help.
danag2
20 Posts
0
May 18th, 2012 05:00
Port 111 has been depricated by use of port 7938. He is runnig on Linux and I am running on Windows 2003/2008 and have started seeing this message. If the "fix" is to restart the service from command line then I'm in trouble because you cant restart the service in a production environment on a daily basis.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 21st, 2016 02:00
The portmapper problem happens when the hostname conflict conflict, the reason could be virtual machine is cloned to other machine and not brought up with new IP/hostname/port properly ..
I faced the same issue , my NetWorker services were not starting up.
Once I resolved the hostname to a new hostname in all the entries in the cloned machine and rebooted the machine, the services automatically came up.