#361 Starting CA starts its clone if clone is installed on the same system.
Closed: migrated 3 years ago by dmoluguw. Opened 11 years ago by awnuk.

Starting CA starts its clone if clone is installed on the same system:

  1. CA and its clone are both "inactive":

systemctl status pki-cad@pki-ca.service
pki-cad@pki-ca.service - PKI Certificate Authority Server pki-ca
Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/pki-cad@.service/pki-ca

systemctl status pki-cad@pki-ca-clone.service
pki-cad@pki-ca-clone.service - PKI Certificate Authority Server pki-ca-clone
Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled)
Active: inactive (dead)
CGroup: name=systemd:/system/pki-cad@.service/pki-ca-clone

  1. CA start:

systemctl start pki-cad@pki-ca.service

  1. CA and its clone are both active:

systemctl status pki-cad@pki-ca.service
pki-cad@pki-ca.service - PKI Certificate Authority Server pki-ca
Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled)
Active: active (running) since Mon, 08 Oct 2012 11:26:57 -0700; 5s ago
Process: 2922 ExecStart=/usr/bin/pkicontrol start ca %i (code=exited, status=0/SUCCESS)
Main PID: 3178 (java)
CGroup: name=systemd:/system/pki-cad@.service/pki-ca
└ 3178 /usr/lib/jvm/jre/bin/java -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin...

systemctl status pki-cad@pki-ca-clone.service
pki-cad@pki-ca-clone.service - PKI Certificate Authority Server pki-ca-clone
Loaded: loaded (/lib/systemd/system/pki-cad@.service; enabled)
Active: active (running) since Mon, 08 Oct 2012 11:26:56 -0700; 13s ago
Process: 2921 ExecStart=/usr/bin/pkicontrol start ca %i (code=exited, status=0/SUCCESS)
Main PID: 3179 (java)
CGroup: name=systemd:/system/pki-cad@.service/pki-ca-clone
└ 3179 /usr/lib/jvm/jre/bin/java -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin...


[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.

Metadata Update from @awnuk:
- Issue set to the milestone: UNTRIAGED

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/932

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata