[Linux-cluster] cluster is not quorate. refusing connection

[Jonathan E Brassow]

Originally, a user had to do a ./configure; make install.  This would 
put lib's in place for the next sub-tree, etc.  Users found this 
annoying/non-intuitive to not have to do a regular 'make'.

It appears that when the option to do just a simple 'make' was added, 
the problem you are seeing was over looked.

The cluster/magma/lib/Makefile is setting the plugin dir, which should 
be the install dir, but isn't because cluster/Makefile overrides the 
install dir to be able to emulate the simple 'make'.

Thanks for all the info, we'll get this fixed.
   brassow

On Dec 13, 2004, at 5:23 PM, Matthew B. Brookover wrote:

>  Ok, starting GFS with the build directory mounted via NFS worked!  
> fence_tool started up on both nodes fouroften and fiveoften.  It looks 
> like whatever sets the path to the plugin directory is setting the 
> path to the build instead of the install directory.
>
>  I still have to do vgchange -aly, vgchange -aln, and then vgchange 
> -aly to get the volume groups to show up in /dev.
>
>  Matt
>
>  On Mon, 2004-12-13 at 16:00, Matthew B. Brookover wrote:
> [root at fouroften mbrookov]# ls `strings 
> /usr/local/GFS/usr/lib/libmagma.a | grep plugins`
> gulm.so*  sm.so*
> [root at fouroften mbrookov]# strings /usr/local/GFS/usr/lib/libmagma.a | 
> grep plugins
> /work/GFS-FEDORA-try5/cluster/build/lib/magma/plugins
> [root at fouroften mbrookov]#
>  I have been using dlm, is gulm.so bad?
>
>  Also, the directory, 
> /work/GFS-FEDORA-try5/cluster/build/lib/magma/plugins, is the build 
> directory and is only available on fouroften.  I did not copy it over 
> to fiveoften.  I will NFS mount /work to fiveoften and retest.  Could 
> this explain why things work on fouroften and not fiveoften?
>
>  FYI -- I have been using the --prefix=/usr/local/GFS option in my 
> builds.  Each time I rebuild I rm -rf /usr/local/GFS to ensure that no 
> old copies of libraries/programs are left laying around.  I did add 
> the lib directories to /etc/ld.so.conf, the bin directories to the 
> front of by PATH, and the man directory to /etc/man.conf.
>
>  The only place I could find magma libraries was in 
> /usr/local/GFS/usr/lib.  /lib, /usr/lib, and /usr/local/GFS/lib were 
> clean.
> [root at fouroften mbrookov]# ls /usr/local/GFS/usr/lib/*magma*
> /usr/local/GFS/usr/lib/libmagma.a                       
> /usr/local/GFS/usr/lib/libmagma_nt.so@
> /usr/local/GFS/usr/lib/libmagmamsg.a                    
> /usr/local/GFS/usr/lib/libmagma_nt.so.DEVEL@
> /usr/local/GFS/usr/lib/libmagmamsg.so@                  
> /usr/local/GFS/usr/lib/libmagma_nt.so.DEVEL.1102700899
> /usr/local/GFS/usr/lib/libmagmamsg.so.DEVEL@            
> /usr/local/GFS/usr/lib/libmagma.so@
> /usr/local/GFS/usr/lib/libmagmamsg.so.DEVEL.1102700899  
> /usr/local/GFS/usr/lib/libmagma.so.DEVEL@
> /usr/local/GFS/usr/lib/libmagma_nt.a                    
> /usr/local/GFS/usr/lib/libmagma.so.DEVEL.1102700899
>
> /usr/local/GFS/usr/lib/magma:
> plugins/
>  I checked fiveoften, it has the same list of files as fouroften.
>
>  Matt
>
>  On Mon, 2004-12-13 at 14:50, Jonathan E Brassow wrote:
> On Dec 13, 2004, at 10:30 AM, Matthew B. Brookover wrote:
> > The only difference
> > between the 2 is the host name and IP address, and the fact that I
> > compiled GFS and the kernel on fouroften and copied it to fiveoften.
> >
>
> Is there anything listed when doing 'ls /lib/*magma*'?
>
> What do you get when you:
> ls `strings /usr/lib/libmagma.a | grep plugins`
> ?
>
>   brassow
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
>  http://www.redhat.com/mailman/listinfo/linux-cluster
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
>  http://www.redhat.com/mailman/listinfo/linux-cluster
>  --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> http://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 4688 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20041213/b7db2a6e/attachment.bin>