[Spread-users] no daemon

[Milind Dumbare]

On Mon, 2005-09-05 at 15:09 -0400, John Schultz wrote:
> I'm not sure if you are doing this or not, but try running spread and 
> spuser in the foreground in two different shells.  You should see your 
> spread daemon go through some initialization, then install a membership 
> and then just sit there, something like this:
I have tried this.....now.....but still has problem
> 
> Conf_init: using file: spread.conf
> Successfully configured Segment 0 [192.168.221.255:9999] with 4 procs:
>                          cloud1: 192.168.221.101
>                          cloud2: 192.168.221.102
>                          cloud3: 192.168.221.103
>                          cloud4: 192.168.221.104

my output does not go beyond this line.......I think its crashing.....is
it possible to find the problem on error message given by spuser I have
sent before
> Finished configuration file.
> Conf_init: My name: cloud1, id: 192.168.221.101, port: 9999
> Membership id is ( -2133009141, 1125946735)
> --------------------
> Configuration at sky1 is:
> Num Segments 1
>          4       192.168.221.255   9999
>                  sky1                    192.168.221.101
>                  sky2                    192.168.221.102
>                  sky3                    192.168.221.103
>                  sky4                    192.168.221.104
> ====================
> ++++++++++++++++++++++
> Num of groups: 0
> 

I have attached the spread.conf see if I can do anything in it .....
-------------- next part --------------

Spread_Segment  192.168.1.255:4803{
	matrix 192.168.1.21
	chanakya 192.168.1.24
}





DebugFlags = { PRINT EXIT }

EventLogFile = testlog.out

EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"

DangerousMonitor = false

#SocketPortReuse = AUTO

#RuntimeDir = /var/run/spread

#DaemonUser = spread
#DaemonGroup = spread