Parity-ethereum: 2.7.2 on Windows just terminating

Created on 12 Feb 2020  ·  10Comments  ·  Source: openethereum/parity-ethereum

  • Parity Ethereum version: 2.7.2
  • Operating system: Windows
  • Installation: parity.exe
  • Fully synchronized: both
  • Network: ethereum
  • Restarted: yes

I downloaded 2.7.2 for Windows today but it always terminates shortly after start, without syncing and without any error message. Even debug output shows nothing peculiar. Tried on two different machines, with and without existing sync. The console output before termination is just the regular info:

2020-02-12 09:54:06  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 09:54:06  Keys path <keys path>
2020-02-12 09:54:06  DB path <db path>
2020-02-12 09:54:06  State DB configuration: fast
2020-02-12 09:54:06  Operating mode: active
2020-02-12 09:54:08  Configured for Ethereum using Ethash engine
2020-02-12 09:54:08  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 09:54:08  Public node URL: enode://b300efb685a44257e667cad6df8fa4f1ea336a6fc6666165ab41e2e19c429b28b41ea2783087a51073816c8d92dc054e4f3c13caa3f6e86991a5bd8431bbc970@127.0.0.1:30303

I had to revert to 2.5.13 which works fine.

F2-bug 🐞 P5-sometimesoon 🌲

Most helpful comment

Hi @esocode, do you think you could try this build on your system?

parity.exe.zip

All 10 comments

@esocode

Could you monitor your memory usage? My best guess is that you ran out of memory.

No, memory is not an issue. One of the machines has 32G (>16 available). And parity fails fast, just prints the console output and then exits. I have also removed any existing config and chain files but that doesn't help either.

Just tried a third machine (with 32G) which had never run parity before with the same effect. Could only be some network problem but as said there's nothing even in the debug log. And 2.5.13 runs without problems. The only error mentioned in the debug log is the following:

2020-02-12 12:26:43   DEBUG ethcore_network_devp2p::ip_utils  IP request error: Request Error. Invalid response from gateway: <?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:GetExternalIPAddressResponse xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1">
<NewExternalIPAddress></NewExternalIPAddress>
</u:GetExternalIPAddressResponse>
</s:Body>
</s:Envelope>

But I assume that is not critical as it is not mentioned outside debug logs.

I can repeat this. It fails very quickly at startup.
This is a regression from 2.6.8.
I have tried with the following flags, all to no effect: --no-jsonrpc, --no-persistent-txqueue, --no-secretstore, --no-ipc, --no-ws, --nat=none, mode=offline.

