-
selsta
vtnerd: not getting this transactions showing up late in mempool issue on testnet
-
selsta
I wonder if someone spun up a lot of nodes that blackhole D++ transactions
-
moneromooo
There are a lot of lying nodes fwiw, which claim your own height.
-
moneromooo
They do relay blocks IIRC. Not sure about txs.
-
tombradyontap[m]
Is there a guide to help with updating to 17.0 using CLI wallet/daemon isolation with Qubes + Whonix?
-
tombradyontap[m]
-
selsta
moneromooo: do you mean --no-sync?
-
moneromooo
No. If --no-sync causes that, it should be killed (or fixed at least).
-
selsta
no, --no-sync does not cause that, I was just asking what "lying" nodes you are talking about
-
moneromooo
They claim your own height.
-
selsta
so someone modified the source to do that?
-
moneromooo
(and it's almost certainly not theirs)
-
moneromooo
Not mine.
-
grydz
selsta, I've just seen your problem while doing a transfer on testnet:
LedgerHQ/app-monero #80. This error also occurred to me when I was playing too much with the hardfork height. Are you using your own node?
-
selsta
grydz: yes I was using my own node
-
grydz
Is there any public testnet node running 0.17.0.0? I've lauched my own node but it takes a lot of time to sync testnet :/
-
sarang
I know the xmr.to team runs nodes, but I do not know their update status (ping binaryFate):
community.xmr.to/nodes.html
-
sarang
^ grydz
-
grydz
Thanks sarang, I've tested with testnet.community.xmr.to and I have the same problem "Error: Reason: invalid input". Don't know what version is used by the daemon.
-
grydz
I'll debug using my own node but it remains ~1.2 days before complete sync.
-
Snipa
.merges
-
xmr-pr
Merge queue empty
-
selsta
grydz: they updated their nodes
-
binaryFate
sarang: yes, xmrto testnet node is running v0.17.0.0, since this morning
-
sarang
Thanks binaryFate!
-
sarang
Unfortunate that this error occurs :/
-
sarang
binaryFate: would it be possible to update that page to indicate what versions are being run on each of the nodes?
-
sarang
Perhaps that could be useful, especially for testers
-
binaryFate
I'll see if we can add it to the health status:
community.xmr.to/node/testnet/health/api/v1
-
sarang
oh neat
-
sarang
Just an idea
-
sarang
And probably only important around upgrade times :)
-
binaryFate
we should probably list the health status links on the connection info page too, would be easier to find. For now you can find links here
community.xmr.to look for health status
-
sarang
Yeah, I had missed those health status APIs
-
sarang
Very convenient
-
ErCiccione[m]
-
selsta
E Failed to get 'C:' filesystem name. Error code: 123
-
selsta
anyone seen that error before?
-
selsta
(first message when starting monerod)
-
iDunk
What's the first line in the output of chkdsk c: ?
-
selsta
if I run cmd as admin
-
selsta
The type of the file system is NTFS.
-
iDunk
Well, that error is ERROR_INVALID_NAME "The filename, directory name, or volume label syntax is incorrect." Looks like there's something monerod doesn't like about one (or more) of those things.
-
selsta
volume name has a space
-
selsta
though not sure if that matters
-
iDunk
Hmm, I have four spaces in my volume name and it works fine.
-
selsta
-
selsta
otherwise it’s a normal VM from here ^
-
selsta
but seems to work fine otherwise
-
iDunk
Actually, I get the same error. I'll try with 0.16.0.3 when 0.17.0.0 syncs up. It's not a fatal error here.
-
iDunk
And mine is bare metal.
-
iDunk
On second thought, I won't try with 0.16.0.3 since that code is not there.
-
iDunk
-
selsta
xiphon ^
-
selsta
I get `Failed to get 'C:' filesystem name. Error code: 123` on NTFS file system, iDunk gets similar message
-
iDunk
monerod also thinks my USB attached ssd is a spinny drive on Linux, but that's a different issue.
-
selsta
yea saw similar with VPS that has SSD
-
xiphon
-
xiphon
does this help?
-
iDunk
I'll build and test.
-
xiphon
thanks
-
iDunk
xiphon: Your patch fixes the error.
-
selsta
xiphon: can you also open
monero-project/monero #6834 against branch?