fstrankowski's latest activity
-
fstrankowski replied to the thread Proxmox node status is showing as unknown.You have configured your corosync to use the internal ip addresses 172.24.129.85 (biomass) and 172.24.124.27 (pve02) but your machine "biomass" has the ip not configured. Thats why your corosync is not working. Did you change the IP of "biomass"... -
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Unter /etc/network/interfaces ist die Netzwerkkonfiguration. Unter /etc/hosts die Hosts Konfiguration. Beides musst du dann anpassen.
-
fstrankowski replied to the thread Proxmox node status is showing as unknown.journalctl -b (upload as file here) cat /etc/pve/corosync.conf on both nodes pveversion -v systemctl status corosync cat /etc/network/interfaces P.S.: Welcome to the Forum!
-
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Mach Dir keine Sorge, wir alle hier im Forum haben irgendwann mal angefangen. Den schwersten Schritt hast Du bereits geschafft, Du hast angefangen Dich mit Proxmox zu beschäftigen! Es ist schwierig Dir zu helfen, wenn Du nicht an deine Maschine...
-
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Was genau ist denn dein Problem? Mach doch mal ein Foto von den Settings, vielleicht kann man Dir noch helfen. Klingt nicht nach einem großen Problem.
-
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Die IP änderst Du im CLI unter /etc/network/interfaces und unter /etc/hosts. Das geht ohne SSH, einfach mit Tastatur und Bildschirm.
-
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Für den Host reicht die Änderung in der hosts und in der network/interfaces. (oder in der GUI)
-
fstrankowski replied to the thread ProxmoX VE IP-Adresse ändern.Hast Du einen managbaren Switch? Dann könntest Du auf einen Port einfach zwei VLANs legen und somit nie wieder den Stecker ziehen müssen :-)
-
fstrankowski reacted to alexskysilk's post in the thread Proxmox QDevice with a 16 node cluster with
Like.
Nodes failing isnt the issue. the quorum device is meant as defense against a silo connectivity "tie". Anything short of a room losing connectivity would be handled normally without it. -
fstrankowski reacted to LnxBil's post in the thread [PROPOSAL/RFC] - Invent a script to check for missed important changes during a clusters/node timespan with Like.
This is a great idea. We use something conceptiually similar to this with any Linux-based OS we have in the field to keep track of changing stuff over the years. Our implementation is kind of simple: store the bash scripts in a special directory...
-
fstrankowski replied to the thread NFS Share on Synology DS218+,.Depends on your firewall. There are firewalls which by default block all ports, others allow all traffic.
-
fstrankowski reacted to unsichtbarre's post in the thread [SOLVED] Ceph cluster network configuration with Like.
Thanks!
-
fstrankowski replied to the thread Proxmox QDevice with a 16 node cluster.I see a problem here and thus i usually discourage from changing the vote strength of devices. Because the setup is inhomogeneous and thus unpredictable. Exactly for the reason you showed.
-
fstrankowski replied to the thread NFS Share on Synology DS218+,.Which KI did you use to generate that answer?
-
fstrankowski replied to the thread zfsutils-linux not upgradable.Welcome to the Forum! When updating Proxmox always do a full-upgrade - so apt full-upgrade or apt-get dist-upgrade. For further information please consult the PVE Administration Guide here.
-
fstrankowski replied to the thread Proxmox QDevice with a 16 node cluster.Best thing is to have 3 replica on 3 locations. i'd advise to buy 8 more m640 for the 3rd room ;-) Another idea: Make 1 Proxmox server spare and split the other 18 in 3x6 (6 per room) and go for one cluster. Is that feasable?
-
fstrankowski replied to the thread NFS Share on Synology DS218+,.Firewall?
-
fstrankowski replied to the thread vm RAM läuft voll.Schau mal hier: https://www.linuxatemyram.com/
-
fstrankowski replied to the thread [SOLVED] Ceph cluster network configuration.cluster_network = 10.26.22.0/24, 10.26.23.0/24
-
fstrankowski posted the thread [PROPOSAL/RFC] - Invent a script to check for missed important changes during a clusters/node timespan in Proxmox VE: Installation and configuration.Hey! Back in February this year, after quite a long round of discussions, Proxmox introduced a change in the corosync config that allows for overriding the default token coefficient and lowering it by default. Quick background: By default...