Fatal error

[bitpop]

I'm getting a fatal error. Qt just says fatal error and crashes. I recently updated to 0.19.0.1. Didn't happen before then. Ran for a day fine.

[jackg]

You running Windows or Linux? Have you updated anything else recently either and do you have an AV?

[BitMaxz]

It seems that your wallet is corrupted during update.

Can you try to restart the PC then try to open it again it might be fixed your issue.

If it doesn't work try to uninstall and install it again and test.

[DaveF]

Looking at this in your log file:

2020-01-19T23:27:07Z ERROR: ReadBlockFromDisk: Errors in block header at FlatFilePos(nFile=1932, nPos=8)
2020-01-19T23:27:07Z *** Failed to read block
2020-01-19T23:27:07Z Error: A fatal internal error occurred, see debug.log for details

It looks like your blocks are corrupted (not your wallet)
Try to start bitcoin-qt  with the -reindex command line option.
Depending on your hardware it can take a while.

Might be a fluke, might be your drive is going.

You have a backup of your wallet.dat file correct?

-Dave

[bitpop]

I'll try those. I'm on Windows 7. I don't see any disk errors.

Reindex seems to be running.

[bitpop]

Also how do I get rid of these, there's thousands. I don't have tor or onion in my configuration.


2020-01-20T00:17:38Z tor: Requesting protocol info failed
2020-01-20T00:17:40Z tor: Requesting protocol info failed
2020-01-20T00:17:41Z tor: Requesting protocol info failed

[tranthidung]

I'll try those. I'm on Windows 7. I don't see any disk errors.

Reindex seems to be running.

Sometimes, suddenly power-lost will result in that corrupt issue when you restart your computer. Did it what really happen with your computer before that fatal error occured with your wallet?

[posi]

I'll try those. I'm on Windows 7. I don't see any disk errors.

Reindex seems to be running.

If you still have the thousand of "2020-01-20T00:17:41Z tor: Requesting protocol info failed" and the fatal error popup messages i will advised you to upgrade your system windows because Microsoft sent out notification last year about Window 7 and this was the message they sent on 14th of this month as showing in the below pic.
I think this could be the source of the problem you're experiencing.

[DaveF]

No, Win 7 going away would not cause any of the issues.
Keeping a wallet on an unsupported OS might have some security implications down the road but as of now its just as updated as any OS.

Did the reindex finish OK?

The tor issue is strange if you do not it configured anywhere.
Could you have set it up for an earlier version and forgotten and it's just been copied from update to update?

Other then that I have no idea.

-Dave

[bitpop]

No, Win 7 going away would not cause any of the issues.
Keeping a wallet on an unsupported OS might have some security implications down the road but as of now its just as updated as any OS.

Did the reindex finish OK?

The tor issue is strange if you do not it configured anywhere.
Could you have set it up for an earlier version and forgotten and it's just been copied from update to update?

Other then that I have no idea.

-Dave

Reindex is still going well. Yeah i had tor before but it's out of the config. Not sure where it's getting it from, maybe registry.

Maybe i need to explicitly disable tor. Anyone know the config file options?

[nc50lc]

Maybe i need to explicitly disable tor. Anyone know the config file options?

Try listenonion=0 the default is '1' enabled.

2020-01-19T23:25:31Z Ignoring unknown configuration value rpctimeout

Also, change your invalid config "rpctimeout" to "rpcservertimeout" in order to remove the very first error in your debug log.

[jackg]

Keep your loyalty with Windows 7, it was one of the best... If you have AV that can still support it then you should be fine to keep running ir and not much can go wrong if you don't have large amounts on the wallet (and if you do you can use an spv client or a hardware wallet on another machine/os).

Tor threading is normally used even if you don't have tor enabled afaik also.

[bitpop]

Keep your loyalty with Windows 7, it was one of the best... If you have AV that can still support it then you should be fine to keep running ir and not much can go wrong if you don't have large amounts on the wallet (and if you do you can use an spv client or a hardware wallet on another machine/os).

Yeah windows 7 was the pinnacle

[DaveF]

No, Win 7 going away would not cause any of the issues.
Keeping a wallet on an unsupported OS might have some security implications down the road but as of now its just as updated as any OS.

Did the reindex finish OK?

The tor issue is strange if you do not it configured anywhere.
Could you have set it up for an earlier version and forgotten and it's just been copied from update to update?

Other then that I have no idea.

-Dave

Reindex is still going well. Yeah i had tor before but it's out of the config. Not sure where it's getting it from, maybe registry.

Maybe i need to explicitly disable tor. Anyone know the config file options?

As far as I know it stores nothing in the registry.

Try what nc50lc said to change in your conf and when the reindex is finished rename the peers.dat to peers.old
I have seen my nodes try to connect to machines that I no longer have on the network because it saw one of them 6 months ago and for some reason it still thinks it's there.
As far as I know (And I admit I know little about it) that is the only place outside of DNS seed nodes it looks for other nodes.
I opened an issue on git years ago about it but they closed it so I let the issue drop.

-Dave

[DaveF]

Try what nc50lc said to change in your conf and when the reindex is finished rename the peers.dat to peers.old
I have seen my nodes try to connect to machines that I no longer have on the network because it saw one of them 6 months ago and for some reason it still thinks it's there.
As far as I know (And I admit I know little about it) that is the only place outside of DNS seed nodes it looks for other nodes.
I opened an issue on git years ago about it but they closed it so I let the issue drop.

-Dave

Do you mean Bitcoin Core trying connect to other node with .onion domain (from peers.dat) even though Bitcoin Core isn't configured to use Tor?

Yep. From what happened to me.
Network 1= 192.168.1.x
Network 2 = Cable Public IP
Network 3 = 192.168.2.x
Network 4 = FiOS Public IP

All in the same physical location with some routing between the 2 privates through a sonic wall.

FiOS and the 192.168.2.x stack went away.
The front end sonic wall was replaced
And in my logs I still saw the nodes on cable / 192.168.1.x trying to reach the 192.168.2.x and the FiOS public.

Everyone said I had something in my .conf file or someplace else. I had at that point NO conf file. When I got rid of the peers.dat it all went away.
Everyone said I was wrong, I threw my hands up and walked away. So, I was just wondering if yeah, if it thought that site.onion was still good for some reason it was trying to reach it. Other then that I have no idea on the errors.

-Dave

[HCP]

As far as I know it stores nothing in the registry.

It does...

Go checkout: HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt

There are a couple of "proxy" and "tor" related settings there... although I believe they should be reflected in the "Settings -> Options -> Network" tab within the GUI.

[DaveF]

As far as I know it stores nothing in the registry.

It does...

Go checkout: HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt

There are a couple of "proxy" and "tor" related settings there... although I believe they should be reflected in the "Settings -> Options -> Network" tab within the GUI.

Sorry, poorly worded.
As far as I knew it stored nothing about networking or peers in the registry. I thought it was all QT / GUI settings.
My bad.

Either way I still do not think it's the issue here.

-Dave
 

[bitpop]

Reindex completed and it seems to be working fine.

listenonion=0 seems to have fixed the tor warnings

Thanks everyone