Topic
8 replies Latest Post - ‏2012-12-28T05:17:41Z by SystemAdmin
Ratan_k00
Ratan_k00
50 Posts
ACCEPTED ANSWER

Pinned topic Communications timeout in ClearCase server error

‏2009-01-16T15:43:17Z |
Hi,

I'm getting the below error while trying to access the VOB. The VOB storage is on a NAS. I'm planning to run fix_prot and regenerate .identity under .vbs folder. Is there any thing that I can try out? Pls let me know

Thanks!

bash-3.00# /usr/atria/bin/cleartool setview ratan_view
  1. cd /vobstg/wdn/wins_vob
View server for mars:/:/vobs/wss/ratan_view.vws not responding still trying (st=5 er=145)
View server for mars:/vobs/wss/ratan_view.vws ok
mvfs: ERROR: view=ratan_view vob=/vobstg/wdn/wins_vob - Communications timeout in ClearCase server
see view_log on host mars for more info
/vobstg/wdn/wins_vob: bad directory
error capture in VIEW_LOG:


2009-01-14T17:08:09+05:30 view_server(2947): Error: vobrpc_contact_call_V2: RPC: Timed out
2009-01-14T17:08:09+05:30 view_server(2947): Error: Unexpected error in VOB "mars:/vobstg/wdn/wins_vob.vbs" op vob_ob_register_replica (df326801.5ac34c82.a17e.42:dd:c9:2d:76:80):timed out trying to communicate with ClearCase remote server
See vobrpc_server_log on host mars
2009-01-14T17:08:09+05:30 view_server(2947): Warning: Unable to open vob 'mars:/vobstg/wdn/wins_vob.vbs': timed out trying to communicate with ClearCase remote server
Updated on 2012-12-28T05:17:41Z at 2012-12-28T05:17:41Z by SystemAdmin
  • Tgefen
    Tgefen
    702 Posts
    ACCEPTED ANSWER

    Re: Communications timeout in ClearCase server error

    ‏2009-01-19T21:34:50Z  in response to Ratan_k00
    Do you use the automounter?

    BR,
    Tamir Gefen
    CM and ALM
    GoMidjets - Automate Your ClearCase advantage
    My CM and ALM blog
    • Ratan_k00
      Ratan_k00
      50 Posts
      ACCEPTED ANSWER

      Re: Communications timeout in ClearCase server error

      ‏2009-01-20T04:44:17Z  in response to Tgefen
      Yes!
      • SystemAdmin
        SystemAdmin
        47293 Posts
        ACCEPTED ANSWER

        Re: Communications timeout in ClearCase server error

        ‏2011-11-17T10:58:19Z  in response to Ratan_k00
        Hi Rathan and Tamir,

        A very short dialog two years ago...
        I have the same symptom:

        
        foo> cd /view/vobadm8_ENIQ_Events_11.3_Services_Consolidation_Performance/vobs/eniq_events/eniq_events_services/services-main/src/main/resources/recurring/  View server 
        
        for ieatx013.eei.ericsson.se:/cc/views07/vobadm8/vobadm8_ENIQ_Events_11.3_Services_Consolidation_Performance.vws not responding still trying (st=5 er=145)
        


        and from this would not have thought of the automounter...
        But yes, we are also using the automounter (as far as I can say--not having root access) for both view and vob storage:
        
        log> ct lsview vobadm8_ENIQ_Events_11.3_Services_Consolidation_Performance * vobadm8_ENIQ_Events_11.3_Services_Consolidation_Performance /cc/views07/vobadm8/vobadm8_ENIQ_Events_11.3_Services_Consolidation_Performance.vws log> df /cc/views07 /cc/views07        (eieatna001:/vol/vol0109/views):99040232 blocks 19668501 files log> ct lsvob /vobs/eniq_events * /vobs/eniq_events    /cc/vobs06/eniq_events.vbs 
        
        public (replicated) log> df /cc/vobs06 /cc/vobs06         (eieatna001:/vol/vol0106/vobs):391315328 blocks 27488063 files log> ypcat auto_master | grep _cc auto_cc log> ypcat auto_cc | egrep 
        'eieatna001:/vol/(vol0109/views|vol0106/vobs)' -rw,hard,bg,intr,nosuid,noquota        eieatna001:/vol/vol0106/vobs -rw,hard,bg,intr,nosuid,noquota        eieatna001:/vol/vol0109/views
        

        Although... Isn't there something missing there? The mount points...
        And the df output looks more like a hard mount, doesn't it?
        On another hand, hard mounts should be foud there, shouldn't they?:
        
        log> egrep -v 
        '^ *(#|$)' /etc/dfs/dfstab log>
        

        Er... That's a bit too few, isn't it?
        I feel helpless without a box on which to perform tests...

        Anyway, is it this '(st=5 er=145)' which would come from the autmounter?
        And what to do then?
        Thanks!
        Marc
        • SystemAdmin
          SystemAdmin
          47293 Posts
          ACCEPTED ANSWER

          Re: Communications timeout in ClearCase server error

          ‏2011-11-17T12:55:14Z  in response to SystemAdmin
          Marc wrote:
          > On another hand, hard mounts should be found there, shouldn't they?:
          OK. It looks like some things have changed on Solaris since last time I had a look...
          
          etc> svcs -a | grep filesystem online         Nov_12   svc:/system/filesystem/root:
          
          default online         Nov_12   svc:/system/filesystem/usr:
          
          default online         Nov_12   svc:/system/filesystem/minimal:
          
          default online         Nov_12   svc:/system/filesystem/local:
          
          default online         Nov_12   svc:/system/filesystem/autofs:
          
          default online         Nov_12   svc:/system/filesystem/volfs:
          
          default etc> svcs -a | grep nfs disabled       Nov_12   svc:/network/nfs/server:
          
          default disabled       Nov_12   svc:/network/nfs/rquota:
          
          default online         Nov_12   svc:/network/nfs/status:
          
          default online         Nov_12   svc:/network/nfs/nlockmgr:
          
          default online         Nov_12   svc:/network/nfs/mapid:
          
          default online         Nov_12   svc:/network/nfs/cbd:
          
          default online         Nov_12   svc:/network/nfs/client:
          
          default
          


          Not that this would answer my initial question, but it explains the funny results I got.
          I am still unsure whether we use the automounter for our ClearCase storage. I now think we don't.
          Marc
          • SystemAdmin
            SystemAdmin
            47293 Posts
            ACCEPTED ANSWER

            Re: Communications timeout in ClearCase server error

            ‏2011-11-17T13:11:29Z  in response to SystemAdmin
            Marc wrote:
            > I am still unsure whether we use the automounter for our ClearCase storage.
            > I now think we don't.

            From grepping /etc/mnttab, I can see that we are not: the storages are marked nfs, not autofs.
            Now, the remote volumes (on the NetApp) are still mentioned in the NIS map used by the automounter (with no mention of mount points that I would understand, as told before).
            Could this cause a conflict?

            Marc
  • Antebai
    Antebai
    1 Post
    ACCEPTED ANSWER

    Re: Communications timeout in ClearCase server error

    ‏2012-03-07T12:28:25Z  in response to Ratan_k00
    Did someone fix this, because I also have this problem?
    • SystemAdmin
      SystemAdmin
      47293 Posts
      ACCEPTED ANSWER

      Re: Communications timeout in ClearCase server error

      ‏2012-03-07T14:20:52Z  in response to Antebai
      Antebai wrote:
      > Did someone fix this, because I also have this problem?
      No resolution on my side.
      Just forgot the issue (probably still lurking somewhere until somebody complains).

      "There is no problem that a persistent absence of solution wouldn't get rid of"
      (Henri Queuille)

      Marc
      • SystemAdmin
        SystemAdmin
        47293 Posts
        ACCEPTED ANSWER

        Re: Communications timeout in ClearCase server error

        ‏2012-12-28T05:17:41Z  in response to SystemAdmin
        Hi Team,

        We are getting the below errors,please whether this alerts are valid, if Yes, please let us know how to resolve.

        OS Details:

        Linux 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
        cat /etc/redhat-release
        Red Hat Enterprise Linux Server release 6.2 (Santiago)

        Error Details.
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out
        view: server view not responding, timed out