On Fri, 2022-01-28 at 16:02 +0100, Florence Blanc-Renaud wrote:
> Hi,
> you can do
> (on another server)
> $ ipa server-del --force server.example.com
# ipa server-del --force server.example.com
Removing server.example.com from replication topology, please wait...
ipa: WARNING: Forcing removal of
Hi Edward,
I think you may try to create the task manually
ldapmodify -D "cn=directory manager" -w ... -a <,cn=entryuuid task,cn=tasks,cn=config
objectClass: top
objectClass: extensibleObject
basedn:
cn: entryuuid_fixup_
!
If you want to fixup only specific entries you many add the following
Hi,
Thanks for the tip.
Any workaround in the mean time?
I couldn't find one.
Thanks
___
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
Fedora Code of Conduct:
Russell Jones via FreeIPA-users wrote:
> Thanks,
>
> I ended up finding the issue from another mailing list post. ntpd was
> not running on this host and the time got skewed too much from the other
> masters.
>
> For what it's worth, the ipa-healthcheck script did not catch this
> issue. Might
Thanks to all for the fix, you save my day!
Le 25/12/2021 à 17:06, Dungan, Scott A. via FreeIPA-users a écrit :
Hi, Per.
I ran into the same problem and Alexander referred me to this link:
https://www.mail-archive.com/freeipa-users@lists.fedorahosted.org/msg12583.html
The fix for us was
Hi,
you can do
(on another server)
$ ipa server-del --force server.example.com
This should clean up all references to server.example.com
(on server.example.com)
$ ipa-client-install --uninstall -U
$ kdestroy -A
$ ipa-client-install ...
$ kinit admin
$ ipa-replica-install ...
HTH,
flo
On Fri,
Thanks,
I ended up finding the issue from another mailing list post. ntpd was not
running on this host and the time got skewed too much from the other
masters.
For what it's worth, the ipa-healthcheck script did not catch this issue.
Might be something to add?
On Fri, Jan 28, 2022 at 2:49 AM
Hey,
thanks for pointing that out.
Issue resolved!
For google:
1. Look at /etc/httpd/conf.d/ipa-pki-proxy.conf for secret.
2. Fix /etc/pki/pki-tomcat/server.xml, 4 occurance of those secrets.
3. Restart tomcat services
4. Profit.
Cheers!
-Chris.
On 28/01/2022 14:21, Rob Crittenden
On Tue, 2022-01-25 at 16:45 +0200, Alexander Bokovoy wrote:
>
> On another server, use the ipa server-del command to delete
> server.example.com from the topology:
Indeed, I missed this part. :-( I suppose this cannot be done now that
the machine has been redployed as a client
Christian Reiss via FreeIPA-users wrote:
> Hey folks,
>
> happyily using FreeIPA in my personal hobbyist space across 50vms and 8
> hosts. It worked like a charm. Ever since a few days ago I am unable to
> delete hosts, disabling/ enabling users for example works, but not
> deleting hosts. I am
Hey folks,
happyily using FreeIPA in my personal hobbyist space across 50vms and 8
hosts. It worked like a charm. Ever since a few days ago I am unable to
delete hosts, disabling/ enabling users for example works, but not
deleting hosts. I am using AlmaLinux 8 with vendor-supplied FreeIPA
Hi,
you can find troubleshooting tips in
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/trouble-gen-replication
HTH,
flo
On Thu, Jan 27, 2022 at 6:54 PM Russell Jones via FreeIPA-users <
12 matches
Mail list logo
