-
chile09[m]
how to troubleshoot not receiving transactions on Whonix
-
selsta
first step would be to check the transaction id on xmrchain.net
-
chile09[m]
ok it's there
-
chile09[m]
sync_info shows target at 43.00%
-
chile09[m]
Doesn't look like the entire blockchain is downloaded
-
chile09[m]
could that be why?
-
chile09[m]
ok now it says 100% but the transaction is not there
-
chile09[m]
Do you need to eneter the block height and block hash along with the transaction hash?
-
selsta
You will need a fully synced node before the transaction shows up.
-
selsta
Alternatively you can connect to a remote node.
-
chile09[m]
It showed fully synced but is not showing the transaction
-
nioc
daemon needs to be synced and then wallet needs to be synced with the daemon
-
chile09[m]
daemon and wallet were both showing as synced but no transaction showing
-
selsta
chile09[m]: if you were at 44% previously you won't be fully synced up a couple minutes later
-
selsta
please post the output of "status"
-
chile09[m]
When running monerod via cli, there is an error message that keeps appearing
-
chile09[m]
WARNING: Insufficient free space to extend database !!: 235 MB available, 1024 MB needed
-
selsta
maybe it stopped syncing because you are out of disk space?
-
chile09[m]
is it related to disk space or RAM
-
selsta
disk space
-
chile09[m]
its 100 GB?
-
selsta
yes, and 30gb pruned
-
selsta
you can start monerod with --prune-blockchain to prune it
-
chile09[m]
can I delete the existing one to start a fresh d/l of the pruned blockchain?
-
selsta
yes
-
chile09[m]
is it referring to disk space available with a specific folder or the entire disk
-
selsta
do you have specific disk space limits on folders?
-
selsta
if it's a VM you have to increase the VM disk space
-
chile09[m]
the problem is that it's maxed out
-
chile09[m]
it's already at system storage max size which is ~ 10 GB
-
chile09[m]
It's asking for 1 GB but I'm not sure if that's the end of it in terms of demand for space
-
chile09[m]
I could definitely find 1 GB to clear
-
selsta
you need 30GB free space for a pruned node and 100GB for an unpruned one
-
selsta
.merges
-
xmr-pr
3379
-
bevanoff[m]
Why is QtQmlModels needed for build?
-
selsta
-
bevanoff[m]
Ah thanks
-
chile09[m]
There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack, or your computer's time is off. Or it could be just sheer bad luck.
-
chile09[m]
^what do?^
-
chile09[m]
A reboot seems to have fixed it
-
chile09[m]
and no it's broken again
-
bevanoff[m]
Sounds like your daemon is disconnecting from the network. Prolly need a log to figure out why
-
chile09[m]
sync_info returns 100% now but the wallet doesn't show any balance
-
selsta
please post the output of "status" or "sync_info"
-
chile09[m]
Height: 1151452/1151452 (100.0%) on mainnet, not mining, net hash 28.07 MH/s, v3, 4(out)+0(in) connections, uptime 0d 0h 53m 16s
-
chile09[m]
^status^
-
-
chile09[m]
^sync_info^
-
selsta
you are not at the correct block height
-
selsta
you don't have any synced peers
-
selsta
so it thinks it is at 100%
-
selsta
do you have enough disk space now?
-
chile09[m]
yeah I increased the disk space and am not getting any further disk space related errors
-
selsta
any monerod error messages?
-
chile09[m]
W There were 0 blocks in the last 90 minutes, there might be large hash rate changes, or we might be partitioned, cut off from the Monero network or under attack, or your computer's time is off. Or it could be just sheer bad luck.
-
moneromooo
Odd you'd have only peers claiming height 1. Might be the asshole again.
-
chile09[m]
what?
-
selsta
moneromooo: if the daemon blocks legit peers for whatever reason only height 1 peers would be leftover
-
moneromooo
I guess. But I would not expect there to be more htan one or two of these at once.
-
moneromooo
chile09[m]: restart with --log-level 1. See if there are errors in the log.
-
moneromooo
If so, paste them to some site (matrix.org works).
-
chile09[m]
isn't log level 1 less verbose
-
chile09[m]
what about level 4
-
moneromooo
1 is enough to se consensus errors. 4 is spammy and unnecessary here.
-
chile09[m]
ok
-
chile09[m]
what am I looking for here
-
moneromooo
Lines with "ERROR" in them.
-
chile09[m]
ok its going mach 15 right now
-
chile09[m]
W -> warning E-> error
-
moneromooo
Yes, the console shortens the messages.
-
chile09[m]
sent block ahead of expected height
-
moneromooo
Then it's likely the asshole, or a bug... Restart with --log-level 2 and paste the log from the process start till the line sauying "ahead of expected height".
-
chile09[m]
the asshole = the source of the problem?
-
chile09[m]
Full command -> DNS_PUBLIC=tcp TORSOCKS_ALLOW_INBOUND=1 torsocks monerod --p2p-bind-ip 127.0.0.1 --no-igd --prune-blockchain --log-level 2
-
moneromooo
Someone's known to spin up many modes lying and sending bad data to try and annoy monero users.
-
chile09[m]
there's no blacklist mechanism?
-
selsta
--enable-dns-blocklist
-
chile09[m]
is that a monerod flag
-
selsta
yes
-
chile09[m]
seems to be flowing now although I can see % progress
-
chile09[m]
can't*
-
chile09[m]
will the wallet sync with the daemon
-
selsta
chile09[m]: post "sync_info" output again
-
-
selsta
are you sure you added --enable-dns-blocklist?
-
chile09[m]
no I didn't why
-
chile09[m]
crappy peers again?
-
selsta
I don't know why your node loses all good nodes
-
selsta
yea, half of your peers are bad peers
-
selsta
the others are on height 0
-
selsta
ok try adding --enable-dns-blocklist and --out-peers 32
-
chile09[m]
what is the --out-peers 32 flag
-
chile09[m]
can you explain it
-
selsta
your daemon will connect to more peers
-
chile09[m]
ok
-
selsta
normally all this is not necessary but like I said don't know problem yet
-
chile09[m]
could it be the torsocks connection?
-
selsta
I don't know, peers can be dropped if the connection speed is too slow
-
selsta
but some people synced fine with torsocks
-
chile09[m]
this is using whonix
-
chile09[m]
btw
-
selsta
not familiar with whonix but should be fine