Search results

you mean bastard operator from hell writing in an it forum,,naa cant be :) well not really easier, its much easier todo this via console and kvm machine, the hole process takes under 4 minutes and you better get used to it if you use zfs as a root system cause its the only way to resucue that...

why going for an usb? also without lara this isnt really much fun either. and hetzner has no ipmi, shame on them. in essence what we do is - start rescue mode (whcih is basically linux in a ramdisk booted from network) - we download install image (into that virtual ram disk in which rescue...

@spirit just fyi, i found out that ovh does uindeed guarantee that 100mbit freebie vlan well theri service quality is just shit but same as the payed 1gbit version

all updated, no crashes ever since. for me its solved

i assume you have the latest patch. provided in this threat by spirit, installed on all nodes ?

@spirit jsut a quick update, now a week in, i remove the second fallback ring/link and keep it on one vrack ring only without adjusting timeout or anything (basically default config otherwise) patch works well. occasional fault on that line for a second without any consequences as far i can...

@David Herselman also that ping give you only a little indication that something is wrong. i would advise you get some monitoring going like https://www.librenms.org/ should be sufficent. that would give you an excet time state of network and you can compare it to error logs @spirit i bet he...

looks promising first 24 hours without any incident Sep 21 08:48:00 h3 systemd[1]: Started Proxmox VE replication runner. Sep 21 08:48:59 h3 corosync[29388]: [KNET ] link: host: 4 link: 0 is down Sep 21 08:48:59 h3 corosync[29388]: [KNET ] link: host: 1 link: 0 is down Sep 21 08:48:59 h3...

lol btw ask him if their colleagues in london are drinking on the job, i have a horrifying support log as a testimony but seriously, im aware that i could hit a bottleneck on the vrouter when some jackass saturates their line but this doesnt really fit the error picture here. my issues where...

the free one, reason is simple that we wanted to leave corosync on a dedicaded alone so that gbit wouldnt help me at all anyway. also 25€ additional for a 100€ server is kinda ridicolous oh btw they DONT gurantee anything at the 1gbit vrack either. what you maybe mean is the public interface...

lol ofc,.. i also deactivated debugging for now and the second ring, run it now purely on the vrack ring. which was the most unstable condition yet, lets see

finally cluster broke today, installed patch, pray for the best

the crazy part is i activated debug almsot 2 days ago, i had a few rx transmission errors but no crashes and cluster is stable. so either its a wierd coincidence or debug alone changed something lol

use the 2012r2 drivers then, they should work on 10 also 10 isnt that different from 2012r2 at all. its the same new codebase based on windows 8. im pretty confident that this isnt really windows the issue but the drivers. which drivers exactly do you use? beta or stable?

tyvm, will follow and debuggin, spamming my logs right now but ofc no hangs yet :) i also added the autorestart in systemd and see if its of any use.

oups i do have fdatas but interrestingly not with creation time at crashes. also the node that usually crash has none at all while all other nodes have 1-3

please,.. first of dont poisen this topic, its to important. second i know what im doing. im fine. since you can´t read or comprehend what i already wrote please dont try to give me advice copy pasted from the basic howtos. since you having a hard time to comprehend, one last time, no other...

so whats the vhost storage? did you check the drives? what driver/storage do you use? virtio? i would recommend trying to switch to scsi, todo that you need to activate that driver first. you can activate it via regestry or (for one machine easier) via the following: simple trick, -add one...

This Stop error describes a KMODE_EXCEPTION_NOT_HANDLED issue. The parameters in this Stop error message vary, depending on the configuration of the computer. Not all "STOP: 0x0000001E" errors are caused by this issue. Cause This issue occurs because of an NTFS file system memory...

i would test it bnut do you reall think it would help to even further reduce the time pong has to come? the patch lowers this value based on average instead of peak. so before, if you max ping was 1.5ms you wont time out on a pong at 1.5. with the new patch you may time out sooner. specially...