Author Topic: !!!CAUTION!!! All public seed nodes down??  (Read 16116 times)

0 Members and 1 Guest are viewing this topic.

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
remove mine.. I had to put it down due to server / hosting moves.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
https://github.com/abitmore/bitshares-2/commit/aa844f56faac4dda0d542520a672c4704fb0e617
I applied this one-liner change and it causes a compile error. I mentioned the error in the telegram channel.

This is the error messages you posted in Telegram:
Code: [Select]
In file included from /root/bitshares-2/libraries/fc/include/fc/log/logger.hpp:5:0,
                 from /root/bitshares-2/libraries/fc/include/fc/exception/exception.hpp:6,
                 from /root/bitshares-2/libraries/fc/include/fc/thread/future.hpp:5,
                 from /root/bitshares-2/libraries/fc/include/fc/thread/task.hpp:2,
                 from /root/bitshares-2/libraries/fc/include/fc/thread/thread.hpp:5,
                 from /root/bitshares-2/libraries/net/node.cpp:61:
/root/bitshares-2/libraries/net/node.cpp: In member function âvoid graphene::net::detail::node_impl::accept_loop()â:
/root/bitshares-2/libraries/fc/include/fc/log/log_message.hpp:161:19: error: expected primary-expression before â(â token
    fc::log_message( FC_LOG_CONTEXT(LOG_LEVEL), FORMAT, fc::mutable_variant_object()__VA_ARGS__ )
But I have no idea what caused it..
OS version? boost version? GCC version?
Try a clean clone?

You can also try to replace that line with:
Code: [Select]
} catch (...) {}
to catch exceptions without logging.
BitShares committee member: abit
BitShares witness: in.abit

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
My witness node has missed a block every day (today it has already missed 2) since June 4th.

I've had several misses on the 4th, 5th and 6th but none since then.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline Thom

Thx for the mention Nico.

BTW, have any of you witnesses noticed any changes to your nodes this week?

My witness node has missed a block every day (today it has already missed 2) since June 4th.

I have looked but see nothing in the disk / log space, memory and cpu use that correlates to the missed blocks.

I didn't spend any time confirming this, but I noticed a very odd (coincidence?) of me checking the Telegram bot on my WiFi connected cell phone to a single missed block. More than once I would pick up the phone, scroll over to the Telegram app, bring up the bot and boom! a missed block would occur. I dismissed it as coincidence, but was I too hasty? Seems like a stretch they are related tho...

Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline wackou

Shouldn't we build more nodes using the fund accumulated by "refund" worker?

Either this, or ask witnesses to provide a seed node on top of the witness node, and vote out those who don't.

If the first case, then I would also fund Thom, who's been providing 4 seed nodes for a long time now without any sort of compensation.
Please vote for witness wackou! More info at http://digitalgaia.io

Offline ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 2300
    • View Profile
  • BitShares: jademont
the latter two should be removed.
faucet.bitshares.org does not exist anylonger
and openledger does not provide a public seed node.

Shouldn't we build more nodes using the fund accumulated by "refund" worker?
BTS committee member:jademont

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
we should get these out of the default seed node list for the next update ..

Happy to remove 104.168.154.160:50696 from the default list as it not playing nice,  my other seed node is solid.

I confirm that my seed-node 185.25.22.21:1776 should be removed from the list also... 

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
the latter two should be removed.
faucet.bitshares.org does not exist anylonger
and openledger does not provide a public seed node.

Offline wackou

thanks guys on the quick reaction time!

@dannotestein are you the one in charge of the following seed nodes?

seed.blocktrades.us:1776
bitshares.openledger.info:1776
faucet.bitshares.org:1776

if not, do you happen to know who is?
Please vote for witness wackou! More info at http://digitalgaia.io

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
there are quite a few seed nodes down or stuck again...

@lafona @puppies @betax @liondani @cube @iHashFury @Harvey

http://status.bitsharesnodes.com/

@abit was working on a patch but it has a compile problem. Abit, have you fixed it?

I thought I had replied earlier..

Code: [Select]
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git checkout 2.0.160328
git submodule update --init --recursive
git cherry-pick aa844f56faac4dda0d542520a672c4704fb0e617
cmake .
make

I cannot find the commit aa844f56faac4dda0d542520a672c4704fb0e617.  Can you show me the direct link to aa844f56faac4dda0d542520a672c4704fb0e617?
https://github.com/abitmore/bitshares-2/commit/aa844f56faac4dda0d542520a672c4704fb0e617

I applied this one-liner change and it causes a compile error. I mentioned the error in the telegram channel.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
there are quite a few seed nodes down or stuck again...

@lafona @puppies @betax @liondani @cube @iHashFury @Harvey

http://status.bitsharesnodes.com/

@abit was working on a patch but it has a compile problem. Abit, have you fixed it?

I thought I had replied earlier..

Code: [Select]
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git checkout 2.0.160328
git submodule update --init --recursive
git cherry-pick aa844f56faac4dda0d542520a672c4704fb0e617
cmake .
make

I cannot find the commit aa844f56faac4dda0d542520a672c4704fb0e617.  Can you show me the direct link to aa844f56faac4dda0d542520a672c4704fb0e617?
https://github.com/abitmore/bitshares-2/commit/aa844f56faac4dda0d542520a672c4704fb0e617
BitShares committee member: abit
BitShares witness: in.abit

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
there are quite a few seed nodes down or stuck again...

@lafona @puppies @betax @liondani @cube @iHashFury @Harvey

http://status.bitsharesnodes.com/

@abit was working on a patch but it has a compile problem. Abit, have you fixed it?

I thought I had replied earlier..

Code: [Select]
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git checkout 2.0.160328
git submodule update --init --recursive
git cherry-pick aa844f56faac4dda0d542520a672c4704fb0e617
cmake .
make

I cannot find the commit aa844f56faac4dda0d542520a672c4704fb0e617.  Can you show me the direct link to aa844f56faac4dda0d542520a672c4704fb0e617?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
there are quite a few seed nodes down or stuck again...

@lafona @puppies @betax @liondani @cube @iHashFury @Harvey

http://status.bitsharesnodes.com/

@abit was working on a patch but it has a compile problem. Abit, have you fixed it?

I thought I had replied earlier..

Code: [Select]
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git checkout 2.0.160328
git submodule update --init --recursive
git cherry-pick aa844f56faac4dda0d542520a672c4704fb0e617
cmake .
make
BitShares committee member: abit
BitShares witness: in.abit

Offline Harvey

  • Sr. Member
  • ****
  • Posts: 244
    • View Profile
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:wss://128.199.143.47:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:ws://128.199.143.47:2018

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
there are quite a few seed nodes down or stuck again...

@lafona @puppies @betax @liondani @cube @iHashFury @Harvey

http://status.bitsharesnodes.com/

@abit was working on a patch but it has a compile problem. Abit, have you fixed it?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.