Search results

You want to enhance your current situation, right? Are you sure you want Ceph with only three nodes? A reliable system with features like self-healing has some pitfalls - beside the (usually) much lower performance than local storage...

Please tell us something about the storage devices (rotating rust? NVMe only?) and show us your datastores cat /etc/pve/storage.cfg and the topology of the ZFS pools zpool status. Basically: if you use a shared resource by two processes then one process may affect the other. In our context this...

From the very same client? One standard pitfall is to accidentally omit the port number. You need to enter https://192.0.2.1:8006 (with your address of course).

Maybe. There are reasons that this is not recommended/documented (as far as I know). You need to follow both https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node and possibly https://pve.proxmox.com/wiki/Renaming_a_PVE_node and cleanup /etc/pve manually of any...

No, don't think so. I just prefer redundancy everywhere (where possible - with a sane amount of technical and monetary effort). Was my reply somewhat too negative? Didn't want to be offending, really. English is not my native language...

This! Of course I do my best to avoid the need of swap. If you need to swap then your hardware needs an upgrade - resources like CPU-power, NICs, Storage can be over-committed. For RAM this has to / should be avoided!

Because the data-part is RaidZ2. You really want to have the same redundancy level --> two devices are allowed to fail. Oh boy! You are living in another world than me. Even in a cluster I don't want that.

Dann ist Zeit, die 3-2-1 Backupstrategie zu überpüfen und ein Restore zu testen ("Schrödingers Backup"...) Dann: memtest86 über Nacht laufen lassen - Speicher (ohne ECC) fällt manchmal tatsächlich aus smartctrl -A <dev> - einen Blick auf die Smart-Daten werfen smartctrl -t long <dev> - einen...

Quick shot: triple check that there are no IP address conflicts. Make sure that /etc/hosts contains the same information on all three nodes. "ping A" must work on A+B+C; "ping B" must ...; - by using their names, not just an IP address.

Depends on your expectations. I have this one: https://localai.io/basics/container/#all-in-one-images in a VM, using the Docker approach (docker run -p 8080:8080 --name local-ai -ti localai/localai:latest-aio-cpu) = without a GPU. For me it works with some of the offered models - and without...

Okay. Den Hinweis auf einen DHCP-Server hast du schon bekommen. Der muss natürlich "irgendwo" herkommen und sinnvoll konfiguriert sein. (( Ich habe einen solchen in einer VM laufen, der meine internen Netze versorgt. Das Netz, welches von der Fritz!Box nach innen angeliefert wird, ist meine...

Na, hier bei mir. Unten in der Küche - da muss ich jetzt auch dringend hin... ;-)

Moin. Eine so generische Frage lässt sich unmöglich beantworten - es gibt etliche Stellen, an denen IP Adressen auftauchen. Falls du gerade einen PVE in Betrieb nimmst, hast du die IP Adresse des Servers bei der Installation eingetragen. Dass du einen anderen Rechner für die Bedienung verwenden...

It is this: https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI iSCSI is "only" the transport for a ZVOL. All(?) ZFS related commands and features are available, but are executed on the target. This sounds great and I had tested it once, some years ago. Unfortunately I dropped that approach...

You can only administrate a cluster (by writing to /etc/pve implicitly) while Quorum is given. What is your situation? Examine pvecm status. If you have only one node left and want to destroy an "old" second one: you may force the remaining node to lie and set pvecm expected 123 - please read...

You can not have multiple NICs in the same network (on the same host). It will work sometimes for a short while and then fail randomly. Remove the IP address from LAN or from MGMT. To use both physical NICs assign IP addresses from different networks to the bridges. To inter-connect different...

Hello @ilu, welcome to the club. You might just follow https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_installation If you encounter problems try to describe your hardware more detailed. Then tell us what you wanted to do (in that step) what you did what you expected what...

Yes! As soon as it is added to the cluster as a member it gets one vote :) The resources it does offer may be completely different in regards of Ram/Cpu/Disk-number/Disk-space etc. Theses technical differences will hinder migration if they do not fit, but as a member it still has a vote.

Yes, you can ignore the 4th node for HA purposes. But that is not the problem! PVE needs Quorum to be established to work as intended. Without Quorum you can not administrate a cluster. This fact is completely independent from activating HA or not. With three nodes you can lose one node without...

Wenn man nur "klassisch" an cron denkt, sieht man "systemd-timer" nicht: systemctl list-timers --all.