Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Problem starting client  (Read 353 times)

Offline lafona

Problem starting client
« on: November 14, 2014, 02:00:18 AM »

Hi I recently began having difficulty running the client. When I attempt to start, I get

Loading blockchain from: /home/ubuntu/.BitShares/chain
Loading config from file: /home/ubuntu/.BitShares/config.json
Not starting RPC server, use --server to enable the RPC interface
Segmentation fault (core dumped)

It was compiled in ubuntu 14.04 if that makes any difference

thanks
BTS Witnesses: delegate-1.lafona     Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: delegate-1.lafona
Witness information: https://github.com/lafona/delegate-1.lafona

Offline lafona

Re: Problem starting client
« Reply #1 on: November 14, 2014, 02:10:21 AM »
output when I run under gdb

(gdb) run
Starting program: /home/ubuntu/Applications/Bitshares/bitshares/programs/client/bitshares_client
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Loading blockchain from: /home/ubuntu/.BitShares/chain
Loading config from file: /home/ubuntu/.BitShares/config.json
[New Thread 0x7ffff638d700 (LWP 1469)]
[New Thread 0x7ffff5b8c700 (LWP 1470)]
[New Thread 0x7ffff538b700 (LWP 1471)]
[New Thread 0x7ffff4b8a700 (LWP 1472)]
[New Thread 0x7fffe7fff700 (LWP 1473)]
[New Thread 0x7fffe77fe700 (LWP 1474)]
[New Thread 0x7fffe6ffd700 (LWP 1475)]
[New Thread 0x7fffcb1e2700 (LWP 1476)]
[New Thread 0x7fffca9e1700 (LWP 1477)]
[New Thread 0x7fffca1e0700 (LWP 1478)]
[New Thread 0x7fffc9996700 (LWP 1479)]
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7fffc90d3700 (LWP 1480)]
[New Thread 0x7fffc88d2700 (LWP 1481)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6f59e9b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
BTS Witnesses: delegate-1.lafona     Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: delegate-1.lafona
Witness information: https://github.com/lafona/delegate-1.lafona

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 936
    • View Profile
Re: Problem starting client
« Reply #2 on: November 14, 2014, 04:19:10 AM »
Try pulling the latest, rather than the tagged 0.4.24 version.  There was a crash patched that isn't in a tagged release yet.

Offline vikram

Re: Problem starting client
« Reply #3 on: November 14, 2014, 04:29:50 PM »
Yes, this is likely the same issue as: https://github.com/BitShares/bitshares/issues/959

It will be officially fixed in 0.4.25 but is already included in the current master branch so you can pull master if desired.

Offline lafona

Re: Problem starting client
« Reply #4 on: November 14, 2014, 11:11:19 PM »
Thanks, is there a command I need to change in order to pull master?
BTS Witnesses: delegate-1.lafona     Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: delegate-1.lafona
Witness information: https://github.com/lafona/delegate-1.lafona

Offline camponez

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Problem starting client
« Reply #5 on: November 15, 2014, 05:20:44 PM »
I just built the master branch and got the same problem.

Here is the gdb output:

Initializing genesis state from built-in genesis file
[New Thread 0x7fff6f325700 (LWP 20187)]
Successfully re-indexed 0 blocks in 0 seconds.                         
Blockchain size changed from 0MiB to 0MiB.
[New Thread 0x7fff6ddae700 (LWP 20191)]
[New Thread 0x7fff6d5ad700 (LWP 20192)]
[New Thread 0x7fff6cdac700 (LWP 20193)]
[New Thread 0x7fff669e0700 (LWP 20194)]
[New Thread 0x7fff661df700 (LWP 20195)]
[New Thread 0x7fff659de700 (LWP 20196)]
[New Thread 0x7fff651dd700 (LWP 20197)]
[New Thread 0x7fff649dc700 (LWP 20198)]
[New Thread 0x7fff43fff700 (LWP 20199)]
[New Thread 0x7fff437fe700 (LWP 20200)]
[New Thread 0x7fff42ffd700 (LWP 20201)]
[New Thread 0x7fff427fc700 (LWP 20202)]
[New Thread 0x7fff41ffb700 (LWP 20203)]
[New Thread 0x7fff4119b700 (LWP 20204)]
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/logo-ico.svg
/webfonts/opensans-regular.woff
/webfonts/fontawesome-webfont.woff
[New Thread 0x7fff1dab5700 (LWP 20205)]
/img/xt-background.jpg
/img/xts-logo-xl-white-shadow.png

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe7e2b138 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
(gdb)

Offline vikram

Re: Problem starting client
« Reply #6 on: November 18, 2014, 09:21:55 PM »
What is the backtrace (use "bt" command in gdb after crash)?

 

Google+