#1391 pkidaemon script checks for the existence of wrong symlinks during nuxwdog startup
Closed: Fixed None Opened 8 years ago by mharmsen.

pkidaemon script checks for the existence of wrong symlinks during nuxwdog startup

How reproducible:

always

Steps to Reproduce:

1, Install the latest Dogtag packages -- ie. CS 10.2.4
2. Configure a CA as normal, and then stop the instance.
3. Convert the CA to use nuxwdog

   pki-server instance-nuxwdog-enable <instance_name>

4. Restart the instance using:

   systemctl restart pki-tomcatd-nuxwdog@<instance_name>.service

Actual results:

Restart fails

[root@spider ~]# systemctl status pki-tomcatd-nuxwdog@pki-tomcat.service -l
pki-tomcatd-nuxwdog@pki-tomcat.service - PKI Tomcat Server pki-tomcat Started by Nuxwdog
   Loaded: loaded (/usr/lib/systemd/system/pki-tomcatd-nuxwdog@.service; enabled)
   Active: failed (Result: exit-code) since Thu 2015-05-28 11:04:13 EDT; 35s ago
  Process: 2054 ExecStartPre=/usr/bin/pkidaemon start tomcat %i (code=exited, status=1/FAILURE)

May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com pkidaemon[2054]: WARNING:  Symbolic link '/etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd@pki-tomcat.service' does NOT exist!
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com pkidaemon[2054]: INFO:  Attempting to create '/etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd@pki-tomcat.service' -> '/lib/systemd/system/pki-tomcatd@.service' . . .
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com pkidaemon[2054]: ln: failed to create symbolic link ‘/etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd@pki-tomcat.service’: Permission denied
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com pkidaemon[2054]: ERROR:  Failed to create '/etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd@pki-tomcat.service' -> '/lib/systemd/system/pki-tomcatd@.service'!
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com systemd[1]: pki-tomcatd-nuxwdog@pki-tomcat.service: control process exited, code=exited status=1
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com systemd[1]: Failed to start PKI Tomcat Server pki-tomcat Started by Nuxwdog.
May 28 11:04:13 spider.idmqe.lab.eng.bos.redhat.com systemd[1]: Unit pki-tomcatd-nuxwdog@pki-tomcat.service entered failed state.

Expected results:

You should be prompted for various passwords and the instance should start 
   successfully

vakwetu provided the following workaround for this ticket:

Workaround so that you can continue testing.

This will just disable the symlink check for the systemd symlinks.

    Edit /usr/share/pki/scripts/operations

    Comment out the following line by putting a # at the start of the line:

    # check_symlinks ${pki_systemd_dir} ${PKI_USER} ${PKI_GROUP}

vakwetu fixed this in 'master':

commit ffd6d399a3ebcd1f96192d7d4bb999a043f5617d
Author: Ade Lee alee@redhat.com
Date: Thu May 28 15:29:35 2015 -0400

BZ1226025 -  pkidaemon script checks for wrong symlinks for nuxwdog startup

Fixed startup script to account for nuxwdog

Metadata Update from @mharmsen:
- Issue assigned to vakwetu
- Issue set to the milestone: 10.2.5

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1952

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata