Operating System - HP-UX
1838250 Members
5092 Online
110125 Solutions
New Discussion

Legato Networker error message

 
Leon A. Howorth
Advisor

Legato Networker error message

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 ??
6 REPLIES 6
RAC_1
Honored Contributor

Re: Legato Networker error message

What does /nsr/logs/messages file say?

Any error there?

Anil
There is no substitute to HARDWORK
G. Vrijhoeven
Honored Contributor

Re: Legato Networker error message

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

RAC_1
Honored Contributor

Re: Legato Networker error message

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


Anil
There is no substitute to HARDWORK
Abdul Rahiman
Esteemed Contributor

Re: Legato Networker error message

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.
No unix, no fun
Robert-Jan Goossens
Honored Contributor

Re: Legato Networker error message

Hi,

Did you change the hostname of the server ?

Could you check the output from

# nslookup hostname
# nslookup ip-address

Regards,
Robert-Jan
Leon A. Howorth
Advisor

Re: Legato Networker error message

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".