• 1 reply
  • Latest Post - ‏2013-01-23T14:04:41Z by pdubovitsky
47283 Posts

Pinned topic Reg Performance issue with Cleacase builds

‏2013-01-23T11:28:25Z |

Clearcase Version: Clearcase v7

Setup Overview:
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 to procedure ypproc_match (,shadow.byname;-1)
refused connect from to procedure ypproc_match (,shadow.byname;-1)

Help required:

Could you please clarify whether the above two error indications can cause a performance drop? Appreciate your help.

Thanks & Regards,
  • pdubovitsky
    189 Posts

    Re: Reg Performance issue with Cleacase builds


    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
    These three are the most common sources of the issues that could suddenly impact VOB server performance. You might need to ask Linux admin to help you with troubleshooting.