Samuel,

     What flavour of LINUX are you using. Run the following command and provide the output.

nsrexecd -D5

Before you use the debug mode you may already look at the appropriate log file using this command:

  nsr_render_log /nsr/logs/daemon.raw

Maybe the info here already points to the problem.

Of course you should also repeat that command after you used the debug mode.

If you don't see nsrexecd, that means daemon was not started.  Try to run it again.  If the same happens, try to run it from CLI in debug mode as mentioned before, but indeed - you may wish to check daemon.raw first.  It might be that something is already blocking standard ports by NW and thus they can't register.

Hi Samuel,

This Networker is a fresh install or it was working?

Attach the daemon.raw log is better to help you.

cheers,

Check if the service/deamon is getting carshed.

Check if the nsr directory, see is there any 'cores' present there inside it. If so it might be core dump issue.

Fresh Installation

Samuel,

I think this could be linked to the version of the libstdc++ Library you have installed. You have not mentioned the specific version of Linux you are using but newer OS has version 6 installed by default and NetWorker needs version 5 to run.

See Articles in Knowledgebase on Support.emc.com for how to correct (basically you install version 5 and it will then start correctly).

Here are the article references:

SUSE12 - 000198556

RedHat7 - 000198499

Regards,

Bill Mason

You could still run the "nsrexecd -D5" for a debug output. Also, provide an output of the rpcinfo command, just to confirm if no other service is using the ports that are required for NetWorker.

Hello All,

Finally I got the solution. Its due to wrong entry in /etc/hosts file.

Thanks all for your suggestion & advise on below issue.

~ Sam

Please close the thread as answered.