Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 32. (Read 284539 times)

Quoted for new page.

Fantastic, thanks for that.  Sadly I won't have time to test until Thursday evening (UK time).  I'll post how it goes.  Good luck with the network monitoring.

Anyone bootstraping let me know when you get in sync or have issues. Would be nice to catch them all now.

0.30.19.3 Windows

Let me know if you have issues, i managed to sync half way and also test a bootstrap. I highly encourage bootstraping, sync times are way faster from start but not as efficient as a bootstrap.

Need to get back to monitoring the network, which is a bit hard now because i have to use command line for each block

Windows for wallet.  Linux VPS for nodes.

Are you on windows or linux?

Great news.  Can't wait to get my hands dirty and write some guides as I learn.

Hi Bitcc,
great news for the moment.
I will try and report later on.

lg t.

Report:

DB corrrption is a result of running out of file descriptors , very subtle issue  -- resolved.

Failure to sync with 40 block warning :- restart client and use rpc command " reconsiderblock XXXXXX"  where XXXXXX is the last accepted block's hash --resolved

Cannot Fresh sync -- resolved

Questions and reported issues:

I have used pngcrush, will report on results once binaries are built.

mining is a trial and error effort, the miner searches for a suitable key in miningkeys.dat, generates a hash and tests to see if it will be accepted. As such all keys will be used. Even if you put a thousand valid keys, they would all eventually be used.

Bittrex has been on hold at my request so I could take a careful look at the issues we had.

Users who have difficulty reading/understanding English , please speak up, we can get you translations.


Other Changes

1) git repo renamed

2) version 0.30.19.3

Today: 

Within an hour i'll mine the first block and get the network moving again.
Within an hour windows will be up (unless something happens)

GUI fixes will start being made

Later

More progress 

The annoying libpng warning can be dealt with by
passing all the png's used by the graphical wallet
thru a program called pngcrush.

http://stackoverflow.com/questions/22745076/libpng-warning-iccp-known-incorrect-srgb-profile
 

Seems like OS repeatedly closes the connection when reading response from a web server. I had the similar issue, something is up with your router / firewall settings. If you have any firewalls running you may wish to turn them off.

going to be doing a test in a few hours.

2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_1_client_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_2_client_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_1_server_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve TLSv1_2_server_method
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_select_next_proto
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
2015-12-15 11:58:59 GUI: QSslSocket: cannot resolve SSL_get0_next_proto_negotiated
2015-12-15 11:59:00 receive version message: /Section32:0.30.19.1/: version 70014, blocks=266996, us=73.153.116.122:8877, peer=1, blockchain=Bitcredit
2015-12-15 11:59:00 Added time data, samples 2, offset -1439 (-23 minutes)
2015-12-15 11:59:00 Misbehaving: 188.193.111.112:49710 (0 -> 1)
2015-12-15 11:59:00 ProcessMessage(version, 132 bytes) FAILED peer=1
2015-12-15 11:59:01 GUI: PaymentServer::LoadRootCAs : Loaded  48  root certificates
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-12-15 11:59:01 GUI: libpng warning: iCCP: known incorrect sRGB profile

my log is quickly becoming gigs of nothing but  GUI: libpng warning: iCCP: known incorrect sRGB profile
my windows 10 machine does not make outgoing connection after this...
socket recv error An established connection was aborted by the software in your host machine.  (10053)
but no connection is attempted outside the program...

Likewise!


Perhaps...


In case you guys are interested in joining the Official BCR Slack channel:

lol, so this is where your hiding :-p

Fancy seeing you here!   

I'm a tad busy at the moment but in a couple of days I'll continue testing the wallet.

Howdy stonehedge, tombcoin, and CHAOSiTEC! Good to see you guys around here.

dev is working on the blockchain errors, expect new wallet at some point

Set up a fresh installed headless Linux with latest git.
New version of BCR does only connect to: 176.56.238.121:8877
with the result:
connect() to 176.56.238.121:8877 failed after select(): Connection refused (111)
socket recv error Connection reset by peer (104)

I didn´t set anything additional in bitcredit.conf.
Only rpcuser and rpcpassword which is needed for daemon to run.

Is this a wanted config?

lg t.

I got the same problems with my BNs:

^{2015-12-14 11:25:38 UpdateTip: new best=000eec7c4c1fd2c1d488dc74d7ac80fa8829a41d3c02c01dae8ac2c87e11970a  height=266996  log2_work=35.947744  tx=276481  date=2015-12-13 20:31:37 progress=0.991034  cache=2583
2015-12-14 11:25:38 ERROR: ConnectBlock(): coinbase key detected in last 40 blocks
2015-12-14 11:25:38 Misbehaving: 91.230.123.86:8877 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-12-14 11:25:38 InvalidChainFound: invalid block=000944bcc77a8e9a81a4b3fc673dda17627830dd1a03bae35c974e580831cc9c  height=266997  log2_work=35.947744}


lg t.