Ah, that'd be wonderful- that will solve my problem as I don't need NFS on
LXC. If I have some time I will try editing the gssproxy unit file and see
if that's the only stopper to running a FreeIPA replica on LXC.
On Thu, Jan 11, 2018 at 9:17 PM, Robbie Harwood wrote:
>
Alex Corcoles via FreeIPA-users
writes:
> Maybe this is a bug in the definition of gssproxy? Should it be a Wants=
> instead of a Requires=?
And anyway something else is broken with proc-fs-nfsd to boot.
Thanks,
--Robbie
signature.asc
Description: PGP
Alex Corcoles via FreeIPA-users
writes:
> Maybe this is a bug in the definition of gssproxy? Should it be a Wants=
> instead of a Requires=?
No, it's a bug I will have fixed in 7.5. The requirement needs to be
from proc-fs-nfsd on gssproxy, not the other
Maybe this is a bug in the definition of gssproxy? Should it be a Wants=
instead of a Requires=?
On Wed, Jan 10, 2018 at 9:41 PM, Robbie Harwood wrote:
> Alex Corcoles via FreeIPA-users
> writes:
>
> > Jan 10 18:47:02
Alex Corcoles via FreeIPA-users
writes:
> Jan 10 18:47:02 ctipa.h2.int.pdp7.net systemd[1]: Dependency failed for
> GSSAPI Proxy Daemon.
> -- Subject: Unit gssproxy.service has failed
> -- Defined-By: systemd
> -- Support:
Wait, so I retried the replica installation on LXC, without CA and DNS and
it worked, no gssproxy issues.
However, I retried with CA and DNS and it failed:
# journalctl -xe
Jan 10 18:47:02 ctipa.h2.int.pdp7.net systemd[1]: Starting GSSAPI Proxy
Daemon...
-- Subject: Unit gssproxy.service has
I meant traceback fot the DNS issue :-)
Could you please provide the reason why gssaproxy didn't start?
journalctl -xe
systemctl status gssproxy
journalctl -u gssproxy
2018-01-09 21:29 GMT+01:00 Alex Corcoles via FreeIPA-users <
freeipa-users@lists.fedorahosted.org>:
> Hi,
>
> I have