Monero is a disaster

I previously wrote about the mess of stacktraces in monerod's
logs: <https://wibblement.blogspot.com/2023/02/monero-log-files-are-mess.html>.

I'm still having trouble getting back the basic capability
to transact.  Monero has bit-rot built in.  The node software
refuses to run if it finds itself "old".  The wallet software
refuses to work with old node software.  The user is thus
forced, if they want to retain a capability to transact, into
continually updating the software in their trusted computing base.
As basic security process design, this is wrong, and puts
the entire Monero edifice firmly in the "shitcoin" category.

I've just compiled from tag v0.18.1.2, the latest tag, and started
a fresh `monerod` instance.  After around a day's syncing (fair
enough), it went back to filling its log, `bitmonero.log` in
the instance's data directory, with these stacktraces, lots
of them, and ongoing:


2023-03-17 08:03:06.478 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1686    Synced 2831548/2843826 (99%, 12278 left)
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:133  Exception: std::bad_alloc
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:134  Unwound call stack:
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:133  Exception: std::bad_alloc
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:134  Unwound call stack:
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:133  Exception: std::bad_alloc
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:134  Unwound call stack:
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [1]  0x116) [0x55efcbc6c476]:__cxa_throw+0x116) [0x55efcbc6c476]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [2] monerod(+0x116f76) [0x55efcbccdf76]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [3] monerod(+0x84a040) [0x55efcc401040]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [4] monerod(+0x847656) [0x55efcc3fe656]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [5] monerod(+0x5af0a5) [0x55efcc1660a5]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [6] monerod(+0x5b0023) [0x55efcc167023]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [7] monerod(+0x59721b) [0x55efcc14e21b]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [8] monerod(+0x597425) [0x55efcc14e425]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [9] monerod(+0x5974c8) [0x55efcc14e4c8]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [10] monerod(+0x52e8bc) [0x55efcc0e58bc]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [11] monerod(+0x5f4990) [0x55efcc1ab990]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [12] monerod(+0x5f507c) [0x55efcc1ac07c]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [13] monerod(+0x532ad4) [0x55efcc0e9ad4]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [14] monerod(+0x55c8cf) [0x55efcc1138cf]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [15] monerod(+0x4ed0be) [0x55efcc0a40be]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [16] monerod(+0x4f3914) [0x55efcc0aa914]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [17] monerod(+0x1cefab) [0x55efcbd85fab]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [18] monerod(+0x1d1853) [0x55efcbd88853]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [19] monerod(+0x4a8b69) [0x55efcc05fb69]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [20] monerod(+0x4aaba9) [0x55efcc061ba9]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [21] monerod(+0x1699c5) [0x55efcbd209c5]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [22] monerod(+0x170773) [0x55efcbd27773]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [23] monerod(+0x46d7be) [0x55efcc0247be]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [24]  0xb787) [0x7f1343714787]:_64-linux-gnu/libboost_thread.so.1.74.0(+0xb787) [0x7f1343714787]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [25]  0x7ea7) [0x7f134337dea7]:_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f134337dea7]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172      [26]  0x3f) [0x7f134329ba2f]:_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f134329ba2f]
2023-03-17 08:03:06.479 [P2P5]  INFO    stacktrace      src/common/stack_trace.cpp:172  
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [1]  0x116) [0x55efcbc6c476]:__cxa_throw+0x116) [0x55efcbc6c476]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [2] monerod(+0x116f76) [0x55efcbccdf76]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [3] monerod(+0x84a040) [0x55efcc401040]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [4] monerod(+0x847656) [0x55efcc3fe656]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [5] monerod(+0x5af0a5) [0x55efcc1660a5]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [6] monerod(+0x5b0023) [0x55efcc167023]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [7] monerod(+0x59721b) [0x55efcc14e21b]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [8] monerod(+0x597425) [0x55efcc14e425]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [9] monerod(+0x5974c8) [0x55efcc14e4c8]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [10] monerod(+0x52e8bc) [0x55efcc0e58bc]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [11] monerod(+0x5f4990) [0x55efcc1ab990]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [12]  0xb787) [0x7f1343714787]:_64-linux-gnu/libboost_thread.so.1.74.0(+0xb787) [0x7f1343714787]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [13]  0x7ea7) [0x7f134337dea7]:_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f134337dea7]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172      [14]  0x3f) [0x7f134329ba2f]:_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f134329ba2f]
2023-03-17 08:03:06.479     7f12ccf8d700        INFO    stacktrace      src/common/stack_trace.cpp:172  
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [1]  0x116) [0x55efcbc6c476]:__cxa_throw+0x116) [0x55efcbc6c476]
2023-03-17 08:03:06.479     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:133  Exception: std::bad_alloc
2023-03-17 08:03:06.479     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:134  Unwound call stack:
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [2] monerod(+0x116f76) [0x55efcbccdf76]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [3] monerod(+0x84a040) [0x55efcc401040]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [4] monerod(+0x847656) [0x55efcc3fe656]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [5] monerod(+0x5af0a5) [0x55efcc1660a5]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [6] monerod(+0x5b0023) [0x55efcc167023]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [7] monerod(+0x59721b) [0x55efcc14e21b]
2023-03-17 08:03:06.479     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [8] monerod(+0x597425) [0x55efcc14e425]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [9] monerod(+0x5974c8) [0x55efcc14e4c8]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [10] monerod(+0x52e8bc) [0x55efcc0e58bc]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [11] monerod(+0x5f4990) [0x55efcc1ab990]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [12]  0xb787) [0x7f1343714787]:_64-linux-gnu/libboost_thread.so.1.74.0(+0xb787) [0x7f1343714787]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [13]  0x7ea7) [0x7f134337dea7]:_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f134337dea7]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172      [14]  0x3f) [0x7f134329ba2f]:_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f134329ba2f]
2023-03-17 08:03:06.480     7f12cc58b700        INFO    stacktrace      src/common/stack_trace.cpp:172  
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [1]  0x116) [0x55efcbc6c476]:__cxa_throw+0x116) [0x55efcbc6c476]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [2] monerod(+0x116f76) [0x55efcbccdf76]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [3] monerod(+0x84a040) [0x55efcc401040]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [4] monerod(+0x847656) [0x55efcc3fe656]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [5] monerod(+0x5af0a5) [0x55efcc1660a5]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [6] monerod(+0x5b0023) [0x55efcc167023]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [7] monerod(+0x59721b) [0x55efcc14e21b]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [8] monerod(+0x597425) [0x55efcc14e425]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [9] monerod(+0x5974c8) [0x55efcc14e4c8]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [10] monerod(+0x52e8bc) [0x55efcc0e58bc]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [11] monerod(+0x5f4990) [0x55efcc1ab990]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [12]  0xb787) [0x7f1343714787]:_64-linux-gnu/libboost_thread.so.1.74.0(+0xb787) [0x7f1343714787]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [13]  0x7ea7) [0x7f134337dea7]:_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f134337dea7]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172      [14]  0x3f) [0x7f134329ba2f]:_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f134329ba2f]
2023-03-17 08:03:06.480     7f12c7fff700        INFO    stacktrace      src/common/stack_trace.cpp:172  
2023-03-17 08:03:11.543 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1686    Synced 2831568/2843826 (99%, 12258 left)

