Does anyone knows what is this error?

The nsrlpcd issues may well be an issue with the Storage Node running out of resources and therefore nsrlpcd cannot create new threads etc.

Your Management console freezes and the nsrlcpd issues i doubt would be related, unless the Management console being on the Storage node, which may well be resource issues as well...

are you getting any specific or unusual errors in the Management console logs ?
i.e. solaris: /opt/LGTOnmc/logs

We saw those issues on 7.3.3 SP3 - there was a big improvement after upgrading to 7.4.3; there are quite a few bug fixes both for nsrlcpd and the NMC by upgrading.

I am currently running version 7.4.3

I almost certain that the freezze of my NMC has to do with nsrlcpd. My networker server (which NMC is installed also). So everytime I started it, to my understanding will try to communcate with my storage node to give an update of my libraries and tape devices.

So it somehow could'nt and freezes.

Does these error message in my storage node appears because he has lost the SAN path to my physical libraries or is it a bug from Networker? I like to know for sure.

If it is a SAN configuration then I'll know where to look.

Message was edited by:
tienlamnguyen

tienlam, its hard to pinpoint an problem like this without getting hands dirty checking through Switch logs (networks) and also the logs on both the storage node etc, if the issues is with the jukebox connectivity itself.

but also consider the system resources as well, as it may be that the networker server is being hit too hard running that and the NMC togther, and your seeing the issues due to the connectivity/communication through the nsrlcpd process being the first to get a problem.

Our experience is that the newer daemons like nsrlcpd still can be a little on the buggy side; you would do well first to upgrade to see if that improves things. Are you in a position where you cannot get working or does this problem happen sometimes, and at other times everything works okay?

This problem causes the networker to not see the library and as a consequence all by backup is queued.

I end up on putting a service request to EMC support ans they sugested that I remove all of my unconfigured devices. Maybe this is causing the problem.

It always maybe with them. Well... It wouldn't harm at this point.

EMC's support is not what it used to be. Whilst there are some knowledgeable people there are some people will hinder you more than they will help you.

nsrlcpd is the Library Control Daemon so if that fails Networker will not be able to shift tapes around and you will get the results you are seeing. Is the library ever stable enough to do backups?

No. It is unstable right now. Every 2 days I get the errors and my networker server lost the connection to my storage node.

My schdedule backup get stalled or queued. After a while my NMC fails and I can start it up.

Today, I just removed all of my unconfigured device. Check my FC switch log to see if there is anything that would suggest a lost connectivity.

I will se if EMC recommendations is right.

Did you have the tape library working in a stable manner earlier? What I am getting at is has this problem cropped up since making some change or has it never worked?

You have 2 Libraries...

nsrlcpd#1 Jukebox `rd=woodroffe-3:M4 DATA@2.2.1' is exiting. The jukebox is no longer managed by nsrlcpd.
nsrlcpd#2 Jukebox `rd=woodroffe-3:QUANTUM@2.1.0' is exiting. The jukebox is no longer managed by nsrlcpd.

At the time you see the above error:

1- Try sjirdtag 2.2.1, and sjirdtag 2.1.0

2- Check the NetWorker Server, do you have nsrmmgdb up and running?

Ok,
I guess the EMC support cam through for me this time. I took off all of my unconfigured devices and my errors hasn't reappear. It's been a week now.