Delegates, please response to this thread if your delegate updated to 0.4.9

[CoinHoarder]

Getting this error after running the client for 10 mins:

--- 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 (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";

Any thoughts?

I woke up to this error this morning. I'm not sure what it is, but it made me miss 8 blocks. 

[maverica]

Getting this error after running the client for 10 mins:

--- 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 (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";

Any thoughts?

[maverica]

bitsapphire up and running, syncing atm

[Ggozzo]

skyscraperfarms is back in the game!

Vote me back in please!

Do the forks purposely purge all the delegates?

[happyshares]

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

[Fox]

Compile @ 74%

Complete.  First block running 0.4.9: 335859

Just a bump to the above notice as I was purged.  My 0.4.9 node is awaiting votes to resume block production.

Thanks,
Fox

[dacsunlimited.com]

In what way you are you associated with dacsunlimited ?

nothing to do with dacsunlimited.  we are using dacsunlimited.com
thanks

[emski]

delegate name: 

hongkong

usa

both are running on version 0.49

In what way you are you associated with dacsunlimited ?

[GaltReport]

any particular reason that I have been voted out?

(mine too) look like a bunch of inits were brought in

Me as well.

Please vote me back in.

[CalabiYau]

Producing blocks again - voting appreciated 

[Xeldal]

PS: What about google spreadsheed containing delegate availability + version

It looks like they're adding that function to the client
https://github.com/BitShares/bitshares_toolkit/issues/710

[emski]

And another issue:
You cant publish price feed if you are not an active delegate.
If you are voted out (or in) what happens to your last feed?
Is it possible for non-active delegates to publish feed (on standby)?

[emski]

Someone needs to collect all the data and update that post.
Usually the original poster is DACSUnlimited so that might not be viable also.
Perhaps second or third post should contain all updated nodes.

BTW: *.bitdelegate are prepared.

PS: What about google spreadsheed containing delegate availability + version

[xeroc]

He got me back in.  Just make sure he knows you're updated.  In the future we should have the tell us when you're updated thread list all the delegates that have updated in the first post.  I think Dan is busy enough already without having to wade through six pages of a thread to see who is ready.

- good point
 - mine are not yet up ..
 - I like how BM has "everything under control" ;-)
 - hard fork is gone .. 90+% participation .. nice and smooth

[bytemaster]

I wanted to error on the safe side...