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
> 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
> $ systemctl status email@example.com
> ● firstname.lastname@example.org - PKI Tomcat Server pki-tomcat
> Loaded: loaded (/lib/systemd/system/pki-tomcatd@.service; enabled)
> Active: failed (Result: resources)
> Dez 08 20:40:13 ipa systemd: Starting PKI Tomcat Server pki-tomcat...
> Dez 08 20:40:13 ipa systemd: Failed to load environment files: No such
> file or directory
> Dez 08 20:40:13 ipa systemd: email@example.com failed to run
> 'start-pre' task: No such file or directory
> Dez 08 20:40:13 ipa systemd: Failed to start PKI Tomcat Server pki-tomcat.
> Dez 08 20:40:13 ipa systemd: Unit firstname.lastname@example.org entered
> failed state.
Is dogtag actually running? ps -ef |grep java
You could try restarting it -
systemctl restart email@example.com
The logs should be found in the journal -->
journalctl -u firstname.lastname@example.org
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
which points to an EnvironmentFile /etc/tomcat/tomcat.conf. Does that
> 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
> 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: Starting 389 Directory Server SNMP
> Dez 09 13:25:04 ipa ldap-agent: ldap-agent: No server instances defined
> in config file
> Dez 09 13:25:04 ipa systemd: dirsrv-snmp.service: control process exited,
> code=exited status=1
> Dez 09 13:25:04 ipa systemd: Failed to start 389 Directory Server SNMP
> Dez 09 13:25:04 ipa systemd: 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.
Manage your subscription for the Freeipa-users mailing list:
Go To http://freeipa.org for more info on the project