Recent content by Donner

+1 i need to set mydomain = mydoamin.org myhostname = mail.mydoamin.org into /etc/pmg/templates/main.cf.in for correct HELO message like in PTR but after that server stops relay incoming messages with

After node shutdown/reboot command, proxmox starts to shutdown all vms and often windows server vms initiate update procesess, so full shutdown may need 10, 20 or even more minutes. Is there a way to forbid that behaviour, cause at critical conditions like shutdown by UPS command we wouldn't...

Ah, find one already https://bugzilla.proxmox.com/show_bug.cgi?id=5071 so, will waiting for fix

I cant do something with it, that pattern like /dev/<zfspoolname>/<zvol> is hardcoded in ZFSoiSCSI storage client. So thats pussibly a bug if there no way to restore old path way

for example: TASK ERROR: Could not open /dev/dRAID3/vm-122-disk-0 zpool is ok and vm-122-disk-0 too, just missing that path. I have several nodes, not all updated yet, so i was seeing that there was "/dev/NVMe" (pool name) before update and restart, and now it gone, only that path, the pool...

Hi, i noticed that after recent updates there no path like /dev/<zfspoolname> anymore. Is there way to fix it? I'm using proxmox host also like a storage for ZFS over iSCSI (LIO) and it seems this feature uses paths like /dev/<zfspoolname>/<zvol> that's not working any more.

figured out. Thats my fall. I'm using "zfs autobackup" and forgot to clear mountpoints, so root fs was mounted multiple time. After clearing mountpoints all start working.

Yes, no luck.

tried update another node - all works fine, even with old kernel (win22 bug) syslog when corosync trying start as a service but if i just strat corosync from shell all start working

Hi, there is some starnge things with corosync after last update of my 4 nodes cluster, one of nodes wonts start corosync.service so vms wont start, cos no quorum, other nodes inaccessive from web gui if i logged from that node etc. systemctl restart corosync.service gives no effect, but if i...

ah, sorry, yes its proxmox host, storage managed by proxmox cluster (storage.cfg) all storage are ZFS pools iscsi target is targetcli sharing some zvols nfs - standart nfs-server sharing some zfs datasets

Hi! After some proxmox updates i realised that after reboot my host cant start iscsi and nfs services correct in time. Logs shows that iscsi cant find vdevs and nfs cant find datasets like Jun 28 01:01:58 smstorage exportfs[2526]: NOTE: this default has changed since nfs-utils version 1.0.x...

Figured out by myself, shows list of iscsi interfaces, choose correct, and for my case will show all targets and make configs in /etc/iscsi/nodes Bring them up by Chill

Hello, i'm trying to move from hyper-v to proxmox at HPE Blade BL460c g9 with VC Flex switch and iSCSI MSA 2040 Blade has HPE 650FLB network card, and with VC Flex switch, can devide regular ethernet and iSCSI links, so i can configure iSCSI inintiator from blades BIOS. I can see my MSA(target)...