I see no crashes on updated ubuntu server 14.04.
I do NOT set incoming connections to 0.
I set max_connections to 50.
It hasn't crashed on 0.4.9.

Quote from: maverica on August 29, 2014, 09:22:11 PM
The segmentation error has caused quite some trouble on our part. I think weve missed quite some blocks because of it. I was wondering if there is a way to decrease the connections as a measure to stop that from happening? What would be the best way to do that?

Same here

I had some limited success using ./bitshares_client --accept-incoming-connections=0

but the connections would slowly move from 5 initially down to zero over some variable amount of time, and I'd start missing blocks again.

I'm currently trying:
network_set_advanced_node_parameters { "peer_connection_retry_timeout": 30, "desired_number_of_connections": 25, "maximum_number_of_connections": 50 }

Its been only 5 hours or so but no segfault crash yet.
 

The segmentation error has caused quite some trouble on our part. I think weve missed quite some blocks because of it. I was wondering if there is a way to decrease the connections as a measure to stop that from happening? What would be the best way to do that?

Quote from: happyshares on August 29, 2014, 05:22:59 PM

Quote from: happyshares on August 28, 2014, 10:28:28 PM
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

Quote from: happyshares on August 28, 2014, 10:28:28 PM
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

Quote from: Riverhead on August 29, 2014, 12:07:45 PM


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 from: pc on August 29, 2014, 11:50:51 AM

Quote from: maverica on August 29, 2014, 04:01:09 AM

Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string (this=this@entry=0xa46a1c0, ll=..., ll@entry=...)
    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?

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 from: pc on August 29, 2014, 11:50:51 AM

Quote from: maverica on August 29, 2014, 04:01:09 AM

Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string (this=this@entry=0xa46a1c0, ll=..., ll@entry=...)
    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

Yhea .. maybe i should reduce the num connections too .. ill wait for the next rush so the network is stronger befoe reducing it

Quote from: xeroc on August 29, 2014, 11:59:10 AM
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.

Quote from: xeroc on August 29, 2014, 11:59:10 AM
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).

My delegate also resets regularily .. :(

Quote from: maverica on August 29, 2014, 04:01:09 AM

Quote
bitsapphire (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x000000000065e91b in fc::exception::to_detail_string (this=this@entry=0xa46a1c0, ll=..., ll@entry=...)
    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

coolspeed

and

*.coolspeed

updated to 0.4.9

now.dacwin

future.dacwin

updated to 0.4.9.

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

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 (
    this=this@entry=0x26d8620, ll=..., ll@entry=...)
    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.