Interestingly issuing a command works: db kill, account list etc. Using other chains seem to work fine, I tried: --chain=goerli and kovan, rinkeby, ropsten and classic. All work.

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=goerli
2020-02-12 11:19:59  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:19:59  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\goerli
2020-02-12 11:19:59  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\goerli\db\b1d518969eab529d
2020-02-12 11:19:59  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:19:59  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:19:59  main INFO ethcore_service::service  Configured for Görli Testnet using Clique engine
2020-02-12 11:19:59  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 11:20:05  IO Worker #1 INFO network  Public node URL: enode://c6d5cd4622a4d1fd6d3388b77cca6f8f45b672391cb20b5dd5108c7d1892fb9c832ee2e0a0d52db9401c046565309cb42f4a2f508283764654b9744897d5e780@127.0.0.1:30303
2020-02-12 11:20:09  IO Worker #3 INFO import  Syncing    #5643 0x5297…1830   559.65 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed     #5643    2/25 peers      1 MiB chain  809 KiB db  0 bytes queue    1 MiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:20:13  main INFO parity_ethereum::run  Finishing work, please wait...

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=kovan
2020-02-12 11:20:28  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:20:28  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\kovan
2020-02-12 11:20:28  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\kovan\db\9bf388941c25ea98
2020-02-12 11:20:28  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:20:28  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:20:28  main WARN engine  Not preparing block; cannot sign.
2020-02-12 11:20:28  main INFO ethcore_service::service  Configured for Kovan Testnet using AuthorityRound engine
2020-02-12 11:20:28  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 11:20:32  IO Worker #1 WARN engine  Not preparing block; cannot sign.
2020-02-12 11:20:32  IO Worker #1 WARN engine  Not preparing block; cannot sign.
2020-02-12 11:20:34  IO Worker #0 INFO network  Public node URL: enode://c6d5cd4622a4d1fd6d3388b77cca6f8f45b672391cb20b5dd5108c7d1892fb9c832ee2e0a0d52db9401c046565309cb42f4a2f508283764654b9744897d5e780@127.0.0.1:30303
2020-02-12 11:20:58  IO Worker #1 INFO import     0/25 peers   803 bytes chain    2 KiB db  0 bytes queue 544 bytes sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:21:28  IO Worker #1 INFO import     0/25 peers   803 bytes chain    2 KiB db  0 bytes queue 544 bytes sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:21:56  IO Worker #2 WARN engine  Running AuRa with an even number of validators (4) is not recommended (risk of network split).
2020-02-12 11:21:58  IO Worker #2 INFO import  Syncing snapshot 6/1859        #0    1/25 peers   803 bytes chain    2 KiB db  0 bytes queue    1 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:22:03  IO Worker #1 INFO import  Syncing snapshot 14/1859        #0    1/25 peers   803 bytes chain    2 KiB db  0 bytes queue    2 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:22:05  main INFO parity_ethereum::run  Finishing work, please wait...

C:\Users\IEUser\Downloads>

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=rinkeby
2020-02-12 11:22:20  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:22:20  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\rinkeby
2020-02-12 11:22:20  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\rinkeby\db\0d824504e4fa37a7
2020-02-12 11:22:20  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:22:20  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:22:20  main INFO ethcore_service::service  Configured for Rinkeby using Clique engine
2020-02-12 11:22:20  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 11:22:25  IO Worker #2 INFO network  Public node URL: enode://c6d5cd4622a4d1fd6d3388b77cca6f8f45b672391cb20b5dd5108c7d1892fb9c832ee2e0a0d52db9401c046565309cb42f4a2f508283764654b9744897d5e780@127.0.0.1:30303
2020-02-12 11:22:30  IO Worker #1 INFO import  Syncing       #0 0x6341…e177     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed        #0    1/25 peers   936 bytes chain   87 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:22:35  IO Worker #0 INFO import  Syncing       #0 0x6341…e177     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed        #0    1/25 peers   936 bytes chain   87 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:22:40  IO Worker #1 INFO import  Syncing       #0 0x6341…e177     0.00 blk/s    0.0 tx/s    0.0 Mgas/s      0+    0 Qed        #0    1/25 peers   936 bytes chain   87 KiB db  0 bytes queue   10 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:22:54  main INFO parity_ethereum::run  Finishing work, please wait...

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=ropsten
2020-02-12 11:23:02  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:23:02  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\ropsten
2020-02-12 11:23:02  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\ropsten\db\ae90623718e47d66
2020-02-12 11:23:02  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:23:02  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:23:03  main INFO ethcore_service::service  Configured for Ropsten Testnet using Ethash engine
2020-02-12 11:23:03  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 11:23:08  IO Worker #0 INFO network  Public node URL: enode://c6d5cd4622a4d1fd6d3388b77cca6f8f45b672391cb20b5dd5108c7d1892fb9c832ee2e0a0d52db9401c046565309cb42f4a2f508283764654b9744897d5e780@127.0.0.1:30303
2020-02-12 11:23:23  IO Worker #1 INFO import  Syncing snapshot 0/3926        #0    3/25 peers   810 bytes chain   87 KiB db  0 bytes queue    3 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:23:28  IO Worker #2 INFO import  Syncing snapshot 0/3926        #0    3/25 peers   810 bytes chain   87 KiB db  0 bytes queue    3 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:23:33  IO Worker #0 INFO import  Syncing snapshot 4/3926        #0    3/25 peers   810 bytes chain   87 KiB db  0 bytes queue    3 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:23:36  main INFO parity_ethereum::run  Finishing work, please wait...

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=classic
2020-02-12 11:24:14  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:24:14  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\classic
2020-02-12 11:24:14  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\classic\db\906a34e69aec8c0d
2020-02-12 11:24:14  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:24:14  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:24:14  main INFO ethcore_service::service  Configured for Ethereum Classic using Ethash engine
2020-02-12 11:24:14  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2020-02-12 11:24:19  IO Worker #1 INFO network  Public node URL: enode://c6d5cd4622a4d1fd6d3388b77cca6f8f45b672391cb20b5dd5108c7d1892fb9c832ee2e0a0d52db9401c046565309cb42f4a2f508283764654b9744897d5e780@127.0.0.1:30303
2020-02-12 11:24:24  IO Worker #1 INFO import  Syncing snapshot 0/208        #0    5/25 peers   810 bytes chain    3 MiB db  0 bytes queue    5 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:32  IO Worker #2 INFO import  Syncing snapshot 3/208        #0    5/25 peers   810 bytes chain    3 MiB db  0 bytes queue    5 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:34  IO Worker #2 INFO import  Syncing snapshot 7/208        #0    5/25 peers   810 bytes chain    3 MiB db  0 bytes queue    6 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:39  IO Worker #0 INFO import  Syncing snapshot 11/208        #0    6/25 peers   810 bytes chain    3 MiB db  0 bytes queue    6 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:44  IO Worker #0 INFO import  Syncing snapshot 14/208        #0    6/25 peers   810 bytes chain    3 MiB db  0 bytes queue    6 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:49  IO Worker #1 INFO import  Syncing snapshot 18/208        #0    7/25 peers   810 bytes chain    3 MiB db  0 bytes queue    6 KiB sync  RPC:  0 conn,    0 req/s,    0 µs
2020-02-12 11:24:49  main INFO parity_ethereum::run  Finishing work, please wait...

