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

[chymian]

Am Mittwoch, 10. Dezember 2014, 10:28:17 schrieb thierry bordaz:
> On 12/09/2014 11:52 PM, chymian wrote:
> >> Am Dienstag, 9. Dezember 2014, 14:10:48 schrieb thierry bordaz:
> >>
> >> On 12/09/2014 01:54 PM, 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.
> >>>
> >>>
> >>> 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.
> >> Hello,
> >>
> >> regarding this issue. Is there a agent log file under /var/log/dirsrv/agent/
> >> ?
> >>
> >> thanks
> >> thierry
> >>
> > thierry,
> > no there aren’t any files, except the slapd-EB8-LAN/ directory in /var/log/dirsrv/
> > not even an  /var/log/dirsrv/agent/
> >
> > anything else I can provide?
> 
> Hello Guenter,
> 
> It is looking like no server have been configured in 
> /etc/dirsrv/config/ldap-agent.conf to be monitored.
> So the ldap-agent started by this service returns an errors at startup.
> As you are not using snmp, like Rich said you may ignore this service 
> failure.
> 
> thanks
> thierry

hello thierry,
yes, it’s seems to be empty – same as on a plain cos6/ipa 3.3 installation.
but there, the service does not get started, and therefore, no error is thrown.
may I suggest to do a check in the startup scripts weather a service is configured or not, or "systemctl disable" it by default?

thx for your help
guenter

  
> >   
> > thanks,
> > guenter
> >
> >>> 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
>