"Block not accepted" - blockchain not updating

My blockchain is not updating. I’ve read through the threads here and elsewhere without finding a fix. The console continually give the message below. Any help would be much appreciated. More details below the message.

[SEVERE] 2018-01-06 19:16:03 nxt.BlockchainProcessorImpl - Block not accepted
nxt.BlockchainProcessor$BlockNotAcceptedException: Previous block hash doesn’t match
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:922)
at nxt.BlockchainProcessorImpl.access$700(BlockchainProcessorImpl.java:30)
at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:215)
at nxt.util.ThreadPool.lambda$start$0(ThreadPool.java:91)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

my setup: windows 10, Qbundle v1.8, Burstcoin Wallet v1.3.6cg

previous (unsucessful) troubleshooting attempts:

  • restarting computer and/or reinstalling Qbundle / Wallet
  • stopping and restarting wallet
  • had same issues with previous Qbundle versions (starting with v1.5 or v1.6)
  • switching to Portable MariaDB (same issue with H2)
  • importing blockchain from various online locations (blockchains had no trouble importing, but there would be no further blockchain updates)
  • playing with windows firewall settings
  • rollback / popoff chain (multiple times)

I’d really appreciate any advice that anyone has. I’ve spent an embarrassing amount of hours trying to fix this issue over the past week.

Just throwing a suggestion out there as I don’t know what this particular error means:

You have made sure your time is synced up? Very important with Burst.

Just follow the time synchronization part here, the other stuff is for an older version of Burst.

Thanks for the quick reply. I haven’t seen that tutorial before.

Unfortunately the same set of messages is still appearing in the console. I tried removing some blocks and stopping and starting the wallet with the net sync, but still the same result.

What you could try is the rollback chain option under menu Wallet->Advanced. Use default option when asked.

Thanks. I have tried this procedure multiple times without success.

Then the database cannot be recovered. You should delete the contents of burst_db folder. and restart wallet.

1 Like

Apologies if I’m misunderstanding something here. I’ve deleted the contents of burst_db folder, but the (partial) blockchain still shows up in my wallet because it is also saved in MariaDB. Which database do you recommend? Which download source do you recommend for the blockchain? If you recommend MariaDB, how can I delete the existing (partial) blockchain so that I can download a fresh one?

Ah, sorry i thought you were using H2. i did not read your full message. shame on me.
If you have a MariaDB database that has gone stuck and cannot roll back you have 3 options.

  1. Do a database import from the repositorys ( not recommended in first place)

  2. If you are using the MariaDB downloaded from Qbundle you can stop wallet and delete MariaDB folder. After this you need to change database back to h2 and then back to maria again to make Qbundle download MariaDB

  3. If you know how to connect and work with databases you can drop current burstwallet database and create a new one using utf8mb4 and unicode_ci

1 Like

Ah, I thought it was recommended to import from a recent repository to reduce the time needed to get the blockchain up to date.

I chose your option #2. (Just to be clear, this is the “Portable MariaDB,” not “Own MariaDB / Mysql,” correct?) After enacting this option, the blockchain started downloading from scratch. The black height grew to 384 before it stopped growing. A new set of error messages is given in the console, which are pasted below.

