Quote from: xnova on March 14, 2014, 05:34:11 PM

Quote from: user1922 on March 14, 2014, 03:42:58 PM

Quote from: user1922 on March 14, 2014, 09:57:11 AM

Trying to get Counterpary running on Desktop Ubuntu 12.04 LTS (64-bit) but seem unable to do so. Building updating, bitcoin reindexing all went fine, tutorials are all quite clear. I am now running counterparty v6.6 and bitcoind v0.8.6.0-g03a7d67-beta

But I get an error message when I try to run the counterparty server:
# counterpartyd server
Status: RESTART
Unhandled exception in thread started by
libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted (core dumped)

I have installed the IA32-libs and there are 2 editions for libgcc_s.so.1:
$ find /lib -name 'libgcc*'
/lib/i386-linux-gnu/libgcc_s.so.1
/lib/x86_64-linux-gnu/libgcc_s.so.1

But I still keep getting this error.
Any tips?

No one to offer any hints on how to solve this?

I have the hunch that the box has a non-standard version of Python on it. If you are on Ubuntu 64-bit, you shouldn't need ia32-libs I believe for anything with Counterparty... actually, from googling that error, it appears that you're probably trying to run counterparty with the 32-bit Python or something similar.... the virtualenv install script probably found a 32-bit Python and used that instead of the 64-bit version, I'm guessing.

To confirm, you could try commands like:

Code:

which python3
ldd `which python3`
python3 -c "import platform;print(platform.architecture())"

The last line should return "('64bit', 'ELF')". (Or, just start up the Python interpreter and see if it mentions 32-bit or 64-bit)... and actually I'd perform the same checks on the python binary over at counterpartyd_build/env/bin/python3 on your box (where ever you installed counterpartyd_build).

The options would be to either remove all that 32-bit compatibility stuff, or work on a fresh Ubuntu install (13.10 x64 is optimal here).

Thanks for the input!
$ ldd `which python3`
   linux-vdso.so.1 => (0x00007fff0e5e6000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7b972df000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7b970db000)
   libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f7b96ed7000)
   libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7b96c79000)
   libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7b9689e000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f7b96686000)
   libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f7b9645c000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7b96160000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7b95d9f000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f7b97522000)
$ python3 -c "import platform;print(platform.architecture())"
('64bit', 'ELF')

So, yes, I am using 64-bit all the way. I did not mention that I installed the IA32-libs as a last resort and *after* building counterparty. This morning I deleted my ~/counterpartyd_build and ~/.config/counterpartyd folders, and started from scratch. And behold: it works now Huh

Do not really understand why because the only thing that has changed is that the IA32-libs where present *before* running the setup. The whole chain is 64-bits, i checked...

Now I am waiting for counterparty server to catch up with the last BTC block. Seeing the rate in which it catches up this might be a couple of days even! Any idea on how long that will take?

(And again: Thanks for all the help I got!)

user1922

Posts

Merits