Search results

You bet: root@xxxx:~# ss -tlpn State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 4096 127.0.0.1:85 0.0.0.0:* users:(("pvedaemon worke",pid=9392,fd=6),("pvedaemon worke",pid=9391,fd=6),("pvedaemon...

Interesting, I'm still on 7.0: root@xxxx:~# pveversion pve-manager/7.0-11/63d82f4e (running kernel: 5.11.22-4-pve)

I'm afraid I don't have a pveproxy file in /etc/default: root@xxxx:~# ls -al /etc/default/ total 110 drwxr-xr-x 3 root root 27 Sep 9 12:48 . drwxr-xr-x 86 root root 174 Nov 16 09:19 .. -rw-r--r-- 1 root root 124 Feb 24 2021 bridge-utils -rw-r--r-- 1 root root 159 Aug 9 07:41 ceph...

I have a Proxmox 7 install ("xxxx" below), which previously was working fine. However I noticed this morning that I cannot connect to the web GUI as I usually do (pveproxy on port 8006). I haven't made any recent changes that I'm aware of. I can see from systemctl that it's up and running, and...

Aah that explains it perfectly - thank you for your help!

I recently set up a new node for my cluster. On previous installs I have done mirrored vdevs, which I understand isn't very space-efficient, but has good redundancy. However in this most recent case I had a stack of spare 3TB drives, so I used RAIDZ3 to get a decent tradeoff for...

I've found this, which is interesting: https://patchwork.kernel.org/patch/7670771/ Mentions a patch to what looks like the kernel code which is generating this.

I'm having an error spam my node console, and I can't seem to even find out where it's originating. I've tried googling, but in many of the examples I am finding, the user seems to at least have an "when I do xyz, I get this message" - I don't know what's happening to trigger this error, so I'm...

Aah ok. I did not know about zed, I'll look that up. Thanks! And yes, I powered down, removed that drive, and powered back up. Everything seems fine, so I guess I wasn't using that drive after all. :) Thanks again!

My email notifications have been broken since I set up my cluster a year ago. I recently fixed them, and immediately got notified that I have one node in my cluster which has a failed sector on one of my disks. The email is the following: This message was generated by the smartd daemon running...

Aha! It was the "tank-proxmox-isos" storage I had set up. It was configured with none content type. Thanks so much for pointing me to that storage file! I was actually not using that storage, so I simply removed it and the messages are gone now. Thanks! :D

dir: local path /var/lib/vz content iso,backup,vztmpl zfspool: local-zfs pool rpool/data content rootdir,images nodes proxmox-a,proxmox-b sparse 1 zfspool: tank pool tank content rootdir,images nodes proxmox-a zfspool...

Oh, I should also note that this container has been cloned from a template. However it's an unlinked clone, so it's not sharing any storage or anything with the parent node it was cloned from.

I have a container which shows the follow error when I try to set values via the terminal: root@my-host-name:~# pct set 132 -protection 0 storage does not support content type 'none' I have tested with other values (such as "-unprivileged") and I receive the same error. Note that the set...

I have some aliases I'd like to load in my container when someone logs into them. I created a file called /etc/profile.d/aliases.sh, and this works as expected when I SSH into my container. However I have noticed that when I log into a container via the pct enter <VMID> command, this file is not...

Yes, I verified with "date" command, and they all match (to the second).

I have two nodes, A and B. I decided to try out two-factor authentication. I logged into node A, clicked the top-right menu in the web GUI, clicked "TFA", and set up a TOTP secret in my phone's 2FA app (scanned the QR code, verified it, etc.). I now am required to enter the 2FA code whenever I...

Excellent explanation. Thank you so much!

I have the following in my container's config file: unprivileged: 1 lxc.mount.entry: /tank/git_repositories mnt/git_repositories none bind 0 0 # GUEST HOST NUM lxc.idmap: u 0 100000 1000 lxc.idmap: u 1000 200101 1 lxc.idmap: u 1001 101001 64535...