[1]
J’ai donc essayé de synchroniser avec g1-test. Après le succès initial, j’obtiens encore une autre erreur 502 Bad Gateway.
duniter.log
2018-04-03T00:43:17+02:00 - ^[[32minfo^[[39m: Try with g1-test.duniter.org:10900 238pNf
2018-04-03T00:43:17+02:00 - ^[[32minfo^[[39m: Sync started.
2018-04-03T00:43:17+02:00 - ^[[32minfo^[[39m: Getting remote blockchain info...
2018-04-03T00:43:17+02:00 - ^[[32minfo^[[39m: Connecting to g1-test.duniter.org...
...
2018-04-03T02:01:52+02:00 - ^[[32minfo^[[39m: Block #158405 added to the blockchain in 178 ms
2018-04-03T02:01:52+02:00 - ^[[32minfo^[[39m: Downloaded 100%, Applied 100%
2018-04-03T02:01:52+02:00 - ^[[32minfo^[[39m: Blocks were not applied.
2018-04-03T02:01:52+02:00 - ^[[32minfo^[[39m: Synchronizing the sandboxes...
...
2018-04-03T02:01:57+02:00 - ^[[32minfo^[[39m: Sync finished.
2018-04-03T02:01:59+02:00 - ^[[32minfo^[[39m: Sibling endpoints:
2018-04-03T02:01:59+02:00 - ^[[32minfo^[[39m: BMA access: guilder-test.nohost.me:80
2018-04-03T02:01:59+02:00 - ^[[32minfo^[[39m: ✔ PEER 4afuUAUA
2018-04-03T02:02:01+02:00 - ^[[32minfo^[[39m: WS2P server 4afuUAUANLEY11LZHj7mxtZQxedJ5SMCp2yi9TR1ZMjx listening on 127.0.0.1:20901
2018-04-03T02:02:36+02:00 - ^[[32minfo^[[39m: Block resolution: 0 potential blocks after current#158405...
2
...
2018-04-03T08:33:06+02:00 - ^[[32minfo^[[39m: Block resolution: 0 potential blocks after current#158405...
2018-04-03T08:33:35+02:00 - ^[[32minfo^[[39m: Block resolution: 0 potential blocks after current#158405...
conf.json
{
"currency": "g1-test",
"endpoints": [
"BASIC_MERKLED_API guilder-test.nl.eu.org 80"
],
"rmEndpoints": [],
"upInterval": 3600000,
"c": 0.0488,
"dt": 86400,
"dtReeval": 631152,
"ud0": 1000,
"stepMax": 5,
"sigPeriod": 86400,
"sigValidity": 12623040,
"msValidity": 6311520,
"sigQty": 5,
"xpercent": 0.8,
"percentRot": 0.67,
"powDelay": 0,
"avgGenTime": 150,
"dtDiffEval": 12,
"medianTimeBlocks": 24,
"httplogs": false,
"udid2": false,
"timeout": 3000,
"isolate": false,
"forksize": 100,
"switchOnHeadAdvance": 3,
"sync": {},
"msPeriod": 1051920,
"loglevel": "info",
"cpu": 0.6,
"port": 10901,
"remoteport": 80,
"upnp": false,
"ipv4": "127.0.0.1",
"remoteipv6": "2001:983:8610:1:2239:6fcb:6144:21d2",
"ipv6": "2001:983:8610:1:2239:6fcb:6144:21d2",
"remoteipv4": "192.168.178.30",
"dos": {
"whitelist": [
"127.0.0.1"
],
"maxcount": 50,
"burst": 20,
"limit": 40,
"maxexpiry": 10,
"checkinterval": 1,
"trustProxy": true,
"includeUserAgent": true,
"errormessage": "Error",
"testmode": false,
"silent": false,
"silentStart": false,
"responseStatus": 429
},
"sigStock": 100,
"sigWindow": 1051920,
"idtyWindow": 1051920,
"msWindow": 1051920,
"rootoffset": 0,
"remotehost": "guilder-test.nl.eu.org",
"nbCores": 4,
"prefix": 1,
"nobma": false,
"bmaWithCrawler": false,
"ws2p": {
"uuid": "dd52a604",
"privateAccess": true,
"publicAccess": true,
"preferedOnly": false,
"privilegedOnly": false,
"upnp": false,
"host": "127.0.0.1",
"port": 20901,
"remoteport": 443,
"remotehost": "guilder-test.nl.eu.org"
},
"proxiesConf": {
"reachingClearEp": "clear",
"forceTor": false
},
"udTime0": 1496527200,
"udReevalTime0": 1496570400
}
[1]
So I tried synchronizing with g1-test. After initial success I get yet another 502 Bad Gateway error.