| 9 Sep 2019 |
|  CrisF joined the room. | 12:16:26 |
| 16 Sep 2019 |
|  @dragonrider-e:matrix.org left the room. | 13:16:38 |
| 7 Nov 2019 |
|  @shossain:matrix.org left the room. | 13:52:32 |
| 13 Dec 2019 |
|  clement joined the room. | 23:59:11 |
| 14 Dec 2019 |
|  wolfgang joined the room. | 17:46:02 |
| 19 Dec 2019 |
|  joe joined the room. | 21:58:41 |
|  @gisela:feneas.org joined the room. | 22:03:50 |
| 22 Dec 2019 |
|  nikolaj joined the room. | 12:02:00 |
| 24 Dec 2019 |
|  kai joined the room. | 14:25:55 |
| 26 Dec 2019 |
|  @julia:ggc-project.de joined the room. | 15:37:33 |
|  @jekaterina:sibnsk.net joined the room. | 16:21:39 |
| 1 Jan 2020 |
|  jeremy joined the room. | 23:39:19 |
| 4 Jan 2020 |
 komodobridge | [discord] <dukeleto> we can't seem to reproduce this, so that is what makes it challenging to debug. This is the most info we have ever gotten about the bug, nobody had given us the error from STDOUT before | 18:34:42 |
| komodobridge | [discord] <dukeleto> so thanks to @zatJUM for that, we know a lot more now | 18:34:50 |
| * komodobridge [discord] <ComputerGenie> is OK with being called a "nobody" | 18:48:10 |
| komodobridge | [discord] <dukeleto> So to recap, this is the first time anybody has given us the actual error to work with: | 18:56:03 |
| komodobridge | [discord] <dukeleto> ```
komodod: coins.cpp:564: const CTxOut& CCoinsViewCache::GetOutputFor(const CTxIn&) const: Assertion `coins && coins->IsAvailable(input.prevout.n)' failed.
``` | 18:56:08 |
| komodobridge | [discord] <dukeleto> that is suspiciously similar to the "sync bug of death" inside KMD that Hush discovered | 18:56:32 |
| komodobridge | [discord] <dukeleto> eerily similar | 18:56:35 |
| komodobridge | [discord] <dukeleto> but now it seems only users who use -pubkey are affected, i have not heard any reports of this from average users | 18:57:10 |
| komodobridge | [discord] <dukeleto> 1 mining pool reports similar issues, i am sure they use -pubkey | 18:57:22 |
| komodobridge | [discord] <dukeleto> @zatJUM do you have high CPU load by chance? is your server close to maxed out on CPU? | 18:57:56 |
| komodobridge | [discord] <ComputerGenie> `this is the first time anybody has given us the actual error to work with`*
*in the Komodo discord | 18:59:47 |
| komodobridge | [discord] <ComputerGenie> `1 mining pool reports similar issues, i am sure they use -pubkey`
No, I don't | 19:00:41 |
| komodobridge | [discord] <dukeleto> Seems like this is a core KMD bug | 19:03:35 |
| komodobridge | [discord] <dukeleto> @zatJUM so, after talking with James a bit, I have a few ideas. Either try a fresh sync (get rid of datadir) or try a -reindex and see if that changes stuff. A previous error (maybe Hush coredumped a while ago?) might have corrupted some data | 19:09:05 |
| komodobridge | [discord] <dukeleto> this especially happened to me with zaddrs recently | 19:09:41 |
| komodobridge | [discord] <dukeleto> a coredump or other bad error, will break the state of our zaddrs and your wallet will think you are trying to double spend, until you reindex | 19:10:04 |
| komodobridge | [discord] <dukeleto> because it never got to say "this zutxo is spent" and write out the data | 19:10:27 |
| komodobridge | [discord] <zatJUM> ```do you have high CPU load by chance?```By chance: no 😉 ```is your server close to maxed out on CPU?```No, it's on my main NN, and I do not mine KMD on it, but 5 smartchains with `genproclimit=1` only | 19:52:46 |
