Synchronization stuck at 0%

Operators who are having troubles with synchronization not kick-starting at all, please provide your full logs here Copy and paste these from Event’s View here into a code-block (important!).

 [DSM-sync]: establishing connection with: 178.63.97.88
 [DSM-sync]: establishing connection with: 89.174.201.46
 [UDT]: connecting to 195.162.68.229
 [UDT]: connecting to 31.183.72.251
 [UDT]: connecting to 178.132.108.238
 [UDT]: connecting to 178.63.97.88
 [UDT]: connecting to 89.174.201.46
 [DSM-sync]: establishing connection with: 195.162.68.224
 [DSM-sync]: establishing connection with: 193.143.121.226
 [DSM-sync]: establishing connection with: 194.34.238.140
 [DSM-sync]: establishing connection with: 148.251.75.43
 [DSM-sync]: establishing connection with: 86.23.75.243
 [UDT]: connecting to 195.162.68.224
 [UDT]: connecting to 193.143.121.226
 [UDT]: connecting to 194.34.238.140
 [UDT]: connecting to 148.251.75.43
 [UDT]: connecting to 86.23.75.243
 [UDT]: connected with 178.63.97.88
 Outgress UDT conversation with 178.63.97.88 has begun.
 [DSM-sync]: establishing connection with: 41.34.138.185
 [UDT]: connecting to 41.34.138.185
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [UDT]: connected with 194.34.238.140
 Outgress UDT conversation with 194.34.238.140 has begun.
 [DSM-sync]: telling 194.34.238.140 to enable block-synchronization on a conversation .
 [UDT]: connected with 195.162.68.229
 Outgress UDT conversation with 195.162.68.229 has begun.
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [UDT]: connected with 148.251.75.43
 Outgress UDT conversation with 148.251.75.43 has begun.
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [UDT]: connected with 193.143.121.226
 Outgress UDT conversation with 193.143.121.226 has begun.
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [UDT]: connected with 195.162.68.224
 Outgress UDT conversation with 195.162.68.224 has begun.
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [UDT]: connected with 41.34.138.185
 Outgress UDT conversation with 41.34.138.185 has begun.
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
 [Network Manager]: Network Threads:44
 [Synchronization]: Target sync connectivity reached.
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 194.34.238.140 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
 [Network Manager]: Network Threads:44
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 194.34.238.140 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM Sync]: expecting large data delivery from 216.219.89.134.
 [DSM Sync]:  block header received from 216.219.89.134 is of interest. Requesting chain-proof now..
 Handling a TX notification..
 [TestNet:Transaction Manager]: Transaction: 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP registered. Receipt: 4NgMQqtvoZb9c3rBg8wNnGK9SFXvtE7MkTWfDk95boCG3gWitX
 [TestNet:Transaction Manager]: Transaction: 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV registered. Receipt: 4jDsFBvku59cxZaizih1guBnivPNQwiSqDWbTuAsh2Y6N7EdMr
 [TestNet:Transaction Manager]: Transaction: 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE registered. Receipt: 4RgiaHtgCx5RXF6yA46N7wtj1532FpJpn7EUQApEKqEyrjFdgr
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [DSM Sync]: I'll notify 216.219.89.134 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 195.162.68.229 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 178.63.97.88 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 195.162.68.224 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 193.143.121.226 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 194.34.238.140 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 148.251.75.43 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 41.34.138.185 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 216.219.89.134 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 195.162.68.229 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 178.63.97.88 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 195.162.68.224 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 193.143.121.226 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 194.34.238.140 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 148.251.75.43 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 41.34.138.185 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 216.219.89.134 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 195.162.68.229 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 178.63.97.88 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 195.162.68.224 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 193.143.121.226 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 194.34.238.140 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 148.251.75.43 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 [DSM Sync]: I'll notify 41.34.138.185 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 Successfully dispatched 24 elements from mem-pool across 8 nodes.
 [DSM-sync]: redundant object received from 41.34.138.185

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:running πŸ”’
9TNiA9jJh9WaUYbH@95.149.227.134:ended
288mtDtw2sbMXx6vj@193.56.254.162:ended
iK9djmJTTmngLhgo@74.88.18.208:ended
3sjup97qSgBPcrnqV@178.232.26.99:ended
2XmS1ct5kS971Scn3@196.221.13.152:ended
4w6esjv6d3UEu4jZV@185.244.212.67:ended
JCbj7fMFkPHixU9e@45.87.104.174:ended
2RygsknHcL6MsMevf@31.171.154.59:ended
3EtuVF5rmGncbt4QA@74.50.76.90:ended
aPNyoW4qYporAGhH@83.7.130.131:ended
1ddwFAMfQKR7xA1U@195.162.68.229:ended πŸ”’
E68hRKpoYoZy2jse@31.183.72.251:ended
4F3GL8rxCGiXX4R3M@178.132.108.238:ended
4RjYiHxSFuQgF1fjy@178.63.97.88:ended πŸ”’
4myTXJPHGg1ucTgDx@89.174.201.46:ended
4Au3HeWsQsvbqEEHJ@195.162.68.224:ended πŸ”’
24BoWQDbhNyjFgJvs@194.34.238.140:ended πŸ”’
VWezDyQAk3wPsAaK@148.251.75.43:ended πŸ”’
3TTKy3TZv1bSuRun1@86.23.75.243:ended
3fksychvsk4U1f3Sb@41.34.138.185:ended πŸ”’
cC1pLyP2hFuMQypS@167.235.35.172:ended
4Zz1nFzck68XRvFdw@95.149.227.134:connecting
42KDVnBGFEfzJSqXR@193.56.254.162:connecting
tP7wgArq9PtQ4LKe@74.88.18.208:connecting
3wRepnCCDyZGaG9F1@178.232.26.99:connecting
t6Mcwj9vfJtYs6qw@196.221.13.152:connecting
w1VcHCgnaNzsQubv@185.244.212.67:connecting
yw6SpEJdTKoVtKx1@45.87.104.174:connecting
55iW2NAUUYnuKipSv@31.171.154.59:connecting
F59DSnCYNcRTzgVw@74.50.76.90:connecting
4rdQGbXhMMtpFfmxj@83.7.130.131:connecting
5UaxXDYrUwQheZz55@195.162.68.229:ending πŸ”’
5gAHuC6fi6sfHWhYo@31.183.72.251:connecting
2hXMVHXjU2JRfT8fq@178.132.108.238:connecting
5a7emZMRxz9kqkYEb@178.63.97.88:ending πŸ”’
4z744dawxHVEPKH4o@89.174.201.46:connecting
4CRSG12ci8gJNUhxN@195.162.68.224:ending πŸ”’
42HADpYhyX7xFwnTM@193.143.121.226:running
3dvwhnbyWkjM7pJUq@194.34.238.140:ending πŸ”’
55a3k6VJJuZQvjXic@148.251.75.43:running
1Fea4j9HdYx1M377@86.23.75.243:connecting
4opP9eHd5EKs2VXaA@41.34.138.185:ending πŸ”’

