Search results

i migrated to RHEL 8 - with a free developer license

In my world Servers should never be submitted to the perils of a DHCP server. - Servers should not receive an IP thru DHCP (even with reservations), but rather set in stone via manual config. As DHCP relies on external availabillity ( and possible set Reservations) you are introducing an...

In you using an USB drive to install i am assuming you have not licensed the iLo functionality to mount an ISO remotely to the server ? I in my situation have licensed them, and always use the iLo way of mounting ISO's remote to a/the server for use (and the remote console) of installing server.

From 192.168.1.150 icmp_seq=1 Destination Host Unreachable Looks more as next to you having a DNS problem you are also facing a routing issue .. gateway correct ?

I had issues with a DL380 Gen5 where it (when installing Debian ( i prefer to have control over how my disk-layout is done) and then moving from Debian to Proxmox as described on the PM Wiki) due to missing drivers. I then found a debian BootISO which already had those missing drivers in them...

I have the strangest thing with just -one- of my VM's where when its being backed up it times out : INFO: Starting Backup of VM 125 (qemu) INFO: Backup started at 2021-11-26 03:12:21 INFO: status = running INFO: VM Name: vm-lx-01 INFO: include disk 'scsi0' 'vms01:125/vm-125-disk-0.qcow2' 64G...

Still suffering from a Timing-issue that when i reboot a node it hangs after shutting down all VM's/Containers. From the cluster-perspective this is quite unwanted. At the moment i just hard-reboot the node from iLO ( HP's solution on servers to manage them from remote via a management board)...

Just an update from my end, it seems the location (since a bit ( now running 7.0.14 PVE) ) of the unitfile has changed, and introduced some issues so i had to adapt my Ansible playbook. --- # ./roles/proxmox/tasks/main.yml - name: remove mcp repository to reset content ansible.builtin.file...

So what do logs say when you mount this dir ? (IMHO) Mounts are OS issues, so before PRoxmox can use them they need to be available on the underlying OS, if that fails then the cause needs to be first sought in the logs from the OS.

just my 5 cents, but .. If a scheduelled power-outage were there, would a scheduelled cronjob on the Proxmox host be equally efficient, without poking around with the API ? - if the scheduelled outage is always the same, then use a cronjob to shutdown the hosts/guests prior to the outage...

What i am curious is the following - as information provided is like at an absolute minimum.... - Why do you want to automate a full install of a Proxmox server ? => (in my opinion) the times you (re-)install a server is like not a day-2-day task If you were running a cluster then sometimes...

I install manually up untill i have network and can login over SSH , then Ansible takes over and configures the rest of the box.

The 'unattended' part is done via Ansible on my end, This keeps the config of my 4-node cluster in check. For this i start out with a Debian box to start with, and then ( as the wiki describes ) the move to Proxmox. Playbooks control what packages are needed, repository setup, specific...

In essence every program is a bunch of lines...

Unclear : are we talking of a Proxmox server or a guest on proxmox ?

Just a general question, as the topic said. I myself have both a cluster and a standalone machine for testing purposes. This machine is the result of a debian-install-move to proxmox based on the Wiki and Buster distro, running the latest 6.x version. When running Lynis security audit...

Only thing i can think of is the intro of cgroupsv2 which isnt supported by older OS's ( like CentOS-7 ) ... i tried to implement the kernel options but that didnt work out, as i ran from the one error into the other error, leaving me with an inoperable CentOS-7 LXC - which was quite important...

The 'additional settings' all point towards the way you implemented your Cluster. This makes it quite hard for me to assume your current situation. As you have stated : - you run a 2-Node cluster - corosync contains the specific reference as such. But the great unknown/not disclosed is : - do...

i would first check if the additional settings needed for a 2-node lcuster are still correct / in place.

This playbook is actively in use on a 4-node cluster