Unable to fetch node health.

[c0deCn]

Before filing a new issue, please provide the following information.

I'm running:

• Which Parity version?:1.11.3
• Which operating system?: Windows
• How installed?: via installer
• Are you fully synchronized?: no
• Which network are you connected to?: ethereum
• Did you try to restart the node?: yes

Why did I restart the node and the prompt "Unable to fetch node health." ?

[c0deCn]

2018-06-09 20:40:56  main WARN ethcore_network_devp2p::node_table  Error reading node table file: ErrorImpl { code: Message("invalid type: floating point `1.24`, expected struct NodeTable"), line: 1, column: 6 }
2018-06-09 20:40:56  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2018-06-09 20:40:56  main WARN jsonrpc_http_server  Multi-threaded server is not available on Windows. Falling back to single thread.
2018-06-09 20:40:58  fetch WARN rustls::session  Sending warning alert CloseNotify

[c0deCn]

2018-06-09 20:42:17   WARN jsonrpc_ws_server::metadata  Error sending a subscription update: Error(ConnectionClosed, State { next_error: None, backtrace: None })
2018-06-09 20:42:18   WARN parity_rpc::v1::impls::pubsub  Cannot send notification: SendError("...")

[roninkaizen]

annoyance/unwanted behavior-
found same while testing 1.11.3.on.windows8.64pro.system.
solved with a restart of os,
and a start from command line
parity.exe db kill first
and afterwards start from command line
with specific command line parameters
e.g.
parity.exe cache-size 2048 --log-file C:\Users\YOURNAMEHERE\Desktop\parity.1..11.3-date.log

[Tbaut]

Can you please give some more background. What's the problem? you see an error in the UI? does it fade away? When do those errors appear? I can't figure out if you're syncing fine in between or not.
Sending warning alert CloseNotify is not a blocking error, you can ignore it.

[c0deCn]

@Tbaut
18-06-17 08:40:54 IO Worker #0 ERROR client Error importing ancient block: 0xc4a6…437e
2018-06-17 08:41:21 IO Worker #0 ERROR client Error importing ancient block: 0x9a6c…3010
2018-06-17 08:41:35 IO Worker #0 ERROR client Error importing ancient block: 0xee74…f5fe
2018-06-17 08:41:56 IO Worker #0 ERROR client Error importing ancient block: 0x126d…bf84
2018-06-17 08:42:07 IO Worker #3 ERROR client Error importing ancient block: 0xb5c7…2756
2018-06-17 08:42:25 IO Worker #3 ERROR client Error importing ancient block: 0x20ea…0b84
2018-06-17 08:42:38 IO Worker #3 ERROR client Error importing ancient block: 0x37b4…9fd4
2018-06-17 08:42:41 IO Worker #3 ERROR client Error importing ancient block: 0xfcec…1874
2018-06-17 08:42:44 IO Worker #1 ERROR client Error importing ancient block: 0xf468…c4f8
2018-06-17 08:43:03 IO Worker #1 ERROR client Error importing ancient block: 0x614d…59b9
2018-06-17 08:43:28 IO Worker #1 ERROR client Error importing ancient block: 0x9b7c…e32f
2018-06-17 08:43:35 IO Worker #1 ERROR client Error importing ancient block: 0x4936…6dc0
2018-06-17 08:43:45 IO Worker #2 ERROR client Error importing ancient block: 0x9a83…e69f
2018-06-17 08:43:55 IO Worker #2 ERROR client Error importing ancient block: 0x6ea6…e311
2018-06-17 08:44:07 IO Worker #2 ERROR client Error importing ancient block: 0x7cca…5e05
2018-06-17 08:44:11 IO Worker #2 ERROR client Error importing ancient block: 0xd0df…7c66
2018-06-17 08:44:21 IO Worker #0 ERROR client Error importing ancient block: 0xdeb0…f043
2018-06-17 08:44:24 IO Worker #0 ERROR client Error importing ancient block: 0x2d91…1ec3
2018-06-17 08:44:33 IO Worker #0 ERROR client Error importing ancient block: 0x2680…f513
2018-06-17 08:44:35 IO Worker #0 ERROR client Error importing ancient block: 0xffb2…05ab
2018-06-17 08:44:52 IO Worker #3 ERROR client Error importing ancient block: 0xac1b…a4c0
2018-06-17 08:45:11 IO Worker #3 ERROR client Error importing ancient block: 0x3d7d…34f2
2018-06-17 08:45:19 IO Worker #3 ERROR client Error importing ancient block: 0x5fa0…4cd1
2018-06-17 08:45:28 IO Worker #3 ERROR client Error importing ancient block: 0x1fda…da87
2018-06-17 08:45:34 IO Worker #1 ERROR client Error importing ancient block: 0x0126…a41e
2018-06-17 08:45:49 IO Worker #1 ERROR client Error importing ancient block: 0xd2ac…7a9f
2018-06-17 08:46:05 IO Worker #1 ERROR client Error importing ancient block: 0xbeb6…eac2
2018-06-17 08:46:18 IO Worker #1 ERROR client Error importing ancient block: 0xa258…9d9c
2018-06-17 08:46:29 IO Worker #2 ERROR client Error importing ancient block: 0xff4e…1f9e
2018-06-17 08:46:37 IO Worker #2 ERROR client Error importing ancient block: 0x1983…091a
2018-06-17 08:46:42 IO Worker #2 ERROR client Error importing ancient block: 0xfb69…e89f
2018-06-17 08:46:54 IO Worker #2 ERROR client Error importing ancient block: 0x6ef4…ec7b
2018-06-17 08:46:58 IO Worker #0 ERROR client Error importing ancient block: 0x1100…88ab
2018-06-17 08:47:11 IO Worker #0 ERROR client Error importing ancient block: 0x496f…1175
2018-06-17 08:47:21 IO Worker #0 ERROR client Error importing ancient block: 0x4a3b…a6d6
2018-06-17 08:47:32 IO Worker #0 ERROR client Error importing ancient block: 0xa901…c354
2018-06-17 08:47:44 IO Worker #3 ERROR client Error importing ancient block: 0x229a…a0f2
2018-06-17 08:47:50 IO Worker #3 ERROR client Error importing ancient block: 0x58a0…5682

[Tbaut]

This error is a bug (fixed in #8832 ), it's actually when the client does manage to import ancient blocks.

It simply looks like the UI is trying to fetch the node health while the node isn't ready yet. It's not a problem