I tried running a wallet instance against it nonetheless, but
didn't get very far.  The wallet started scanning the
blockchain for transactions, an O(length) operation apparently
required by Monero's design.  When I checked back, something
had happened, but the information had been deleted from
the console because some dipshit Monero "developer" decided
to draw a picture of a cow instead:



It is literally a lolcow.  Some "developer" has presumed to
go vertical, adding their own little lock function in the
application.  Don't bother about console locking by the OS, people,
Monerotard will draw a picture of a cow for you instead.

So I issued the command `refresh`.  It started scanning again,
displaying its progress.  This isn't visible in the terminal
screenshot because it's done in-place and overwritten.
Then, at a seemingly random point,
it failed, giving error message `Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 141311`.  This is a bad
error message, as until the moment it did that, it was happily talking
to the daemon on the specified port.



Monero is a shitshow.  Like other shitcoins, it has a convincing
web site.  The marketing is full of lies ("specified", "offline wallet",
implicitly "works", etc).
Avoid.




Comments

Post a Comment

Popular posts from this blog

the persistent idiocy of "privileged ports" on Unix

TCP and UDP have ports.  These are 16 bit; there are 65535 or so per IP address. These protocols don't care to differentiate between the ports.  Elsewhere, IANA presumes to operate a process to allocate "well-known" ports in the range 1-1023, "registered ports" in the range 1024-49151, and to reserve the remainder, 49152–65535, for "ephemeral" ports.  The caller end has to have a port, which is how replies get back within the virtual connection, and these are conventionally picked from the ephemeral range by the OS's networking stack. The whole idea of ports is ridiculous, because it allows ISPs to arse around presuming to decide which services they will "not allow".  Anything that allows IPSs to do anything other than shift opaque packets will allow ISPs to meddle and break things, and due to the Law of Meddling, if they can, they will.  I am currently working around an issue with Claro, a pretend ISP, blocking port 5060, allocated to SI
Read more

google is giving more and more 500 errors

Image
Total state capture and moral bankruptcy are not the only problems facing Google.  They are also giving an increasing rate of 500 Internal Server errors.  This is the sort that means they've messed up, but not in a way that they should have messed up.  On the other hand, they have drawn a lovely picture of a robot falling apart. Today's example is from Google Calendar under calendar.google.com.  I was trying to make an appointment, and now I'm doing this. I remember, in 2018, a friend trying to convince me that 500 Internal Server Errors no longer happened, or if they did it was my fault, and that they hadn't seen any for years, and some other things.  They assured me that they would love to see screenshots of such a rare specimen, which I bored them with for a while.  That friend happens to be a Google employee. Well, there are plenty of others posting about Google Calendar on twitter today, including screenshots of 500 Internal Server errors, so I doubt this one is en
Read more

Guernsey Waste in incorrect bag-rejection horror May 6th, 2024

Image
The rubbish collection folk at my new place seem pickier than at other places on Guernsey. Last week, they removed some card packaging that I'd included in the card and paper (plastic) clear bag, and left it on the lane.  This week, they have attached a rejection label entitled "Polite Notice".  Just like modern software-engineered error messages (see attached tag "extremely_general_error_handling"), this does not give a specific reason why the bag was rejected, but instead lists miscellaneous possible "reasons", leaving the victim guessing, or perhaps trying to follow a process of elimination. In this case, some possible reasons, which the label does not claim to be exhaustive ("was most likely because ..."), and of which none apply, are: (i) "did not have the required payment sticker" -- no, I applied to 90 litre sticker; or  (ii) (a) "too heavy" -- no, I estimate it was 3kg, and I easily supported the bag's weight o
Read more