[forwarded from Hiroshi IMAI] Re: [daip] START_AIPS

[Patrick P Murphy]

------- start of forwarded message (RFC 934 encapsulation) -------
Mime-version: 1.0
Content-Length: 2378
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Return-Path: <imai at jive.nl>
Received: from cv3.cv.nrao.edu (cv3.cv.nrao.edu [192.33.115.2])
	by polaris.cv.nrao.edu (8.11.6/8.11.6) with ESMTP id h4R7mCZ20281
	for <pmurphy at nrao.edu>; Tue, 27 May 2003 03:48:12 -0400
Received: from server4.nfra.nl (fwuser at firebox.nfra.nl [192.87.1.200])
	by cv3.cv.nrao.edu (8.11.6/8.11.6) with ESMTP id h4R7m9m09511
	for <pmurphy at nrao.edu>; Tue, 27 May 2003 03:48:10 -0400
Received: from [10.87.6.10]
	([10.87.6.10])
	by server4.nfra.nl; Tue, 27 May 2003 09:48:25 +0200
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2106
In-Reply-To: <16082.10200.202611.607563 at polaris.cv.nrao.edu>
X-MailScanner: Found to be clean
From: Hiroshi IMAI <imai at jive.nl>
To: Patrick P Murphy <pmurphy at nrao.edu>
Subject: Re: [daip] START_AIPS
Date: Tue, 27 May 2003 09:47:57 +0200
Message-ID: <BAF8E4CC.E0E%imai at jive.nl>
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.1, required 7,
	DEAR_SOMEBODY, IN_REP_TO, LINES_OF_YELLING, SPAM_PHRASE_01_02,
	USER_AGENT, USER_AGENT_MACOE)

Dear Pat,

We have just recovered the problem. The cause was what you explained in the
final part of the previous e-mail.

We aknowledge you for kind help.

Best regards,

Hiroshi
 
> It's a holiday here in the US today (Memorial day) so Eric and others
> may not be accessible.  I may be able to offer some advice from the
> sidelines, however.
> 
> On Mon, 26 May 2003 14:51:44 +0200, Hiroshi IMAI <imai at jive.nl> said:
> 
>> ZLOCK: No locks available
>> ZERROR: ON FILE TSTMEM:MED000000;
>> ZERROR: IN ZDAOPN ERRND = 37 (No locks available)
> 
> Is your $TSTMEM area ($AIPS_VERSION/$ARCH/MEMORY) on a NFS-mounted file
> system?  If so, is it possible to do fcntl()-style file locking on files
> on that partition?  These are system questions, clearly.  There is a
> utility/diagnostic program in $SYSUNIX called WHOLOCKED.C that may help
> (it needs copied to wholocked.c and compiled before you can run it).
> 
> I suspect file locking is the root of the problem.  When we had this
> message appear on our systems years ago, it was usually because one of
> the NFS daemons on either the client or the server was misbehaving or
> not running.  Generally there are two daemons: statd and lockd, though
> they may be called rpc.statd or rpc.lockd instead.
> 
>> To understand these messages, we have made some trials, e.g.
>> exchange START_AIPS and MED000000; to the older version files,
> 
> That won't help if NFS file locking is not working.
> 
>> We would like to understand what happend and
>> to which AIPS complains only in the LINUX machine.
> 
> Ah.  What version of Linux, and are you running these:
> 
> portmap
> nfs
> nfslock
> 
> (on my Red Hat 8.0 system, a "chkconfig --list" shows many services,
> including these three; portmap is its own RPM and the other two are in
> the nfs-utils RPM).
> 
> Hope this helps.
> - Pat
- ------------------------------------------------------------------------
        *          Hiroshi IMAI, Ph.D.
   *         *
 *             *   EVN Support Scientist,   E-mail: imai at jive.nl
     European
*     VLBI      * 
      Network       Joint Institute for VLBI in Europe (JIVE)
 *             *    Postbus 2, 7990 AA Dwingeloo, the Netherlands
   *         *      Tel: +31 521 596540 (Office) FAX: +31 521 597332
        *           URL: www.jive.nl/~imai
- ------------------------------------------------------------------------

------- end -------