Search results

yes, the problem is solved, own network all nodes, and all same version all nodes is running, Thanks for your help! :P proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2...

i5 was working good before the problem(switch reboot >1min off), and i don´t understand the question "own interface"? Thanks for your interested :P

LOL, i solved the problem with apt-get install --reinstall corosync-pve the cluster joined again.

could i try this?: apt-get -s install --reinstall corosync-pve

same messages on log yes,omping is right too. i added my corosync.conf Thanks! :D

Hi! i tried systemctl stop pve-cluster systecmtl restart corosync and "systecmtl restart corosync" and timeout again, without luck =S and my setup is Raid1 by hardware without ZFS and with NFS for shared storage.

hello, Thanks for reply, the last change on corosync.conf was 9December. when i try - systemctl restart corosync Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details. i added my syslog from /var/log/ too Thanks.

Hello guys!, we did reboot on the switch and the cluster crashed, (we have 4 nodes, and 3 nodes show "Cannot initialize CMAP service") . -systemctl status corosync.service ● corosync.service - Corosync Cluster Engine Loaded: loaded (/lib/systemd/system/corosync.service; enabled) Active...

this is normal, Note: When you gracefully shutdown a node, it services won't get migrated by the HA stack. You have to migrate them manually before you power off your node (for example for hardware maintenance). More info : https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x

Hello, https://forum.proxmox.com/threads/ve-4-0-kernel-panic-on-hp-proliant-servers.24015/https://forum.proxmox.com/threads/ve-4-0-kernel-panic-on-hp-proliant-servers.24015/ Good luck :D

Re: HP proliant Randoms reboots we had better experiences for cluster with the last updates, and I would advise hardware raid for production Regards :D

Re: HP proliant Randoms reboots Hello, im working with HDD RAID-1 by hardware on the nodes and on the NAS : HDD (RAID1)+SSD-CACHE(Write-Read) (I use NAS for Virtual Machine Images). But i tested ZFS on proxmox 4.0 STABLE and It seemed to work well, I had no problems with ZFS, i had problems...

Re: HP proliant Randoms reboots My system has 7 days uptime, we changed the switch and no more reboots. Thanks :)

no, i checked this and don´t fix the problem =S i add image with the problem. https://gyazo.com/a29d433d3d30ce26ae92eb0b1f463224 Thanks!

Hello! when i reboot the machine, the system entered on emergency mode and the log display this. [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack to clear. [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A...

Re: Cluster crashed Again Okay, Thanks for the info, i will do :P

Re: Cluster crashed Again Hello!, I did apt-get dist-upgrade and solved on Node 4 , IP1 solved too with reboot.

Hello! I added my 4 node with "pvecm add IP1-cluster" and IP1-cluster and the new node can´t join on the cluster. All nodes reseted with i added the 4 node, and IP1 cant join to the cluster, i can´t access SSH, Web interface, and i can do ping. (this problem is on 4 Node and IP1. Proxmox...

Re: HA with 3 Servers - Failover not working Hello! Note: When you gracefully shutdown a node, it services won't get migrated by the HA stack. You have to migrate them manually before you power off your node (for example for hardware maintenance) more info...

Re: HP proliant Randoms reboots Update: timedatectl #ntp was inactive on timedatectl timedatectl set-ntp on could be the problem? Thanks!