topic Re: Legato Networker error message in Operating System - HP-UX

Legato Networker error message

Leon A. Howorth — Mon, 21 Jun 2004 12:55:48 GMT

The following error message appears when trying to start Legato networker on an HP-UX 11.11 system:
06/21/04 12:21:49 nsrd: server notice: started
06/21/04 12:21:50 nsrlmc: nsrd did not respond. nsrd must be started before running nsrlmc.
If nsrd is running, you may have exceeded a resource limit

The sequence of commands is:
nsrexecd
nsrd

Any idea what "resource limit" is being exceeded ??

Re: Legato Networker error message

RAC_1 — Mon, 21 Jun 2004 13:26:10 GMT

What does /nsr/logs/messages file say?

Any error there?

Anil

Re: Legato Networker error message

G. Vrijhoeven — Mon, 21 Jun 2004 13:57:26 GMT

Hi,

In addition to Anil, take a look at /nsr/logs/deamon.log for more info.

Is the port nsrd tries to use free?
Did you try a restart?
/sbin/init.d/networker stop
/sbin/init.d/networker start

Found simular error:

http://216.239.59.104/search?q=cache:FhcjheQxMZgJ:support.mti.com/MTICare/Legato/Documents/license_manager/licmgrag.pdf++nsrlmc:+nsrd+did+not+respond&hl=en

HTH,

Gideon

Re: Legato Networker error message

RAC_1 — Mon, 21 Jun 2004 13:59:31 GMT

Are all licenses in place??
I do not know a command, to check license details on Legato??

Anil

Re: Legato Networker error message

Abdul Rahiman — Mon, 21 Jun 2004 14:42:16 GMT

This error message soud like a license related error,

Check your networker license using the nsrlic command..

# nsrlic -v -s "servername"

Resource that it may be referring to could eb tape drives, juke box etc. limited by the license.

regds,
Abdul.

Re: Legato Networker error message

Robert-Jan Goossens — Mon, 21 Jun 2004 15:01:27 GMT

Hi,

Did you change the hostname of the server ?

Could you check the output from

# nslookup hostname
# nslookup ip-address

Regards,
Robert-Jan

Re: Legato Networker error message

Leon A. Howorth — Tue, 22 Jun 2004 09:29:51 GMT

Thanks for the replies. Robert Jans-Goossens reply was especially helpful. It was a simple host naming issue. The server is using /etc/hosts rather than DNS and the server's name in /etc/hosts was not fully qualified (such as myserver.xyzcompany.com), it was simply "myserver".