0.16.2 binary gives error after latest compiled client has run #14048

1. 
   ghost commented at 10:48 am on August 24, 2018: none

   – Describe the issue

   Ran the latest self compiled version of bitcoind on my bitcoin full node datadir. Later when running 0.16.2 precompiled binary, it gives this error

   You need to rebuild the database using -reindex to change -txindex.

   Please restart with -reindex or -reindex-chainstate to recover.

   You need to rebuild the database using -reindex to change -txindex. Please restart with -reindex or -reindex-chainstate to recover. Aborted block database rebuild. Exiting.

   — What behavior did you expect? –

   Full node starting as usual

   0.16.2 -> gives an error self compiled client -> works 0.16.2 -> gives error etc.

   – What type of machine are you observing the error on (OS/CPU and disk type)? –

   Ubuntu 16.04, amd processor

   – Any extra information that might be useful in the debugging process. –

   On a side note, the self compiled client prints debug output in the terminal screen, even though I started with the command “./bitcoind &”

2. 
   ken2812221 commented at 12:17 pm on August 24, 2018: contributor

   You can’t downgrade bitcoin core.
3. 
   MarcoFalke commented at 12:24 pm on August 24, 2018: member

   Downgrades are usually supported to the latest point release of the previous major release and often work down to all versions that are not EOL https://bitcoincore.org/en/lifecycle/#schedule

   If it is not possible to downgrade from 0.17.0 to 0.16.2 with txindex enabled, that should be mentioned in the release notes.

4. MarcoFalke added this to the milestone 0.17.0 on Aug 24, 2018
5. MarcoFalke added the label Docs on Aug 24, 2018
6. MarcoFalke added the label Needs release notes on Aug 24, 2018
7. 
   ghost commented at 2:27 pm on August 24, 2018: none

   Yup, backward compatibility is what I assumed, so good to know this issue was worth making.
8. 
   mmortal03 commented at 1:49 pm on October 8, 2018: none

   Milestone on this should be updated, or was this fixed?
9. 
   ghost commented at 2:00 pm on October 8, 2018: none

   Not ‘fixed’, but the issue can be closed, I guess. Core 16.99 client db wasn’t compatible with 16.3 and under when txindex=1 and vice versa. Using Core version 17 now. Thanks for the reminder.
10. unknown closed this on Oct 8, 2018

    ---

11. fanquake removed the label Needs release note on Mar 20, 2019
12. MarcoFalke locked this on Dec 16, 2021

Contributors
ghost ken2812221 MarcoFalke mmortal03

Labels
Docs

Milestone
0.17.0