Hi,one of my nodes keeps repeating this message in the logs: "Unable to send transaction(s), no available connections", it is syncing correctly though and tried flush_txpool but didn't help, anybody knows how to fix this ?

you say that it is syncing

you can't send a tx until it is synced

No it's fully synced

since I am only first level help, lol, you can try exiting and restarting your node

lol i've tried that

not that many people on at this time

maybe Mochi102 can help, he is a nice and helpful guy

refactor_ring, you can just ignore that message

It's not saying that about your transactions.

It's a network thing.

Very safe to ignore.

top level help :)

Ha great, it's spamming my logs quite a bit

I do see that there are no incoming connections, could that be related ?

nope

refactor_ring: do you have tor, i2p setup on that node?

selsta, no it does however use the add-exclusive-node configuration

why?

it's on my local network and connects to my open node

it's a weird setup, why not directly connect to the open node with your wallets?

to speed up syncing, internet at my home is spotty at times

can't you just add it as priority node instead of exclusive node?

if your daemon only has a single peer the experience will be spotty

that's why you get the message

Ah ok that makes sense, I also liked this setup because it acts as a proxy of sorts

I will try the priority node instead, thanks!

setting it as priority node should solve the problem because your node will have more peers that add resilience

Hello dear monero channel: I need to use get_accounts function like that: '{"jsonrpc":"2.0","id":"0","method":"get_accounts","params":{"tag":"d*"}}' i want to list accounts, which tags starts with d. "d*" is not worked. Any way for this?

If you mean a regular expression, then no. It'd be fairly easy to add and might actually be useful...

moneromooo, can you push this case to monero github?

ok

thanks you. it will be very very useful.

Hello. I am trying to start my node, within Whonix (Gateway + Workstation). I am running into a problem. For 2 times already, the synch process fails at a certain point (68% first time, 70% second time) with monerod giving the following error:

INFO: logging contrib/epee/src/mlog.cpp:273 New log categories: *WARNING, net:FATAL, net.http:FATAL, net:ssl:FATAL, ..... etc

now the blockchain is corrupted and I should start again from the beginning. But is there a way to resume the synch from a certain block number, rather than from the first?

(I am talking using the cli "monerod" command)

Thanks you in advance for any help

re

Does dmesg show any hardware I/O issue ?

no, it's a virtual machine in KVM

Is the directory you're syncing to weird in any way, like filesystem, mount point to external hw, etc ?

its' the default .bitmonero/lmdb/

I guess I am asking if there is a way to use a damaged blockchain (where only the last block or last few blocks are damaged) or it is necessary to restart from 0.

I assume the answer to my question is "no" then.

You could try running once with --db-salvage, it might help.

But in general, there are no checkpoints, you can't magically restart from an old block height.

monerod is supposed to not leave the db in a corrupted state if it crashes though.

If it doesn't show errors and dmesg doesn't either, you may want to enable core files, assuming they're not. Then see if a core is left.

If one is: gdb /path/to/monerod /path/to/core

then: bt

thanks mooo. I will try :)

i heard that zcash had found a way, with halo arc to circumvent the "trusted setup"? Is this correct?

slave_blocker: Halo 2 has no trusted setup

@runfox I've received XMR from fixedfloat, it works.