02:08:22 <refactor_ring> 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 ?
02:17:49 <nioc> you say that it is syncing  
02:17:52 <nioc> you can't send a tx until it is synced
02:18:43 <refactor_ring> No it's fully synced
02:19:26 <nioc> since I am only first level help, lol, you can try exiting and restarting your node
02:20:26 <refactor_ring> lol i've tried that
02:22:15 <nioc> not that many people on at this time
02:22:51 <nioc> maybe Mochi102 can help, he is a nice and helpful guy
02:23:14 <Mochi102> refactor_ring, you can just ignore that message
02:23:46 <Mochi102> It's not saying that about your transactions.
02:23:52 <Mochi102> It's a network thing.
02:23:57 <Mochi102> Very safe to ignore.
02:24:13 <nioc> top level help :)
02:24:47 <refactor_ring> Ha great, it's spamming my logs quite a bit
02:25:46 <refactor_ring> I do see that there are no incoming connections, could that be related ?
02:25:58 <nioc> nope
05:22:21 <selsta> refactor_ring: do you have tor, i2p setup on that node?
05:33:34 <refactor_ring> selsta, no it does however use the add-exclusive-node configuration
05:33:50 <selsta> why?
05:34:33 <refactor_ring> it's on my local network and connects to my open node
05:35:34 <selsta> it's a weird setup, why not directly connect to the open node with your wallets?
05:36:09 <refactor_ring> to speed up syncing, internet at my home is spotty at times
05:36:34 <selsta> can't you just add it as priority node instead of exclusive node?
05:37:24 <selsta> if your daemon only has a single peer the experience will be spotty
05:37:32 <selsta> that's why you get the message
05:38:33 <refactor_ring> Ah ok that makes sense, I also liked this setup because it acts as a proxy of sorts
05:39:03 <refactor_ring> I will try the priority node instead, thanks!
05:40:41 <selsta> setting it as priority node should solve the problem because your node will have more peers that add resilience
14:01:32 <NakedKing> 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?
14:03:51 <moneromooo> If you mean a regular expression, then no. It'd be fairly easy to add and might actually be useful...
14:04:30 <NakedKing> moneromooo, can you push this case to monero github?
14:04:50 <moneromooo> ok
14:04:59 <NakedKing> thanks you. it will be very very useful.
14:35:40 <makkiato> 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:
14:36:18 <makkiato> INFO: logging contrib/epee/src/mlog.cpp:273  New log categories: *WARNING, net:FATAL, net.http:FATAL, net:ssl:FATAL, ..... etc
14:37:07 <makkiato> 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?
14:37:19 <makkiato> (I am talking using the cli "monerod" command)
14:37:25 <makkiato> Thanks you in advance for any help
14:37:39 <Awaru> re
14:40:59 <moneromooo> Does dmesg show any hardware I/O issue ?
14:43:37 <makkiato> no, it's a virtual machine in KVM
14:44:15 <moneromooo> Is the directory you're syncing to weird in any way, like filesystem, mount point to external hw, etc ?
14:46:11 <makkiato> its' the default .bitmonero/lmdb/
14:49:44 <makkiato2> 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.
15:01:50 <moneromooo> I assume the answer to my question is "no" then.
15:02:10 <moneromooo> You could try running once with --db-salvage, it might help.
15:02:29 <moneromooo> But in general, there are no checkpoints, you can't magically restart from an old block height.
15:02:55 <moneromooo> monerod is supposed to not leave the db in a corrupted state if it crashes though.
15:03:40 <moneromooo> 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.
15:03:50 <moneromooo> If one is: gdb /path/to/monerod /path/to/core
15:03:53 <moneromooo> then: bt
15:05:24 <makkiato2> thanks mooo. I will try :)
19:29:16 <slave_blocker> i heard that zcash had found a way, with halo arc to circumvent the "trusted setup"? Is this correct?
19:53:53 <kayabaNerve> slave_blocker: Halo 2 has no trusted setup
22:22:39 <kobe> @runfox I've received XMR from fixedfloat, it works.