Please login or register.
Login with username, password and session length

HEAT Forum

June 20, 2019, 11:31:28 AM
News: 2017-10-10 Heatledger 2.0 with Heatwallet 2.2.0 released! NOTE: Balance leasing and hard fork at block 777777 https://github.com/Heat-Ledger-Ltd/heatwallet/releases
Pages: [1]   Go Down

Author Topic: server didn't accept blocks  (Read 1422 times)

OrgiOrg wrote server didn't accept blocks on November 15, 2017, 09:32:02 PM
get an error in the debug, that block not accepted and there is a message at the start page of the wallet "Downloading blockchain last block height: 826504, time 2017-11-15 12:03:19"

Miner2525 wrote Re: server didn't accept blocks on November 16, 2017, 07:11:41 AM
Last Edit: November 16, 2017, 07:23:23 AM by Miner2525
I'm seeing this now too.  What does it mean?  I'm on 2.2.0.  Mining no longer works.






VonGraff wrote Re: server didn't accept blocks on November 17, 2017, 01:01:06 PM
Hi both, just sharing some suggestions here a I am not able to share a full solution:
- Questions: What version are you on (server must be 2.0.0, this is incorporated in the Desktop version of 2.2.0)? Are you running on Windows? Did it work as normal before?
- What you can Always try is to delete the blockchain folder in the heatledger folder (should be in appdata somewhere), and after that just start the server again and see whether it is able to get in sync normally. This happens to some very occasionally. Once in sync, you can start forging as usual

Anything you guys already tried yourself to get it to work again?

https://heatpool.org > Forging HEAT while it's HOT!
Miner2525 wrote Re: server didn't accept blocks on November 17, 2017, 01:43:36 PM
I nuked the blockchain dir and resynced and it works fine now.  Shrug.

VonGraff wrote Re: server didn't accept blocks on November 17, 2017, 02:56:50 PM
I nuked the blockchain dir and resynced and it works fine now.  Shrug.
Excellent, great to hear!

https://heatpool.org > Forging HEAT while it's HOT!
Miner2525 wrote Re: server didn't accept blocks on November 26, 2017, 05:37:47 AM
Last Edit: November 26, 2017, 05:47:47 AM by Miner2525
Problem is back.  So I nuked the blockchain dir again but it will not fully sync and is stuck in a perpetual rollback loop on block 683129:







This is getting annoying.  While forging seems to work at this point, who knows if its mining its own chain or not.  And would you please tell the devs to fix the damn latest line in the status window so I don't have to constantly mouse scroll up each and every time to see it.

So what to do at this point?  It takes too long to delete the blockchain dir just to get synced now -- if it even works.

Miner2525 wrote Re: server didn't accept blocks on November 26, 2017, 03:12:13 PM
Good news!  I was able to get it to sync past the stoppage by deleting just the replication directory (heat_db).

Warnersus wrote server didnt accept blocks on December 25, 2018, 08:08:34 AM
is there some information on some where from the server when its down and why?

JameBUYv wrote server didnt accept blocks on January 06, 2019, 03:34:35 AM
What you have to do is join anyway. Then it will say "starting server" the wait 30 seconds. And connect.

EJsElog wrote server didnt accept blocks on January 13, 2019, 03:35:28 PM
Does the Bizhat free hosting server accept PHP?  It wont read the PHP I have.


vCAP

________________________________________________
Sir Elton John is my favourite singer of the world. I’m very glad to present for you this setlist. Check Elton John Arizona this link to get your best ticket for the final Elton John tour.

TimothyHef wrote server didnt accept blocks on January 29, 2019, 09:55:14 PM
Thanks Guys for the server, is there anyway we could get rid of the kill-cam,  it stinks that someone can figure out where you are after you kill them

Pages: [1]   Go Up