Systemctl does not seem to work

[pjakobi]

I issued the following command :systemctl enable pki-tomcatd@pki-tomcat
Then, I rebooted my server.
When server ready, I run "systemctl enable pki-tomcatd@pki-tomcat". Result : "inactive (dead)"...
There is certainly something I miss...
Can someone help ?

[fmarco76]

Before the enable command was the instance working? How did you install? What is written in the log? What system are you using?

[pjakobi]

Now for your questions :
1/ I run on Fedora 42. The system has just been installed fresh. The only additional package is 389-ds.
2/ "systemctl [start | restart] pki-tomcatd@pki-tomcat" works perfectly.
3/ I ran "systemctl enable --now pki-tomcatd@pki-tomcat" and rebooted.
4/ After reboot, pki-tomcatd is not running. I could not find anything in the logs but I may have not read the correct file.
5/ Doing a "systemctl restart" is effective : "systemctl status" returns "Active (running)"

[pjakobi]

Thxs again for your help

[fmarco76]

after point 3 the status shows the service enabled?

[fmarco76]

It could be a problem of boot order (es. DS starting after PKI). You should find something in the pki log (in /var/log/pki/pki-tomcat/ca/)

[pjakobi]

after point 3 the status shows the service enabled?
Yes. You can see it in the log I sent.

I will inspect the /var/log/pki/pki-tomcat/ca/ files later tonight.
Best,

[pjakobi]

Traces ::
root@dogtag:/var/log/pki/pki-tomcat# reboot

Broadcast message from [email protected] on pts/1 (Thu 2025-07-17 17:13:16 CEST):

The system will reboot now!

root@dogtag:/var/log/pki/pki-tomcat# Connection to dogtag closed by remote host.
Connection to dogtag closed.
pascal@g4:$ ssh dogtag
Last login: Thu Jul 17 14:45:44 2025 from 192.168.122.1
pascal@dogtag:$ sudo -i
root@dogtag:# systemctl status pki-tomcatd@pki-tomcat
○ [email protected] - PKI Tomcat Server pki-tomcat
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: inactive (dead)
root@dogtag:# systemctl restart pki-tomcatd@pki-tomcat
root@dogtag:~# systemctl status pki-tomcatd@pki-tomcat
● [email protected] - PKI Tomcat Server pki-tomcat
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: active (running) since Thu 2025-07-17 17:13:55 CEST; 2s ago
Invocation: 5d3ba130c7a2440e9e777531e5f7c319
Process: 1074 ExecStartPre=/usr/sbin/pki-server upgrade pki-tomcat (code=exited, status=0/SUCCESS)
Process: 1077 ExecStartPre=/usr/sbin/pki-server migrate pki-tomcat (code=exited, status=0/SUCCESS)
Process: 1136 ExecStartPre=/usr/bin/pkidaemon start pki-tomcat (code=exited, status=0/SUCCESS)
Main PID: 1148 (java)
Tasks: 20 (limit: 2302)
Memory: 223M (peak: 223.3M)
CPU: 5.848s
CGroup: /system.slice/system-pki\x2dtomcatd.slice/[email protected]
└─1148 /usr/lib/jvm/jre-21-openjdk/bin/java -Dcom.redhat.fips=false -classpath /usr/share/tomcat/bin/bootstrap.ja>

Jul 17 17:13:55 dogtag.dev server[1148]: Java virtual machine used: /usr/lib/jvm/jre-21-openjdk/bin/java
Jul 17 17:13:55 dogtag.dev server[1148]: classpath used: /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli>
Jul 17 17:13:55 dogtag.dev server[1148]: main class used: org.apache.catalina.startup.Bootstrap
Jul 17 17:13:55 dogtag.dev server[1148]: flags used: -Dcom.redhat.fips=false
Jul 17 17:13:55 dogtag.dev server[1148]: options used: -Dcatalina.base=/var/lib/pki/pki-tomcat -Dcatalina.home=/usr/share/tomc>
Jul 17 17:13:55 dogtag.dev server[1148]: arguments used: start
Jul 17 17:13:55 dogtag.dev server[1148]: NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add->

[pjakobi]

As far as I can see, your software does not create a symlink when issuing "systemctl enable [email protected]" (try with another service and compare messages).
So I created the link manually :
ln -s /etc/systemd/system/pki-tomcatd.target.wants/[email protected] /etc/systemd/system/multi-user.target.wants/[email protected]
and now it works : dogtag is automatically started at reboot.

[fmarco76]

It should by done by systemctl and not by the software. Could you open an issue to investigate the problem?

[pjakobi]

done. Thxs.

[fmarco76]

@pjakobi Thanks!