[Spread-users] spread.log saying "BUG WORKAROUND...swallowing token"
Martin Schu
martin.sc11111 at gmail.com
Wed Feb 1 04:14:56 EST 2017
Hi John,
we have a spread-4.4.0 installation and observe some mysterious problems.
We have configured multicast and we have multiple interfaces per machine.
Perhaps something is wrong with the configuration for multicast in our
network.
In spread.log we see a strange error message saying *"**Prot_handle_token:
BUG WORKAROUND...swallowing token"*. This message is occurring 4 times per
minute. See below.
Digging in the source code of spread-5.0.0-rc2 we see that strange message
is still implemented there.
Can you give us some hints which circumstances could induce that strange
"BUG WORKAROUND" message? Is this a "workaround" for a bug in spread or for
a bug in network setup?
In our situation there is a total malfunction. No spread communication
possible at all.
If we remove the multicast setup from our configuration everything is
working fine on the same machines/network.
Best regards,
Martin
--
Spread_Segment 239.192.2.1:5555 {
easydb20-ref-back 1.2.3.131 { 1.2.3.131 }
}
Spread_Segment 239.192.2.2:5555 {
easy22-ref-back 1.2.3.4 { 1.2.3.4 }
easy23-ref-back 1.2.3.5 { 1.2.3.5 }
easy24-ref-back 1.2.3.6 { 1.2.3.6 }
}
Spread_Segment 239.192.2.3:5555 {
easydb21-ref-back 1.2.3.195 { 1.2.3.195 }
}
Spread_Segment 239.192.2.4:5555 {
easy25-ref-back 1.2.3.68 { 1.2.3.68 }
easy26-ref-back 1.2.3.69 { 1.2.3.69 }
easy27-ref-back 1.2.3.70 { 1.2.3.70 }
}
...
2017-01-31 10:25:10 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:25:25 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:25:43 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:25:58 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:26:16 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:26:31 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:26:34 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:26:37 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
...
2017-01-31 10:39:42 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:39:42 GMT Aru: 0
2017-01-31 10:39:42 GMT My_aru: 3366
2017-01-31 10:39:42 GMT Highest_seq: 0
2017-01-31 10:39:42 GMT Highest_fifo_seq: 0
2017-01-31 10:39:42 GMT Last_discarded: 0
2017-01-31 10:39:42 GMT Last_delivered: 0
2017-01-31 10:39:42 GMT Last_seq: 3366
2017-01-31 10:39:42 GMT Token_rounds: 501
2017-01-31 10:39:42 GMT Last Token:
2017-01-31 10:39:42 GMT type: 0x80050080
2017-01-31 10:39:42 GMT transmiter_id: -1726901244
2017-01-31 10:39:42 GMT seq: 0
2017-01-31 10:39:42 GMT proc_id: -1726901244
2017-01-31 10:39:42 GMT aru: 0
2017-01-31 10:39:42 GMT aru_last_id: -1726901179
2017-01-31 10:39:42 GMT flow_control: 33
2017-01-31 10:39:42 GMT rtr_len: 144
2017-01-31 10:39:42 GMT conf_hash: -2016107656
2017-01-31 10:39:57 GMT Prot_handle_token: BUG WORKAROUND: Too many rounds
in EVS state; swallowing token; state:
2017-01-31 10:39:57 GMT Aru: 0
2017-01-31 10:39:57 GMT My_aru: 3366
2017-01-31 10:39:57 GMT Highest_seq: 0
2017-01-31 10:39:57 GMT Highest_fifo_seq: 0
2017-01-31 10:39:57 GMT Last_discarded: 0
2017-01-31 10:39:57 GMT Last_delivered: 0
2017-01-31 10:39:57 GMT Last_seq: 3366
2017-01-31 10:39:57 GMT Token_rounds: 501
2017-01-31 10:39:57 GMT Last Token:
2017-01-31 10:39:57 GMT type: 0x80050080
2017-01-31 10:39:57 GMT transmiter_id: -1726901244
2017-01-31 10:39:57 GMT seq: 0
2017-01-31 10:39:57 GMT proc_id: -1726901244
2017-01-31 10:39:57 GMT aru: 0
2017-01-31 10:39:57 GMT aru_last_id: -1726901179
2017-01-31 10:39:57 GMT flow_control: 33
2017-01-31 10:39:57 GMT rtr_len: 144
2017-01-31 10:39:57 GMT conf_hash: -2016107656
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spread.org/pipermail/spread-users/attachments/20170201/88d59b42/attachment.html>
More information about the Spread-users
mailing list