How many peers am I connect to?

[rds]

@damncourier,

wow, thanks, never saw that button. Chrome browser showed last link at the bottom as "contacts". I de zoomed to 80% and bang, peer. blocks, alais, and messages appeared.

Thanks again, I'm connected to 26 peers, nice.

[Tate A]

@haitch When will well known peers like burst.ninja, pool.burstcoin.biz, be updated to 1.2.8?

[LithStud]

@rds that sidebar thingamajing is a bane of my life been trying to make it scrollable if doesnt fit into window. But whatever CSS rule i used it just resist me ;) might as well try to rewrite that part of wallet and see if it helps. Anyway good thing you reminded about it. Going to put it on issue list so its not forgoten again.

[haitch]

@Tate-A Ninja I can't speak for, but my pools will be updated over the next few days when the wallet has shown to be stable in the other instances I'm running.

[LithStud]

@haitch a very nice thing about new client at least for me was its slim usage of RAM - stabilized at about 250MB for me and that is huge improvement since last version, also its impact on my network seems to be better optimized (might be just a perceived thing tho)

[haitch]

@LithStud Good to know - I'll post back at what my RAM usage is like

[LithStud]

@haitch daWallet had similar numbers (slighly larger but still under 500)

[nixxda]

wow, below 80Mb RAM usage on the windows AIO Wallet!!

I'm having a terrible time with syncing today however! Both my windows and linux wallets are constantly getting stuck!
always with the same type of error

2017-02-22 16:00:58 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 80053366 current time is 80053258, previous block timestamp is 80052934

nothing that I do seems to help!-/ "poping of" blocks and restarting, blacklisting all 1.2.2 and 1.2.3 peers and replacing the whole db!
Anybody else having this problem today?

[haitch]

@nixxda Check your PC clock is correct, the error looks like the wallet thinks it's getting blocks from the future.

[damncourier]

@nixxda i got that after upgrading- the wallet seems to stop updating to new blocks afterwards (pop off didn't help).

i bumped up logging level to FINE and got an error to effect of new block broadcast being ignored because it is already in block cache (sorry i didn't save the log). tracked the error down in the code and there have been some recent commits near it relating to cleaning block cache. messed with the code a bit but no luck with a few attempts to revert.

ended up removing forward on peer port (8123 default) so new blocks are pulled instead of pushed.

and yes i had synced to ntp.

[nixxda]

@haitch could be! something weird is going on with my time syncs!-/ but I'm running "dimenson4" on win and "chrony" on linux

@damncourier by setting "nxt.shareMyAddress=false" you mean? I

[LithStud]

@nixxda that error is expected. Its actually a debug message to show why block wasnt accepted ;) there os a recompiled version with that debug dissabled ;)

[damncourier]

@nixxda nah on the router, had previously added the forward to allow incoming connection (on which other wallets are able to push block, transaction, etc) which i removed, so my wallet gets new blocks by connecting to peers and requesting them.

try changing your log level and see if you get errors following that one.
in conf/logging-default.properties change last line to "java.util.logging.ConsoleHandler.level = FINE" and restart

[luxe]

Moved to Help&Support

[nixxda]

@damncourier waiting and watching!-) seems like the wallet is not "really" stuck! I get the new blocks after a restart.

@LithStud A recompiled version? where? on linux I've been using "compile.sh" straight out of your git. But I get the same type of error on linux and win!? 2 machines different ports

[LithStud]

@nixxda ahh i havent had a chance to sync my fork with official repo ;) and it seems changes are not published there yet, so if @luxe could point me what to change i can update it on my fork manually

[luxe]

@LithStud what changes are not published?

[LithStud]

@luxe i think you mentioned that you recompiled so cmd client doesnt show the debug message, unless i am mistaking it?

[luxe]

@LithStud ah ok, but that does not change any bahavior, it's just less log details ...
https://forums.burst-team.us/topic/4019/new-wallet-version-1-2-8/14

I just removed the bold part (, e) ... Logger.logMessage("Block not accepted", e);

[LithStud]

@luxe look up at @nixxda post ;) since i cant explain how to compile it so it shows less logs :) i thuoght its some kind of edit that would be visible on repo but obviously i am wrong :D

just noticed the comment about e :D