Author Topic: Problems with the latest release.  (Read 2250 times)

gaianhuuto on: January 20, 2016, 04:26:37 PM

  • Grand Fimker
  • ****
  • Posts: 466
    • View Profile
Hello. Just downloaded the latest and noticed that the database won't download. It disconnects after 719 block, says my peer is blacklisted...
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

Dirk Diggler #1 on: January 20, 2016, 04:28:30 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Disconnects from 1 peer probably. Not from the network.
Just let it sit and chain will be downloaded.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

gaianhuuto #2 on: January 20, 2016, 04:56:11 PM

  • Grand Fimker
  • ****
  • Posts: 466
    • View Profile
I had it 'sit' for half an hour... just keeps on disconnecting.

TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

gaianhuuto #3 on: January 20, 2016, 05:20:08 PM

  • Grand Fimker
  • ****
  • Posts: 466
    • View Profile
I downloaded the blockchain uploaded by Eliphaz. It downloads nicely to block 926879 and then the disconnecting starts... So no luck here...
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

Dirk Diggler #4 on: January 20, 2016, 05:20:38 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
I see... Seems one nasty transaction slipped through the cracks.
Seeing it here to.
Working on a fix, will release 0.6.2 shortly.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

gaianhuuto #5 on: January 20, 2016, 05:24:32 PM

  • Grand Fimker
  • ****
  • Posts: 466
    • View Profile
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

Dirk Diggler #6 on: January 20, 2016, 09:52:22 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Still working on a fix. I'm sure if given enough time the network will sort itself out.
The transaction causing the error will eventually time out.
But to be sure i'm running diagnostics, which take a long time.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

gaianhuuto #7 on: January 21, 2016, 07:55:22 AM

  • Grand Fimker
  • ****
  • Posts: 466
    • View Profile
Still working on a fix. I'm sure if given enough time the network will sort itself out.
The transaction causing the error will eventually time out.
But to be sure i'm running diagnostics, which take a long time.

Good mornin'! Got my client fixed by using the old one and Eliphaz uploaded db. It downloaded the rest of the blockchain without major issues. Then I just copied it to the latest clients db-folder. Everything is w(f)orking well now ^^ Maybe it is time to keep some backup db's on my comp from now on :)
TurnTrips.poker - Ässät pöytään ja kryptovaluutat jakoon.

Dirk Diggler #8 on: January 21, 2016, 09:20:28 AM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
Good mornin'! Got my client fixed by using the old one and Eliphaz uploaded db. It downloaded the rest of the blockchain without major issues. Then I just copied it to the latest clients db-folder. Everything is w(f)orking well now ^^ Maybe it is time to keep some backup db's on my comp from now on :)

Morning, thats great news to wake up to.
Will still put out a fixed version, hopefully later today.
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

warmach #9 on: January 21, 2016, 02:55:32 PM

  • Senior Fimker
  • ***
  • Posts: 227
    • View Profile
I see... Seems one nasty transaction slipped through the cracks.
Seeing it here to.
Working on a fix, will release 0.6.2 shortly.

Does this have to do with block 15122779678927210415 

When I hit API getBlock I get a java buffer underflow exception.  It happens on all three of my servers.
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

Dirk Diggler #10 on: January 21, 2016, 09:26:31 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
When I hit API getBlock I get a java buffer underflow exception.  It happens on all three of my servers.

I see.. Somehow a transaction got through that was of the old byte format (pre private assets).
Probably everyone else is blacklisting or disconnecting from your servers the second they receive that block.

Pretty sure your servers are on a fork that will not survive.

I've just completed scanning + validating the blockchain for the 6th time to make sure everything works. We will release a new server version tomorrow. When you run that version a scan + validation will be done and the affected block will be lost.

You could try and delete one of your blockchains and have it load again. Because of the way we did the hard fork (through aliases) it could make a difference that the alias was set a longer while ago now.

