Search results

  1. L

    USB ports change on host restart

    No, I didn't. But after switching to "Use USB Vendor/Device ID", the problem didn't show up again, afair.
  2. L

    iSCSI: Unnütze Einträge bzgl. "no route to host" im daemon.log

    Auch nach einem Neustart keine weiteren Einträge mehr. Allerdings wüsste ich zu gerne, warum das auf einmal auftrat, denn nach der Einrichtung des SAN, die erst wenige Monate her ist, kam das noch nicht.
  3. L

    iSCSI: Unnütze Einträge bzgl. "no route to host" im daemon.log

    Habe die nicht benötigten IPs/Verbindungen nun auf einem Host testweise entfernt und seitdem sind bisher keine weiteren Einträge im Log bzgl "no route to host" aufgetaucht. Neustart des Servers wird die Tage noch getestet, wenn es passt. iscsiadm -m node -T ${IQN} -p 10.1.4.170 -I...
  4. L

    iSCSI: Unnütze Einträge bzgl. "no route to host" im daemon.log

    atl-vm04:~# iscsiadm -m node 10.0.1.100:3260,1 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.1.100:3260,1 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.2.120:3260,3 iqn.1986-03.com.hp:storage.msa2040.15472745cf 10.0.2.120:3260,3 iqn.1986-03.com.hp:storage.msa2040.15472745cf...
  5. L

    iSCSI: Unnütze Einträge bzgl. "no route to host" im daemon.log

    Wurde bei der Einrichtung vor ein paar Monaten so gemacht: iscsiadm -m discovery -t sendtargets -p 10.0.3.140 -I iscsi_enp2s0f0 && \ iscsiadm -m discovery -t sendtargets -p 10.1.3.150 -I iscsi_enp2s0f1 D.h. selbst wenn ich das nun manuell lösche und es zunächst funktioniert, wird es immer...
  6. L

    iSCSI: Unnütze Einträge bzgl. "no route to host" im daemon.log

    Hallo, wir nutzen ein SAN im Zusammenspiel mit Proxmox, welches direkt (ohne Switch) über zwei Kabel am Server angeschlossen ist. Alles funktioniert soweit, aber mir sind störende Einträge im Log aufgefallen, die ich gerne unterbinden würde. Der Server hat zwei Interfaces für iSCSI. Je eines...
  7. L

    PVE sending email notifications on successful backup jobs

    Same here, waiting for a fix. Don't want to mess up the settings in "Datacenter > Notifications" as it is unclear to me what should be done there.
  8. L

    [SOLVED] Setting of "keep-last" is ignored?

    Should have checked the other backup problem first... Just noticed this: 109: 2023-08-13 10:37:13 INFO: running 'proxmox-backup-client prune' for 'vm/109' 109: 2023-08-13 10:37:14 ERROR: prune 'vm/109': proxmox-backup-client failed: Error: permission check failed - missing...
  9. L

    [SOLVED] Setting of "keep-last" is ignored?

    Hello, I have changed the retention settings from using the storage defined one (something like 3 daily, 3 weekly or so) to specifying it at PVE level with "keep-last=2". Waited around two weeks, but after the (failed) backup last weekend, the older backups still exist. Will they only be...
  10. L

    Connection Error to port 8006

    Thanks for letting other users know... ;-)
  11. L

    [SOLVED] Failed login with Active Directory authentication

    Turned out the certificate was missing (probably deleted by accident). I recreated it and imported it into the "NTDS\Personal" certificate store (local computer store didn't work). Then I was able to connect again, no restart needed. This thread helped in finding the cause.
  12. L

    Authentication using LDAP / AD stopped working

    Thanks a lot! This showed "no peer certificate available" which lead me to the solution: As the once existing cert somehow got lost, I recreated it and imported it into the "NTDS\Personal" certificate store. Worked instantly, no restart needed.
  13. L

    Are the backups "windows active directory aware" ?

    Thanks, wasn't aware of this. I found this article explaining the technical stuff: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/introduction-to-active-directory-domain-services-ad-ds-virtualization-level-100 Interesting part: A more recent article about why restoring...
  14. L

    [SOLVED] Failed login with Active Directory authentication

    When a user tries to login with AD credentials, he only gets "Failed login" and in /var/log/daemon.log I see this: Mar 1 17:31:38 atl-vm03 pvedaemon[1695423]: authentication failure; rhost=::ffff:192.168.120.52 user=jdoe@ActiveDirectory msg=Connection reset by peer I found several other...
  15. L

    Are the backups "windows active directory aware" ?

    You wrote "...caused USN rollback errors when a virtual active directory server was restored from an image...". Exactly this might happen when you have more than one DC and restore a backup (even if that backup itself is consistent and would work if you only had one DC).
  16. L

    Authentication using LDAP / AD stopped working

    Same problem here. @stanislav: Could you please explain what your exact problem with the ssl cert was? How did you check this? How did you fix it?
  17. L

    Are the backups "windows active directory aware" ?

    Be careful when there is more than one DC (which is recommended). You should never restore a DC in this case: https://www.itprotoday.com/server-virtualization/never-snapshot-domain-controller-here-s-why
  18. L

    Backup eines Exchange Server: Best Practice

    Ok, schade ;-) Aber danke für die Info.
  19. L

    Task history doesn't show backups anymore

    Other task logs look normal. Partial output from journalctl from yesterday. Nothing unusual afaics. Nov 21 22:30:12 atl-vm03 proxmox-backup-proxy[333160]: starting new backup on datastore 'atl-vm04': "vm/109/2022-11-21T21:30:04Z" Nov 21 22:30:12 atl-vm03 proxmox-backup-proxy[333160]: download...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!