[Spread-users] Memb_token_loss: bug !!! state is 2

John Robinson jr at vertica.com
Fri Apr 25 07:51:07 EDT 2008


I've noticed that you have to wait a few seconds between reloads.

I assume spmonitor is enough rope to hang yourself if not used sparingly.

/jr
---
Adrian Revill wrote:
> Hi im using 4.0 and when ever i issue a reload from spmonitor the spread 
> daemon crashes and gives the error
> 
> Net_recv: Received Packet - packet length(36), packed message length(36)
> Conf_load_conf_file: using file: ../spread.conf
> Successfully configured Segment 0 [172.1.255.255:4800] with 16 procs:
>                     master1: 172.1.0.10
>                     master2: 172.1.0.11
>                        boot: 172.1.0.5
>                       boot1: 172.1.0.6
>                       boot2: 172.1.0.7
>                    athlon-1: 172.1.1.1
>                      opto-1: 172.1.2.1
>                      opto-2: 172.1.2.2
>                      opto-3: 172.1.2.3
>                      opto-4: 172.1.2.4
>                      opto-5: 172.1.2.5
>                      opto-6: 172.1.2.6
>                      opto-7: 172.1.2.7
>                      opto-8: 172.1.2.8
>                    opto-201: 172.1.2.201
>                      quad-1: 172.1.3.1
> Set Alarm mask to: fffeefee
> Finished configuration file.
> Hash value for this configuration is: 2149500836
> Conf_load_conf_file: My name: boot2, id: 172.1.0.7, port: 4800
> Memb_token_loss: I lost my token, state is 1
> Scast_alive: State is 2
> Net_recv: Received Packet - packet length(36), packed message length(36)
> Conf_load_conf_file: using file: ../spread.conf
> Successfully configured Segment 0 [172.1.255.255:4800] with 16 procs:
>                     master1: 172.1.0.10
>                     master2: 172.1.0.11
>                        boot: 172.1.0.5
>                       boot1: 172.1.0.6
>                       boot2: 172.1.0.7
>                    athlon-1: 172.1.1.1
>                      opto-1: 172.1.2.1
>                      opto-2: 172.1.2.2
>                      opto-3: 172.1.2.3
>                      opto-4: 172.1.2.4
>                      opto-5: 172.1.2.5
>                      opto-6: 172.1.2.6
>                      opto-7: 172.1.2.7
>                      opto-8: 172.1.2.8
>                    opto-201: 172.1.2.201
>                      quad-1: 172.1.3.1
> Set Alarm mask to: fffeefee
> Finished configuration file.
> Hash value for this configuration is: 2149500836
> Conf_load_conf_file: My name: boot2, id: 172.1.0.7, port: 4800
> Memb_token_loss: bug !!! state is 2
> Exit caused by Alarm(EXIT)
> 
> 
> Looking in this forum a similar problem was reported last march but 
> never replied to, did anyone get an answer?
> 
> regards
> Adrian
> 
> 
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users




More information about the Spread-users mailing list