Search results

  1. Add firewall rule to whole cluster via pvesh

    Hi everyone, I would like to add a firewall rule via pvesh API to the cluster. First, my proxmox version: root@tfg ~ # pveversion -v proxmox-ve: 6.1-2 (running kernel: 4.19.0-8-amd64) pve-manager: 6.1-8 (running version: 6.1-8/806edfe1) pve-kernel-helper: 6.1-8 pve-kernel-5.3: 6.1-6...
  2. Unable to use api_user and api_password from Ansible's Proxmox module

    Yes, I was using an old version of Ansible. Thanks you can close it :)
  3. Unable to use api_user and api_password from Ansible's Proxmox module

    Thank you for asnwer. I forgot to add the @pam to the api_user var :rolleyes:. Anyways i'm getting an other error. The proxmox module for Ansible doesn't have debugger mode so I don't have many info. The access.log of pvproxy shows 2 requests that seem okey: 2a01:4f8:173:159c::2 - -...
  4. Unable to use api_user and api_password from Ansible's Proxmox module

    I have to add that when I run curl -k -d "username=root@pam&password=xxxxxx" https://xxxxxxxx:8006/api2/json/access/ticket I got the ticket correctly as a JSON response using the same user and password than before
  5. Unable to use api_user and api_password from Ansible's Proxmox module

    Hi, I have installed on a debian 10 buster server Proxmox 6.1-8. I'm trying to run an Ansible script that adds a public key to the proxmox server. The code, using the Ansible docs: - proxmox: api_user: " {{ proxmox.api_user }}" api_password: "{{ proxmox.api_password }}" api_host...
  6. Backups configuration changes doesn't take effect

    Okey I can see now my error. the name storage-backups was correct but we changed it later... Okey thank you very much problem solved
  7. Backups configuration changes doesn't take effect

    cat /etc/pve/vzdump.cron # cluster wide vzdump cron schedule # Automatically generated file - do not edit PATH="/usr/sbin:/usr/bin:/sbin:/bin" 0 2 * * * root vzdump --quiet 1 --compress lzo --mailnotification failure --storage storagebox-backups --mailto mail@mail.com --exclude...
  8. Backups configuration changes doesn't take effect

    Hi every1, Last week, we changed our backups storage box from one named storagebox-vzdump to an other named storagebox-backups. We have a backup that's being made every day at 2.00 am and it's failing because can't find old storage box. I added a picture with the backup configuration. The...
  9. Backups storage became inactive

    The mount point is correctly mounted on the system. The user is from an external storagebox and we have the password located on /etc/pve/priv/storagebox-backups.cred, I logged manually to the storagebox and works fine.
  10. Backups storage became inactive

    Hi, We have a proxmox cluster with 11 nodes. We have an external storage box for our backups and 2 days ago became inactive. Seems that there's an auth problem but It was working 2 days ago and no changes to the storage box users made. Here is the output of /etc/pve/storage.cfg dir: local...
  11. About live migrations

    Yes, on the first phase we can see like 2 sub phases. First migration without logs. This first transfer we monitorize it via our switch, and we can see from 4 to 8 Mbps. Then the second phase where we can see logs and a progress bar and it goes very fast Gbps. I dont't know if the normal...
  12. About live migrations

    Hello, We have some virtual machines on our proxmox enviorment and a cluster of about 8 servers. Each server is configured with thin lv like the VMS. The fact is that, when we live migrate a VM from a server to an other we see like 3 phases: 1st fase. On this first phase the migration is slow...
  13. Problem adding new node to cluster

    Yes, that was the problem now its working with: pvecm add i1 --ring1_addr=192.168.xxx.xxx, Thank you.
  14. Problem adding new node to cluster

    Hi, We have a cluster with 8 nodes with proxmox 5.4-2 and corosync 3.0.2 configured. We do have an extra ring so a node configuration in corosync.conf look like this: node { name: i8 nodeid: 8 quorum_votes: 1 ring0_addr: 192.168.100.8 ring1_addr: 192.168.101.8 } On the...
  15. Problem adding new node to cluster

    Yes, thank you! We can close this thread.
  16. Problem adding new node to cluster

    Yes thank you! Last question, is there any easy way to downgrade our proxmox 6.0 on a debian buster to 5.4?
  17. Problem adding new node to cluster

    I don't know if this can cause any problem but we do have a redundant "ring1" net for corosync (configured as a TINC network) in case "ring0" fails. That's because we are using vSwitchs to interconnect machines and we were having issues and loosing packages. So we added a second network using...
  18. Problem adding new node to cluster

    The rest nodes have the same version of the following packages
  19. Problem adding new node to cluster

    Sorry you were right, the new node I'm trying to add is running on proxmox 6.0-2. So they are incompatible with proxmox 5.4 nodes?

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!