Search results

On my Proxmox Hosts (Version 4/jessie) I did not get the fixed Version of the microcode package. I have installed: 3.20170707.1~deb8u1 The fixed version is: intel-microcode/3.20180108.1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367 It is not released until now , right?

Strange, the reboot solved my problem. After that I could configure the two unconfigured packages: dpkg --configure proxmox-ve:all pve-manager:amd64 Unitl now, the problem occured only on one host of 7 others ... If somebody else has this issue, be sure that as many as possible or all other...

"kill" and "kill -9" ... nothing... I have tried some other "things" to ... I have absolutely no idea! 4 0 25072 24520 20 0 22484 2600 poll_s S+ pts/21 0:00 \_ systemctl start pveproxy.service 0 0 25093 25072 20 0 0 0 exit Z+ pts/21 0:00...

@fabian: Any ideas?

Is it possible and safe to reboot and try it again to configure? All packages except proxmox-ve and pve-manager are configured, also the kernel. /usr/bin/dpkg --configure proxmox-ve:all dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-manager; however...

# this hangs service pveproxy start # ps tree 0 19121 18747 20 0 24376 6376 wait Ss pts/20 0:00 \_ -bash 4 0 2761 19121 20 0 22484 2540 poll_s S+ pts/20 0:00 \_ systemctl start pveproxy.service 0 0 2795 2761 20 0 13176 1544 poll_s S+...

"pve-cluster restart" on the corrupt node did not help...

No there is no pve-proxy running. ps waux | grep pveproxy pveversion -v proxmox-ve: not correctly installed (running kernel: 4.4.76-1-pve) pve-manager: not correctly installed (running version: 4.4-21/e0dadcf8) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.35-1-pve: 4.4.35-77...

It looks like an hanging cronjob which is also blocked by the "/bin/systemctl restart pveproxy.service" 4 0 1648 1 20 0 27504 2840 hrtime Ss ? 0:56 /usr/sbin/cron -f 5 0 22364 1648 20 0 42240 2604 wait S ? 0:00 \_ /usr/sbin/CRON -f 4 0 22367...

Do need really the full output, it is a running system the output would be about 1.100 lines... Or is this extract sufficient? 4 0 21543 31254 20 0 82740 5848 poll_s Ss ? 0:00 \_ sshd: root@pts/27 4 0 21655 21543 20 0 24344 6340 wait Ss pts/27 0:00 | \_...

Unfortunately I killed the command, I was to impatient ;-) So everything in the dpkg --configure command after pve-manager is unconfigured now - including the kernel and proxmox-ve :( "pve-manager:amd64 proxmox-ve:all pve-kernel-4.4.76-1-pve:amd64 tcpdump:amd64" At the moment the System is...

Hi, today I am trying to upgrade from an Proxmox 4 Version to the current Proxmox 4 Version in my cluster on the no-subscription repo. The first node has no problems. The second node hangs in the configuring step of "pve-manager". My Starting Version proxmox-ve: 4.4-93 (running kernel...

OK, removing and rezap the disk starts the recovery. For me it was suspicious that the error happend after the upgrade, because something like that never happens before... but never say never ;-)

On all nodes the directory is: /var/lib/ceph/osd/ceph-[OSDID] /var/lib/ceph/osd/ceph-2# ls -l total 5242932 -rw-r--r-- 1 root root 469 Jan 31 10:40 activate.monmap -rw-r--r-- 1 ceph ceph 3 Jan 31 10:40 active -rw-r--r-- 1 ceph ceph 37 Jan 31 10:40 ceph_fsid...

Hi, yesterday i have upgraded a cluster to the current Proxmox Version (4-4-87). (ceph: 10.2.7-1~bpo80+1) It is also a threenode ceph cluster with one osd per node and pg_size/min 3/2. (data gets replicated to all three nodes, a minimum of 2 nodes must be up that the ceph cluster is accessible)...

Perhaps offtopic - and only my opinion: We have a similar infrastructure, but we separate ProxMox from pfSense (redundant HA-Setup with two nodes). Because of security reasons, I would always separate the main firewall from the VM infrastructure, if it is possible. Setup dedicated boxes for...

Yes we have HA enabled in this cluster. OK, this means it does not happen with future upgrades... To avoid this problem, while upgrading our other clusters, I have to disable HA during the upgrade process, right?

Hi, yesterday I have done a rolling upgrade of one of our cluster from UI 4.4-78 to 4.4-87 (current) I did the upgrade via the GUI, a "apt-get dist-upgrade" is executed. There was a full crash on all nodes, all VMS are crashed and the system reboots automatically. The symptom was the same on...

After several reboots and upgrades i cannot get some disks synced of my 3 Nodes Cluster connecting again. I have tried several different approaches but nothing helps: drbdmanage list-nodes +--------------------------------------------------------------------------------------------------+ |...

@laci_ur: Thanks a lot, the verification is running now. I set the verification alg before every verification, because after a reboot the setting gets lost. drbdmanage net-options --verify-alg crc32c --common drbdadm verify all Has anyone experience which verify alg is the fastest? In the post...