-------

 [Kademlia: Reports] - aware of 24 nodes.
 [DSM-sync]: establishing connection with: 216.219.89.134
 [UDT]: connecting to 216.219.89.134
 [UDT]: connected with 216.219.89.134
 Outgress UDT conversation with 216.219.89.134 has begun.
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .

-- Registered WebSock Conversations --
none
-------

 [TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Network Manager]: Network Threads:34
 [UDT]: unable to connect with 95.149.227.134
 [UDT]: unable to connect with 193.56.254.162
 [UDT]: unable to connect with 196.221.13.152
 [UDT]: unable to connect with 178.232.26.99
 [UDT]: unable to connect with 74.88.18.208
 [UDT]: unable to connect with 45.87.104.174
 [UDT]: unable to connect with 185.244.212.67
 [UDT]: unable to connect with 31.171.154.59
 [UDT]: unable to connect with 74.50.76.90
 [UDT]: unable to connect with 83.7.130.131
 [UDT]: unable to connect with 178.132.108.238
 [UDT]: unable to connect with 89.174.201.46
 [UDT]: unable to connect with 31.183.72.251
 [UDT]: unable to connect with 86.23.75.243
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: establishing connection with: 167.235.35.172
 [UDT]: connecting to 167.235.35.172
 [UDT]: connected with 167.235.35.172
 Outgress UDT conversation with 167.235.35.172 has begun.
 [DSM-sync]: telling 167.235.35.172 to enable block-synchronization on a conversation .
 [Network Manager]: Network Threads:6
 [Synchronization]: Target sync connectivity not yet reached.
 [DSM Sync]: I'll notify 167.235.35.172 about 2RwBBPs5NtN1nU9H6WwRTfYEKdpHBPEa7PQR54F5wnomVE14PP
 [DSM Sync]: I'll notify 167.235.35.172 about 2nUh1jtuUPvV8yspR6h4NJQscJfii6qfC9QMKDGt329bnRs3oV
 [DSM Sync]: I'll notify 167.235.35.172 about 2UwYLqrpnGrHhfQ4aS6QoM7otTKNYyS3938EFUvEfprVBG1yuE
 Successfully dispatched 3 elements from mem-pool across 3 nodes.
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Network Manager]: Network Threads:2

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
9TNiA9jJh9WaUYbH@95.149.227.134:ended
288mtDtw2sbMXx6vj@193.56.254.162:ended
iK9djmJTTmngLhgo@74.88.18.208:ended
3sjup97qSgBPcrnqV@178.232.26.99:ended
2XmS1ct5kS971Scn3@196.221.13.152:ended
4w6esjv6d3UEu4jZV@185.244.212.67:ended
JCbj7fMFkPHixU9e@45.87.104.174:ended
2RygsknHcL6MsMevf@31.171.154.59:ended
3EtuVF5rmGncbt4QA@74.50.76.90:ended
aPNyoW4qYporAGhH@83.7.130.131:ended
1ddwFAMfQKR7xA1U@195.162.68.229:ended πŸ”’
E68hRKpoYoZy2jse@31.183.72.251:ended
4F3GL8rxCGiXX4R3M@178.132.108.238:ended
4RjYiHxSFuQgF1fjy@178.63.97.88:ended πŸ”’
4myTXJPHGg1ucTgDx@89.174.201.46:ended
4Au3HeWsQsvbqEEHJ@195.162.68.224:ended πŸ”’
24BoWQDbhNyjFgJvs@194.34.238.140:ended πŸ”’
VWezDyQAk3wPsAaK@148.251.75.43:ended πŸ”’
3TTKy3TZv1bSuRun1@86.23.75.243:ended
3fksychvsk4U1f3Sb@41.34.138.185:ended πŸ”’
cC1pLyP2hFuMQypS@167.235.35.172:ended
4Zz1nFzck68XRvFdw@95.149.227.134:unableToConnect
42KDVnBGFEfzJSqXR@193.56.254.162:unableToConnect
tP7wgArq9PtQ4LKe@74.88.18.208:unableToConnect
3wRepnCCDyZGaG9F1@178.232.26.99:unableToConnect
t6Mcwj9vfJtYs6qw@196.221.13.152:unableToConnect
w1VcHCgnaNzsQubv@185.244.212.67:unableToConnect
yw6SpEJdTKoVtKx1@45.87.104.174:unableToConnect
55iW2NAUUYnuKipSv@31.171.154.59:unableToConnect
F59DSnCYNcRTzgVw@74.50.76.90:unableToConnect
4rdQGbXhMMtpFfmxj@83.7.130.131:unableToConnect
5UaxXDYrUwQheZz55@195.162.68.229:ended πŸ”’
5gAHuC6fi6sfHWhYo@31.183.72.251:unableToConnect
2hXMVHXjU2JRfT8fq@178.132.108.238:unableToConnect
5a7emZMRxz9kqkYEb@178.63.97.88:ended πŸ”’
4z744dawxHVEPKH4o@89.174.201.46:unableToConnect
4CRSG12ci8gJNUhxN@195.162.68.224:ended πŸ”’
42HADpYhyX7xFwnTM@193.143.121.226:ended
3dvwhnbyWkjM7pJUq@194.34.238.140:ended πŸ”’
55a3k6VJJuZQvjXic@148.251.75.43:ended πŸ”’
1Fea4j9HdYx1M377@86.23.75.243:unableToConnect
4opP9eHd5EKs2VXaA@41.34.138.185:ended πŸ”’
4Hp2CyZqvTsx4dMmo@216.219.89.134:running πŸ”’
3K7zAjHHQyL3SPrc9@167.235.35.172:ended πŸ”’

