00:01:33 I had a couple of unexpected computer shutdowns and now when I try to open my wallet it is stating that it can't because the .keys program is opened by another wallet program (it is not). 00:01:34 Fortunately I have a backup that is not too old, but anyone know how to fix this? 00:06:37 Does your user have rw permissions on that keys file ? 00:06:57 Yes 00:08:36 Run with strace, eg: strace -o foo.log ./monero-wallet-cli your-usual-args-here 00:08:42 I have force-moved the files to another folder, renamed and moved back. Which seems to work 00:08:49 Then check near the end of foo.log which syscall fails and with what errno. 00:09:58 It is windows by the way 00:11:25 My condolences. 00:12:12 I'm just realizing I do not know what a condolence actually is... 00:12:19 * moneromooo goes find out 00:21:25 So i've noticed that if you get monerod to print a miner tx, it says it is pruned even if the blockchain is not pruned (because obviously coinbases do not have RingCT, signature etc data); is this potentially misleading in that someone might think that their blockchain is pruned when it isn'/t? 00:22:31 Probably. 00:42:23 yeah someone was confused by exactly that a while ago 02:08:34 <[discord] bemore#3657>: I wish i had some kind of scavenger hunt prepared for expensivebead 07:08:37 Is there any function in monerod to, given a global index of a pubkey in the blockchain (from e.g. the first offset mentioned in a transaction or the second added to the first, and so on) find the transaction hash associated with it? 07:11:23 e.g. for the transaction 154e84777811d9c07c732e1a9b47fe7d14dcc9c2aedc3dc7a6730816597d2e12 (picked arbitrarily because it is the first in a recent block, block 2139697) there are the key offsets: 07:11:36 [ 5901669, 12083962, 5250, 89498, 268573, 298673, 194549, 21000, 10999, 22530, 2027] 07:12:25 How does one go from that to the transactions originating those pubkeys? 07:13:25 Presumably monerod itself does so somewhere in the background otherwise it couldn't verify the signature and similar data 07:26:02 Does this work: https://monero.stackexchange.com/questions/7576/rpc-method-to-translate-key-offsets ? 07:28:36 Is there an equivalent command for that with non-rpc monerod? 08:28:38 Anyone take a prepaid card for btc? 09:50:33 Whose here 09:50:39 Skrimant 15:02:32 my monerod keeps crashing :-( 15:03:22 I was on 0.15 and it crashed so I upgraded to 0.16 and it's still crashing 15:03:28 any clue? 15:04:14 Did your computer crash or similar ? 15:05:00 no 15:05:07 well, I may have suspended it[6~ 15:05:12 *it 15:05:13 Do you have a stack trace ? 15:05:40 not at present 15:05:53 I take it this isn't a known issue then? 15:07:08 I can't know without the info first :) 15:09:20 are there known issues of monerod crashing randomly? 15:10:05 are you saying you can't determine which of the many issues of monerod crashing randomly I'm experiencing? 15:10:21 Yes. LMDB likes to crash a lot when the underlying db is corrupted. 15:10:33 That's the only known crash I can think of. 15:10:35 what operating system rah ? 15:10:48 gingeropolous: Debian GNU/Linux 15:10:52 rah: Which version do you have? I had issues with 16.0.0 15:11:23 GUI or CLI? 15:11:46 xmrpow: 0.16.0.1-release 15:11:48 gingeropolous: CLI 15:12:45 yeah, if u wanna debug we can go that route, or if you just want it working, probably delete your data.mdb and resync. 15:13:37 or you can copy the data.mdb to a different name and then upload it to a server that i have yet to host so that someone can investigate the database corruption 15:14:00 if its that 15:14:27 u on a spinny or a ssd? 15:17:58 it seems to be syncing the blockchain 15:18:22 it crashes, downloads a bit, crashes, downloads a bit, etc. 15:18:37 (I've set it up to automatically restart) 15:18:56 UI/SitRepPanel.cpp 15:18:59 oops 15:19:57 <[discord] Yonatan#6948>: I have a dumb question 15:20:15 <[discord] Yonatan#6948>: I see here that there's a monero node that's near me: https://monerohash.com/nodes-distribution.html 15:20:23 <[discord] Yonatan#6948>: But I can't view it for some reason 15:20:30 <[discord] Yonatan#6948>: Does anyone know why? 15:23:21 If it crashes all the time, should be simple to get a stack trace: gdb monerod; run $your-usual-options; bt 15:24:17 if you move data.mdb to a different name and start it up, so that it starts syncing from scratch, does it still crash? 15:28:05 I don't want to run it with gdb just yet, I want to try and actually use it :-) 15:29:19 how are you going to use it if it keeps crashing? 15:29:41 in case it's not obvious, a single crash is not normal, let alone repeated crashes 15:30:25 gdb should not make it crash more fwiw. 15:30:34 2020-07-11 15:02:04.430 I Monero 'Nitrogen Nebula' (v0.16.0.1-release) 15:30:34 Forking to background... 15:30:34 2020-07-11 15:08:02.261 I Monero 'Nitrogen Nebula' (v0.16.0.1-release) 15:30:34 Forking to background... 15:30:34 2020-07-11 15:15:01.222 I Monero 'Nitrogen Nebula' (v0.16.0.1-release) 15:31:00 jbg: good question, I guess I'll find out when I try 15:31:07 moneromooo: the critical word there is "should" :-) 15:31:19 gdb will slow it down though regardless 15:31:32 you might want to remove --detach from the options if you run it under gdb so that it doesn't fork 15:31:45 sure, but crashing slows it down too 15:32:06 and there is probably some underlying thing wrong like a corrupted db, so trying to use it might not be very smart 16:29:11 here's a backtrace: https://paste.debian.net/1156039/ 16:29:24 looks like it's segfaulting in epee::net_utils::network_address::serialize_map 16:32:31 I don't see anything obviously wrong in the code. If I give you a log patch, can you build it and paste the output ? 16:33:45 I suppose 16:34:37 I suspect it's a problem with the IPv6 stack 16:35:24 everything seems to have problems with v6 addresses on the machine 16:35:33 I could be wrong though 16:35:38 something to bear in mind at least 16:40:10 Building with asan would be even better if you can :) 16:40:30 There's a fuzz target for this. It'll build with asan enabled. 16:40:34 ie, make fuzz 16:52:45 moneromooo: are you going to give me a patch? 16:52:56 Yes. 16:53:08 I'm building it first. 16:53:59 ok 17:10:02 https://paste.debian.net/hidden/fb9b361d/ 17:10:36 I'm only interested in the dozen lines or so before it crashes. 17:28:51 moneromooo: ok, I'm off for a few hours but I'll sort it out when I get back 17:29:01 Sounds good, thanks. 21:03:09 moneromooo: https://paste.debian.net/hidden/df95cff1/ 21:05:18 just a quick browse through the (lots and lots of) ouput previous to that, I can't see any "IPv6" 21:05:25 it seems like that was the first 21:06:18 nope, tell a lie, there was at least one was at least one before that 21:07:07 s/was at least one was at least one/was at least one/ 21:13:26 Looks like the crash is in boost. The internal representation is a 16 byte buffer so I'm not sure why it'd crash, even if uninitialized. 21:13:46 What boost version, and are you sure you did not use mismatched boost versions ? 22:38:16 :) 22:39:12 saluton 22:39:33 saluton mia amiko moneromooo 22:39:43 that's all the esperanto I know, been meaning to learn more. 22:40:07 I don't actually speak esperanto either, but I could understand what you said. It works :)