Recent content by liska_

Well, after trying this for few hours last week and after letting it be now for some time, it was resolved by itself. Probably some network stack problem, but very strange to me. I just have to wait for few minutes before managing restored vm ...

Hi, I have a strange problem which I am not able to solve. When I restore vm machine from backup, I can not make network working again. It was not a problem until proxmox 4.x. If I ping google.com or internal network IP I get around 97% packet loss, few packets in a row are successful then many...

Hi, unfortunately it is not working again. I googled for solution but I have not found anything regarding this. I tried to pull cable off as well as kill corosync or shutdown the interface, but no restart has happened. When I tried to restart watchdog service without blacklisted module softdog...

Yeah, it is working and no logs anywhere. But now it is working, we will se after upgrade.

This is my file /etc/default/pve-ha-manager, it`s the same on all nodes. I just wanted to try softdog, so I did not make any changes in this topic. <code> # select watchdog module (default is softdog) #WATCHDOG_MODULE=ipmi_watchdog </code> Is there any place where I could find any logs...

Great, that has solved my problem. I just removed it from blacklisted a restarted the node and after killing corosync it got restarted. But why is that blacklisted by default if it is needed? It is like that on every node. And what is going to happen after upgrading kernel? This softdog module...

As I said, I have no idea unfortunately;( lsmod | grep dog softdog 16384 0 In syslog I can see kernel: [ 391.830718] softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0) I tried to add this module to /etc/modules and reboot but it...

<code> systemctl status watchdog-mux.service ● watchdog-mux.service - Proxmox VE watchdog multiplexer Loaded: loaded (/lib/systemd/system/watchdog-mux.service; static) Active: failed (Result: start-limit) since Tue 2016-01-05 12:35:04 CET; 1 day 2h ago Process: 5087...

I wanted to try just software watchdog, as these nodes are just desktops. I did not make any changes from default config. In dmesg I can see this line on all nodes: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter This is output of lsmod of one node (other nodes are...

This i the output: <code> proxmox-ve: 4.1-30 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-4 (running version: 4.1-4/ccba54b0) pve-kernel-2.6.32-27-pve: 2.6.32-121 pve-kernel-4.2.6-1-pve: 4.2.6-30 pve-kernel-3.10.0-1-pve: 3.10.0-5 pve-kernel-2.6.32-23-pve: 2.6.32-109 pve-kernel-4.2.0-1-pve...

Hi, I try new proxmox 41 in test environment without hardware watchdogs. Unforunately, I can not make the failed node restart. I tried few commands I have found on this forum like ifconfig vmbr1 down kill -9 corosync Any node got disconnected, but it stay turned on. Sometimes I got these...

Good point. I would recommend to distribute existing drives across the rest of the servers and use ceph just because of HA. If HA is not so important I would use omnios + nappit.

I added storage through GUI. I have two servers mirroring data for other hosts via gluster and ceph. My config follows some howtos on proxmox wiki and other sources: Volume Name: virtual Type: Replicate Volume ID: c18748c4-b9f6-45a5-8f51-e7a4c1e32cb0 Status: Started Number of Bricks: 1 x 2 = 2...

I tried some benchmarks and it showed me difference in just a few percent between zol and openindianna. If you are ok with linux cli, don`t be afraid of solaris. It is very similar and with nappit there is a big probability you would not need anything else. Anyway I left this solution in favor...

I tried it now on my systems and I noticed some delays when installing debian8 on glusterfs when using virtio. After using iscsi it seems ok to me. Maybe it could help to change cache or drive settings? Anyway, I can only use vm on glusterfs when using cache write through.