-------

 [TestNet:Blockchain Manager]: Freed 21 UDT Conversations
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [Kademlia: Reports] - aware of 24 nodes.
 [Synchronization]: Target sync connectivity not yet reached.
 [Network Manager]: Network Threads:2
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [DSM-sync]: telling 216.219.89.134 to enable block-synchronization on a conversation .
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
4Zz1nFzck68XRvFdw@95.149.227.134:unableToConnect
42KDVnBGFEfzJSqXR@193.56.254.162:unableToConnect
tP7wgArq9PtQ4LKe@74.88.18.208:unableToConnect
3wRepnCCDyZGaG9F1@178.232.26.99:unableToConnect
t6Mcwj9vfJtYs6qw@196.221.13.152:unableToConnect
w1VcHCgnaNzsQubv@185.244.212.67:unableToConnect
yw6SpEJdTKoVtKx1@45.87.104.174:unableToConnect
55iW2NAUUYnuKipSv@31.171.154.59:unableToConnect
F59DSnCYNcRTzgVw@74.50.76.90:unableToConnect
4rdQGbXhMMtpFfmxj@83.7.130.131:unableToConnect
5UaxXDYrUwQheZz55@195.162.68.229:ended πŸ”’
5gAHuC6fi6sfHWhYo@31.183.72.251:unableToConnect
2hXMVHXjU2JRfT8fq@178.132.108.238:unableToConnect
5a7emZMRxz9kqkYEb@178.63.97.88:ended πŸ”’
4z744dawxHVEPKH4o@89.174.201.46:unableToConnect
4CRSG12ci8gJNUhxN@195.162.68.224:ended πŸ”’
42HADpYhyX7xFwnTM@193.143.121.226:ended
3dvwhnbyWkjM7pJUq@194.34.238.140:ended πŸ”’
55a3k6VJJuZQvjXic@148.251.75.43:ended πŸ”’
1Fea4j9HdYx1M377@86.23.75.243:unableToConnect
4opP9eHd5EKs2VXaA@41.34.138.185:ended πŸ”’
4Hp2CyZqvTsx4dMmo@216.219.89.134:ending πŸ”’
3K7zAjHHQyL3SPrc9@167.235.35.172:ended πŸ”’

