[Spread-users] trying to run spread on 64bit linux

[Martin Hedenfalk]

12 sep 2008 kl. 23.17 skrev Michael Peters:

> I've built spread (4.0.0) on a 64bit linux box but it's failing to  
> start. No errors in the log, nothing. I have it running fine on  
> other 32bit boxes in the same cluster, but not the 64bit ones.  
> Here's what I get from Spread:
>
> [user at box user]$ spread
> / 
> = 
> = 
> = 
> = 
> = 
> = 
> =====================================================================\
> | The Spread  
> Toolkit.                                                       |
> | Copyright (c) 1993-2006 Spread Concepts  
> LLC                               |
> | All rights  
> reserved.                                                      |
> ... more crazy long credits ...
>
> | Version 4.00.00 Built 29/November/ 
> 2006                                    |
> \= 
> = 
> = 
> = 
> = 
> = 
> =====================================================================/
> Conf_load_conf_file: using file: /usr/local/etc/spread.conf
> Successfully configured Segment 0 [10.32.255.255:4803] with 11 procs:
> 	              tools1: 10.32.100.134
> 	                svr3: 10.32.100.102
> [user at box user]$
>
> That's it, no warnings, no errors and nothing in the log. Just to  
> make sure it's linking against the right libs, etc
> [user at box user]$ ldd `which spread`
> 	linux-vdso.so.1 =>  (0x00007fff66bfd000)
> 	libm.so.6 => /lib64/libm.so.6 (0x0000003813200000)
> 	libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003814e00000)
> 	libc.so.6 => /lib64/libc.so.6 (0x0000003812a00000)
> 	/lib64/ld-linux-x86-64.so.2 (0x0000003812600000)
>
>
> Any ideas?

We tried running spread on OpenBSD/amd64. No problems compiling, or  
running it (in the sense that the process didn't die). It worked  
really, really strange though. Running 2 or 3 nodes was ok, but adding  
another one partitioned the network.

We moved to i386 and have not seen the same problems since.

	-martin