00:22:05 <Dean_Guss> turns out my 1 core @ 100% monerod problem is back.  It happened right after the Tor process exited suddenly.  SystemD attempted to restart the service a few times and 5 minutes later it was back up, and since then monerod has had 1 thread taking 100% of 1 cpu core
00:22:10 <Dean_Guss> https://paste.debian.net/hidden/7c8722ec/
00:22:25 <Dean_Guss> obviously I need to figure out why tor is crashing, but also this seems like a monero bug
00:25:21 <Dean_Guss> ExecStart=/usr/bin/torsocks /usr/local/bin/monerod --config-file /etc/monero/monero.conf --non-interactive --pidfile /run/monero/monero.pid
00:25:28 <Dean_Guss> is how systemd is calling monerod
01:48:23 <selsta> Dean_Guss: does it also happen without torsocks?
01:49:27 <selsta> Also any reason you are running monerod over Tor instead of using --tx-proxy ?
01:50:17 <Dean_Guss> I just haven't used the new option yet
01:50:22 <Dean_Guss> I will try
01:51:12 <selsta> ./monerod --tx-proxy tor,127.0.0.1:9050 --add-peer xwvz3ekocr3dkyxfkmgm2hvbpzx2ysqmaxgter7znnqrhoicygkfswid.onion:18083 --add-peer zbjkbsxc5munw3qusl7j2hpcmikhqocdf4pqhnhtpzw5nt5jrmofptid.onion:18083
01:51:38 <selsta> If you also want anonymous inbound connections see https://github.com/monero-project/monero/blob/master/ANONYMITY_NETWORKS.md
01:51:52 <Dean_Guss> ok ty
01:53:03 <selsta> if this is on a server it would be cool if you add anonymous inbound connections, monero benefits from every i2p / tor node :)
01:54:54 <Dean_Guss> OK i will test it out.. I am pretty low resources though so I may turn it off again if it uses too much cpu/ram
05:41:24 <DeanGuss> selsta: --tx-proxy arg                        Send local txes through proxy:
05:41:38 <DeanGuss> I need more than just to send my own transactions through tor
05:41:45 <DeanGuss> I want all communications going through tor
05:46:01 <TamaraneanGirl> Why are #monero-community:matrix.org and #freenode_#monero-dev:matrix.org locked? Does it have anything to do with the spam about power levels?
05:46:59 <TamaraneanGirl> Bridge is broken?
05:47:21 <Mochi101> spam
05:47:24 <TamaraneanGirl> Spam?
05:47:45 <Mochi101> Someone is spamming the channel.
05:47:46 <TamaraneanGirl> Is there a motive?
05:48:00 <Mochi101> For the spam?
05:48:09 <Mochi101> Just general disruption.
05:49:06 <Mochi101> Nothing to do with Matrix though.
09:44:34 <kayront> https://romotow.com/
09:44:36 <kayront> when XMR?
09:44:38 <kayront> :D
12:57:55 <Lyza> just fyi spn* and sel* are the only two i2p mipseeds I've been able to reliable connect to for the last ~24ish hours
16:19:47 <ErCiccione> moneromooo could you give my IRC hande voice in -dev? (erciccione[irc])
16:20:48 <moneromooo> No. Needs an op.
16:20:59 <dEBRUYNE> You're an OP :p
16:21:08 <moneromooo> :o
16:21:20 <ErCiccione> aren't you OP in -dev?
16:21:22 <ErCiccione> :P
16:21:27 <moneromooo> sorry, didn't realize, done now.
16:21:38 <moneromooo> I thought it was core team only.
19:15:49 <john_r365> win 4
19:36:13 <selsta> Lyza: I just setup a second i2p mipseed, so hopefully s3l* will also be reliable in the future
19:55:21 <gingeropolous> mine says i2pzero is already running
19:56:23 <gingeropolous> is there a way to get status or any sort of info on if its doing what it should?
19:56:33 <gingeropolous> stupid daemons just lurking in the top shadows
19:57:32 <selsta> gingeropolous: can you run print_cn on daemon?
19:57:45 <selsta> also according to Lyza your i2p node is reliable
19:57:48 <gingeropolous> on monerod?
19:57:58 <selsta> yes on monerod
19:58:30 <gingeropolous> yeah i can run print_cn
19:58:40 <gingeropolous> im actively screening for AHP on this node
19:58:46 <selsta> does it show i2p peers?
19:59:04 <Lyza> selsta that's great can I get the full address to add to my daemon manually? also I'm running a connectable i2p node if y'all wanted to add it. Should have pretty good up time and I plan to run it for the foreseeable future
20:00:21 <selsta> s3l6ke4ed3df466khuebb4poienoingwof7oxtbo6j4n56sghe3a.b32.i2p
20:00:26 <Lyza> ty
20:00:30 <selsta> but I just started it, this i2p stuff takes time
20:00:36 <selsta> so might not work yet
20:00:41 <Lyza> yeah no worries
20:02:17 <gingeropolous> selsta, yeah i got an i2p peer
20:02:55 <selsta> Lyza: theoretically it should work with only adding one i2p peer
20:02:59 <Lyza> s3l is already working :)
20:03:15 <Lyza> it does but i2p peers get dropped a lot
20:03:15 <selsta> nice :D
20:03:45 <selsta> I wonder if this is a bug or if this is just because we barely have i2p / tor peers yet
20:03:51 <Lyza> I still have this issue and ahve to keep several nodes added as priority nodes in order to be able to reliable send i2p transactions https://github.com/monero-project/monero/issues/6631
20:04:11 <selsta> gingeropolous: you can also setup tor anonymous inbound
20:04:18 <selsta> on the same server
20:04:26 <Lyza> it could be a lack of peers but it appears imo that the daemon needs to try harder to maintain at elsat one outbound i2p connection at all times
20:04:35 <gingeropolous> selsta, is there copypasta for that?
20:04:44 <selsta> almost, can give you one
20:04:55 <selsta> ubuntu?
20:05:09 <gingeropolous> ill get the parmesan
20:05:12 <gingeropolous> yeah, ubuntu
20:05:35 <gingeropolous> but im loggin off here in a sec, and my bouncer is stupid
20:05:49 <gingeropolous> sometimes it bounces stuff after i log... sometimes not
20:06:43 <gingeropolous> so ploppin on a repo would be ideal :)
20:26:10 <viperperidot[m]> If I synced the monero blockchain to 65% and then downloaded the raw blockchain and imported it, would my sync/verification start at 65% where I left off or restart from 0%?
20:27:00 <selsta> I don’t think the raw blockchain is updated currently.
20:31:42 <viperperidot[m]> So would it still pick up verification where I left off and then once it hit the height of the imported blockchain download the remaining part from peers?
20:32:35 <selsta> the blockchain.raw on getmonero.org is apparently outdated
20:32:55 <selsta> I would just sync with daemon, if possible
20:35:19 <Inge-> sync with daemon and possible add more out-peers ?
20:36:57 <viperperidot[m]> Im trying but it is just really really slow, it will take over a month at current pace. I have my out peers set to 16.
20:37:08 <asymptotically> viperperidot[m]: do you have a hard drive or an ssd?
20:37:19 <viperperidot[m]> ssd
20:37:58 <selsta> raspberry IIRC?
20:38:41 <viperperidot[m]> Yes but I was having very slow speeds with my laptop as well
20:40:44 <selsta> does your laptop have ssd?
20:41:02 <selsta> you can try setting out_peers to 64
20:43:01 <selsta> this is with v0.17.1.1 I assume?
20:43:04 <viperperidot[m]> I was using the external ssd for that as well
20:43:09 <viperperidot[m]> Yes latest release
20:43:31 <asymptotically> external ssd is your problem
20:45:00 <kayront> yes, monero without a fast disk is a bit of a nightmare
20:45:42 <selsta> still surprised that it makes that much of a difference, seeing that syncing in 2h+ is possible with nvme and good hardware
20:46:41 <kayront> my theory is that an hdd will seek a lot because of the constant looking up for older chain data (decoys)
20:47:16 <kayront> obviously hardly a factor with a fast ssd/nvme
20:47:45 <artefact> i suspect page cache plays a huge role as well
20:48:14 <kayront> well, i got a caching NVMe in front of a zpool, and that's the saving grace
20:48:27 <kayront> but i can always tell when monerod is busy (data not in nvme cache)
20:48:37 <kayront> and by tell i mean hear :D
20:50:04 <Inge-> spinning rust ftw
20:50:52 <kayront> it's very painful after a reboot (thankfully, rare) as there's nothing in cache then
20:51:06 <kayront> or restoring an old wallet, that's gonna take its sweet time
23:39:06 <yanmaani> Doesn't monero do assumevalid?