-------

 [TestNet:Blockchain Manager]: Freed 5 UDT Conversations
 [Synchronization]: Target sync connectivity not yet reached.
 [TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
 [Network Manager]: Network Threads:1
 [Vitals Monitoring]: Blockchain Controller seems dead.

-- Registered WebSock Conversations --
none
-------

 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [Synchronization]: Target sync connectivity not yet reached.
 [DSM-sync]: establishing connection with: 195.162.68.229
 [DSM-sync]: establishing connection with: 178.63.97.88
 [DSM-sync]: establishing connection with: 195.162.68.224
 [DSM-sync]: establishing connection with: 193.143.121.226
 [DSM-sync]: establishing connection with: 194.34.238.140
 [DSM-sync]: establishing connection with: 148.251.75.43
 [UDT]: connecting to 195.162.68.229
 [UDT]: connecting to 178.63.97.88
 [UDT]: connecting to 195.162.68.224
 [UDT]: connecting to 193.143.121.226
 [UDT]: connecting to 194.34.238.140
 [UDT]: connecting to 148.251.75.43
 [DSM-sync]: establishing connection with: 41.34.138.185
 [UDT]: connecting to 41.34.138.185
 [UDT]: connected with 194.34.238.140
 Outgress UDT conversation with 194.34.238.140 has begun.
 [UDT]: connected with 148.251.75.43
 [UDT]: connected with 178.63.97.88
 [DSM-sync]: telling 194.34.238.140 to enable block-synchronization on a conversation .
 Outgress UDT conversation with 148.251.75.43 has begun.
 Outgress UDT conversation with 178.63.97.88 has begun.
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [UDT]: connected with 193.143.121.226
 Outgress UDT conversation with 193.143.121.226 has begun.
 [UDT]: connected with 195.162.68.224
 Outgress UDT conversation with 195.162.68.224 has begun.
 [UDT]: connected with 195.162.68.229
 Outgress UDT conversation with 195.162.68.229 has begun.
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [UDT]: connected with 41.34.138.185
 Outgress UDT conversation with 41.34.138.185 has begun.
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [Network Manager]: Network Threads:15
 [DSM Sync]: temporarily banning 194.34.238.140 (for 1h 51m 49s) due to excessive redundant objects received.
 [DSM-sync]: redundant object received from 194.34.238.140
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Security]: Max connection time with 95.149.227.134 reached. Killing it.
 [Security]: Max connection time with 193.56.254.162 reached. Killing it.
 [Security]: Max connection time with 74.88.18.208 reached. Killing it.
 [Security]: Max connection time with 178.232.26.99 reached. Killing it.
 [Security]: Max connection time with 196.221.13.152 reached. Killing it.
 [Security]: Max connection time with 185.244.212.67 reached. Killing it.
 [Security]: Max connection time with 45.87.104.174 reached. Killing it.
 [Security]: Max connection time with 31.171.154.59 reached. Killing it.
 [Security]: Max connection time with 83.7.130.131 reached. Killing it.
 [Security]: Max connection time with 31.183.72.251 reached. Killing it.
 [Security]: Max connection time with 178.132.108.238 reached. Killing it.
 [Security]: Max connection time with 89.174.201.46 reached. Killing it.
 [Security]: Max connection time with 86.23.75.243 reached. Killing it.

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
4Zz1nFzck68XRvFdw@95.149.227.134:unableToConnect
42KDVnBGFEfzJSqXR@193.56.254.162:unableToConnect
tP7wgArq9PtQ4LKe@74.88.18.208:unableToConnect
3wRepnCCDyZGaG9F1@178.232.26.99:unableToConnect
t6Mcwj9vfJtYs6qw@196.221.13.152:unableToConnect
w1VcHCgnaNzsQubv@185.244.212.67:unableToConnect
yw6SpEJdTKoVtKx1@45.87.104.174:unableToConnect
55iW2NAUUYnuKipSv@31.171.154.59:unableToConnect
F59DSnCYNcRTzgVw@74.50.76.90:unableToConnect
4rdQGbXhMMtpFfmxj@83.7.130.131:unableToConnect
5gAHuC6fi6sfHWhYo@31.183.72.251:unableToConnect
2hXMVHXjU2JRfT8fq@178.132.108.238:unableToConnect
4z744dawxHVEPKH4o@89.174.201.46:unableToConnect
42HADpYhyX7xFwnTM@193.143.121.226:ended
55a3k6VJJuZQvjXic@148.251.75.43:ended πŸ”’
1Fea4j9HdYx1M377@86.23.75.243:unableToConnect
4Hp2CyZqvTsx4dMmo@216.219.89.134:ending πŸ”’
3K7zAjHHQyL3SPrc9@167.235.35.172:ended πŸ”’
2V2Rfk69WDZEdYqPs@195.162.68.229:running πŸ”’
4dG7vPou3vjkYizhu@178.63.97.88:running πŸ”’
49GFPzG4pFeNwuSiy@195.162.68.224:running πŸ”’
TGhSWiiN2BcsPA22@193.143.121.226:running
bE7Xtx2vfpdZBMiZ@194.34.238.140:ended πŸ”’
hKCqY4mxw7vSCMEy@148.251.75.43:running
4LXtTsc7RudsMQNfe@41.34.138.185:running πŸ”’