C:\Users\IEUser\Downloads>"parity (1).exe" --mode=active -lmain=trace --chain=eth
2020-02-12 11:24:56  main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.7.2-stable-d961010f63-20200205/x86_64-pc-windows-msvc/rustc1.41.0
2020-02-12 11:24:56  main INFO parity_ethereum::run  Keys path C:\Users\IEUser\AppData\Roaming\Parity\Ethereum\keys\ethereum
2020-02-12 11:24:56  main INFO parity_ethereum::run  DB path C:\Users\IEUser\AppData\Local\Parity\Ethereum\chains\ethereum\db\906a34e69aec8c0d
2020-02-12 11:24:56  main INFO parity_ethereum::run  State DB configuration: fast
2020-02-12 11:24:56  main INFO parity_ethereum::run  Operating mode: active
2020-02-12 11:24:57  main INFO ethcore_service::service  Configured for Ethereum using Ethash engine

C:\Users\IEUser\Downloads>

@esocode I don't have a fix for you (yet) but I do have a workaround: if you specify the spec file for mainnet with --chain it seems to work. The file you need is here and the full command would look something like parity.exe --chain=c:\path\to\foundation.json.

Thanks, with this parameter parity doesn't terminate and starts synching.

@esocode What windows version(s) did the machines run where you saw this on? I can repeat the problem on my Windows 10 Version 1809 (OS Build 17763.1039) box, but on Windows 10 Version 1903 (OS Build 18362.30) it works fine. It would be great to have more info.

In case you don't know how to show the exact build, hit Win + r and then type winver and run the utility; a small window will pop up with the exact version and build number.

All 3 machines are up-to-date, running the latest build 1909-18363.657. This is the latest patch from this week and I noticed the problem with the previous version, but it persists.

Hi @esocode, do you think you could try this build on your system?

parity.exe.zip

Yeah, that version works as it should, syncs without any extra parameters.

Was this page helpful?
0 / 5 - 0 ratings