Attempted to close connection while not yet open

[chevdor]

This occurred for me first yesterday.

I run parity (master) as:

parity [--testnet] ui

Things go well until I hit Ctrl-C in the console. When I do so, I get the following output:

Imported #2606637 e040…cc74 (0 txs, 0.00 Mgas, 0.35 ms, 0.52 KiB)
^C2016-11-11 11:34:23  Finishing work, please wait...
2016-11-11 11:34:23  Attempted to close connection while not yet open.
2016-11-11 11:34:23  Attempted to close connection while not yet open.
2016-11-11 11:34:23  Attempted to close connection while not yet open.
2016-11-11 11:34:23  Attempted to close connection while not yet open.
2016-11-11 11:34:23  Attempted to close connection while not yet open.
^[[A2016-11-11 11:34:25  Imported #2606638 dda3…c94a (21 txs, 0.73 Mgas, 10.61 ms, 3.61 KiB)
2016-11-11 11:34:26  Imported #2606639 bf95…44ca (1 txs, 0.02 Mgas, 0.61 ms, 0.63 KiB)
^C2016-11-11 11:34:38      0/23/25 peers     18 MiB db    6 MiB chain  0 bytes queue    3 MiB sync
2016-11-11 11:34:58  Imported #2606640 c1ea…b267 (3 txs, 0.07 Mgas, 2.67 ms, 0.85 KiB)
2016-11-11 11:35:02  Imported #2606641 4feb…84a8 (1 txs, 0.02 Mgas, 1.00 ms, 0.63 KiB)

Subsequent ctrl-c are just ignored.

and parity keeps going... unstoppable :)

[tomusdrw]

That messages seems to appear only in debug mode, closing Parity in debug mode may take quite a while (if you have some blocks in the queue).
Did it close eventually?

[chevdor]

I am running in debug mode indeed. I gave it a few minutes, it kept on Importing and did not close.
I did not let it run an hour...

[chevdor]

The issue seems to occur if you are stressed on the ctrl-c

In other words, pressing ctrl-c ONCE seems to work as expected.
If you hit it twice, fast enough, the issue occur.

I can reproduce the issue 100% of the attempts.

[chevdor]

You can see it pretty good here. Watch for the ^C

^C2016-11-11 12:32:15  Finishing work, please wait...
^C2016-11-11 12:32:15  Attempted to close connection while not yet open.
2016-11-11 12:32:16  Public node URL: enode://5ac4a535d8a01523143b53134d0ee1cec1450fc60dc33db0ec8158ce0d4cc56941f618b10240269d39de8006ab801ec11bb99c577758f293b59362f99fa361f1@192.168.0.58:30303
^C^C^C2016-11-11 12:32:36      0/ 5/25 peers      4 MiB db  484 KiB chain  0 bytes queue   14 KiB sync
2016-11-11 12:33:06      0/ 5/25 peers      4 MiB db  484 KiB chain  0 bytes queue   14 KiB sync
2016-11-11 12:33:19  Imported #1853158 55fc…1981 (0 txs, 0.00 Mgas, 8.55 ms, 0.53 KiB)
2016-11-11 12:33:34  Imported #1853159 8127…4453 (38 txs, 1.78 Mgas, 278.11 ms, 6.80 KiB)
2016-11-11 12:33:36      0/ 5/25 peers      4 MiB db  490 KiB chain  0 bytes queue   21 KiB sync
2016-11-11 12:33:39  Imported #1853160 5686…b83a (77 txs, 1.62 Mgas, 223.67 ms, 9.10 KiB)
^C^C^C

[chevdor]

See #3332 & #3356

[chevdor]

@tomusdrw the message appears also in release mode. I can also reproduce the issue in release.