-------

 [TestNet:Blockchain Manager]: Freed 4 UDT Conversations
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [Kademlia: Reports] - aware of 24 nodes.
 [Network Manager]: Network Threads:13
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .

-- Registered WebSock Conversations --
none
-------

 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Network Manager]: Network Threads:13
 [Kademlia: Reports] - aware of 24 nodes.
 [DSM Sync]: expecting large data delivery from 195.162.68.229.
 [DSM Sync]:  block header received from 195.162.68.229 is of interest. Requesting chain-proof now..
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [Security]: Max connection time with 216.219.89.134 reached. Killing it.

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
4Zz1nFzck68XRvFdw@95.149.227.134:ended
42KDVnBGFEfzJSqXR@193.56.254.162:ended
tP7wgArq9PtQ4LKe@74.88.18.208:ended
3wRepnCCDyZGaG9F1@178.232.26.99:ended
t6Mcwj9vfJtYs6qw@196.221.13.152:ended
w1VcHCgnaNzsQubv@185.244.212.67:ended
yw6SpEJdTKoVtKx1@45.87.104.174:ended
55iW2NAUUYnuKipSv@31.171.154.59:ended
4rdQGbXhMMtpFfmxj@83.7.130.131:ended
5gAHuC6fi6sfHWhYo@31.183.72.251:ended
2hXMVHXjU2JRfT8fq@178.132.108.238:ended
4z744dawxHVEPKH4o@89.174.201.46:ended
1Fea4j9HdYx1M377@86.23.75.243:ended
4Hp2CyZqvTsx4dMmo@216.219.89.134:ending πŸ”’
2V2Rfk69WDZEdYqPs@195.162.68.229:running πŸ”’
4dG7vPou3vjkYizhu@178.63.97.88:running πŸ”’
49GFPzG4pFeNwuSiy@195.162.68.224:running πŸ”’
TGhSWiiN2BcsPA22@193.143.121.226:running
bE7Xtx2vfpdZBMiZ@194.34.238.140:ended πŸ”’
hKCqY4mxw7vSCMEy@148.251.75.43:running
4LXtTsc7RudsMQNfe@41.34.138.185:running πŸ”’

