Author Topic: Lompsa 0.4.10 Problem  (Read 5191 times)

warmach #15 on: January 05, 2016, 06:23:23 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
I made a mistake. I accidentally put out a version where the database versions don't match the previous update numbers.
During development I've added some tables which i then removed before releasing the whole thing.
Since I had a database file with the correct version numbers it worked for me and it skipped my attention.

The only solution is probably to just let it download. I'll make sure i pay closer attention next time.

sorry  :-\

I have this same problem again with the latest FIM server 0.6.0 download.  In fact, the log file show the exact same problem as with last release...

From FIM Server 0.6.0 logs

2016-01-05 17:19:16 FINE: Will apply sql:
CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
2016-01-05 17:19:16 SEVERE: Database error executing CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
java.lang.RuntimeException: Database error executing CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height)
   at nxt.db.DbVersion.apply(DbVersion.java:90)
   at nxt.NxtDbVersion.update(NxtDbVersion.java:738)
   at nxt.db.DbVersion.init(DbVersion.java:62)
   at nxt.db.BasicDb.init(BasicDb.java:136)
   at nxt.Db.init(Db.java:39)
   at nxt.Nxt$Init.<clinit>(Nxt.java:339)
   at nxt.Nxt.init(Nxt.java:313)
   at nxt.Nxt.main(Nxt.java:300)
Caused by: org.h2.jdbc.JdbcSQLException: Table "VOTE" not found; SQL statement:
CREATE INDEX IF NOT EXISTS vote_height_idx ON vote(height) [42102-176]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
   at org.h2.message.DbException.get(DbException.java:178)
   at org.h2.message.DbException.get(DbException.java:154)
   at org.h2.schema.Schema.getTableOrView(Schema.java:439)
   at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:61)
   at org.h2.command.CommandContainer.update(CommandContainer.java:79)
   at org.h2.command.Command.executeUpdate(Command.java:254)
   at org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:132)
   at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:117)
   at nxt.db.FilteredStatement.executeUpdate(FilteredStatement.java:45)
   at nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:256)
   at nxt.db.DbVersion.apply(DbVersion.java:81)
   ... 7 more
2016-01-05 17:19:16 INFO: Shutting down...
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Dirk Diggler #16 on: January 05, 2016, 07:22:01 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
What version FIMK did you use to download the first part of your blockchain?
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

warmach #17 on: January 05, 2016, 07:30:29 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
What version FIMK did you use to download the first part of your blockchain?

0.5.1  When I had my last problem, I just stayed with 0.5.1
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Dirk Diggler #18 on: January 05, 2016, 08:17:37 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
I see. Well i did pay close attention to see that it worked with 0.5.2.
To be honest i dont think we will do a new release for this.
Best advise i could give is delete blockchain and have it download again, should go much quicker now we have websocket p2p connectors.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

warmach #19 on: January 05, 2016, 09:42:46 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
I see. Well i did pay close attention to see that it worked with 0.5.2.
To be honest i dont think we will do a new release for this.
Best advise i could give is delete blockchain and have it download again, should go much quicker now we have websocket p2p connectors.

While I respect your decision, I might reconsider given this is a major upgrade and there is a hard fork in two weeks.  The upgrade path from 0.5.1 and earlier broke with 0.5.2  If there are others like me, they just didn't upgrade because it was a minor update and seemed like an unnecessary hassle. Instead, I waited for the next major version to fix the upgrade bug.  You are now expecting all full nodes to have to re-download the blockchain.  They either did it with the 0.5.2 version, or now with the 0.6.0 version.  As this is a major upgrade, I think the upgrade path from all previous versions should be working.

Now, I need to re-download 800+ MB, which might download faster with websockets but my Raspberry Pi takes a while to "process" each block.  As a pool operator, I must now decide to shuffle live and backup nodes while each one re-downloads/copies the blockchain or just take the pool front end offline while the live node updates.  It is a hassle either way.

Again, I am only offering my opinion and will respect the final decision.


Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Eliphaz Fimk #20 on: January 05, 2016, 11:15:35 PM

  • FIMKrypto coordinator
  • Administrator
  • *****
  • Posts: 825
    • View Profile
    • FIMKrypto
Now, I need to re-download 800+ MB
If possible, the association prefers to help the loyal FIMK supporters. Would it be of any help if we make the new blockchain available for download in a zip file?

warmach #21 on: January 06, 2016, 12:46:11 AM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
If possible, the association prefers to help the loyal FIMK supporters. Would it be of any help if we make the new blockchain available for download in a zip file?

That would surely help.  Thanks!
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Eliphaz Fimk #22 on: January 06, 2016, 12:13:43 PM

  • FIMKrypto coordinator
  • Administrator
  • *****
  • Posts: 825
    • View Profile
    • FIMKrypto
Blockchain of about 911k blocks (221MB packed):

http://fimk.fi/material/fim.h2.db.zip

warmach #23 on: January 06, 2016, 12:45:33 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
Blockchain of about 911k blocks (221MB packed):

http://fimk.fi/material/fim.h2.db.zip

Thanks again!  After 12 hours, my raspberry pi had only downloaded and processed up to block 293000 with an average transaction time of 0.144 seconds
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Dirk Diggler #24 on: January 06, 2016, 01:52:48 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Because of structural changes to the database it has to both verify and rescan the entire blockchain.
Thats likely causing the slowness, but 0.144 seconds is pretty damn slow even for a raspberry pi.
I'm on a pretty low end (slow) desktop myself just to make sure everything performs, even on my machine, but I guess yours is even slower than that.

You are of course pushing the envelope somewhat on such a minimal device.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

warmach #25 on: January 06, 2016, 10:14:59 PM

  • Senior Fimker
  • ***
  • Posts: 234
    • View Profile
Because of structural changes to the database it has to both verify and rescan the entire blockchain.
Thats likely causing the slowness, but 0.144 seconds is pretty damn slow even for a raspberry pi.
I'm on a pretty low end (slow) desktop myself just to make sure everything performs, even on my machine, but I guess yours is even slower than that.

You are of course pushing the envelope somewhat on such a minimal device.

Yeah, I am pushing it a bit. This pi is one of the first that came out. They have upped the specs a bit since then.

This is my dev machine. I figure if it can run on an original pi B then it can run on anything! Actually, once the block chain is fully up to date, it runs fine.
 I can run a full node and my pool scripts(with Apache, php, and MySQL) with out being too slow.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...