2 staging problems

Question

Hi

My second post. Do anybody know something about following error:

07/19/06 17:08:10 nsrd: backupserver:cloning session saving to pool 'tapepool' (tapepool.025)
07/19/06 17:08:14 nsrd: cloning session: 1 save set(s) reading from diskpool.001.RO 5888 KB of 30 MB
pools supported: tapepool;
07/19/06 17:08:19 nsrd: nsrmmdbd has exited with status 253
07/19/06 17:08:19 nsrd: networker daemons critical: nsrmmdbd has exited with status 253
07/19/06 17:08:19 nsrd: shutting down

And server is down

What do status 253 mean?
This error happens ocasionally.

Second problem (also during staging):

pools supported: tapepool;
07/20/06 12:34:00 ansrd: xdr_bool on clone xdr failed
pools supported: tapepool;
07/20/06 12:34:00 nsrd: backupserver:cloning session done saving to pool 'tapepool' (tapepool.027)
07/20/06 12:34:00 ansrd: ansrd_clone FAILED: errnum is 25004 and errstr is RPC receive operation failed. A network connection could not be established with the host.
07/20/06 12:34:00 ansrd: failed to execute MODE_CLONE
nsrstage: RPC error: RPC receive operation failed. A network connection could not be established with the host.
nsrstage: Cannot open nsrstage session with backupserver
nsrstage: Failed to clone the following save sets:
4273813214
.................

Server is alive, but staging is aborted.

Help please!

Regards

ble1 · Answer

Ooops... media db crashing... that's not good. Very very bad... be scared

Anyway, NW went down as one of its critical daemons had fatal failure. The real question is what is wrong with media db - probably there is a corruption with certain entry and when proceeded it caused fatal error and daemon to exit with that error code. What it is exactly is for your support to check it out.

As for second error, during staging of ssid 4273813214 something went wrong - not sure if that ssid is bad or simply things failed during the operation on that ssid. Again, support should give you steps to check it out.

Anyway, if you are back online with server now, do:
nsrck -m
nsrim -X
nsrck -L6

Then check daemon.log for any unsual message (and there should be few probably). Then try to stage ssid above and if it works fine - if not then open up this with your support as severity 1.

jbmcgowan2 · Answer

What version of Networker are you running?

In the latest releases of Networker there are several issues with the nsrmmd.exe and nsrmmdbd.exe processes as well as some staging issues. I have seen a little from each and as of 7.3.1 things are looking better but there are still some nsrmmd.exe issues that I am working with support on.

Patch your software would be my suggestion. Thanks.

ble1 · Answer

He is on 7.3.1 - in that case the best thing would be to talk to support asap.

abartosz · Answer

This problem have happend on both 7.3 and 7.3.1. I don't know if it's important, but I think it happens when You make a some configuration modifiactions (I deleted definition of client from Networker server, but don't delete it's save sets)

Regards

ble1 · Answer

And if you put the client back - what does then happen?

NetWorker

2 staging problems

Was this post helpful?