-------

 [TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: establishing connection with: 167.235.35.172
 [UDT]: connecting to 167.235.35.172
 [UDT]: connected with 167.235.35.172
 Outgress UDT conversation with 167.235.35.172 has begun.
 [DSM-sync]: telling 167.235.35.172 to enable block-synchronization on a conversation .
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Network Manager]: Network Threads:15
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [Kademlia: Reports] - aware of 24 nodes.
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 167.235.35.172 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .

-- Registered WebSock Conversations --
none
-------

 [Synchronization]: Target sync connectivity reached.
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 167.235.35.172 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [Security]: Max connection time with 216.219.89.134 reached. Killing it.

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
4Zz1nFzck68XRvFdw@95.149.227.134:ended
42KDVnBGFEfzJSqXR@193.56.254.162:ended
tP7wgArq9PtQ4LKe@74.88.18.208:ended
3wRepnCCDyZGaG9F1@178.232.26.99:ended
t6Mcwj9vfJtYs6qw@196.221.13.152:ended
w1VcHCgnaNzsQubv@185.244.212.67:ended
yw6SpEJdTKoVtKx1@45.87.104.174:ended
55iW2NAUUYnuKipSv@31.171.154.59:ended
4rdQGbXhMMtpFfmxj@83.7.130.131:ended
5gAHuC6fi6sfHWhYo@31.183.72.251:ended
2hXMVHXjU2JRfT8fq@178.132.108.238:ended
4z744dawxHVEPKH4o@89.174.201.46:ended
1Fea4j9HdYx1M377@86.23.75.243:ended
4Hp2CyZqvTsx4dMmo@216.219.89.134:ending πŸ”’
2V2Rfk69WDZEdYqPs@195.162.68.229:running πŸ”’
4dG7vPou3vjkYizhu@178.63.97.88:running πŸ”’
49GFPzG4pFeNwuSiy@195.162.68.224:running πŸ”’
TGhSWiiN2BcsPA22@193.143.121.226:ended
bE7Xtx2vfpdZBMiZ@194.34.238.140:ended πŸ”’
hKCqY4mxw7vSCMEy@148.251.75.43:running πŸ”’
4LXtTsc7RudsMQNfe@41.34.138.185:running πŸ”’
4hBij1sC8vRZyjcwC@167.235.35.172:running

