Search results

  1. L

    Proxmox & Ceph

    I am planning to get in touch with Ceph on Proxmox. Let me first introduce my hardware I am planning to use before having my questions. Here is the motherboard with CPU, and it got one downside more of that in a second: https://geizhals.de/biostar-a10n-8800e-v6-1-a2280308.html The downside of...
  2. L

    Some Certification Issue

    This helped: https://forum.proxmox.com/threads/novnc-spice-not-working-on-clustered-nodes.67163/post-301461 But still nVNC not working on node2
  3. L

    Some Certification Issue

    I was cowardly trying to repair the not working noVNC client on node2. so I run: ```pvecm updateverts -f``` As it sometime happens with coward actions, things get worse. Now I cannot handle the machines on node2 when I logged in to node1. How can I fix this?
  4. L

    No Replication is done over Bond

    There is an old trick to solve this, go "Datacenter" > "Options" > "Migration Settings" and guess what ... :P
  5. L

    No Replication is done over Bond

    I noticed the replication of VM/LXC is not done over the Bond configured on Cluster creation. When looking at RX/TX, with the following command, I noticed the traffic only goes over vmbr0. ip -s link show vmbr0 Only some bytes use bond0, where do I have to configure to use the bond for...
  6. L

    Snapshot rpool/ROOT/pve-1@preHistory.txt-deleted

    Okay, this is wired: Screen still shows "^@ Reading all physical volumes. This may take a while..." but the server is actually running and all looks as expected. Do I have to do something to get the normal login screen? [Edit] Yes, CTRL + ALT + F2 gives the login.:D
  7. L

    Snapshot rpool/ROOT/pve-1@preHistory.txt-deleted

    Hi something went wrong, testing zfs rollback I cannot start the Proxmox Server anymore, here is how I did the snapshot and rollback: zfs snapshot rpool/ROOT/pve-1@preHistory.txt-deleted zfs rollback rpool/ROOT/pve-1@preHistory.txt-deleted reboot Now it looks like it is stuck when rebooting on...
  8. L

    Error when updating using apt.

    Oh thanks for the hint, here is something missing, put the ip and FQDN and run apt install proxmox-mailgateway-container again
  9. L

    Error when updating using apt.

    127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # --- BEGIN PVE --- 127.0.1.1 mail.der-space.de mail # --- END PVE ---
  10. L

    Error when updating using apt.

    Meine Fehlermeldung, hier steht etwas von hostname lookup, deshalb mal die FQDN des Servers: # hostname -f mail.der-space.de # hostname mail ing up libpve-apiclient-perl (3.0-3) ... Setting up proxmox-spamassassin (3.4.4-2) ... Setting up libxml-parser-perl (2.44-4) ... Setting up...
  11. L

    Error when updating using apt.

    Oh looks like I may got the same error, can I hijack this threat?
  12. L

    'SOLVED' awk buggy - % = modulo

    That did it, don't know why I didn't think about the percent as modulo.
  13. L

    'SOLVED' awk buggy - % = modulo

    tried with gawk also, same result for me, my workaround is to devide the numbers so they are have only one position to the left side of the comma. awk version: GNU Awk 4.2.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.1.2)
  14. L

    'SOLVED' awk buggy - % = modulo

    Awk does not compare numbers correct. Input data: Filesystem Type 1048576-blocks Used Available Capacity Mounted on udev devtmpfs 7933 0 7933 0% /dev tmpfs tmpfs 1598 10 1589...
  15. L

    Monitoring: LXC - VMalloc & Committed Memory

    How to think about Critical Warnings within a monitoring system in regards to VMalloc and Committed Memory when using LXC? Attached screenshot shows phobos and daimos as PVE and the other two are LXC containers doing their things:
  16. L

    Migration fails: " found stale volume copy"

    Problem gelöst, im Verzeichnis /rpool waren noch reste des subvolumes vorhanden nach "rm -r /rpool/data/subvol-103-disk-0" konnte problemlos migriert werden ( ͡° ͜ʖ ͡°)
  17. L

    Migration fails: " found stale volume copy"

    Ein Tag zuvor ist der Host, in diesem Fall "daimos" vollgelaufen, da die Backup Platte nicht gemounted war. Nachdem die Backups beseitigt waren liess sich die Kiste nicht neustarten. Also alle LXC Container heruntergefahren und den Host vom Strom getrennt. Nach dem Boot sind alle Container...
  18. L

    New LDAP Sync feature - questions around "full" sync, and ETA?

    You can try to add the CA Certificate to your Proxmox Host: Assuming the CA Certificate is allready copied from host ldap1.example.com to proxmox.example.com. mkdir /usr/local/share/ca-certificates/extra scp root@ldap1.example.com:/opt/improvisedCA/certs/cacert.pem...
  19. L

    New LDAP Sync feature - questions around "full" sync, and ETA?

    Somehow users don't populate. Not sure if the syntax for group_filter is correct, but this one works with ldapsearch. my domains.cfg ldap: ldap base_dn ou=people,dc=example server1 ldap2.example user_attr uid bind_dn uid=ldap.read,ou=services,dc=example...