4 Jan 2020 |
komodobridge | [discord] <zatJUM> I hadn't noticed it, but hushd had stopped: ```[HUSH3] ht.151813 txi.3 signedmask.810122120a20a200 numvins.13 numvouts.2 <<<<<<<<<<< notarized
[HUSH3] matched.1 VALID (HUSH3) MoM.9e2db433588f8cd62b52f7cb614cb340d03298391b07984428878256d1b2300e [4] CCid.2
[HUSH3] ht.151813 NOTARIZED.151806 HUSH3.00000000ecbd32f9c25de7272c2ad9506ee4eafaaa1f5217f1062da28ed3d5b1 KMDTXID.4cc87f07f16c6c7a41b3769b749a0896e35882ace72059411fb25230df278687 lens.(146 117) MoM.9e2db433588f8cd62b52f7cb614cb340d03298391b07984428878256d1b2300e 131076
GenerateBitcoins: nThreads.0 fGenerate.0
StartShutdown: fRequestShudown=true
Shutdown: start
Shutdown: stopping HTTP/REST/RPC
GenerateBitcoins: nThreads.0 fGenerate.0
Shutdown: stopping node```Trying to `-reindex` now | 19:59:50 |
komodobridge | [discord] <dukeleto> @zatJUM ok, a fresh sync might be the only way to fix corrupt data, but -reindex might work. That error protects against corrupt local data | 20:02:01 |
komodobridge | [discord] <zatJUM> ```2020-01-04 20:01:54 Binding RPC on address 127.0.0.1 port 18031 failed.
2020-01-04 20:01:54 Unable to bind any endpoint for RPC server
2020-01-04 20:01:54 Error: Unable to start HTTP server. See debug log for details.
2020-01-04 20:01:54 Shutdown: In progress...
2020-01-04 20:01:54 StopRPC: waiting for async rpc workers to stop
2020-01-04 20:01:54 StopNode()
2020-01-04 20:01:54 scheduler thread interrupt
2020-01-04 20:01:54 Shutdown: done``` | 20:03:54 |
komodobridge | [discord] <zatJUM> because of RPC port? 🤔 | 20:04:25 |
komodobridge | [discord] <cipi> port 18031 is likely already in use
`sudo netstat -natp | grep 18031` | 20:07:14 |
komodobridge | [discord] <dukeleto> that means it's already running, usually | 20:07:15 |
komodobridge | [discord] <dukeleto> cipi types faster and has a nice command to check 😉 | 20:07:48 |
komodobridge | [discord] <zatJUM> Resync'ing from scratch | 20:09:26 |
komodobridge | [discord] <dukeleto> I am making 🍿 | 20:10:54 |
komodobridge | Redacted or Malformed Event | 20:14:29 |
komodobridge | [discord] <dukeleto> What I have learned recently is that `-reindex` fixes many sins, but some can only be fixed with a resync, such as some coredumps or `kill -9` issues where data is not written correctly | 20:16:35 |
komodobridge | Redacted or Malformed Event | 20:27:51 |
komodobridge | Redacted or Malformed Event | 20:38:08 |
komodobridge | [discord] <zatJUM> It's ok. All synchronized and running. Let's wait for the 1rst nota for 11 days on hush3 😫 | 20:51:20 |
komodobridge | [discord] <dukeleto> @zatJUM that is very good to hear! Now I know to recommend people a fresh sync if this ever happens. Most likely a previous coredump or `kill -9` got your datadir into an inconsistent state | 22:45:23 |
komodobridge | [discord] <dukeleto> thank you very much for reporting the bug, it's still very good to know things work for you. And what to suggest others who run into this | 22:46:02 |
5 Jan 2020 |
komodobridge | [discord] <zatJUM> <https://kmd.explorer.dexstats.info/> is down | 09:20:29 |
komodobridge | [discord] <ComputerGenie> @CHMEX 👆🏽 | 13:00:57 |
komodobridge | [discord] <CHMEX> Thanks back | 14:11:07 |
komodobridge | [discord] <eclips> how much is the bounty to break dpow ? | 17:40:59 |
komodobridge | [discord] <ComputerGenie> define "break" | 17:43:26 |
komodobridge | [discord] <eclips> reverse a transacton | 17:49:11 |
komodobridge | [discord] <eclips> either on kmd or ac | 17:49:32 |
komodobridge | [discord] <jl777c> how do you propose to do this? if you can achieve it on a notarized transaction, we can give a bounty for it | 17:57:19 |
komodobridge | [discord] <jl777c> transactions that are not notarized have no dPoW protection and is not covered | 17:57:39 |
komodobridge | [discord] <eclips> (it's a french dude asking elsewhere, just the messenger here) | 17:58:56 |
komodobridge | [discord] <jl777c> if they can reverse an already notarized tx, then it would definitely deserve a big bounty. but it would need to be responsibly disclosed | 18:01:34 |
| ismael joined the room. | 23:33:47 |
2 Feb 2020 |
| @carola:utwente.io joined the room. | 11:59:10 |
5 Feb 2020 |
| @carola:utwente.io left the room. | 14:25:45 |