[Freeipa-users] Unit pki-tomcatd at pki-tomcat.service entered failed state @ vanilla install on jessie – with log attached

[Ade Lee]

On Tue, 2014-12-09 at 13:54 +0100, chymian wrote:
> hey people,
> 
> after a successful install of ipa 4.0.5-2 on jessie, the named services started flawless during setup. see attached log, Installation summary (line 3107)
> but after reboot, it refuses to start. (did this install a couple times, on vanilla jessie)
> 
> I can reach & work with Dogtag https://ipa.eb8.lan:8443/ca, but not the admin-services on https://ipa.eb8.lan/ca/ee/ca and https://ipa.eb8.lan/ca/agent/ca.
> 
> 
> $ systemctl status pki-tomcatd at pki-tomcat.service
> ● pki-tomcatd at pki-tomcat.service - PKI Tomcat Server pki-tomcat
>    Loaded: loaded (/lib/systemd/system/pki-tomcatd at .service; enabled)
>    Active: failed (Result: resources)
> 
> Dez 08 20:40:13 ipa systemd[1]: Starting PKI Tomcat Server pki-tomcat...
> Dez 08 20:40:13 ipa systemd[1]: Failed to load environment files: No such file or directory
> Dez 08 20:40:13 ipa systemd[1]: pki-tomcatd at pki-tomcat.service failed to run 'start-pre' task: No such file or directory
> Dez 08 20:40:13 ipa systemd[1]: Failed to start PKI Tomcat Server pki-tomcat.
> Dez 08 20:40:13 ipa systemd[1]: Unit pki-tomcatd at pki-tomcat.service entered failed state.
> 
> 

Is dogtag actually running?  ps -ef |grep java

You could try restarting it - 
systemctl restart pki-tomcatd at pki-tomcat.service

The logs should be found in the journal --> 
journalctl -u pki-tomcatd at pki-tomcat.service

Other debug logs should be found under /var/log/pki/pki-tomcat/.  Please
provide a tar of that directory.

I am curious what the unit file looks like:  On Fedora, its
at /etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd at pki-tomcat.service
which points to an EnvironmentFile /etc/tomcat/tomcat.conf.  Does that
file exist?

Ade

> a second service fails to start:
> 
> $ systemctl status dirsrv-snmp.service
> ● dirsrv-snmp.service - 389 Directory Server SNMP Subagent.
>    Loaded: loaded (/lib/systemd/system/dirsrv-snmp.service; enabled)
>    Active: failed (Result: exit-code) since Di 2014-12-09 13:25:04 CET; 5min ago
>   Process: 156 ExecStart=/usr/sbin/ldap-agent /etc/dirsrv/config/ldap-agent.conf (code=exited, status=1/FAILURE)
> 
> Dez 09 13:25:04 ipa systemd[1]: Starting 389 Directory Server SNMP Subagent....
> Dez 09 13:25:04 ipa ldap-agent[156]: ldap-agent: No server instances defined in config file
> Dez 09 13:25:04 ipa systemd[1]: dirsrv-snmp.service: control process exited, code=exited status=1
> Dez 09 13:25:04 ipa systemd[1]: Failed to start 389 Directory Server SNMP Subagent..
> Dez 09 13:25:04 ipa systemd[1]: Unit dirsrv-snmp.service entered failed state.
> 
> 
> except these, I was able to subscribe a jessie-client with autodiscovery right after I did configure the ipa-server, before first reboot.
> 
> 
> any help appreciated, since I do not have much experience with IPA – yet.
> guenter