Clearcase Version: Clearcase v7
There are Linux(RHEL 5.5) and Windows(XP and 7) build servers and there are four VOB servers running RHEL 5.5. The Authentication for the entire linux setup(VOBS+build) is NIS and the windows env uses ADS authentication. The Windows machines accesses the VOBS through SMB share.
Suddenly there was a performance drop in all(linux+windows) build servers on all the builds.
While we checked the clearcase logs in VOBS servers, the below found in db_server logs.
db_server(7303): Error: do_ypcall: clnt_call: RPC: Timed out
While we checked the NIS server logs, the below logs found which resolves to the VOBS servers
refused connect from 10.201.64.84:49165 to procedure ypproc_match (in.nds.com,shadow.byname;-1)
refused connect from 10.201.64.87:49165 to procedure ypproc_match (in.nds.com,shadow.byname;-1)
Could you please clarify whether the above two error indications can cause a performance drop? Appreciate your help.
Thanks & Regards,
This topic has been locked.
1 reply Latest Post - 2013-01-23T14:04:41Z by pdubovitsky
Pinned topic Reg Performance issue with Cleacase builds
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-23T14:04:41Z at 2013-01-23T14:04:41Z by pdubovitsky
pdubovitsky 100000N35Y189 PostsACCEPTED ANSWER
Re: Reg Performance issue with Cleacase builds2013-01-23T14:04:41Z in response to SystemAdminHi,
It is unlikely that shadow.byname call could cause any performance issues, but if you can find similar errors for other NIS calls, it might be what is causing the problem.
If it happened suddenly and impacted all hosts, most likely the problem is related to the VOB server, VOB storage, or NFS server exporting the storage (it could be the VOB server or a dedicated NAS device).
- check the processes running on the VOB server, CPU and memory utilization
- check for naming resolution related issues
- check for cache configuration (passwd, groups, hosts). Is nscd or sssd running on the system?
- check VOB storage IO stats
- check for NFS lock-related issues