I'm currently on the latest release and might have to do this. I have a CentOS node with 3 targets, and I removed one of them but still have proxmox trying to make connections to it? It's very strange I'm wondering if I run the command will it cause issues with the other iSCSI targets?
Was sure I wasn't going to get a response as it's a bit of a strange issue. For those who may run into this strange issue I'm not sure if this will fix it for you, but I fixed this by running #apt reinstall gzip --purge
Both Live/Time-Range mode aren't showing anything. Below is my JournalD config perhaps I may have made an unsupported change?
Not sure what happened or what I'm even supposed to look at. I have an old proxmox server that's not really doing anything. Its fully up to date. I was just poking around and noticed Syslog in the GUI isn't showing anything? But I can see it if I tail/cat it manually in the server.
So I have 2 Interfaces on my NAS. One is a 10G fiber and one is a LAGG with 4 1G. I switched to the LAGG port and it worked for me without an issue.... Been struggling with this for like ever now... Not sure if MTU has anything to do with the issues? I've tried all different configurations for...
I'm not seeing the 5.15 kernel is this only available for enterprise subscription?
deb https://ftp.debian.org/debian bullseye main contrib
deb https://ftp.debian.org/debian bullseye-updates main contrib
deb https://httpredir.debian.org/debian/ bullseye main contrib non-free
Dell r720 - Proxmox 7.1.7
Dell r720 - Truenas 12.0-U7
They're on separate subnets but it's always been like this and they both can communicate both ways nothing has changed other than the errors just showing up one day and my backups are not working...
I have no idea what it is I've freshly...