sx command line utilities - Empower The Sysadmin With Bitcoin Tools - page 5.

genjix

legendary

Activity: 1232

Merit: 1076

Quote from: dexX7 on April 04, 2014, 11:50:19 AM

Hmm.. I'm not sure, what I'm doing wrong. I installed sx with the install script on several systems.

After running "sx fetch-last-height" and some other commands I receive the following error:

Code:

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid

Any help is very appreciated!

What system are you using? 32 bit or 64 bit? Thanks.

dexX7

legendary

Activity: 1106

Merit: 1026

Hmm.. I'm not sure, what I'm doing wrong. I installed sx with the install script on several systems.

After running "sx fetch-last-height" and some other commands I receive the following error:

Code:

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid

Any help is very appreciated!

grue

legendary

Activity: 2058

Merit: 1452

the multisig documentation is broken. sx sign-input ouputs debug messages so it breaks the shell substitution in the second last step. Even if you fix that, you will get:

Code:

Usage: set-input FILENAME N SIGNATURE_AND_PUBKEY_SCRIPT

gwlloyd

newbie

Activity: 50

Merit: 0

Quote from: ?? on ??

Ugh, my server is currently down because ever since I've updated the sx stack, it errors out. Tried removing the blockchain, no luck.

Code:

Using config file: /etc/obelisk/worker.cfg
Press CTRL-C to shut down.
DEBUG [worker]: Listening: tcp://*:9091
INFO [worker]: worker ready
DEBUG [worker]: Heartbeat: tcp://*:9092
obworker: blockchain/database/stealth_database.cpp:17: libbitcoin::stealth_database::stealth_database(libbitcoin::mmfile&): Assertion `file_.data() != nullptr' failed.
Aborted (core dumped)

I'm no expert and I'm sure Amir will reply, until then.. did you "init blockchain" correctly (matching your configured folder) after removing the data and also have you tried a new location just in case of some kind of lock preventing access to the DB file.

genjix

legendary

Activity: 1232

Merit: 1076

Quote from: gwlloyd on March 21, 2014, 10:19:04 PM

Sorry but I have to conclude that Obelisk doesn't work on low memory (1.5 Gb), non-SSD virtual machines. Just for anyone out there trying. I've lost count how many times I've had to rm -R ./* and start again over the past 4 weeks or so due to some fatal error or another. Shame, because I really didn't want to use any more electricity with yet another physical server but I really want to have these sx tools available to me so I guess it has to be so.

you can still use the tools and we're running a public server at obelisk.unsystem.net:8081

genjix

legendary

Activity: 1232

Merit: 1076

Quote from: instagibbs on March 18, 2014, 03:27:32 PM

edit2: Getting an error with the libbitcoin step now. Help? I already checked, my libbitcoin dependencies all seem correct:

Quote

make[1]: Entering directory `/usr/local/src/libbitcoin-git/src'
CXX satoshi_serialize.lo
CXX getx_responder.lo
CXX threadpool.lo
CXX network/network.lo
network/network.cpp: In member function 'void libbitcoin::perform_connect_with_timeout::start(boost::asio::ip::basic_resolver::iterator, size_t, libbitcoin::network::connect_handler)':
network/network.cpp:77:9: error: 'async_connect' is not a member of 'boost::asio'

Getting this error. I think I've installed everything people are saying to install, and can't find any obvious packages via googling.

edit: It appears that software needs g++ newer than the version I'm running, according to its github page.

yep although this error is caused by using an older version of boost

gwlloyd

newbie

Activity: 50

Merit: 0

Sorry but I have to conclude that Obelisk doesn't work on low memory (1.5 Gb), non-SSD virtual machines. Just for anyone out there trying. I've lost count how many times I've had to rm -R ./* and start again over the past 4 weeks or so due to some fatal error or another. Shame, because I really didn't want to use any more electricity with yet another physical server but I really want to have these sx tools available to me so I guess it has to be so.

instagibbs

member

Activity: 114

Merit: 12

edit2: Getting an error with the libbitcoin step now. Help? I already checked, my libbitcoin dependencies all seem correct:

Quote

