-
Notifications
You must be signed in to change notification settings - Fork 1.7k
parity --config=dev
doesn't shutdown correctly
#10378
Comments
Can you try shutting down with |
(I know that I was messing around with dev on beta 2.3.3 earlier today and didn't see this issue so there must be more to it than just running on dev) |
|
I should probably stop asking for that specific logging module because I've never seen useful output from it 🙏 thanks, I'll look into this more tomorrow morning. |
Parity Ethereum version: version Parity-Ethereum/v2.5.0-beta-b52ac2066-20190408/x86_64-windows-msvc/rustc1.33.0 Start parity.exe --config dev // note account hasn't been unlocked |
It sounds like the Signer is blocking the shutdown process, thanks for the report @gpersoon - could you please try running with |
I've add the logfiles. If you need any other logfiles please let me know. |
Probably fixed by #10689 |
I just compiled the current github version and it still has the shutdown issue. |
@gpersoon I tried this in a virtualbox using a recent build and shutdown seems to work here. I'll figure out a way to give you the same build I used to try on your end.
|
The shutdown still doesn't work for me (after have done the curl as shown above; without the curl it stops ok) - i guess it is somehow waiting for the account unlock C:\blockchain_test\Parity>.\parity.exe --config dev
2019-06-12 15:41:12 Starting Parity-Ethereum/v2.6.0-nightly-7827cc048-20190607/x86_64-windows-msvc/rustc1.34.2
2019-06-12 15:41:12 Keys path C:\Users\gerar\AppData\Roaming\Parity\Ethereum\keys\DevelopmentChain
2019-06-12 15:41:12 DB path C:\Users\gerar\AppData\Local\Parity\Ethereum\chains\DevelopmentChain\db\1484bce8c021f2ca
2019-06-12 15:41:12 State DB configuration: fast
2019-06-12 15:41:12 Operating mode: active
2019-06-12 15:41:12 Configured for DevelopmentChain using InstantSeal engine
2019-06-12 15:41:12 Cannot read logs: Io(Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." })
2019-06-12 15:41:12 Listening for new connections on 127.0.0.1:8546.
2019-06-12 15:41:12 Multi-threaded server is not available on Windows. Falling back to single thread.
2019-06-12 15:41:17 Public node URL: enode://5a9195f21f7a306a346ed56b2210a5bc51672dfd16e89308b9d6570d9c9ebb53c70b5b42b79bed2afbd44b6f39f83e862e8f683825229deab508f8e277b5ac33@127.0.0.1:30303
2019-06-12 15:41:31 eth_sendTransaction is deprecated and will be removed in future versions: Account management is being phased out see #9997 for alternatives.
2019-06-12 15:41:47 0/25 peers 8 KiB chain 12 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2019-06-12 15:42:17 0/25 peers 8 KiB chain 12 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2019-06-12 15:42:26 Finishing work, please wait...
2019-06-12 15:43:26 Shutdown is taking longer than expected.
2019-06-12 15:47:26 Shutdown timeout reached, exiting uncleanly.
''' |
I've tried the latest build and i still see the issue: >.\parity.exe --config dev
2019-07-22 10:51:28 Starting Parity-Ethereum/v2.7.0-nightly-d1b28bf57-20190721/x86_64-windows-msvc/rustc1.36.0
2019-07-22 10:51:28 Keys path C:\Users\gerar\AppData\Roaming\Parity\Ethereum\keys\DevelopmentChain
2019-07-22 10:51:28 DB path C:\Users\gerar\AppData\Local\Parity\Ethereum\chains\DevelopmentChain\db\1484bce8c021f2ca
2019-07-22 10:51:28 State DB configuration: fast
2019-07-22 10:51:28 Operating mode: active
2019-07-22 10:51:29 Configured for DevelopmentChain using InstantSeal engine
2019-07-22 10:51:29 Multi-threaded server is not available on Windows. Falling back to single thread.
2019-07-22 10:51:34 Public node URL: enode://5a9195f21f7a306a346ed56b2210a5bc51672dfd16e89308b9d6570d9c9ebb53c70b5b42b79bed2afbd44b6f39f83e862e8f683825229deab508f8e277b5ac33@127.0.0.1:30303
2019-07-22 10:51:59 0/25 peers 735 bytes chain 17 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2019-07-22 10:52:17 eth_sendTransaction is deprecated and will be removed in future versions: Account management is being phased out see #9997 for alternatives.
2019-07-22 10:52:29 0/25 peers 735 bytes chain 17 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2019-07-22 10:52:44 Finishing work, please wait...
2019-07-22 10:53:45 Shutdown is taking longer than expected.
2019-07-22 10:57:45 Shutdown timeout reached, exiting uncleanly. |
When I run
parity --config=dev
and try to kill it withctrl+c
it hangs forever, see the following log:Edit: I've just noticed #10364. The issue looks the same. Mine might be easier to reproduce.
The text was updated successfully, but these errors were encountered: