remove mine.. I had to put it down due to server / hosting moves.

Quote from: cube on June 10, 2016, 09:00:51 AM

Quote from: abit on June 10, 2016, 08:45:15 AM
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:

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:

} catch (...) {}

to catch exceptions without logging.

Quote from: Thom on June 10, 2016, 03:54:50 PM
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.

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...

Quote from: ripplexiaoshan on June 10, 2016, 01:23:50 PM
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.

Quote from: xeroc on June 10, 2016, 11:06:57 AM
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?

Quote from: iHashFury on June 09, 2016, 04:02:25 PM

Quote from: xeroc on June 09, 2016, 03:30:50 PM
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... 

the latter two should be removed.
faucet.bitshares.org does not exist anylonger
and openledger does not provide a public seed node.

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?

Quote from: abit on June 10, 2016, 08:45:15 AM

Quote from: cube on June 10, 2016, 03:22:35 AM

Quote from: abit on June 09, 2016, 06:01:39 PM

Quote from: cube on June 09, 2016, 04:21:21 PM

Quote from: wackou on June 09, 2016, 03:00:49 PM
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 Expand


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.

Quote from: cube on June 10, 2016, 03:22:35 AM

Quote from: abit on June 09, 2016, 06:01:39 PM

Quote from: cube on June 09, 2016, 04:21:21 PM

Quote from: wackou on June 09, 2016, 03:00:49 PM
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 Expand


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

Quote from: abit on June 09, 2016, 06:01:39 PM

Quote from: cube on June 09, 2016, 04:21:21 PM

Quote from: wackou on June 09, 2016, 03:00:49 PM
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 Expand


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?

Quote from: cube on June 09, 2016, 04:21:21 PM

Quote from: wackou on June 09, 2016, 03:00:49 PM
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..


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


mine is online now.

Quote from: wackou on June 09, 2016, 03:00:49 PM
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?