10:38:38 <xyz_> hello
10:40:42 <rottensox> salutations.
10:40:42 <SoiMatter> hi
10:40:44 <SerHack> hi
10:56:34 <nonie> salve
11:38:46 <ErCiccione[m]> So, apparently the biggest Monero community on matrix is about mining, with more than 4000 people and i never heard of it before: #xmrmine:matrix.org
11:40:21 <ErCiccione[m]> oh it's relayed on telegram apparently, so i guess it's a mix of the two platforms. That's why it's so big
13:54:46 <kiwi_7> Hi everyone, I'm getting an error message when trying to run a local node (I've downloaded the blockchain for about 95%), is this the right channel to ask for help?
14:01:26 <nonie> Whats the error message?
14:01:59 <nonie> kiwi_7 -^
14:02:26 <kiwi_7> Error generating CryptonightR code
14:04:21 <kiwi_7> I haven't really found anything by googling, if I increase the log level to 4 it says: Block with hash <id> not found in db
14:04:32 <kiwi_7> But it's not clear to me if that's an error
14:08:36 <gingeropolous> kiwi_7, can you provide more information?
14:08:44 <nonie> But the monerod did not stop syncing, did it?
14:08:48 <gingeropolous> operating system namely. where you got the source code, or binary. etc
14:09:06 <gingeropolous> hardware - are you on a spinny or SSD?
14:09:34 <kiwi_7> I'm running v0.15.0.1-unknown on debian, and I'm downloading the blockchain on a hard drive
14:09:42 <gingeropolous> usually block with hash bug is a corrupt blockchain caused by a windows computer getting its power cord pulled out
14:09:58 <kiwi_7> monerod stopped syncing with that error, and when I try to restart it it returns the same error
14:10:03 <gingeropolous> have u tried restarting the daemon... ok
14:10:31 <gingeropolous> checkout the --help on monerod, there's a recover flag you could try
14:10:35 <kiwi_7> I've also restarted my computer, the last thing monerod spits out before the error message is SYNCRONISATION started
14:10:56 <Mochi101> kiwi_7, are you running a pruned db?
14:11:16 <gingeropolous>  --db-salvage
14:11:31 <kiwi_7> gingeropolous I cannot find the recover flag
14:11:32 <moneromooo> What arch ? x86_64 or other ?
14:11:38 <gingeropolous> so try ./monerod --db-salvage
14:11:38 <kiwi_7> 64 bit
14:11:51 <kiwi_7> Ok I'll try that
14:12:08 <gingeropolous> which should be changed to recover probably. salvage is some serious english
14:12:26 <Mochi101> Salvage is correct.
14:12:34 <Mochi101> Totally broken... trying to salvage it
14:12:36 <moneromooo> If that was an answer to my question, I'll assume it's x86_64 and you don't know other archs exist :)
14:12:37 <kiwi_7> Running monerod with --db-salvage returns the same error unfortunately
14:12:51 <moneromooo> Do you have anything like apparmor or the like running ?
14:13:10 <kiwi_7> No nothing like apparmor (at least to my knowledge)
14:13:17 <gingeropolous> how much free space do you have on your disk?
14:13:19 <kiwi_7> I downloaded monerod through the debian repositories
14:13:30 <gingeropolous> hrmmm
14:13:35 <manifest> smells like some old ass monero relese then
14:13:35 <kiwi_7> 555G avaiable
14:13:56 <manifest> what version of monerod you runnin
14:13:57 <kiwi_7> I'm pretty sure it's the latest version, I'm pulling from debian unstable
14:14:03 <gingeropolous> yeah id try downloading bin straight from getmonero.org or compiling yourself
14:14:06 <kiwi_7> v0.15.0.1
14:14:15 <moneromooo> The two possible causes I see are (1) mrpotect failing and some buffer overflow. Do you know how to use strace ?
14:14:30 <manifest> hmm, guess thats the newest then
14:14:35 <moneromooo> Actually, nvm: strace -o bitmonero.out $YOURCOMMANDHERE
14:14:38 <kiwi_7> moneromooo I've never used strace but I'm willing to try
14:14:52 <moneromooo> Then check near the end of bitmonero.out to see whether mprotect is failing.
14:14:59 <gingeropolous> i'll bow out. seems you've made it past triage
14:16:47 <moneromooo> grep mprotect bitmonero.out should show the line. If the return is 0, it's good. If -1, error.
14:17:13 <kiwi_7> Alright thank you I'll give it a shot, give me a few minutes
14:20:12 <kiwi_7> moneromooo The return is 0 for every mprotect (call?)
14:21:42 <kiwi_7> It also says it is killed by SIGABRT
14:25:36 <moneromooo> OK, then it looks like it's the program doens;t have enough space to be written to. Which is odd since it's deterministic.
14:25:55 <moneromooo> Can you build your own with an extra log line ?
14:26:04 <moneromooo> (which I would give you to add to the source)
14:26:38 <kiwi_7> Yeah I can try that, but in that case maybe I will first just trying to get the version from the site instead of the debian repository and see if that works
14:26:51 <kiwi_7> Unless you think that that will not help
14:26:57 <moneromooo> If it does, then something is very wrong somewhere.
14:27:07 <moneromooo> But that might be a good data point.
14:31:25 <kiwi_7> moneromooo Alright so the precompiled binary from getmonero.org seems to be working, so I'm sorry I didn't try that before
14:31:30 <moneromooo> https://paste.debian.net/hidden/58f142c6/
14:32:26 <moneromooo> I assume you got a prebuilt binary from debian ?
14:32:41 <kiwi_7> Thanks for your help, I can still try compiling the binary with that extra source code if you want (if you want to determine the error), but since the precompiled version works I'll use that now
14:32:52 <kiwi_7> Yes exactly I got the prebuilt binary
14:33:10 <moneromooo> OK, so if you did not build it yourself, any version you build is likely to be good.
14:33:27 <kiwi_7> Yes probably
14:33:28 <moneromooo> And since it's a prebuilt binary, you have no idea what sort of shite the builder did.
14:33:55 <moneromooo> Oh wait, deb packages do include the diffs. So you could look. And hope the diffs match the actual binary...
14:34:38 <moneromooo> Not sure I'm interested enough to dig more though.
14:34:49 <kiwi_7> Yeah no that's understandable
14:34:50 <moneromooo> sech1: if you are ^
14:35:16 <kiwi_7> My problem is fixed so thank you for helping me, I guess I learnt my lesson and will use the site binaries from now on, instead of the debian ones
14:35:26 <moneromooo> Keep the failing binary for a bit in cases someone wants to look into it.
14:35:35 <nonie> Maybe running gdb on the debain binary could help.
14:35:42 <nonie> bt
14:35:51 <nonie> if the binary is not striped already.
14:36:33 <asymptotically> nonie: i think the debug symbols get copied into another package. so they aren't there by default but you can easily grab them,
14:36:45 <moneromooo> If you want to try that, you'd have to break in v4_generate_JIT_code. It's going to be annoying though.
17:48:08 <prisonfortrans> how come this woman messages me intensively for a day or two then blows me off for a while then messages me intensively again? bipolar disorder?
17:48:56 <charuto> playing hard to get probably
17:49:07 <charuto> something something stockholm syndrome
17:49:07 <prisonfortrans> whats playing hard to get
17:51:07 <charuto> to pretend that shes not interested as much as you are so she can see to what lengths you invest on a depreciating asset or if you just cut losses and forget about her.
17:51:23 <charuto> something like that
17:51:38 <prisonfortrans> whats the endgame
17:51:48 <prisonfortrans> will she start acting normally eventually
17:51:59 <charuto> https://www.psychologytoday.com/us/blog/the-attraction-doctor/201606/how-and-why-play-hard-get
17:53:14 <charuto> it's all a mystery to me
19:30:05 <azizLIGHT> what is the start trigger for bg_mining ? i just see "background mining is enabled, but not started, waiting until start triggers"
19:30:15 <azizLIGHT> ive waited about 10 minutes
19:30:27 <azizLIGHT> probably more
19:57:42 <moneromooo> CPU idle ratio, battery.
20:49:06 <azizLIGHT> and what does bg_mining do different than regular mining? could i use it while working simultaneously?
20:49:29 <Mochi101> yes
20:49:33 <Mochi101> Background Mining
20:49:52 <Mochi101> It should let go of resource when you need them.
20:49:57 <azizLIGHT> i was expecting it to be time, but if its cpu %, my cpu is never at 0%
20:50:22 <azizLIGHT> *idle time
20:50:33 <yanmaani> I might already have asked this
20:50:39 <yanmaani> but what exactly is the purpose of Kovri?
20:50:51 <yanmaani> why is Tor with its larger anonymity set not 'good enough'?
20:51:08 <mmxxx[m]> wtf is kovri?
20:51:19 <mmxxx[m]> oh, i2p crap
20:51:21 <mmxxx[m]> meh
20:52:18 <azizLIGHT> i havent seen bg_mining activate for me, so im not sure its good for my scenario. i always have some cpu tasks running, have no battery, but i do get up and walk away and generate idle time. if the miner things my cpu tasks running during idle are real tasks then it will never run, which seems to be the case
20:52:28 <azizLIGHT> *thinks
20:52:53 <asymptotically> azizLIGHT: try setting the ignore battery option to true. i think it picks some desktop systems up as having 0% battery sometimes
20:53:34 <moneromooo> Tor is made to talk to clearnet really.
20:53:38 <moneromooo> Set the idle % lower then.
20:53:49 <moneromooo> Default is 90% IIRC.
20:54:11 <mmxxx[m]> does anybody actually use i2p?
20:54:19 <mmxxx[m]> can you link me to working eepsites?
20:54:21 <Mochi101> My grandmother
20:54:41 <Mochi101> She's very security conscious.
20:55:03 <asymptotically> mmxxx[m]: there's an exchange called exchanged.i2p :D, i'm not sure how much volume they get though. i would guess not very much
20:55:11 <Mochi101> oops... I'm in the wrong channel.
20:57:00 <yanmaani> mmxxx[m]: No, it's horribly broken in the implementation, so there's a hard cap on 200 kbit or so
20:57:06 <yanmaani> when it theoretically could reach normal speeds
20:57:20 <yanmaani> moneromooo: What difference does it make?
20:59:58 <mmxxx[m]> i haven't seen a working eepsite in about 3 years
21:00:07 <mmxxx[m]> project seems dead
21:02:10 <moneromooo> Ask someone who's familiar with both.
21:02:18 <yanmaani> well yes of course, why would you want to use it when Tor does a better job?
21:14:00 <azizLIGHT> i added all the mining switches i see relevant and still cant get it to background mine. no cpu % increase, and "Miner thread was started [0-4]
21:14:16 <azizLIGHT> background mining is enabled, but not started, waiting until start triggers
21:14:32 <azizLIGHT> ~/Downloads/cryptocurrency/monero-x86_64-linux-gnu-v0.15.0.1/monerod --data-dir --start-mining walletaddress --mining-threads 4 --bg-mining-enable --bg-mining-ignore-battery --bg-mining-min-idle-interval 1 --bg-mining-idle-threshold 1
21:14:51 <azizLIGHT> also tried --bg-mining-idle-threshold 99
21:16:26 <azizLIGHT> mistake in pasting command, but there is a argument path for --data-dir
21:21:59 <azizLIGHT> i guess i can make a script of my own that measure cpu idle time and then switch between all possible cpu threads, and 75% threads during non-idle
21:58:51 <moneromooo> Or fix the trigger in the first place.
23:46:44 <aces> what is b est way to load cpu/gpu monero miner on linux? ive downloaded numeros options and cant get it working. i have an old school core dou w\ 2.66 ghz and nvidia card for now