make[1]: Entering directory `/usr/local/src/libbitcoin-git/src'
CXX satoshi_serialize.lo
CXX getx_responder.lo
CXX threadpool.lo
CXX network/network.lo
network/network.cpp: In member function 'void libbitcoin::perform_connect_with_timeout::start(boost::asio::ip::basic_resolver::iterator, size_t, libbitcoin::network::connect_handler)':
network/network.cpp:77:9: error: 'async_connect' is not a member of 'boost::asio'

Getting this error. I think I've installed everything people are saying to install, and can't find any obvious packages via googling.

edit: It appears that software needs g++ newer than the version I'm running, according to its github page.

genjix

legendary

Activity: 1232

Merit: 1076

Quote from: gwlloyd on March 17, 2014, 09:55:50 PM

Quote from: genjix on March 17, 2014, 09:39:11 PM

From now on use tcp://obelisk.unsystem.net:8081 as your server if you don't have one. No guarantees about uptime (at least for now) but I'll try to migrate it as I get more servers and maintain it as a public one.

If I donate a cheap VPS and point it at your balancer does that help?

It's OK, we did the darkwallet campaign. It's more about manpower to develop the tools since we're testing and improving the software.

gwlloyd

newbie

Activity: 50

Merit: 0

Quote from: genjix on March 17, 2014, 09:39:11 PM

From now on use tcp://obelisk.unsystem.net:8081 as your server if you don't have one. No guarantees about uptime (at least for now) but I'll try to migrate it as I get more servers and maintain it as a public one.

If I donate a cheap VPS and point it at your balancer does that help?

genjix

legendary

Activity: 1232

Merit: 1076

From now on use tcp://obelisk.unsystem.net:8081 as your server if you don't have one. No guarantees about uptime (at least for now) but I'll try to migrate it as I get more servers and maintain it as a public one.

genjix

legendary

Activity: 1232

Merit: 1076

Quote from: gwlloyd on March 16, 2014, 04:17:16 PM

Quote from: genjix on March 16, 2014, 03:11:44 PM

ok, if you do then run the latest script. I've made lots of changes.

FYI on the latest install script it fails to remove the package libzmq on debian because it doesn't exist, only libzmq-dev does in the standard repositories (or at least on mine install).. removing that item from the script corrects the issue.

Weird, because I'm testing on Debian Wheezy virtual machines. I'll look further, thanks.

Edit: OK, I've changed it to a wildcard.

gwlloyd

newbie

Activity: 50

Merit: 0

Quote from: genjix on March 16, 2014, 03:11:44 PM

ok, if you do then run the latest script. I've made lots of changes.

FYI on the latest install script it fails to remove the package libzmq on debian because it doesn't exist, only libzmq-dev does in the standard repositories (or at least on mine install).. removing that item from the script corrects the issue.

genjix

legendary

Activity: 1232

Merit: 1076

ok, if you do then run the latest script. I've made lots of changes.

gwlloyd

newbie

Activity: 50

Merit: 0

One is a fresh Wheezy and one is an upgraded Debian 6 that has been in use for years. I installed Obelisk about 10 days ago but I've done a few attempts to sync in that time.. I'm not using SSD but they are VirtualBox VMs so it's sortof SSD - that wouldn't explain why it always gets to this specific block and then never any further. I guess I'll just try another sync from the start.

genjix

legendary

Activity: 1232

Merit: 1076

I'm using Debian Wheezy, what are you using? When did you install it? When did you start the daemon? Are you using an SSD? I would recommend an SSD because a lot of the code assumes you're using SSDs (0 seek times) as I believe they're the future of storage.

gwlloyd

newbie

Activity: 50

Merit: 0

bitcoind has been running for months, fully up-to-date and regularly used. I've tried pointing obelisk to it exclusively, not pointing to it at all and pointing to it with other public connections too. restarting obelisk makes no difference and like I say I have started a fresh obelisk on a different server and when it hits this block, the same happens.

Edit: Debian 7 servers (one 64, one 32), open files limits increased, installed using your automatic install script and I'm very familiar with Linux & coding so feel free to get technical.

genjix

legendary

Activity: 1232

Merit: 1076

have you configured it to only connect to your bitcoind? if so, how many blocks does your bitcoind have? use ./bitcoind getinfo to see. if bitcoind has the correct number of blocks then try restarting obelisk and/or restarting bitcoind. does it start syncing?

gwlloyd

newbie

Activity: 50

Merit: 0

Quote from: genjix on March 16, 2014, 06:59:14 AM

Quote from: gwlloyd on March 15, 2014, 07:39:01 PM

I'm now on my fifth attempt using 2 different servers (one a pretty much clean Debian VM and one an established server).. every time I get nearly to the end of the blockchain sync it just seems to sit around not receiving new blocks and spewing reams of errors such as below. I'm assuming blockchain database corruption but it always seems to be somewhere in the 27#### block range (I've just noticed this). Is this normal? Is there maybe something about this range of blocks, was that when someone was spamming the blockchain? Getting a bit frustrated here sapping so much time and bandwidth and still haven't got a sync'd copy to play with. I don't want to download a torrent copy.

WARNING: Error storing memory pool transaction c0c958698d61b260a885115a7e2ccec1a25c8a121c0da9ec6165f0ce11920c9b: Spent input not found

Nope it looks fine. Those errors aren't a problem. Example: memory pool isn't full yet and there's txs depending on other txs in the mempool that aren't yours. It's normal. I'll make the wording sound less extreme.

Important is that you're able to run 'sx fetch-last-height' and the block height matches blockchain.info or somewhere else.

I need to document these tools better. Sorry about that. I'll be making efforts towards that goal as documentation is important.

The docs aren't that bad and the error does make sense - if it hasn't got the full blockchain then there are going to be transactions that don't make sense to it, so it can't store them.

It's sticking on block 278746 every time and once it gets to that block it is still using CPU but nowhere near the levels it normally uses when sync'ing. Looking up the blocks around this time it doesn't seem to be a gorilla block. Any ideas? Perhaps start fresh without my local bitcoind as one of the manual nodes.. is there any way my bitcoind could have a bad blockchain and not know about it?

genjix

legendary

Activity: 1232

Merit: 1076

If anyone is using unSYSTEM Obelisk servers, then they will be upgraded today (Sun 16 March). If you experience problems with the new unSYSTEM servers, then upgrade SX:

Code:

$ wget http://sx.dyne.org/install-sx.sh
$ sudo bash install-sx.sh

or

Code:

$ wget http://sx.dyne.org/install-sx.sh
$ bash install-sx.sh /home/genjix/usr/

You also have the option to run a different server with an older version of Obelisk, although I'll be encouraging operators to upgrade soon. List of servers: https://wiki.unsystem.net/index.php/Obelisk/Servers - let me know if you have a server to add to the list.

Topic: sx command line utilities - Empower The Sysadmin With Bitcoin Tools - page 5. (Read 240156 times)