r/gridcoin•
Rodalli

Gridcoin Wallet Silent Crashes: what can be done?

This is getting out of hand. I can't seem to keep this application running for longer than 4 hours at a time. I've tried everything that's been suggested by other users, mostly things like limiting the number of maxconnections. Nothing helps. I've checked both the Windows application event log and the app's debug.log. No clues in either as to why the app is terminating itself. The debug.log itself indicates nothing is wrong... it just simply stops logging.

I know other people must be having this problem, as it seems to occur with every release, just in different frequency. For example, 3.5.9.9 would run for 24-48 hours before a silent crash. 3.6.x can't seem to make it past 4-5 hours. Has anyone been able to figure this out? Is there any verbose logging features I can enable to gather info on this?

Posted Sep 3, 2017, 4:04 PM UTC

813
csmVR•

I'm having issues now as well.

The PC it runs on was off for a couple of days. It's running v3.6.0.2. I had been having problems with it freezing up since upgrading the current version. Not crashing, or shutting down, it looked fine. But as soon as you moved the mouse over it, it froze up and went into "not responding" mode and had to be restarted. On restart, it seemed fine. But this repeated itself.

Already had these problems before the machine was off for a couple of days.

Last reward received was 29 August.

Started it on Friday (1 September). Left it running and open to stake. It ran overnight Friday OK. Was still responsive Saturday morning. Two payments came through on Saturday. One for around 30 GRC, one much smaller. Maybe 2 GRC or something. I think. I wish I'd taken a note of the amounts now because ...

But both sat as "unconfirmed" for several hours on Saturday. I went away overnight on Saturday. Left it running. Assuming it would confirm. Have come back today (early evening Sunday - UK time) and the two payments were both still unconfirmed. Which didn't seem right to me. They had well over 24 hours to confirm.

Restarted the wallet.

And the payments have vanished. No sign of them in the wallet at all. No sign of them on gridcoinstats.eu. They are just ..... gone.

Gridcoinstats shows my last payment as 4 and a bit days ago. Which is correct aginst my wallet. Maybe the larger (vanished) payment was only 20 GRC as it shows I'm due 25 DPoR + 2.5 Interest. And thats with a further 24 hours BOINCing since the ghost payments.

So what were the rogue transactions which subsequently vanished. Why didn't they ever confirm? And why does my wallet fail a lot of the time?

Stability and reliability recently have not been great. :(

PC is a pretty heavy duty gaming rig running Win 7 Pro 64. I had some stability issues with the waller when I first started running it. Killed off more gaming stuff running in the background and it was fine. Issues seem to re-appeared since the 3.6 updates.

*** UPDATE ***

Just noticed the link to the steemit article about V8 superblock issues.

Going to eat then read through that. Suspect it may provide some clues ....

3
Viggers619•

The "rogue" transactions likely occurred while you were on a forked chain. Once you got back onto the right chain those payments didn't exist because they didn't happen.

2
csmVR•

So it's re-synced on restart?

It looks OK. No out of sync messages. Plenty connections. Responsive. Showing block 1011943. Was about to start checking blockhashes and suchlike. Looks like it's been a bit of a messy update.

Diff is low? 3.075

Net weight: Almost 18m

My mag is low tho .... :(

1
Personthingman2•

Yeah, the diff has been low since V8. But it looks like you're on the main chain at the moment.

1
Viggers619•

Sounds like you're back on the right chain.

1
csmVR•

Yep. Looks like it's back on track. Staked overnight and seems to be confirmed OK this time.

Odd that I didn't get any out of sync messages if I'd ended up on the wrong chain? When that's happened before, I've got just such messages until I got it back on the main chain again.

1
csmVR•

Aaaaaaand back to "not responding" again. :(

1
Jimmy-1•

My wallet crashes often. I'm lucky if I can get it to create an automatic back-up (every ~900 blocks). The last time it ran for 900 blocks without crashing was June.

It runs on a modern Windows 10 machine and the crashes that I've bothered to investigate corresponded to a .NET Runtime Error. I've been told to delete the Neural Network folder, which seemed to help for a very short amount of time.

Some users report zero problems whatsoever, but others, like you and me, experience some issues. Obviously there are still a few bugs to exterminate.

2
mmalluck•

My wallet was getting crash-happy with the update to 3.5.9.9 and didn't improve with 3.6.x.

The only thing that's improved things is a complete uninstall and reinstall. Seems more stable now. I had to download the entire block chain again too because my copy had become corrupt at some point.

2
kovah44•

While mine doesn't fully crash I've been getting the "Unable to send beacon, client is offline!" message every few hours and have to restart my client to make it go away ever since 3.6.x.x. The client itself doesn't actually show offline and I've been too lazy to check the logs but I'll do that next time I get the message.

I also just moved my wallet to my laptop from my gaming PC as it eats sooooo much memory and I had to close it just to run a game. Now the auto-unlock for staking isn't working but I suspect that's something I've mis-configured.

Sorry this isn't an actual help for your situation. I'm no longer on IRC but maybe try asking there? Freenode IRC, #gridcoin(registration required) or #gridcoin-help(no reg req)

[EDIT]: "Unable To Send Beacon! Unlock Wallet!" is the actual message I get after a few hours of running. Wallet stays unlocked for staking already. Set it to full unlocked and I'm still seeing that message. Beacon was sent back in March so not sure why I'm even seeing that message. Logs don't show anything. I also get the occasional "Not Responding" freeze as mentioned by another poster in this thread.

1
AnglebertFunkyDinx•

Auto unlock must be reset in the gridcoinresearch.conf for different devices, you must go to execute encrypt <your pass here>.

I actually can't get my PC to use any more than about 900MB RAM SO I don't know why you would be having troubles, I actually told Gridcoin to use more RAM.

1
kovah44•

I did that @ redid the encrypt and pasted it to the .conf, still not working. Admittedly haven't messed around with it more than the initial try.

I wasn't having troubles, per se, was just utilizing a lot of memory which made certain games crash if I left it open on my gaming PC. Moving it to the lappy makes more sense in my case. I only really use the laptop once a week but that use shouldn't be bothered by the 650'ish RAM that GRC uses so I should be able to keep it running 24/7 now.

1
AnglebertFunkyDinx•

some things you can try to reduce RAM is to limit connections and reduce the block index load.

If you get more than 8 connections, you can try one of several things. If you don't want to serve the blockchain to other nodes you can set listen=0 in the conf, this will limit you to the 8 outgoing connections. If you do want to allow incoming but want less than you are getting set listen=1 and also set maxconnectioncount= to any number less than 128 (it's default value), setting to less than 8 isn't recommended. If you are running two nodes and want one to connect to the rest of the network, and the other (ie your laptop) just to make one connection to that node, remove all the addnodes and replace with connect=192.168.x.x and your Laptop will make just one connection to your other node on your LAN, but if that node loses connection or goes on a bad fork, so will your laptop of course.

The other setting is dbcache= it defaults to 25MB but I think you can reduce that to a minimum of 4 but bear in mind that only gives you 21MB freed up and means your wallet has to write to and from risk much more often. I increase this on nodes with plenty of RAM.

It's probably wise to keep a backup of your current .conf file before you start messing with any of this.

1