Topic: [TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 10. (Read 19296 times)

do you have libboost 1.53?

Awesome!  Here's what it outputs:

$ ldd ./saucy_amd64_cryptonite-qt_14071722 -testnet -resync
./saucy_amd64_cryptonite-qt_14071722:
   linux-vdso.so.1 =>  (0x00007fffb1bc2000)
   libboost_system.so.1.53.0 => not found
   libboost_filesystem.so.1.53.0 => not found
   libboost_program_options.so.1.53.0 => not found
   libboost_thread.so.1.53.0 => not found
   libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007f6fbff4e000)
   libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007f6fbfc01000)
   libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007f6fbf72f000)
   libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x00007f6fbf4b2000)
   libprotobuf.so.7 => /usr/lib/libprotobuf.so.7 (0x00007f6fbf1c2000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6fbefa5000)
   libdb_cxx-4.8.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-4.8.so (0x00007f6fbec1a000)
   libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f6fbe9ab000)
   libminiupnpc.so.8 => /usr/lib/libminiupnpc.so.8 (0x00007f6fbe7a0000)
   libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f6fbe542000)
   libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f6fbe166000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f6fbde66000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6fbdb6a000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f6fbd953000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6fbd593000)
   libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f6fbd35d000)
   libaudio.so.2 => /usr/lib/x86_64-linux-gnu/libaudio.so.2 (0x00007f6fbd144000)
   libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f6fbce4f000)
   libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007f6fbcc27000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6fbca0f000)
   libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f6fbc773000)
   libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f6fbc524000)
   libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6 (0x00007f6fbc31b000)
   libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6 (0x00007f6fbc101000)
   libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007f6fbbef1000)
   libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f6fbbce6000)
   libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f6fbbad5000)
   libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f6fbb7a0000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6fbb59b000)
   librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f6fbb393000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f6fc209c000)
   libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007f6fbb14e000)
   libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f6fbaf09000)
   libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f6fbacdf000)
   libXt.so.6 => /usr/lib/x86_64-linux-gnu/libXt.so.6 (0x00007f6fbaa78000)
   libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f6fba875000)
   libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f6fba638000)
   libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f6fba42f000)
   libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f6fba22a000)
   libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f6fba00b000)
   libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f6fb9e05000)
-testnet:
ldd: ./-testnet: No such file or directory
-resync:
ldd: ./-resync: No such file or directory

A neat trick I learned from this project is the ldd command. Put that in front of the binary and run it and will tell you if you meet the dependencies or not. Post what it shows and we get you up and running bud.

Man, I was intimidated by those new files.  I read through the thread and followed the steps, downloaded libboost, etc.  I'm using Ubuntu 12.04, and downloaded the Saucy binary.  Got this error, googled it, still don't understand.  Gonna look into it more tomorrow:

$ ./saucy_amd64_cryptonite-qt_14071722 -testnet -resync
./saucy_amd64_cryptonite-qt_14071722: error while loading shared libraries: libboost_system.so.1.53.0: cannot open shared object file: No such file or directory

aha! No sir, they are not

Go here http://gpile.it/cryptonite/ and download the most recent files for your OS

I used these links:
gpile.it/files/cryptonited
gpile.it/files/cryptonite-qt

Are those not the most up-to-date?

are you sure you have the most current version? Only reason I ask is there were old versions that had that bug where it would get stuck on the blockchain

Deleted everything in the cryptonite data directory and that worked, but now it won't sync.  It stays on block 32 in both cryptonited and cryptonite-qt Linux.  Here's some of what it displays in terminal:

Update: 161 11196 11196 12196 0
OS 33 NS 33
received slice 000000b036c2c23fb9547d45eee49cb8c875258c770a3304d0585a0c57075817 0000000000000000000000000000000000000000 7fffffffffffffffffffffffffffffffffffffff
Slice not accepted
received slice 000000b036c2c23fb9547d45eee49cb8c875258c770a3304d0585a0c57075817 8000000000000000000000000000000000000000 ffffffffffffffffffffffffffffffffffffffff
Slice not accepted
Accept block header

It appears to be trying to read an old trie.dat file. Those are incompatible with new code. Not sure exactly why resync doesn't work. But just delete the data folder if you have really old stuff lying around.

Replaced old version of cryptonited from about 1 month ago with new version on Linux, and got this:

$ ./cryptonited -testnet -resync
Fail branch 4: 1341
Fail branch 4: 1363
Fail branch 4: 1385
Fail branch 4: 1407
Fail branch 4: 1429
Fail
activeHeight: -1, headersHeight: -1
indexSize: 2140, orphansSize: 2140
askedSize: 0, missingSize: 0
validSize: 0
activeHeight: -1, headersHeight: -1
indexSize: 2140, orphansSize: 2139
askedSize: 0, missingSize: 0
validSize: 0
Segmentation fault (core dumped)

Sorry if this is a noob-problem.  Ran the old version of cryptonited and it started up fine, but was on the wrong fork.

I see, FWIW, I used "cryptonite-qt.exe --testnet" when I ran it on win7 and it worked.  When I initially ran it, I forgot to add testnet at all, and it didn't work.

It just depends on the application. Windows apps typically use /, linux uses - or -- depending on whims of the author. In this case both linux/windows binaries use the same single -

Ahh yes.  From my experience, that sounds right

Well I could be mistaken on this BUT I am pretty sure linux uses just one and windows two? I know for a fact about linux but do not use windows much for wallets and when I do it's never with flags. I usually rock a config file since those are cross platform/universal.

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.

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.

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?  

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

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

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.