Thanks LnxBil. Somehow it should be obvious, if I'd have watched the syslog closely enough. Works like a charm. If anyone wants to do the same, here's my solution:
Add the script to "/etc/rsyslog.d".
nano /etc/rsyslog.d/pushover-web.conf
module(load="omprog")
template(name="webloginmsg"...
For security reasons I implemented an rsyslog config script to send a push notification on every ssh login attempt. Can this be done for the web login too?
To chime in here, it's the same issue here on my LXC reverse proxy, which is a vanilla debian 11 installation, just with nginx and lego. Disabling IPv6 did not fix it, as it was already disabled on router and proxmox. It happens once a day. A reboot fixes it. I have a DHCP lease time of 24...
I did several proxmox installations on various hardware. But this one's puzzling me. It's a quite simple setup: 32 GB RAM, ZFS-RAID on a six core CPU. Onboard are two Intel e1000e NICs. Under a Debian live installation (bullseye) they work fine. But the proxmox ISO has no luck. In Debug...
root@ct:~# ip r
default via 192.168.0.1 dev eth0
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.131
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.66
Both show the same routing tables. IPv6 is disabled.
This is something really confusing: I have a proxmox server with two networks. Each network has its own internet connection. Network interfaces of VMs and CTs can be assigned to any of them via VLAN tagging. There's one CT with Debian 11 and a nginx reverse proxy. It has both of these two...
Tested it with another Debian VM, editing the conf file by hand. Switching from "scsi0" to "sata0" and vice versa doesn't harm the VM. Changing cache mode also not. Thanks a lot for all those clarifications.
Thanks a lot for this. Interresting insights. Can changes at the vdisk settings be done without any risk? And how can I tell, if the disk is qcow2 or raw? I used trimming on other VMs before, but they were freshly installed VM, not migrated VMs like this one. You may ask, why i won't make a...
This is a fresh installation with ZFS. I have successfully migrated a 2TB VM from VirtualBox into Proxmox. Afterwards I deleted many unneeded big files within this VM. How can I tell what physical disk space this VM's disk is taking? I'm completely unsure, if the VM's trim mechanism works...
Okay, got it. The USB HDD was not mounted and what was shown was the bare directory of the root file system. Mounting the HDD shows the correct size for it. Why doesn't proxmox remount USB file systems at reboot? Does it have to be manually added in fstab?
But the issue with the root disks size...
sde 8:64 0 7.3T 0 disk
└─sde1 8:65 0 7.3T 0 part
Strangely its the same with the main volume. Its a ZRAID with 4 x 4TB HDDs. The node says under Disks/ZFS: size = 16 TB, free = 3.5 TB, allocated = 12.5 TB. But under summary: HD space 2.46 of 3.86 TB
Hi! This is something, I did not see anywhere else. I've got PVE 7.1-7 with a single node. For backup purposes an 8TB USB HDD is attached. "Disks" shows /dev/dsde and sde1 as 8 TB (it's one single EXT4 partition). When I click on that Volume (listed below the node's VMs), the summary shows 4.24...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.