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?

hmm

doubtful

I'd be curious to figure out if it was CPU bound

The GUI sets --max-concurrency to half of the available threads because people complained about CPU usage

i have 6 cores, and a CPU display that was showing maybe 10% util

selsta ah ok i'll try that

but still 70 minutes sounds long

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

this is normal for me btw, it always takes a huge amount of time. i have >100mbit/s internet

knaccc: so you might want to try setting custom flag --max-concurrency 12 inside gui settings

to see if it results in higher CPU usage

selsta thanks, yes i'll try that. i wish i could rewind my gui and try those last 14 days again with that setting :)

you can pop blocks

ah yes, i'll do that now, thanks

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?

yes

Settings -> Log

you should be aböle to enter the pop_blocks 10000 command there

able*

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

it should take couple minutes

though I have only used the monero-blockchain-import version in the past

cool, ok i'll leave it running for as long as it takes

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.

It's theorerically possible to make it much faster but IIRC it was a bit hairy for not much benefit.

moneromooo ??? Can't it just recalc long term weight for blocks N-10000...N once and then use these values?

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.

(and I know I use them too, I suck as much as the rest of em)

I mean, you can calculate all long-term weights before popping blocks

starting from the earliest one

You could do that. It's slower than calculating just the last one though.

took about 10 mins to pop 10000 blocks. i guess people won't ever need to pop more than a few blocks though

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

i tried the popping and resyncing a few times, and it always was slow

knaccc: seems like I also get 20-30% CPU usage

selsta does it take about an hour for you too?

knaccc: yep

knaccc: but my macbook is 6 years old so I would guess yours should be faster

is pruning more effective for solving scalability issues compared to sharding of the blockchain?

!balance

.seen tippero

selsta oh so it is normal for it to take an hour

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

I guess someone has to analyze it and find the bottleneck

but yea, daemon is meant for always running

i guess the 'force stop' labelling does help suggest people should leave it running

still though, that won't survive a reboot

maybe monero should by default install in the background and start on reboot

Hello Is this the right place to ask technical questions regarding Monero?

Yes.

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

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.

Needless to say, I also tried to kill any and all monero processes and then run the same commands, as well

What filesystem ?

Hm? I run NixOS, so a Unix filesystem?

And when it does that, run | ps aux | grep monero

And when it does that, run: ps aux | grep monero

Just to make sure, and sorry for asking, but, you're running the wallet just once, right ?

ps auxw | grep monero 7955 XXXX 0:00 /nix/store/b0vjq4r4sp9z4l2gbkc5dyyw5qfgyi3r-gnugrep-3.4/bin/grep --color=auto 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.

The keys file has a file lock on it. This is normally done by the wallet when it starts, and released when it dies.

maybe that syscall is borked on your OS, though that doesn't seem super likely...

Try: fuser /path/to/keys/file

Understood. There are two different files: the `wallet` file and the `wallet.keys` file. I've tried opening both etc. to not effect

>Try: fuser /path/to/keys/file

This yields no results

Hmm. Annoyingly, I get no results either when I do that on an open wallet.

Can I give you any other info to debug? either about the system or anything else?

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.

Can you try: cp foo.keys foo2.keys; cp foo foo2; then run the wallet on foo2 ?

you got it!

Maybe something else has an advisory lock one file for some reason.

Not sure how to work out what though.

Right; I thought of that. I tried running the CLI even without monerod and get the same rror.

monerod won't touch the wallet file.

Ah OK

Since you say you did this after a reboot, possibly it's locked by itself like an idiot. Hmm.

>moneromooo 19:46:30>Can you try: cp foo.keys foo2.keys; cp foo foo2; then run the wallet on foo2 ?This worked!

Any explanation? Anything I can do to the original files to make it run normally?

fwiw I put the `*_2` files in /tmp

I don't suppose you have some @reboot cronjob that runs monero-wallet-cli on that original wallet ?

er, monero-wallet-rpc

Ah, no, it'd have showed up in ps, nvm.

Nope

Ah, lslocks will show locks.

Hrm. And it doesn't print this lock for me wallet.

Yeah I see no lock

but get the same error regardless

Ah it does once I put the password in.

The monero-wallet password?

So back to filesystem. Try to put the *2 copies in the same directory. Does it still work ?

Yes.

huh the *2 files in the pwd work!

Run the wallet on the original files, with --log-level 1.

Check the log. Any errors ?

Same directory as the binary.

oof I think I figured it out

I am a newb at reading the output off `ll` but it does look like the original files are read/write protected...

I have no recollection of changing their read/write permissions (certainly not since the last time I opened these files with monero-wallet-cli)