parity 1.9.5 stable breaks backwards compatibility with system libraries

[Melvillian]

I'm running:
parity 1.9.5
OS: Ubuntu 14.04.05
How Installed: first via installer, but then it seemed to update itself (see paste below)
Are you fully synchronized?: No
Which network are you connected to: Kovan
Did you try to restart the node?: yes

expected behavior: I start the node and it fully synchronizes and then starts reading new blocks as they come in

actual: parity doesn't start correctly. Here is a paste of the relevant logs from when it was working, and then it seems like it tries to update itself while it's running (why?) but then fails because it relies on system libraries which don't exist

2018-03-21 14:36:28 UTC Imported #6489348 2a40…00fa (2 txs, 0.28 Mgas, 2.71 ms, 0.84 KiB)
2018-03-21 14:36:28 UTC Imported #6489348 2a40…00fa (2 txs, 0.28 Mgas, 2.71 ms, 0.84 KiB)
2018-03-21 14:36:29 UTC   11/25 peers      5 MiB chain    4 MiB db  0 bytes queue   70 KiB sync  RPC:  0 conn,  5 req
/s,  77 µs
2018-03-21 14:36:29 UTC   11/25 peers      5 MiB chain    4 MiB db  0 bytes queue   70 KiB sync  RPC:  0 conn,  5 req
/s,  77 µs
2018-03-21 14:36:32 UTC Attempting to get parity binary f447…3769
2018-03-21 14:36:32 UTC Attempting to get parity binary f447…3769
2018-03-21 14:36:32 UTC Imported #6489349 afba…c634 (4 txs, 0.20 Mgas, 3.03 ms, 1.25 KiB)
2018-03-21 14:36:32 UTC Imported #6489349 afba…c634 (4 txs, 0.20 Mgas, 3.03 ms, 1.25 KiB)
2018-03-21 14:36:33 UTC Fetched latest version (1.9.5-stable-ff82…8db2) OK to /tmp/vm3PnMIS4LLP
2018-03-21 14:36:33 UTC Fetched latest version (1.9.5-stable-ff82…8db2) OK to /tmp/vm3PnMIS4LLP
2018-03-21 14:36:33 UTC Installed updated binary to /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2
2018-03-21 14:36:33 UTC Installed updated binary to /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2
2018-03-21 14:36:33 UTC Completed upgrade to 1.9.5-stable-ff82…8db2
2018-03-21 14:36:33 UTC Completed upgrade to 1.9.5-stable-ff82…8db2
2018-03-21 14:36:33 UTC Finishing work, please wait...
2018-03-21 14:36:33 UTC Finishing work, please wait...
/home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2: /lib/x86_64-linux-gnu/libcrypto.so.1.0.0: version `OPENSSL_1.0.2' not found (required by /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2)
/home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2: /lib/x86_64-linux-gnu/libssl.so.1.0.0: version `OPENSSL_1.0.2' not found (required by /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2)
/home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2)
/home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2)
/home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /home/bitgo/.local/share/io.parity.ethereum-updates/parity-1.9.5-ff821daf1da42865f229aee35f2e74e7b2dd8db2)
pure virtual method called
terminate called without an active exception

Note, I had upgraded from 1.7.12 to 1.9.5

[tomusdrw]

Hi @Melvillian we've rolled out a critical update for Kovan (upcoming Hard Fork). Your node is updating because --auto-update=critical is enabled by default.

The binary your node auto-updates to is build against openssl1.0.2 as you may notice. We are working on resolving the issues and the fix will most likely be rolled out with 1.10.1 (see #8132).

As a workaround, please either:

• Update to 1.10.0-beta manually (release packages will be available shortly)
• use --force-direct CLI option
• Remove updated binary and run with --auto-update=none
• touch your current binary (this will override the update and will fallback to your old version)

[Melvillian]

@tomusdrw Thank you for the update. Then we'll wait on the 1.10.0-beta release packages. Once they're out I'll let you know how these 4 steps go.

[tomusdrw]

@Melvillian ok! To clarify those are not steps, those are possible options if you still want to use your old binary. I've amended the post a bit to reflect that more clearly.

New binaries for 1.10.0 can be found here, we are still working on the release notes though.

[5chdn]

1.10 is out