Otherwise wait a day, we will release 0.6.2 tomorrow (can't do it right now, a scan + validate is running for the 7th time).
FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog

Dirk Diggler #11 on: January 22, 2016, 02:17:10 PM

  • FIMK Staff
  • *****
  • Posts: 486
    • View Profile
    • Krypto Fin ry
We're adding hard fork helper functionality to the server core, the crap we are now experiencing has annoyed us long enough and has to end now.

From this coming release we will do things slightly different which will lead to faster iteration times and more streamlined hard forks over our beloved decentralized peer 2 peer network.

Hard forks are unpleasant but inevitable with a young and fast developing crypto currency like FIMK. We have tons of ideas for new features but are always severely limited by how difficult it is to get our software installed on all peers out there.

There already is a sophisticated database versioning mechanism in FIMK core which basically allows anyone running any version to simply install a newer version and have the complete blockchain/db structure dynamically updated to that newest version. With this mechanism already in place requiring peers to periodically update their software is in my view very reasonable.

We all want FIMK to develop further don't we?



Starting with this coming release when you start FIMK a check is made if your version is either OUTDATED is being PHASED OUT or has an UPDATE AVAILABLE. This version information is distributed over the blockchain through aliases controlled by the non profit association who makes FIMK - Krypto Fin ry - http://fimk.fi.

These three levels of software version status will allow us to quickly move through new versions (and through hard forks).

We will still announce new versions on the forum and our website but you no longer have to track that, the software will from now on warn you if you need to update. These warnings are clearly visible from either the console logs or from the desktop client, these warnings contain details on how to update.

No more forks after updates.

To prevent forking the network after updates peers will from now on actively start blacklisting nodes that run a version up or below the current OUTDATED version.

To prevent peers from not noticing that their version has expired which will undoubtedly put them on either a fork or disconnect them from the network (since no one will connect to them) we will actively shutdown the FIMK server and print a big fat notification to the logs that your version is outdated and that you need to update.

This way third party software which builds on FIMK (currency exchanges, merchants etc) will immediately be able to notify their operators through the FIMK log what has happened and that they should update their versions.

How hard is updating?

Now for the million dollar question, how difficult is it to update? How bad is it what we would be putting all you users out there through.

Luckily not difficult at all. I had something like this in mind for an update notification (you will find this in the FIMK console log).
Instructions apply to a Linux server, probably most servers running FIMK are Linux servers.


############################################################################
## WARNING!!
##
## YOU ARE RUNNING OUTDATED SOFTWARE
## FOLLOW INSTRUCTIONS BELOW TO UPDATE
##
## YOUR CURRENT VERSION IS 0.6.2
## THE LATEST VERSION IS 0.7.0
############################################################################
##
## FOR LINUX USERS RUN THE FOLLOWING COMMAND
## (requires `curl` and `zip` packages to be installed)
##
## $ FIMK_VERSION=0.7.0 sh update_fimk
##
## USERS ON OTHER PLATFORMS SHOULD DOWNLOAD THEIR UPDATE HERE..
##
## https://github.com/fimkrypto/fimk/releases/download/v0.7.0/fim-0.7.0.zip
##
############################################################################


Hopefully this way we can finally start to streamline the whole versioning and more important update process which will lead to a more stable and more frequently updated network.

Posted this same message to our blog: http://fimkchat.com/2016/01/solving-the-hard-fork-dilemma/

Dirk.

FIMK Developer | GPG fingerprint: CEF2 7C39 43BE 6800 504E  71BC 7E87 A7B0 AC34 E2D5 | mofowallet.com | blog


warmach #13 on: January 22, 2016, 02:51:50 PM

  • Senior Fimker
  • ***
  • Posts: 227
    • View Profile
I look forward to this simpler update pathway.   :cheers:
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...

warmach #14 on: January 22, 2016, 02:52:24 PM

  • Senior Fimker
  • ***
  • Posts: 227
    • View Profile
Warmach's Forging Pool
http://fim.warmach.info/pool/
May the forge be with you...