-------

 [TestNet:Blockchain Manager]: Freed 14 UDT Conversations
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [Kademlia: Reports] - aware of 24 nodes.
 [Network Manager]: Network Threads:13
  -- Registered Swarms: 1 --
1) [Local Peers]: 0 [Remote Peers]: 0
 -----------------------

 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 167.235.35.172 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [TestNet:Transaction Manager]: Min. # of objects for block formation: 1
 [Synchronization]: Target sync connectivity reached.
 [Network Manager]: Network Threads:13
 [Kademlia: Reports] - aware of 24 nodes.
 [Vitals Monitoring]: Synchronization seems stuck.
 [Vitals Monitoring]: Blockchain Controller seems dead.
 [DSM-sync]: telling 195.162.68.224 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 195.162.68.229 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 148.251.75.43 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 178.63.97.88 to enable block-synchronization on a conversation .
 [DSM-sync]: telling 41.34.138.185 to enable block-synchronization on a conversation .

-- Registered WebSock Conversations --
none
-------

 [TestNet:Transaction Manager]: Initiating Mem-Pool clean-up
 [FORCED Shutdown] UDT Conversation (ID:4Hp2CyZqvTsx4dMmo) due to a timed-out idle state.
 [Security]: Max connection time with 216.219.89.134 reached. Killing it.

-- Registered UDT Conversations --

zDbikcWXgKaDNjtp@216.219.89.134:ended πŸ”’
4Hp2CyZqvTsx4dMmo@216.219.89.134:ending πŸ”’
2V2Rfk69WDZEdYqPs@195.162.68.229:running πŸ”’
4dG7vPou3vjkYizhu@178.63.97.88:running πŸ”’
49GFPzG4pFeNwuSiy@195.162.68.224:running πŸ”’
TGhSWiiN2BcsPA22@193.143.121.226:ended
hKCqY4mxw7vSCMEy@148.251.75.43:running πŸ”’
4LXtTsc7RudsMQNfe@41.34.138.185:running πŸ”’
4hBij1sC8vRZyjcwC@167.235.35.172:running
1 Like

I think this is the related error

Sync stuck at 0% forever issue
gridnet_sync0_stuck_log.zip (48.9 KB)

1 Like

Hi, sync stays at 0%.
Not sure what part of events view needs to be supplied as it is ongoing.

Just a small snippet:

Blockquote

[Bootstrap grace period]: Still outlooking the Heaviest Chain-Proof…465 sec.
[DSM-sync]: telling 193.143.121.226 to enable block-synchronization on a conversation .
[Bootstrap grace period]: Still outlooking the Heaviest Chain-Proof…464 sec.
[Network Manager]: Network Threads:43
[DSM Sync]: expecting large data delivery from 216.219.89.134.
[DSM Sync]: block header received from 216.219.89.134 is of interest. Requesting chain-proof now…
[DSM-sync]: telling 74.50.76.90 to enable block-synchronization on a conversation .
[Bootstrap grace period]: Still outlooking the Heaviest Chain-Proof…463 sec.
[Vitals Monitoring]: Synchronization seems stuck.
[Vitals Monitoring]: Blockchain Controller seems dead.
[TestNet:Transaction Manager]: Min. # of objects for block formation: 1

Blockquote

please help cant resync still shuting down gridcore :frowning:

This is possibly related to Block 34705 Issue - #35 by Sirius

A hot-fix resolution is pending.