Kristian Petersen via FreeIPA-users wrote:
> You mentioned that once before, but that path doesn't seem to exist on
> my server for some reason. When I go to /var/log/pki i get:
> -bash-4.2$ cd /var/log/pki/
> -bash-4.2$ ls
> pki-server-upgrade-10.4.1.log pki-upgrade-10.4.1.log server
>
> In
You mentioned that once before, but that path doesn't seem to exist on my
server for some reason. When I go to /var/log/pki i get:
-bash-4.2$ cd /var/log/pki/
-bash-4.2$ ls
pki-server-upgrade-10.4.1.log pki-upgrade-10.4.1.log server
In a previous reply, I ran a command you asked me to that show
Kristian Petersen wrote:
I'm still struggling with this one and it seems at least partially
responsible for the UI misbehaving as we discussed in another thread.
Have you had any new insights regarding this?
I'd start with looking at /var/log/pki/pki-tomcat/ca/debug. You want to
find the lates
I'm still struggling with this one and it seems at least partially
responsible for the UI misbehaving as we discussed in another thread. Have
you had any new insights regarding this?
On Mon, Oct 9, 2017 at 3:54 PM, Kristian Petersen
wrote:
> The installation is a standard RedHat IdM install wit
The installation is a standard RedHat IdM install with DNS, SMB, and CA
services installed.
The output of the ldapsearch you mentioned is:
-bash-4.2$ ldapsearch -LLL -Y GSSAPI -b
cn=ipa1.chem.byu.edu,cn=masters,cn=ipa,cn=etc,dc=chem,dc=byu,dc=edu
SASL/GSSAPI authentication started
SASL username:
Kristian Petersen wrote:
> That path does not exist.
Ok, then you need to describe your installation, particularly what
services are enabled.
IPA will try to start services based on this search so seeing this
output would be useful as well:
$ ldapsearch -LLL -Y GSSAPI -b
cn=`hostname`,cn=masters
That path does not exist.
On Tue, Oct 3, 2017 at 8:03 AM, Rob Crittenden wrote:
> Kristian Petersen via FreeIPA-users wrote:
> > When I recently updated one of my IPA servers (it reports
> > 4.5.0-21.el7_4.1.2 in yum), the result was that it could start back up
> > because pki-tomcatd kept faili
Kristian Petersen via FreeIPA-users wrote:
> When I recently updated one of my IPA servers (it reports
> 4.5.0-21.el7_4.1.2 in yum), the result was that it could start back up
> because pki-tomcatd kept failing. I was able to get it running for now
> by ignoring the failure of that one service, bu
