Recent content by Ryan Anderson

  1. R

    PVE API Return Values

    It looks like I need to get the CPUs, Memory, and Disk size from /nodes/{node}/qemu/{vmid}/status/current instead. That is giving me the information I need.
  2. R

    PVE API Return Values

    I'm on Proxmox 8.2.4. Below is the result of the pvesh get command. It doesn't have this information in the config file, but the API documentation says this is optional information, I guess I'm confused on how to see what resources are allocated to this machine. I can see the HD size and could...
  3. R

    PVE API Return Values

    Can anyone tell me why I'm only getting some of the information for the config when I use the API? I'm really wanting the Memory/vCPUs/ and HD Size. This it the only information I'm getting from: /api2/json/nodes/{node}/qemu/{vmid}/config. However the API documentation show a whole lot more...
  4. R

    Email Notifications

    @Dunuin & @Neobin - Thanks for the information. I was thinking I was missing something obvious. I will look into a separate monitoring tool for node connectivity as that is my main concern.
  5. R

    Email Notifications

    I'm sorry if this is posted somewhere else, maybe my searching skills need polished. PVE 7.2-11 What email notifications are supposed to be sent out? The only notifications that I receive are when backups run. Are there other notifications and if so how do I configure them? I do successfully...
  6. R

    How to automate backup process?

    That isn't going to be part of this script. Just place a text file called .pxarexclude in the folder that you want to exclude files/folders from and put in that file the excluded files/folders. More detailed explanation...
  7. R

    Proxmox Backup Client Hangs

    Hello, I currently have the client on a physical computer trying to backup the home directory of a user, however is seems to be getting stuck uploading new chuck. Are there any logs that I can look though? Example Output on Client: root@office:~# proxmox-backup-client backup...
  8. R

    How to automate backup process?

    I agree with the plain text password issue. I currently have the script in my /root folder so only root has access. I also have the backups limited by the prune settings on the PBS. I currently keep 7 days, 4 weeks, 2 months, 1 year.
  9. R

    How to automate backup process?

    I created a script like the following (I didn't want to leave the passwords as variables, so I cleared them after use): export PBS_PASSWORD=PASSWORD export PBS_ENCRYPTION_PASSWORD=PASSWORD (If you don't use encryption you can leave this line out) export...
  10. R

    PVE to PBS Encryption

    Ok, thanks for clarifying.
  11. R

    PVE to PBS Encryption

    I want to know if I am missing anything on the encryption of my backups from my PVE nodes to my PBS. Everything seems to be running okay, but when I go the the PBS, i see that the backups are "mixed". I expect that from the top level as some aren't encrypted. But when I drill down to the last...
  12. R

    Cluster Communication

    Also, here is my corosync.conf for each machine: PVE01 logging { debug: off to_syslog: yes } nodelist { node { name: pve01 nodeid: 1 quorum_votes: 1 ring0_addr: pve01-corosync } node { name: pve02 nodeid: 2 quorum_votes: 1 ring0_addr: pve02-corosync...
  13. R

    Cluster Communication

    Here is my network configs (I have also attached them if that easier to read): PVE01 # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please...
  14. R

    Cluster Communication

    This seems to describe my issue perfectly, except that I'm not using a Linux bridge for my Corosync network. I'm using the NIC directly. https://forum.proxmox.com/threads/proxmox-ve-4-0-cluster-multicast-problems.24635/ Anything anyone else can think of to help?
  15. R

    Cluster Communication

    I tried on pve01-corosync and pve02-corosync and got different responses: PVE01 root@pve01:~# omping -m 239.192.177.19 pve01-corosync pve02-corosync pve02-corosync : waiting for response msg pve02-corosync : waiting for response msg pve02-corosync : waiting for response msg pve02-corosync ...