Re: spread connection error
John Lane Schultz <[email protected]> Tue, 2 May 2017 10:43:16 -0400
| Newsgroups | gmane.network.spread.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Emmanuel, =
> How many segments should we use ?
Your segments should correspond to your LANs that support single-hop broadc=
ast, or preferably, multicast transmission between all of the daemons in th=
e segment.
> Which network masks/range ?
If your network gear supports it, then you should prefer to use multicast a=
ddresses for your segment addresses instead of broadcast addresses. That i=
s more efficient, in terms of interrupts for uninvolved machines on the net=
work, and you don=92t have to worry about getting your network masking / ad=
dressing exactly correct.
> Are there any limits in spread use hit by our config ? (max segments, max=
computer per segment, max computers in the whole config =85)
In 4.4, there should be no new limitations on the number of daemons you can=
have in a segment or in a configuration. It is possible, however, that so=
me Windows specific regressions may have been introduced at some point beca=
use we don=92t have a great environment in which to test large Windows depl=
oyments.
To better debug your problems, I=92d need you to send some log file outputs=
from the daemons with the following debug flags enabled:
DebugFlags =3D { PRINT EXIT CONFIGURATION MEMBERSHIP }
If you could also run an sp_monitor at the same time and have it query the =
status of all the involved daemons and give me some of that output, that mi=
ght help too.
Cheers!
-----
John Lane Schultz
Spread Concepts LLC
Cell: 443 838 2200
On Apr 28, 2017, at 8:34 AM, MAGNIER Emmanuel [EIFFAGE ENERGIE] <Emmanuel.M=
[email protected]> wrote:
Dear spread users,
=
We're upgrading an old setup made with :
=95 Spread 3
=95 Windows XP computers
=95 Windows 2003 computers
=
To this new setup :
=95 Spread 4.4
=95 Windows 10 computers
=95 Windows 2016 computers
=
First spread.conf :
=
Spread_Segment 172.21.164.255:4803 {
GTC_T_ACQ_Q1 172.21.164.10
GTC_T_PE1_Q1 172.21.164.11
}
=
Spread_Segment 172.22.164.255:4803 {
GTC_T_ACQ_Q2 172.22.164.10
GTC_T_PE1_Q2 172.22.164.11
GTC_T_PE1_PC3 172.22.164.15
GTC_T_PE2_PC3 172.22.164.16
GTC_T_BDD 172.22.164.19
GTC_T_ACQ_GTE 172.22.164.22
GTC_T_PE3_CLI 172.22.164.23
GTC_T_PE1_GTE 172.22.164.25
}
=
Spread_Segment 172.23.164.255:4803 {
GTC_T_ACQ_Q3 172.23.164.10
GTC_T_PE1_Q3 172.23.164.11
GTC_T_PA1_MAI 172.23.164.15
GTC_T_ARC 172.23.164.24
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_ACQ_Q4 172.24.164.10
GTC_T_PE1_Q4 172.24.164.11
GTC_T_PA1_ADM 172.24.164.15
# GTC_T_PA1_BDT 172.24.164.16
GTC_T_PE1_CLI 172.24.164.18
GTC_T_PE2_CLI 172.24.164.19
GTC_T_AS1_Q4 172.24.164.25
GTC_T_AS2_Q4 172.24.164.27
GTC_T_PE4_CLI 172.24.164.28
GTC_T_PE1_SI1 172.24.164.50
VERDI 172.24.164.240
}
=
Spread_Segment 172.27.112.255:4803 {
GTC_B_ACQ 172.27.112.10
GTC_B_PE1_PCS 172.27.112.13
GTC_B_PA1_ADM 172.27.112.16
}
=
Spread_Segment 172.26.146.255:4803 {
GTC_R_ACQ 172.26.146.10
GTC_R_PE1_CLI 172.26.146.12
GTC_R_PA1_ADM 172.26.146.14
GTC_R_PE1_GTE 172.26.146.18
}
=
=
Spread_Segment 172.28.116.255:4803 {
GTC_A_PE1_PCS 172.28.116.12
GTC_A_ACQ 172.28.116.14
}
=
#Spread_Segment 172.20.16.255:4803 {
# VERDI 172.20.16.87
#}
=
DangerousMonitor =3D true
=
=
This doesn't work :
=95 When starting spread.exe on more than 2 computers in the same segments
OR
=95 When starting spread.exe on more than 8 computers
=
We're getting "spread connection refused" error.
=
We tried this second spread.conf :
=
Spread_Segment 172.21.164.255:4803 {
GTC_T_ACQ_Q1 172.21.164.10
GTC_T_PE1_Q1 172.21.164.11
}
=
Spread_Segment 172.22.164.255:4803 {
GTC_T_ACQ_Q2 172.22.164.10
GTC_T_PE1_Q2 172.22.164.11
}
=
Spread_Segment 172.22.164.255:4803 {
GTC_T_PE1_PC3 172.22.164.15
GTC_T_PE2_PC3 172.22.164.16
}
=
Spread_Segment 172.22.164.255:4803 {
GTC_T_BDD 172.22.164.19
GTC_T_ACQ_GTE 172.22.164.22
}
=
Spread_Segment 172.22.164.255:4803 {
GTC_T_PE3_CLI 172.22.164.23
GTC_T_PE1_GTE 172.22.164.25
}
=
Spread_Segment 172.23.164.255:4803 {
GTC_T_ACQ_Q3 172.23.164.10
GTC_T_PE1_Q3 172.23.164.11
}
=
Spread_Segment 172.23.164.255:4803 {
GTC_T_PA1_MAI 172.23.164.15
GTC_T_ARC 172.23.164.24
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_ACQ_Q4 172.24.164.10
GTC_T_PE1_Q4 172.24.164.11
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_PA1_ADM 172.24.164.15
# GTC_T_PA1_BDT 172.24.164.16
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_PE1_CLI 172.24.164.18
GTC_T_PE2_CLI 172.24.164.19
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_AS1_Q4 172.24.164.25
GTC_T_AS2_Q4 172.24.164.27
}
=
Spread_Segment 172.24.164.255:4803 {
GTC_T_PE4_CLI 172.24.164.28
GTC_T_PE1_SI1 172.24.164.50
}
=
Spread_Segment 172.24.164.255:4803 {
VERDI 172.24.164.240
}
=
Spread_Segment 172.27.112.255:4803 {
GTC_B_ACQ 172.27.112.10
GTC_B_PE1_PCS 172.27.112.13
}
=
Spread_Segment 172.27.112.255:4803 {
GTC_B_PA1_ADM 172.27.112.16
}
=
Spread_Segment 172.26.146.255:4803 {
GTC_R_ACQ 172.26.146.10
GTC_R_PE1_CLI 172.26.146.12
}
=
Spread_Segment 172.26.146.255:4803 {
GTC_R_PA1_ADM 172.26.146.14
GTC_R_PE1_GTE 172.26.146.18
}
=
Spread_Segment 172.28.116.255:4803 {
GTC_A_PE1_PCS 172.28.116.12
GTC_A_ACQ 172.28.116.14
}
=
#Spread_Segment 172.20.16.255:4803 {
# VERDI 172.20.16.87
#}
=
DangerousMonitor =3D true
=
=
It seems better with few computers (others aren't installed yet), but it's =
still strange for us.
=
Please advise us about :
=95 How many segments should we use ?
=95 Which network masks/range ?
=95 Are there any limits in spread use hit by our config ? (max segments, =
max computer per segment, max computers in the whole config =85)
=
Thank you for your help
=
Best Regards
=
Emmanuel MAGNIER
Responsable d'=E9tudes
=
T=E9l. : +33 (0)9 53 43 79 29
=
Cet e-mail et ses =E9ventuelles pi=E8ces jointes peuvent contenir des infor=
mations confidentielles et sont exclusivement adress=E9s au(x) destinataire=
(s) mentionn=E9(s) ci-dessus. Toute diffusion, exploitation ou copie sans a=
utorisation de cet e-mail et de ses pi=E8ces jointes est strictement interd=
ite. Si vous recevez ce message par erreur, merci de le d=E9truire et d' av=
ertir imm=E9diatement l'exp=E9diteur. EIFFAGE d=E9cline toute responsabilit=
=E9 si ce message a =E9t=E9 modifi=E9 ou falsifi=E9. =
This message and any attachments may contain confidential information and a=
re established exclusively for his or its recipients. Any use of this messa=
ge, for which it was not intended, any distribution or any total or partial=
publication is prohibited unless previously approved. If you receive this =
message in error, please destroy it and immediately notify the sender there=
of. The EIFFAGE Group declines all responsibility concerning this message i=
f it has been altered or tampered with. ___________________________________=
____________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users