dogtagpki

#2874 nuxwdog won't start on Fedora
Closed: fixed Opened by mharmsen.

Closed: fixed
Reopen Issue

After installation of a running CA, I shut it down and attempted to follow the instructions to restart it under nuxwdog:

  • http://pki.fedoraproject.org/wiki/Nuxwdog

It was determined that there is a separate bug related to SELinux, so I set selinux Permissive and tried once more.

It would still not start, but Ade provided a hint on what might be wrong:

(1) start the instance without nuxwdog
(2) then do a ps for the java process
(3) compare that ps  to whats inthe nuxwdog.conf file
(4) and merge differences

Following these instructions:

# setenforce Permissive
# getenforce
Permissive
# systemctl stop pki-tomcatd@pki-tomcat.service
# pki-server nuxwdog enable

Edit "/var/lib/pki/pki-tomcat/nuxwdog.conf" and change:

ExeFile /usr/share/java-utils/java-wrapper
ExeArgs /usr/share/java-utils/java-wrapper -DRESTEASY_LIB=/usr/share/java/resteasy . . .

to:

ExeFile /usr/lib/jvm/jre-1.8.0-openjdk/bin/java
ExeArgs /usr/lib/jvm/jre-1.8.0-openjdk/bin/java -agentpath:/usr/lib/abrt-java-connector/libabrt-java-connector.so=abrt=on -DRESTEASY_LIB=/usr/share/java/resteasy . . .

and restart:

# systemctl restart pki-tomcatd-nuxwdog@pki-tomcat.service
[pki-tomcat] Please provide the password for internal: ************
[pki-tomcat] Please provide the password for internaldb: ********
[pki-tomcat] Please provide the password for replicationdb: **********

This issue has been filed since 'pki-server' creates the "nuxwdog.conf" configuration file, and this logic needs to be changed to generate it with the changes included above.

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: critical
- Issue set to the milestone: 10.5

commit 19f04606cb58f7dc6e2872e39f62d3dad427ae22
Author: Matthew Harmsen mharmsen@redhat.com
Date: Fri Dec 8 17:17:34 2017 -0700

Fix nuxwdog to work on all platforms
- dogtagpki Pagure Issue #2874 - nuxwdog won't start on Fedora
Change-Id: I5ff65c75087aeb939cb58ee7cf888bbbacb57ad5

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.3 (was: 10.5)
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.3-1.fc27

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

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
None
None
None
None
Low
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.