Author Topic: Delegates, please response to this thread if your delegate updated to 0.4.9  (Read 10778 times)

0 Members and 1 Guest are viewing this topic.

Offline maverica

  • Jr. Member
  • **
  • Posts: 22
    • View Profile
bitsapphire up and running, syncing atm

Offline maverica

  • Jr. Member
  • **
  • Posts: 22
    • View Profile
Getting this error after running the client for 10 mins:
Quote
--- currently syncing at 206 blocks/sec, 10 minutes remaining
--- there are now 46 active connections to the p2p network
--- there are now 47 active connections to the p2p network
--- there are now 46 active connections to the p2p network
--- there are now 47 active connections to the p2p network
--- there are now 48 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 48 active connections to the p2p network
--- there are now 47 active connections to the p2p network
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string ([email protected]=0xa46a1c0, ll=..., [email protected]=...)
    at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";
Any thoughts?

Offline CoinHoarder

  • Hero Member
  • *****
  • Posts: 660
  • In Cryptocoins I Trust
    • View Profile
Getting this error after running the client for 10 mins:
Quote
--- currently syncing at 206 blocks/sec, 10 minutes remaining
--- there are now 46 active connections to the p2p network
--- there are now 47 active connections to the p2p network
--- there are now 46 active connections to the p2p network
--- there are now 47 active connections to the p2p network
--- there are now 48 active connections to the p2p network
--- there are now 49 active connections to the p2p network
--- there are now 48 active connections to the p2p network
--- there are now 47 active connections to the p2p network
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string ([email protected]=0xa46a1c0, ll=..., [email protected]=...)
    at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";
Any thoughts?

I woke up to this error this morning. I'm not sure what it is, but it made me miss 8 blocks.  >:(
https://www.decentralized.tech/ -> Market Data, Portfolios, Information, Links, Reviews, Forums, Blogs, Etc.
https://www.cryptohun.ch/ -> Tradable Blockchain Asset PvP Card Game

Offline BunkerChainLabs-DataSecurityNode

We are experiencing the same issue just attempting to get a delegate setup.

Code: [Select]
Finished scanning for new transactions.
OK
--- there are now 17 active connections to the p2p network
--- there are now 18 active connections to the p2p network
--- there are now 19 active connections to the p2p network
--- there are now 16 active connections to the p2p network
--- there are now 15 active connections to the p2p network
 Scanning for new transactions in block: 187/259352actions in block: 173/259352
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string (
    [email protected]=0x26d8620, ll=..., [email protected]=...)
    at /usr/src/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<
my->_what<<"\n";
As soon as we unlock the wallet it starts scanning and will crash anywhere from 180 to 300 blocks with an error similar to this.
Ubuntu 14.04 latest and running the latest build from a few hours from now. Hardware is running ok.

What can we do for a hotfix or will there be an update?

Thanks.
+-+-+-+-+-+-+-+-+-+-+
www.Peerplays.com | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

Offline coolspeed

  • Hero Member
  • *****
  • Posts: 536
    • View Profile
    • My Blog
now.dacwin

future.dacwin

updated to 0.4.9.
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

Offline coolspeed

  • Hero Member
  • *****
  • Posts: 536
    • View Profile
    • My Blog
coolspeed

and

*.coolspeed

updated to 0.4.9
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string ([email protected]=0xa46a1c0, ll=..., [email protected]=...)
    at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";

I've been getting loads of these since 0.4.8, see https://github.com/BitShares/bitshares_toolkit/issues/647#issuecomment-53440518
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
My delegate also resets regularily .. :(
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
My delegate also resets regularily .. :(

Interesting thing is that my delegates are relatively (1 crash on 0.4.7?) stable with no modifications  (except max_connections = 50).

Offline Riverhead

My delegate also resets regularily .. :(


Mine has been solid as a rock but it's also behind a firewall...not sure if that's why.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Yhea .. maybe i should reduce the num connections too .. ill wait for the next rush so the network is stronger befoe reducing it
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline Riverhead



I'm not sure if the dependencies are static or not. I'll often do a apt-get update, apt-get <list of dependencies from BUILD_UBUNTU.md>. So far my delgate client hasn't seg faulted once.

Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string ([email protected]=0xa46a1c0, ll=..., [email protected]=...)
    at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";

I've been getting loads of these since 0.4.8, see https://github.com/BitShares/bitshares_toolkit/issues/647#issuecomment-53440518

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG


I'm not sure if the dependencies are static or not. I'll often do a apt-get update, apt-get <list of dependencies from BUILD_UBUNTU.md>. So far my delgate client hasn't seg faulted once.

Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string ([email protected]=0xa46a1c0, ll=..., [email protected]=...)
    at /root/bitsharesx/libraries/fc/src/exception.cpp:144
144           ss << variant(my->_code).as_string() <<" " << my->_name << ": " <<my->_what<<"\n";

I've been getting loads of these since 0.4.8, see https://github.com/BitShares/bitshares_toolkit/issues/647#issuecomment-53440518

I also keep mine up to date... Could this be an issue?
bitsapphire - why dont you try to update and tell us the result?

Offline happyshares

  • Jr. Member
  • **
  • Posts: 33
    • View Profile
please vote me back in: happyshares-2    @0.4.9
thanks

since 24H i'm on standby @ version 0.4.9 , please vote me in again.
thank you

Ggozzo

  • Guest
please vote me back in: happyshares-2    @0.4.9
thanks

since 24H i'm on standby @ version 0.4.9 , please vote me in again.
thank you

Me too! I think Bytemaster was pulling most of the weight by directing his or I3 or DACsun shares towards most delegates. This is why we get purged on the forks and a lot of init-delegates are back in the mix. I'd like to get back in! Votes are obviously hard to come by for a delegate that doesn't have a huge bank roll.  ;) in due time I suppose.  :D