Search results

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.

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...

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...

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

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.

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.

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...

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...

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).

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?

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

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

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...

No new ones are showing up. I can still see the old ones. Backup jobs are still running successfully, yes.

Hello, I used to have entries in "Task History" for each container or VM that informed about the daily backup. Since January 11th 2022, there are no further entries anymore. The filter is set to show ALL entries. Should it really be like this? Is there a way for the backup entries to be shown...

Hi Gregor, hattest Du hier eine Lösung zu gefunden? Gruß, Lars

Not sure, but I think there could have been quotation marks in the mails that were not filtered out (the first ones surely didn't have those). I have adapted the filter to ^"?Medizin-Shop"? and didn't get any more mails since a week, so I guess this should be ok.

ok, understood

I would still have quite a long list after splitting up. Besides, it would be a bit clumsy. Could the logging be improved to e.g. include the element ID? At least if the list wasn't changed after a mail was blocked, this would precisely tell me what to look for.

Hello, I have setup a custom spam rule that contains multiple elements for filtering against reply-to, subject, etc.. This custom rule is linked in "Mail Filter > Rules". It wouldn't be feasible to create a single rule for each element. Now, when a mail is rejected, in the logs I can only see...