Test

Unknown command 'test' Try again.

XD

after giving up on getting my monerod to work for 6 months, then seeing 5 or so stability fixes in the latest linux cli release, I gave monero another shot at syncing today and I am still running into the problem of it consuming 100% of 1 cpu core and monero.log saying:

2021-07-03 03:24:28.411 [P2P9] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1680 Synced 2313976/2396226 (96%, 82250 left)

2021-07-03 03:25:26.669 [P2P9] WARNING global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2910 monerod is now disconnected from the network

and it stops syncing

If anybody would like to help me track down what is going on I would love to help in any way I can

I am however pretty dumb so you'll have to dumb it down for me :)

thanks, sethsimmons

selsta: is it known, that the default ubuntu-latest is now 20.04? If no, should we revert to 18 explicitly?

(in Github actions that is)

Anyways, in order to be able to test various Boost versions, I need to use various Ubuntu versions explicitly anyway, since a given year's version typically only supports up to 2 Boost versions.

OK, now I see why we shouldn't roll back to 18.04 for now - because it doesn't build under it. I'll start a couple of PRs that address this.

DeanGuss: Have you already tried using a different drive to sync the blockchain to?

... or an SSD?

HI guys, I hope you all are doing well. I want to experiment with Monero, but both faucets seem to be down. Anyone experiencing similar issues?

Dunno, but testnet difficulty should be tiny, you'll get blocks fast.

<moneromooo "Dunno, but testnet difficulty sh"> I didn't get what you meant at first, but now I do. Thanks, I will try this.

dEBRUYNE: no I have not tried another drive. It's a 2tb usb sata external drive... curiously I get no info when I do hdparm -I /dev/sdb

I will at least try moving the usb to a different port/controller

DeanGuss, I have bad experience with external drives like this one. Even the USB cable can be a culprit at times.

or for instance too little power given to the drive.

interesting theory mj-xmr, I will look into one of those external power cables as well. Thank you

DeanGuss, the 2nd case (re: power) is rather the PC's problem. I had this on some low powered fanless PCs.

But all of this might be a false clue.

Justr sth to try out.

That's a pretty good clue, this is an old, fanless, low power 'nettop' type pc

oops

I slapped a 220G SSD in an old Compaq laptop, x86_64 Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz GenuineIntel GNU/Linux, running monerod, a few wallet-rpc, Apache, MySQL and some other stuff without breaking a sweat. That SSD save this old piece of junk from the scrap yard.

.merge+ 7762

Added

selsta: I guess my question in 7768 is somewhat hard. Do you think it makes sense to support (via CI) Ubuntu 16.04 for the next 3 months?

It can be removed at any time of course.

I mean our support.

I could also imagine compiling Boost from source. I have scripts for that.

i would use ubuntu 20.04 + boost compiled from source

For boost, ok.

selsta: 18.04 still needs to be checked, regardless of boost, to avoid problems like with 7762/. It would detect it

But in that case 18.04 doesn't need the "matrix", just plain old default libboost-all-dev

Since these are 2 separate cases, I'll create another 2 PRs and close 7768. One will be 18.04 and the other one will be 20.04 ("latest") with 2 extreme boost versions.

Does it sound OK?