Quote from: lfloorwalker on November 09, 2016, 01:12:31 AM

agreed, i have a theory that because there wasn't too many full nodes that many of them got onto the "wrong" chain, this caused stability problems for all main full nodes. Please correct me if I am off here.
I was thinking through and the only way to improve this is to have more full nodes so the probability after each fork of this happening decreases.
I realized yesterday after doing TXID certifications for our solar plant reports, that we were on the wrong fork (possibly for 2 days). So all of our wallets have been repaired now.
The main way to fix it was to "reload blockchain". In general reliability for us is (1. Windows, 2. MAC, 3. Linux...) and I am not sure of the reasons for differences in reliability across platforms.
Has anyone got a stable 2.1.6 Linux full node synced? I am very far behind on block count on ours.

Quote from: corather on November 07, 2016, 07:05:57 PM

Looks like the wallet occasionally reports the wrong amount of coins available also. After a rescan it works itself out. We need some serious bugs fixes.

Hey, Im going to try and run a fullnode for the first time as I think I have a low power solution Im prepared to leave on 24/7, do I just have to add 'listen=1' to my config file? EDIT; What ports to forward?