[INFO] 2018-01-07 13:41:38 nxt.BlockchainProcessorImpl - Last block height: 0
[SEVERE] 2018-01-07 13:41:38 nxt.http.API - Failed to start API server
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.http.API$1.run(API.java:144)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Exception in thread “Thread-5” java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at nxt.http.API$1.run(API.java:148)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.http.API$1.run(API.java:144)
… 1 more
[SEVERE] 2018-01-07 13:41:38 nxt.peer.Peers - Failed to start peer networking server
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.peer.Peers$Init$1.run(Peers.java:290)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Exception in thread “Thread-4” java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at nxt.peer.Peers$Init$1.run(Peers.java:294)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.peer.Peers$Init$1.run(Peers.java:290)
… 1 more
[SEVERE] 2018-01-07 13:41:38 nxt.Nxt - Errors running startup tasks:
java.net.BindException: Address already in use: bind
java.net.BindException: Address already in use: bind
java.lang.RuntimeException: Errors running startup tasks:
java.net.BindException: Address already in use: bind
java.net.BindException: Address already in use: bind
at nxt.util.ThreadPool.runAll(ThreadPool.java:169)
at nxt.util.ThreadPool.start(ThreadPool.java:74)
at nxt.Nxt$Init.(Nxt.java:286)
at nxt.Nxt.init(Nxt.java:202)
at nxt.Nxt.main(Nxt.java:193)
[SEVERE] 2018-01-07 13:41:38 nxt.peer.Peers - Failed to start peer networking server
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.peer.Peers$Init$1.run(Peers.java:290)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Exception in thread “Thread-4” java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at nxt.peer.Peers$Init$1.run(Peers.java:294)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.peer.Peers$Init$1.run(Peers.java:290)
… 1 more
[SEVERE] 2018-01-07 13:41:38 nxt.http.API - Failed to start API server
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.http.API$1.run(API.java:144)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Exception in thread “Thread-5” java.lang.RuntimeException: java.net.BindException: Address already in use: bind
at nxt.http.API$1.run(API.java:148)
at nxt.util.ThreadPool$2.run(ThreadPool.java:150)
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at nxt.http.API$1.run(API.java:144)
… 1 more
[SEVERE] 2018-01-07 13:41:38 nxt.Nxt - Errors running startup tasks:
java.net.BindException: Address already in use: bind
java.net.BindException: Address already in use: bind
java.lang.RuntimeException: Errors running startup tasks:
java.net.BindException: Address already in use: bind
java.net.BindException: Address already in use: bind
at nxt.util.ThreadPool.runAll(ThreadPool.java:169)
at nxt.util.ThreadPool.start(ThreadPool.java:74)
at nxt.Nxt$Init.(Nxt.java:286)
at nxt.Nxt.init(Nxt.java:202)
at nxt.Nxt.main(Nxt.java:193)
[INFO] 2018-01-07 13:41:39 nxt.OCLPoC - OCL max items: 768

You have some software that collides with the API server of the wallet.
Maybe another miner or similar?
I suggest you either reconfigure that software or change port of local wallet under settings.

Thanks for your continued help.

I’m not running any other mining software. The other process that is using that port is a java.exe process that is only present when the Burst Wallet software is running. Changing the port doesn’t change the behavior.

Here is another tidbit of info that might be useful in troubleshooting: When I first open the Burst Wallet software, the block height grows by a small number (10’s to 100 or so). Then the block height will not grow any longer until I stop the wallet, shutdown the software, and reopen the software again.

The Burst Wallet also takes several minutes to stop. I don’t know if that is normal or not.

When using H2 db it takes several minutes to stop yes, This is because the db needs to shutdown clean. If you however switch to mariaDB it will be much faster to start and stop

1 Like

Hmm, I’m using MariaDB and it takes a long time to stop.

More importantly, the only process that is using port 8125 is process created by the Qbundle. How can I stop it from interfering with itself?

Qbundle itself does not open ports. Only the core wallet does. By your descriptions it seems like you are running as a unpriviledged user. That is usualy fine but some functions in Qbundle will be limited backend. In this case the Sanitycheck that looks for other corewallet instances.If you are running MariaDB then it should not take several minutes to stop the wallet if not the computer is very old.

This line:
Caused by: java.net.BindException: Address already in use: bind

Indicates that either another instance of the wallet is running or that some other program is using that port. Maybe a restart of computer will solve your issues.

1 Like

Possibly stupid question: How do I run as a user with appropriate privileges? I tried running the burst wallet as an administrator in Windows 10, but the results are the same. I’ve also tried restarting the computer several times with the same results.

Downloading Qbundle v1.9 has not solved this issue. The blockchain gets downloaded for a minute or so, and then the download stops. There is no error or warning message that I’m aware of.

Try disable openCL (gpu acceleration) in settings. and restart wallet.

1 Like

You have done the impossible - the blockchain is now continuously downloading to my local machine! Disabling openCL did the trick.

Thanks for your persistence and advice. I appreciate being able to get more involved with burst coin.

Thanks again.

1 Like