Search results

following output: balloon: actual=8192 max_mem=8192 last_update=1756638096 interesting, last update August 31. 01:51 oclock. about that time i did a minor PVE update + reboot + updated virtio drivers to 0.1.271 checked on different VM where memory is shown correctly: balloon: actual=4096...

pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) one of the windows VMs shows 100.xx% memory usage in PVE VM summary. windows 11 guest, memory 16384MB, ballooning enabled, minimum memory 16384MB. virtio 0.1.271 (updated from 0.1.240 to 0.1.266 and 0.1.271 due that issue)...

btw. there is an old topic by a well known and helpful user Dunuin, who suggests a more interesting approach: https://forum.proxmox.com/threads/feature-request-userscripts-in-webui.119305/

again, this needs to be maintained and supported. those debian templates are not maintained by the Proxmox team AFAIK. also someone wants ubuntu, arch, suse (god beware) but still, i understand your point. maybe a link to RTFM, where some suggestions could be proposed in the wiki, when that does...

interesting, but then people want official templates and images for everything. Proxmox offers official templates for their own products, like Proxmox Mail Gateway. they really should not add "Proxmox official" tags for third party products. they would need to support that then. no, really. the...

Didn't read the whole thread, but why would you want Proxmox VE to run/manage Docker? Question is, why overcomplicating things? - Docker/Podman network would/could interfere with PVE network - Security issues may pop up - There are some good/free/open source management tools (with WebUI) to...

- just the ipv4 tcp timeout higher in systctl.conf, but returned to original values, since no change. - both, source and destination are operational, no other errors, warnings or something in any logs. hardware is ok. backups running perfectly. also the connection between both PBSes is 1Gbit...

Hello, PBS 3.4.3 on both sides. WAN connection is super stable 1Gbps. Source PBS reports: "Timestamp: TASK ERROR: connection error: connection reset: connection reset" Destination PBS (the one with the sync job) reports after a while: "Timestamp: sync group vm/405 failed - timed out" for every...

i have updated to ceph 19.2, still spamming, but here is some interesting info: https://ceph.io/en/news/blog/2024/v19-2-0-squid-released/ https://docs.ceph.com/en/latest/rados/troubleshooting/log-and-debug/#confval-mon_cluster_log_level will try that at available service time window.

Thats right, but on the PDM the remote is stored and when the remote is removed via gui, it is sometimes not cleaned from the config files, so you can't readd it again. For me it was the above file. it will be added in future. this is an alpha version of PDM, a technical preview. here is the...

@jpass022 it can happen, check the file /etc/proxmox-datacenter-manager/remotes.cfg on your PDM and remove it there manually, after that you can readd the token. another way: (not clean) on your pve you generate a new token with a different name. on the short hand i cant find the actual...

Awesome! Thanks for the Christmas gift! - little bug: search field is case sensitive - question: renaming a remote in /etc/proxmox-datacenter-manager/remotes.cfg is ok? or need to delete and re-add? - and a request: please, make the "No valid subscription, At least one remote does not have a...

Thank you, that explains it. I thought, i still could sync back broken chunks, that are in the older backups. And yes, on the PBS with broken chunks were backups running every day, and the missing chunks got visible for some older backups on the weekends Verify job (+ re verify already verified).

I would like to dig this question out. two pbs, one onsite, one offsite. onsite pbs lost a few chunks due to an "administrative" error. trying to sync back from offisite (remote) to the onsite (local)... "skipped: 1 snapshot(s) (2024-09-10T19:05:21Z) - older than the newest local snapshot" guess...

you might want do update your bios.

wrong, you have to persist, since chunks, that might be removed from index in your non persistant dream case, are also needed for older backups. a file based database might get corrupted as a whole, when not persistant. as a antipole to file based databases, there are real databases (i don't...

oh, wait, redis is a RAM based database! this is why it is fast in i/o but you don't want a crash, while it wasn't finished saving the file on disk. redis is only for small and unimportant data, like configs (where in case of crash the old config still readable). ... no words, except of...

because zfs has the instruments for that as kernel extention. zfs read operations are cached, write operations are on premise if needed, but can be cached if not important. also, zfs solves a lot of other issues and offers redundancy, that people faced a few years ago with hardware raid or...

yes, pbs is not the fastest architecture. on the other side, you might consider a file based database (like sqlite) as a solution. it is not. because when sqlite, or even some real database servers, as mysql/mariadb, postgersql, mssql, oracle...etc. are set to write on premise (ignoring caches...

wow! why do you not contribute on the open source repository, if its dirt cheap? a diagram is also a good idea, at the cheapest least. btw. Dominik: tho my brain tends to support the idea of an independent database for chunk-indexing, but i see the issues. no ram caches please :)