06:53:18 <knaccc> I hadn't opened my monero gui wallet for 14 days, and had to sync just under 10k blocks. it took 70 mins, on a fast macbook pro with 3.2GB/s SSD. Was hardly using any system resources. I am behind a firewall though. Is this a problem with not enough peers with enough outgoing bandwidth for me to leech?
07:24:48 <fluffypony> hmm
07:24:54 <fluffypony> doubtful
07:25:07 <fluffypony> I'd be curious to figure out if it was CPU bound
07:26:09 <selsta> The GUI sets --max-concurrency to half of the available threads because people complained about CPU usage
07:26:14 <knaccc> i have 6 cores, and a CPU display that was showing maybe 10% util
07:26:49 <knaccc> selsta ah ok i'll try that
07:27:01 <selsta> but still 70 minutes sounds long
07:28:38 <knaccc> i've calculated it's essentially taking 26ms to process each tx, based on a 7 day avg of 453 tx/hr = 15.1 tx/block
07:31:34 <knaccc> this is normal for me btw, it always takes a huge amount of time. i have >100mbit/s internet
07:42:46 <selsta> knaccc: so you might want to try setting custom flag --max-concurrency 12 inside gui settings
07:42:57 <selsta> to see if it results in higher CPU usage
07:43:16 <knaccc> selsta thanks, yes i'll try that. i wish i could rewind my gui and try those last 14 days again with that setting :)
07:43:34 <selsta> you can pop blocks
07:44:01 <knaccc> ah yes, i'll do that now, thanks
07:49:05 <knaccc> selsta doh i was going to type "./monero-blockchain-import --pop-blocks 10000" but the gui doesn't have monero-blockchain-import executable. can i send a command to monerod somehow?
07:49:24 <selsta> yes
07:49:30 <selsta> Settings -> Log
07:50:09 <selsta> you should be aböle to enter the pop_blocks 10000 command there
07:50:14 <selsta> able*
08:00:27 <knaccc> selsta does that command take a really long time to execute? it didn't give me an acknowledgement that it had completed, and so i tried to stop the daemon and it's taken 8 mins so far and has not shut down yet. maybe it's just a slow process
08:02:12 <selsta> it should take couple minutes
08:02:47 <selsta> though I have only used the monero-blockchain-import version in the past
08:03:06 <knaccc> cool, ok i'll leave it running for as long as it takes
11:21:44 <moneromooo> Popping is very slow now, as it has to go through 100k blocks at every block to recalc the long term weight, and there's only an incremental mode when pushing one.
11:22:14 <moneromooo> It's theorerically possible to make it much faster but IIRC it was a bit hairy for not much benefit.
11:26:30 <sech1> moneromooo ??? Can't it just recalc long term weight for blocks N-10000...N once and then use these values?
11:28:53 <moneromooo> Can you ask a non negative question ? These really bug me as I either never know whether to say yes or no or end up using the wrong one.
11:29:26 <moneromooo> (and I know I use them too, I suck as much as the rest of em)
11:45:29 <sech1> I mean, you can calculate all long-term weights before popping blocks
11:46:01 <sech1> starting from the earliest one
12:08:48 <moneromooo> You could do that. It's slower than calculating just the last one though.
13:45:33 <knaccc> took about 10 mins to pop 10000 blocks. i guess people won't ever need to pop more than a few blocks though
14:37:29 <knaccc> selsta i tried resyncing the last 10000 blocks using --max-concurrency 12 and i did notice CPU usage was a bit higher than before, perhaps peaking at 20%. but it still took an hour
14:37:53 <knaccc> i tried the popping and resyncing a few times, and it always was slow
14:48:55 * anicow lays in a pile of mining cpus. see this, this is what cpu cycles are good for
14:49:03 * anicow curls up and goes to sleep
15:41:47 <selsta> knaccc: seems like I also get 20-30% CPU usage
16:07:17 <knaccc> selsta does it take about an hour for you too?
16:09:31 <selsta> knaccc: yep
16:10:38 <selsta> knaccc: but my macbook is 6 years old so I would guess yours should be faster
17:10:47 <ayahuaza> is pruning more effective for solving scalability issues compared to sharding of the blockchain?
17:19:59 <rithm> !balance
17:21:11 <niocbrrrrrr> .seen tippero
17:47:21 <knaccc> selsta oh so it is normal for it to take an hour
17:47:48 <knaccc> hmmm so then i guess it's either leave monero running all the time, or put up with an hour delay if you want to use it
17:47:51 <selsta> I guess someone has to analyze it and find the bottleneck
17:48:06 <selsta> but yea, daemon is meant for always running
17:48:44 <knaccc> i guess the 'force stop' labelling does help suggest people should leave it running
17:48:53 <knaccc> still though, that won't survive a reboot
17:49:03 <knaccc> maybe monero should by default install in the background and start on reboot
23:36:15 <new-to-monero> Hello Is this the right place to ask technical questions regarding Monero?
23:36:25 <moneromooo> Yes.
23:38:20 <new-to-monero> Perfect! I am running 16.0.0. I first ran monerod, caught up to the most recent block height, and tried to open my wallet. I got this error: Error: failed to load wallet: internal error: "XXX" is opened by another wallet program
23:38:50 <new-to-monero> I tried to run every permutation of monerod, monero-wallet-cli and monero-wallet-gui I could think of but ended up with the same error. I also restarted my computer; same thing.
23:39:32 <new-to-monero> Needless to say, I also tried to kill any and all monero processes and then run the same commands, as well
23:39:32 <moneromooo> What filesystem ?
23:40:48 <new-to-monero> Hm? I run NixOS, so a Unix filesystem?
23:40:49 <moneromooo> And when it does that, run | ps aux | grep monero
23:41:02 <moneromooo> And when it does that, run: ps aux | grep monero
23:42:08 <moneromooo> Just to make sure, and sorry for asking, but, you're running the wallet just once, right ?
23:42:16 <new-to-monero> ps auxw | grep monero 7955 XXXX   0:00 /nix/store/b0vjq4r4sp9z4l2gbkc5dyyw5qfgyi3r-gnugrep-3.4/bin/grep --color=auto monero
23:42:48 <new-to-monero> Please don't be sorry for asking! Yes I am running the wallet just once. I killed all instances of Monero and also reboot my computer and same thing.
23:42:59 <moneromooo> The keys file has a file lock on it. This is normally done by the wallet when it starts, and released when it dies.
23:43:21 <moneromooo> maybe that syscall is borked on your OS, though that doesn't seem super likely...
23:43:33 <moneromooo> Try: fuser /path/to/keys/file
23:43:38 <new-to-monero> Understood. There are two different files: the `wallet` file and the `wallet.keys` file. I've tried opening both etc. to not effect
23:44:13 <new-to-monero> >Try: fuser /path/to/keys/file
23:44:17 <new-to-monero> This yields no results
23:44:39 <moneromooo> Hmm. Annoyingly, I get no results either when I do that on an open wallet.
23:44:58 <new-to-monero> Can I give you any other info to debug? either about the system or anything else?
23:45:25 <new-to-monero> My name is a misnomer; I'm a long-time user of Monero and have urn albeit older versions of the software on this OS for years.
23:46:30 <moneromooo> Can you try: cp foo.keys foo2.keys; cp foo foo2; then run the wallet on foo2 ?
23:46:41 <new-to-monero> you got it!
23:46:50 <moneromooo> Maybe something else has an advisory lock one file for some reason.
23:46:59 <moneromooo> Not sure how to work out what though.
23:47:47 <new-to-monero> Right; I thought of that. I tried running the CLI even without monerod and get the same rror.
23:48:09 <moneromooo> monerod won't touch the wallet file.
23:48:26 <new-to-monero> Ah OK
23:49:06 <moneromooo> Since you say you did this after a reboot, possibly it's locked by itself like an idiot. Hmm.
23:49:15 <new-to-monero> >moneromooo 19:46:30>Can you try: cp foo.keys foo2.keys; cp foo foo2; then run the wallet on foo2 ?This worked!
23:49:43 <new-to-monero> Any explanation? Anything I can do to the original files to make it run normally?
23:49:57 <new-to-monero> fwiw I put the `*_2` files in /tmp
23:51:17 <moneromooo> I don't suppose you have some @reboot cronjob that runs monero-wallet-cli on that original wallet ?
23:51:26 <moneromooo> er, monero-wallet-rpc
23:52:02 <moneromooo> Ah, no, it'd have showed up in ps, nvm.
23:52:10 <new-to-monero> Nope
23:53:29 <moneromooo> Ah, lslocks will show locks.
23:54:54 <moneromooo> Hrm. And it doesn't print this lock for me wallet.
23:55:00 <new-to-monero> Yeah I see no lock
23:55:06 <new-to-monero> but get the same error regardless
23:55:19 <moneromooo> Ah it does once I put the password in.
23:55:35 <new-to-monero> The monero-wallet password?
23:55:48 <moneromooo> So back to filesystem. Try to put the *2 copies in the same directory. Does it still work ?
23:55:51 <moneromooo> Yes.
23:56:30 <new-to-monero> huh the *2 files in the pwd work!
23:57:28 <moneromooo> Run the wallet on the original files, with --log-level 1.
23:57:33 <moneromooo> Check the log. Any errors ?
23:57:41 <moneromooo> Same directory as the binary.
23:57:49 <new-to-monero> oof I think I figured it out
23:58:23 <new-to-monero> I am a newb at reading the output off `ll` but it does look like the original files are read/write protected...
23:59:23 <new-to-monero> I have no recollection of changing their read/write permissions (certainly not since the last time I opened these files with monero-wallet-cli)