Recent content by sterzy

Thanks for creating that, I added the Bugzilla issue to our internal tooling as well, so updates should follow there once available!

Feel free to open a bug report for this, it might be sensible and give other user a heads-up that we are already tracking this. However, I did already add this to our internal issue tracking as a point for improvement. So hopefully it won't get lost either way. To my knowledge InfluxDB uses an...

Yeah, it sounds like the metrics collection task is struggling with the initial import here. There is just so much data on that remote, that the request takes almost three minutes to complete. That runs into a timeout on the PDM side. So yeah, we'll need to increase the timeout here or make the...

This sounds like the request takes a very long time and eventually fails. What does the following return: time pvesh get /cluster/metrics/export --history 1 --local-only 0 --start-time 0 > /dev/null on a node of the affected cluster?

Hm yeah, it seems that our Rust code is a bit stricter here. The Perl variant only checks if a connection can be established, while the Rust code does try to carry out an actual search. Since the search requires a bind, adding the realms fails. I'll update the thread here once I know more/how to...

This error indicates that you need to specify bind information in order to be allowed to search the realm. Essentially, the realm does not seem to support an anonymous search. Can you make sure that your AD host is correctly configured to allow anonymous search from the PDM?

Makes sense and happy to help, please mark this thread as “Solved” by clicking the “Edit Thread” button above and adding the “SOLVED” prefix. This should help other users with similar issues find this solution faster. Thanks!

That sounds like the remote that's trying to initialize the migrating is encountering an internal server error. Is there any more information in that host's logs that could give us a hint? Going off this message alone, my guess would be that something about your network topology may have...

Alright 1.1.4 should have made its way to enterprise. Please try to update with the workaround outlined above. Thank you for your patience!

It looks like the users you are trying to sign in are restricted in some way: At least that's what LDAP wiki says about your error (AcceptSecurityContext error), with data 52f: https://ldapwiki.com/wiki/Wiki.jsp?page=Common%20Active%20Directory%20Bind%20Errors

At time of my last post it wasn't published at all yet, by now it made its way to no-subscription. So no, currently this is not in the enterprise repo yet. You'll either have to wait a little longer, or go down to the no-sub repository, then update once from there and switch back to enterprise...

As promised a short update: The patch got applied and will be included in the 1.1.4 update for proxmox-datacenter-manager [1]. The package has not yet been published, it will likely become available shortly. Once it is available you should be able to update from the enterprise repository with...

I send a patch for this, I'll update this thread once we have an update ready for you! https://lore.proxmox.com/pdm-devel/20260603115442.361184-2-s.sterz@proxmox.com/

Can you run the following commands and post the output here? proxmox-datacenter-manager-admin support-status update proxmox-datacenter-manager-admin support-status get Make sure the output does not include any sensitive information before posting it.

Thanks for the notice, I'll see if I can take another look there. Sorry for the inconvenience.