Monero logs

00:32:06 hinto:monero.social: `+3,631-11,624` 😭

00:33:58 boog900:monero.social: yeahhh :D

00:47:46 hinto:monero.social: I'll start by re-syncing and running it for now

00:48:05 hinto:monero.social: anything config changes to note?

00:48:14 hinto:monero.social: any*

00:48:40 boog900:monero.social: yes it will now automatically set the p2p block downloader queue size

00:50:08 boog900:monero.social: I also set the storage threads to 4x the `available_parallelism` rather than 1/4

00:50:29 boog900:monero.social: Some other changes as well, I would recreate the file

00:51:54 boog900:monero.social: you will alos need to delete the old DB, it wont do it for you

00:52:12 boog900:monero.social: I don't _think_ it would impact cuprated if you kept it around though

00:54:13 hinto:monero.social: I'll run it first with old files around

00:54:26 hinto:monero.social: I assume different extension/filename for the new DBs?

00:54:29 hinto:monero.social: `.fjall` or `.tapes`?

00:54:50 boog900:monero.social: different path

00:55:08 boog900:monero.social: the txpool and blockchain are no longer seperate

00:55:56 boog900:monero.social: as the txpool now uses fjall and having 2 fjall DBs is overly expensive as fjall has its own thread pool and workers.

01:00:44 boog900:monero.social: it shouldn't take long to sync :)

01:01:07 boog900:monero.social: although if you only give it 2 GBs it may get killed

01:01:11 boog900:monero.social: we'll see

01:01:24 hinto:monero.social: will try full verification then fast sync

01:01:42 hinto:monero.social: and raise RAM slowly until no OOMs

01:10:25 hinto:monero.social: seem to be stuck in a panic loop:

01:10:31 hinto:monero.social: ```

01:10:32 hinto:monero.social: thread 'cuprated-tokio' (561366) panicked at /Boog900/cuprate/p2p/p2p/src/block_downloader.rs:323:9:

01:10:33 hinto:monero.social: We need requests inflight to be able to send the request again

01:10:35 hinto:monero.social: ```

01:10:40 hinto:monero.social: https://github.com/Cuprate/cuprate/blob/new-db/p2p/p2p/src/block_downloader.rs#L323-L326

01:10:43 boog900:monero.social: yay

01:11:20 hinto:monero.social: this was after an initial panic on: `ERROR net{zone="ClearNet"}: Error in inbound connection listener: Address already in use (os error 98)`

01:11:31 hinto:monero.social: (18080 was used by monerod on same machine)

01:12:05 hinto:monero.social: seems unrelated to DB changes though

01:12:25 boog900:monero.social: yeah was just about to say that should be unrelated

01:12:36 boog900:monero.social: does it keep happening on every run?

01:13:17 hinto:monero.social: yup, I'll try without the old files

01:13:26 boog900:monero.social: hmmm

01:13:40 boog900:monero.social: what OS is this?

01:13:46 hinto:monero.social: Linux x64

01:15:27 boog900:monero.social: can you edit this value in the config: `in_progress_queue_bytes` to 125_000_000 and `buffer_bytes` to 250_000_000

01:16:00 boog900:monero.social: I am wondering if it isn't reading the RAM size and is setting it to 0 for some reason

01:17:18 hinto:monero.social: that worked

01:17:22 boog900:monero.social: damn

01:18:04 boog900:monero.social: Well the value for RAM is used elsewhere too

01:18:25 hinto:monero.social: this is with a 2GB cap for reference

01:19:03 boog900:monero.social: yeah it should still handled that, I think it is reading the total RAM as 0 for some reason

01:27:27 hinto:monero.social: maybe this should be `max(reasonably_small_value, buffer_mem)`?: https://github.com/Cuprate/cuprate/pull/587/changes#diff-6d75e447e3327caf5ac1c2bf3e162690ac5df0c16338dc6b612ad0a6c963

01:27:50 hinto:monero.social: sysinfo output probably shouldn't be relied upon 100%

01:29:52 hinto:monero.social: fyi it's syncing around 100 blocks per second with full sync

01:30:25 hinto:monero.social: I'll resync old cuprated for up to date reference values later

01:30:52 boog900:monero.social: fjall is going to be nerfed with no cache as it also goes off of RAM size.

01:31:37 boog900:monero.social: I agree although I also want to know why it can't read your RAM value.

01:32:37 hinto:monero.social: perhaps systemd returns 0 on available memory

01:32:55 hinto:monero.social: it could be the parameters too, there's a bunch of security related ones turned on in the default service file

01:33:06 hinto:monero.social: max memory*

01:38:08 boog900:monero.social: True

01:38:55 boog900:monero.social: It is annoying as the block downloaded settings have quite a big impact on fast sync speed

01:39:29 boog900:monero.social: So on systems with more ram they will be limited by a small default

01:40:49 boog900:monero.social: Maybe we add a config value for ram which is a defaulted field and then if we can't read ram we error and ask the user to change that field?

01:41:19 boog900:monero.social: So we require a user to put it in manually

01:43:48 hinto:monero.social: hmm sounds fine although it probably should note it shouldn't be touched in most cases

01:44:06 hinto:monero.social: I imagine most cases sysinfo will return correct info

15:37:16 boog900:monero.social: hinto: pushed that new config value + error message when maximum memory is 0.

18:48:26 hinto:monero.social: ok, re-running with `target_max_memory = 2_147_483_648`

18:48:43 hinto:monero.social: previous run got to `start_height=1938649`

18:49:56 hinto:monero.social: ```

18:49:57 hinto:monero.social: ● cuprated.service

18:49:59 hinto:monero.social: Loaded: loaded (/etc/systemd/system/cuprated.service; enabled; preset: enabled)

18:50:01 hinto:monero.social: Active: active (running) since Thu 2026-03-05 01:16:22 UTC; 17h ago

18:50:03 hinto:monero.social: Main PID: 562018 (cuprated)

18:50:05 hinto:monero.social: Tasks: 42 (limit: 9516)

18:50:07 hinto:monero.social: Memory: 1.9G (high: 2.0G max: 2.0G available: 184.0K)

18:50:09 hinto:monero.social: CPU: 3d 5h 53min 37.354s

18:50:11 hinto:monero.social: CGroup: /system.slice/cuprated.service

18:50:13 hinto:monero.social: └─562018 /home/cuprate/cuprated --config-file /home/cuprate/Cuprated.toml

18:50:15 hinto:monero.social: Mar 05 18:47:30 vmi2497432 cuprated[562018]: 2026-03-05T18:47:30.881224Z INFO incoming_block_batch{start_height=1937866 len=87}: Successfully added block batch fast_sync=false

19:08:36 boog900:monero.social: Not bad