trouble starting pvm:urgent

[Andrew Shewmaker]

On Tue, 7 May 2002 14:48:17 -0400 (EDT)
"Robert G. Brown" <rgb at phy.duke.edu> wrote:

> which is a LOT more useful than the message you got.  A more common
> source of failure is to try to start a pvmd on a host that already has
> one running.  This would likely produce the bind error you describe, as
> a new pvmd cannot bind to the usual socket -- something is already there
> (another pvmd).  This traces out to:

<snip>

> PVM Daemon Files Found on lucifer!
> Either PVM is Already Running or else it
> crashed and left behind a /tmp/pvmd.<uid>
> daemon file.
> Halt PVM if it is running on lucifer, or else
> remove any leftover /tmp/pvmd.* files.
> 
> ...which also shows pretty much how you can manually diagnose your
> problem.
> 
> I'd suggest FIRST upgrading to pvm 3.4.3 (or the latest stable release),
> doing a new build for your systems if necessary.  For linux systems you
> should be able to just use current RPM's -- my pvm came straight out of
> standard Red Hat 7.2, for example.  Read the new documentation -- in
> addition to auto-diagnosing most failures AND telling you how to fix
> them (awesome concept!) there are a variety of new environment variables
> (such as PVM_RSH, PVM_TMP) that can be used to configure intelligent
> behavior in certain environments.

A user can run multiple separate pvms as of pvm 3.4.4  The VMID can either be 
set in the hostfile or with the PVM_VMID environment variable.  I really like 
this feature.

>From my pvmd man page:

id=VMID   A new feature in PVM 3.4.4 is the concept of a "Virtual Machine  ID".
          You can now set the VMID to an arbitrary string and this will distin­
          guish and allow multiple virtual machines to run on the same  set  of
          hosts under the same userid.  (This feature was originally introduced
          by SGI in their commercial PVM product, and has now been  generalized
          for  the public PVM system.)  This feature seems to be something that
          people often want, and the PVM_VMID is the cleanest  way  to  provide
          this  functionality,  rather  than overloading the SHAREDTMP compiler
          flag and other internals.  By default, all hosts which are  added  to
          the  virtual  machine will inherit the same VMID.  If hosts are added
          to the virtual machine which are running older versions of PVM (prior
          to  3.4.4),  then the VMID will be ignored for those hosts, and hence
          these machines can only be added to one virtual machine for the given
          user.   The  VMID  need  not be consistent on every host in a virtual
          machine (although this is not necessarily advisable).
_______________________________________________
Beowulf mailing list, Beowulf at beowulf.org
To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf