[TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds)

[catia]

You don't have to be running latest build. In theory the network protocol is all stable now. Just need to get the clients hammered out.

[1715030573]

1715030573

[billotronic]

Groovy. I figured as much but wanted to make sure. The *nix box I test on is left on unattended for many hours during the day and I would hate to mess things up for the test because of it.

[catia]

New builds up. Primary change as that win64 should work better. With any of these builds you will need to delete data directory or run with -resync due to change in the transaction database.

Current is 14071622

@Billotronic that is good you have machine running for extended time. I have noticed a bug, it was in QT, but probably also in CLI. You can kind of see if it's happened to you from the

Update: 11659 11659 11659 11659 1

lines that are printed. When the bug happens, the third number will be less than the 4th by large amount. So like

Update: xxxxx xxxxx 10559 11659 x

Otherwise, the client will appear to be operating normally. Mining may work, transactions will be sent and received, no crashes, no errors. I think this is why there have been no reports. Restarting the client fixes it, I accidentally did that the last 2 times this bug happened. So if you see it, please grab a log before doing anything else. This bug is very serious, show stopper style as it can and will cause large scale forks. Currently no way to reproduce it and very little data on what is actually happening.

[mrvegad]

I am running new build cryptonited with wine on my pclinuxos, so far it is running good. I haven't used the qt build yet, will try it out after i run with cryptonited for awhile.

[billotronic]

New builds up. Primary change as that win64 should work better. With any of these builds you will need to delete data directory or run with -resync due to change in the transaction database.

Current is 14071622

@Billotronic that is good you have machine running for extended time. I have noticed a bug, it was in QT, but probably also in CLI. You can kind of see if it's happened to you from the

Update: 11659 11659 11659 11659 1

lines that are printed. When the bug happens, the third number will be less than the 4th by large amount. So like

Update: xxxxx xxxxx 10559 11659 x

Otherwise, the client will appear to be operating normally. Mining may work, transactions will be sent and received, no crashes, no errors. I think this is why there have been no reports. Restarting the client fixes it, I accidentally did that the last 2 times this bug happened. So if you see it, please grab a log before doing anything else. This bug is very serious, show stopper style as it can and will cause large scale forks. Currently no way to reproduce it and very little data on what is actually happening.

How large? I just killed the client to update and this was the last line:

Update: 11759 11759 11675 11759 1

[catia]

Pretty much anything larger than 2. Please send log.

[billotronic]

will do. I killed and left it so I will shoot that over tonight when I get home.

Still trying to make some time for the win qt... but damn people are making me work while at work... the nerve

[catia]

@Billotronic,
 
    Btw, on the machine that got the bug, were you running CLI/QT? I am toying with the idea that somehow QT is causing this as it has never been seen before and the primary node has been running for almost a week now without any issues.

[billotronic]

That was on the Qt.


OK win7 64

First launch:

Code:

2014-07-17 18:19:55 Cryptonite version v0.1.1.0-unk-beta (2014-07-11 15:05:34 -0400)
2014-07-17 18:19:55 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-07-17 18:19:55 Default data directory C:\Users\Parts1\AppData\Roaming\Cryptonite
2014-07-17 18:19:55 Using data directory C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3
2014-07-17 18:19:55 Using at most 125 connections (2048 file descriptors available)
2014-07-17 18:19:55 Using 4 threads for script verification
2014-07-17 18:19:55 Using wallet wallet.dat
2014-07-17 18:19:55 init message: Verifying wallet...
2014-07-17 18:19:55 CDBEnv::Open : LogDir=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\database ErrorFile=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\db.log
2014-07-17 18:19:55 Bound to [::]:18253
2014-07-17 18:19:55 Bound to 0.0.0.0:18253
2014-07-17 18:19:55 init message: Loading block index...
2014-07-17 18:19:55 Opening LevelDB in C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\blocks\index
2014-07-17 18:19:55 Opened LevelDB successfully
2014-07-17 18:19:55 LoadBlockIndexDB(): last block file = 0
2014-07-17 18:19:55 LoadBlockIndexDB(): transaction index enabled
2014-07-17 18:19:55 Best Block: 0000000000000000000000000000000000000000000000000000000000000000
2014-07-17 18:19:55 Initializing databases...
2014-07-17 18:19:56 Pre-allocating up to position 0x1000000 in blk00000.dat
2014-07-17 18:19:56 Connect tip : 00000a501a16765657517d8389f4a0639e887791b0c6dbdd075ce9b51539941e

Client asks for data dir, I click ok, it crashes with no info other then what is here in the log.

Launch Two:

Warning window: Incorrect of no Genisis block found. Wrong data dir for network?

Click ok then crashes

Log:

Code:

2014-07-17 18:44:22 Cryptonite version v0.1.1.0-unk-beta (2014-07-11 15:05:34 -0400)
2014-07-17 18:44:22 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-07-17 18:44:22 Default data directory C:\Users\Parts1\AppData\Roaming\Cryptonite
2014-07-17 18:44:22 Using data directory C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3
2014-07-17 18:44:22 Using at most 125 connections (2048 file descriptors available)
2014-07-17 18:44:22 Using 4 threads for script verification
2014-07-17 18:44:22 Using wallet wallet.dat
2014-07-17 18:44:22 init message: Verifying wallet...
2014-07-17 18:44:22 CDBEnv::Open : LogDir=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\database ErrorFile=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\db.log
2014-07-17 18:44:22 Bound to [::]:18253
2014-07-17 18:44:22 Bound to 0.0.0.0:18253
2014-07-17 18:44:22 init message: Loading block index...
2014-07-17 18:44:22 Opening LevelDB in C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\blocks\index
2014-07-17 18:44:22 Opened LevelDB successfully
2014-07-17 18:44:22 LoadBlockIndexDB(): last block file = 0
2014-07-17 18:44:22 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=1, size=174, heights=0...0, time=2014-07-05...2014-07-05)
2014-07-17 18:44:22 LoadBlockIndexDB(): transaction index enabled
2014-07-17 18:44:22 Best Block: 0000000000000000000000000000000000000000000000000000000000000000
2014-07-17 18:45:19 Initialization result: 0
2014-07-17 18:45:20 Requesting shutdown
2014-07-17 18:45:20 Running Shutdown in thread
2014-07-17 18:45:20 Shutdown : In progress...
2014-07-17 18:45:20 StopNode()
2014-07-17 18:45:20 Writing file 0000000000000000000000000000000000000000000000000000000000000000

Launch Three:

Error Window: Assertion Failed! File: treeview.cpp Line 20 / Expression: fread(&m_bestBlocks,1,32,filein) with the option to abort, retry, ignore

Clicking ignore causes crash and this log:

Code:

2014-07-17 18:46:09 Cryptonite version v0.1.1.0-unk-beta (2014-07-11 15:05:34 -0400)
2014-07-17 18:46:09 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-07-17 18:46:09 Default data directory C:\Users\Parts1\AppData\Roaming\Cryptonite
2014-07-17 18:46:09 Using data directory C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3
2014-07-17 18:46:09 Using at most 125 connections (2048 file descriptors available)
2014-07-17 18:46:09 Using 4 threads for script verification
2014-07-17 18:46:09 Using wallet wallet.dat
2014-07-17 18:46:09 init message: Verifying wallet...
2014-07-17 18:46:09 CDBEnv::Open : LogDir=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\database ErrorFile=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\db.log
2014-07-17 18:46:09 Bound to [::]:18253
2014-07-17 18:46:09 Bound to 0.0.0.0:18253
2014-07-17 18:46:09 init message: Loading block index...
2014-07-17 18:46:09 Opening LevelDB in C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\blocks\index
2014-07-17 18:46:09 Opened LevelDB successfully

This is getting long. Will continue in next post

[billotronic]

Restarting and this time clicking Ignore gives this error window:

 Assertion Failed! File: treeview.cpp Line 22 / Expression: fread(&sz,1,4,filein) with the option to abort, retry, ignore

Ignored

Next window:  Assertion Failed! File: treeview.cpp Line 24 / Expression: fread(buf,sz,1,filein) with the option to abort, retry, ignore

Ignored

Client does not fireup and also does not give a windows window saying the exe has crashed (which is kinda weird) Confirmed with taskmgr and the exe is definitely not running.

Log:

Code:

2014-07-17 18:50:35 Cryptonite version v0.1.1.0-unk-beta (2014-07-11 15:05:34 -0400)
2014-07-17 18:50:35 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-07-17 18:50:35 Default data directory C:\Users\Parts1\AppData\Roaming\Cryptonite
2014-07-17 18:50:35 Using data directory C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3
2014-07-17 18:50:35 Using at most 125 connections (2048 file descriptors available)
2014-07-17 18:50:35 Using 4 threads for script verification
2014-07-17 18:50:35 Using wallet wallet.dat
2014-07-17 18:50:35 init message: Verifying wallet...
2014-07-17 18:50:35 CDBEnv::Open : LogDir=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\database ErrorFile=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\db.log
2014-07-17 18:50:35 Bound to [::]:18253
2014-07-17 18:50:35 Bound to 0.0.0.0:18253
2014-07-17 18:50:35 init message: Loading block index...
2014-07-17 18:50:35 Opening LevelDB in C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\blocks\index
2014-07-17 18:50:35 Opened LevelDB successfully
2014-07-17 18:53:59 Loaded trie at 0000000000000000000000000000000000000000000000000000000000000000 0
2014-07-17 18:53:59 LoadBlockIndexDB(): last block file = 0
2014-07-17 18:53:59 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=1, size=174, heights=0...0, time=2014-07-05...2014-07-05)
2014-07-17 18:53:59 LoadBlockIndexDB(): transaction index enabled
2014-07-17 18:53:59 Best Block: 0000000000000000000000000000000000000000000000000000000000000000

[catia]

Try starting it with -testnet -resync options

[billotronic]

ok apparently I missed the exe in the taskmgr. It was still running in the background (but no GUI)

-resync gives just a plain crash with this in the log:

Code:

2014-07-17 19:04:22 Cryptonite version v0.1.1.0-unk-beta (2014-07-11 15:05:34 -0400)
2014-07-17 19:04:22 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-07-17 19:04:22 Default data directory C:\Users\Parts1\AppData\Roaming\Cryptonite
2014-07-17 19:04:22 Using data directory C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3
2014-07-17 19:04:22 Using at most 125 connections (2048 file descriptors available)
2014-07-17 19:04:22 Using 4 threads for script verification
2014-07-17 19:04:22 Using wallet wallet.dat
2014-07-17 19:04:22 init message: Verifying wallet...
2014-07-17 19:04:22 CDBEnv::Open : LogDir=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\database ErrorFile=C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\db.log
2014-07-17 19:04:22 Bound to [::]:18253
2014-07-17 19:04:22 Bound to 0.0.0.0:18253
2014-07-17 19:04:22 init message: Loading block index...
2014-07-17 19:04:22 Opening LevelDB in C:\Users\Parts1\AppData\Roaming\Cryptonite\testnet3\blocks\index
2014-07-17 19:04:22 Opened LevelDB successfully
2014-07-17 19:04:22 LoadBlockIndexDB(): last block file = 0
2014-07-17 19:04:22 LoadBlockIndexDB(): transaction index enabled
2014-07-17 19:04:22 Best Block: 0000000000000000000000000000000000000000000000000000000000000000
2014-07-17 19:04:22 Initializing databases...
2014-07-17 19:04:22 Pre-allocating up to position 0x1000000 in blk00000.dat
2014-07-17 19:04:22 Connect tip : 00000a501a16765657517d8389f4a0639e887791b0c6dbdd075ce9b51539941e

[catia]

What is a "plain crash" in windows? It doesn't give you any info, like GPF at 0xXXXXXXXXXXXX

[billotronic]

exactly. something along the lines pf "win64....exe has stopped working" and nothing of value though I supposed I could check out the event viewer and see if there is anything there. Let me see if I can get you any more info sir.

[edit]

Found some more info

Code:

Faulting application name: win64_cryptonite-qt_14071323.exe, version: 0.9.0.99, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000005
Fault offset: 0x0000000000018e5d
Faulting process id: 0x1dbc
Faulting application start time: 0x01cfa200ee1eaa72
Faulting application path: C:\Users\Parts1\Desktop\Bills Backup TOP SECRET\Back UP\win64_cryptonite-qt_14071323.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Faulting application name: win64_cryptonite-qt_14071323.exe, version: 0.9.0.99, time stamp: 0x00000000
Faulting module name: win64_cryptonite-qt_14071323.exe, version: 0.9.0.99, time stamp: 0x00000000
Exception code: 0x40000015
Fault offset: 0x000000000059cc31
Faulting process id: 0x2140
Faulting application start time: 0x01cfa1ef5ef91989
Faulting application path: C:\Users\Parts1\Desktop\Bills Backup TOP SECRET\Back UP\win64_cryptonite-qt_14071323.exe
Faulting module path: C:\Users\Parts1\Desktop\Bills Backup TOP SECRET\Back UP\win64_cryptonite-qt_14071323.exe
Report Id: 1ff1ea99-0de3-11e4-a855-d4bed9984d59

Hope this helps

[catia]

I haven't had any trouble. I think it might be random thing. Try deleting the entire data folder and launching repeatedly. Eventually I think it will go. Probably some uninitialized memory somewhere.

[billotronic]

I will give it another go tomorrow sir

in the meantime, here is my linux qt log from earlier

https://mega.co.nz/#!N5tCBLiQ!fzPHpDSuS0RZFffT8xh8J4ocFjT6zKW_yZEk__EZ_2s

[catia]

New builds are up. 14071722/23   These have fix for the block issue and some QT performance improvements that while very large are probably not noticeable unless you have incoming transactions.

So currently no known issues with linux QT/CLI and we aren't having any luck reproducing win64 problems over here. Seems we are looking pretty good

[watuba]

Sorry, I asked how I could help about a month ago, then went MIA.

I tried running the latest qt on a win7 64bit and got similar errors to @billotronic(client asks for data dir, then crashes, opened again, crashes).  But then I ran it with --testnet, and the qt appears to be up and running, syncing and everything.  Exciting!

@catia, you asked me if I could help mining before.  I've admittedly never mined before.  Is this something I can figure out easily?  I can't seem to find a tutorial online for mining a coin like this, without a pool, etc.  

Thanks and hope I can help without getting in the way!

EDIT:  I just tried mining through the windows qt, using the debug window and “setgenerate true -1".  I'm getting block rewards.  Is this the correct way to do it?  

[billotronic]

hmmm now that I see your post I wonder if I had one - or two in front of testnet... That would fit my track record! lol

The other possibility is I made a damn mess of this system trying to get it to work yesterday.

Either way, current build is working now so happy days (and I might be my own worst enemy)

@watuba yes and the -1 flag means to use all available cores and is the default setting for setgenerate. If you didn't want to use all available you would change the -1 to the number of cores. ie setgenerate true 2 to use just 2 cores.

[watuba]

hmmm now that I see your post I wonder if I had one - or two in front of testnet... That would fit my track record! lol

The other possibility is I made a damn mess of this system trying to get it to work yesterday.

Either way, current build is working now so happy days (and I might be my own worst enemy)

@watuba yes and the -1 flag means to use all available cores and is the default setting for setgenerate. If you didn't want to use all available you would change the -1 to the number of cores. ie setgenerate true 2 to use just 2 cores.

I think I got lucky that I used two -.  What is the difference between one - and two -?  I know I've used one - for things before.