Hello Oscar,

since round about ten days we have a NSR 7.3 test installation with a SLES9 
networker server, because we must update our productive landscape very 
urgent (to get SLES9 support for storage nodes in a SAN).

It looks like that there is sometimes a synchronisation problem between the 
nsrd and nsrmmd processes - the nsrd starts a request to a nsrmmd bevor 
this nsrmmd is started - call is open by legato technical:
03/02/06 22:45:02 nsrd: [Jukebox `HP660', operation # 45]. Cannot find an 
available nsrmmd service for operation on device '/dev/nst1'. Try again.
03/02/06 22:45:03 nsrmmd #3: Start nsrmmd #3, with PID 30207, at HOST 
guardian.alisrz.de

At the end we get errors like this:
03/02/06 22:45:07 nsrmmgd: Cannot find an available nsrmmd service for 
operation on device '/dev/nst0'. Try again.
03/02/06 22:45:09 nsrmmgd: Jukebox `HP660' failed to load the requested 
volume.
03/02/06 22:45:13 nsrd: [Jukebox `HP660', operation # 45]. Finished with 
status: retryable
03/02/06 22:45:13 nsrmmgd: RAP error: Invalid resource data.
03/02/06 22:45:13 nsrmmgd: Cannot update operation status resource 
(instance 45).
03/02/06 22:45:13 nsrd: [Jukebox `HP660', operation # 46]. Finished with 
status: retryable
03/02/06 22:45:13 nsrmmgd: RAP error: Invalid resource data.
03/02/06 22:45:13 nsrmmgd: Cannot update operation status resource 
(instance 46).

The result is that the load operation failed, legato starts no retry, just 
pending until end of time. "Solution" in such a situation is to load the 
volumes manual, thats it.

For the moment we have stop our update plan next week and wait of a 
reaction from legato.

Greetings,
Stefan 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER