we have temporarily canceled the cockpit deployment and retrieved a freeipa
backup to recover the normal state while we understand how to make freeipa and
cockpit work together
Thanks for your help Rob
___
FreeIPA-users mailing list --
Phinees Garandi via FreeIPA-users wrote:
> For your question : Is there a reason you are forcing domain, realm and
> server?
>
> I have to provides server and realm as discovery never readlly worked.
>
> Indeed DNS seems to be ok regarding below commands
>
> [root@test ~]# host -t SRV
The server returned a 401 to the authentication request. You'll want to
look in the apache error log file on the IPA server to see if that holds
any clues.
rob
Phinees Garandi via FreeIPA-users wrote:
> Hello Rob,
>
> I also tested using the --force flag the output is the same
>
> this is the
For your question : Is there a reason you are forcing domain, realm and server?
I have to provides server and realm as discovery never readlly worked.
Indeed DNS seems to be ok regarding below commands
[root@test ~]# host -t SRV _kerberos._udp.toto.fr
_kerberos._udp.toto.fr has SRV
Hello Rob,
I also tested using the --force flag the output is the same
this is the content of /var/log/ipaclient-install
`2021-12-02T15:31:13Z DEBUG Logging to /var/log/ipaclient-install.log
2021-12-02T15:31:13Z DEBUG ipa-client-install was invoked with arguments [] and
options: {'unattended':
Important detail I installed cockpit "https://cockpit-project.org/; and it was
after that I had the bug.
I don't know if the cockpit installation had an impact
___
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an
Phinees Garandi via FreeIPA-users wrote:
> Hello everyone
>
> I encountered a bug while installing freeipa client.
>
> the command fail and I have this as an error message :
>
> `Please make sure the following ports are opened in the firewall settings:
> TCP: 80, 88, 389
> UDP: 88
lejeczek via FreeIPA-users wrote:
>
>
> On 06/01/18 19:51, lejeczek via FreeIPA-users wrote:
>> Failed to obtain host TGT: Major (851968): Unspecified GSS failure.
>> Minor code may provide more information, Minor (2529638936):
>> Preauthentication failed
>
> hi guys,
> I hit that error again.
On 06/01/18 19:51, lejeczek via FreeIPA-users wrote:
Failed to obtain host TGT: Major (851968): Unspecified GSS
failure. Minor code may provide more information, Minor
(2529638936): Preauthentication failed
hi guys,
I hit that error again. What I noticed is
- on that candidate client when
lejeczek via FreeIPA-users
writes:
> On 08/01/18 08:46, Florence Blanc-Renaud wrote:
>> On 01/06/2018 08:51 PM, lejeczek via FreeIPA-users wrote:
>>>
>>> $ ipa-client-install --no-ntp --force-join
>>> Discovery was successful!
>>> ...
>>> Also note that
On 08/01/18 22:46, Robbie Harwood wrote:
lejeczek via FreeIPA-users
writes:
$ ipa-client-install --no-ntp --force-join
krb5kdc[1560686](info): preauth (encrypted_timestamp) verify
failure: Preauthentication failed
But after many tries(randomly)
On 08/01/18 22:46, Robbie Harwood wrote:
lejeczek via FreeIPA-users
writes:
$ ipa-client-install --no-ntp --force-join
krb5kdc[1560686](info): preauth (encrypted_timestamp) verify
failure: Preauthentication failed
But after many tries(randomly)
lejeczek via FreeIPA-users
writes:
> $ ipa-client-install --no-ntp --force-join
>
> krb5kdc[1560686](info): preauth (encrypted_timestamp) verify
> failure: Preauthentication failed
>
> But after many tries(randomly) suddenly it would succeed.
Do the
On 08/01/18 08:46, Florence Blanc-Renaud wrote:
On 01/06/2018 08:51 PM, lejeczek via FreeIPA-users wrote:
hi everyone
I'm trying a client, when I do:
$ ipa-client-install --no-ntp --force-join
Discovery was successful!
...
Also note that following ports are necessary for
ipa-client
On 01/06/2018 08:51 PM, lejeczek via FreeIPA-users wrote:
hi everyone
I'm trying a client, when I do:
$ ipa-client-install --no-ntp --force-join
Discovery was successful!
...
Also note that following ports are necessary for ipa-client working
properly after enrollment:
TCP: 464
15 matches
Mail list logo