#775 ipa-server-install abrt on java in tomcat
Closed: Fixed None Opened 10 years ago by nkinder.

We're seeing abrt crashes during ipa-server-install. They don't appear so far
to be affecting the install but, thought I'd get another opinion.

Steps to Reproduce:
1. /usr/sbin/ipa-server-install --setup-dns --no-forwarder -p Secret123 -P
Secret123 -a Secret123 -r TESTRELM.COM -n testrelm.com --ip-address=$MASTER_IP
--hostname=hp-z600-02.testrelm.com -U

Actual results:
1. see abrt crash but server appears installed.

Expected results:
2. no crash

Additional info:

abrt emailed report:

abrt_version: 2.1.7
cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on
-DRESTEASY_LIB=/usr/share/java/resteasy-base -classpath /usr/share/tomcat/bin/b
ootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daem
on.jar -Dcatalina.base=/var/lib/pki/pki-tomcat
-Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs=
-Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp -Djava.security.manager
-Djava.security.policy==/var/lib/pki/pki-tomcat/conf/catalina.policy
-Djava.util.logging.config.file=/var/lib/pki/pki-tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start
executable: /usr/share/tomcat/bin/bootstrap.jar
java_executable:
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x86_64/jre/bin/java-abrt
kernel: 3.10.0-33.el7.x86_64
last_occurrence: 1381706256
pid: 7135
pkg_arch: noarch
pkg_epoch: 0
pkg_name: tomcat
pkg_release: 2.el7
pkg_version: 7.0.40
runlevel: N 3
time: Sun 13 Oct 2013 07:17:36 PM EDT
uid: 0
username: root

backtrace:
:Exception in thread "Thread-2" java.util.MissingResourceException: Can't find
bundle for base name LogMessages, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(ResourceBund
le.java:1499) [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x8
6_64/jre/lib/rt.jar!/java/util/ResourceBundle.class]
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322) [j
ar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x86_64/jre/lib/rt.
jar!/java/util/ResourceBundle.class]
at java.util.ResourceBundle.getBundle(ResourceBundle.java:721) [jar:fi
le:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x86_64/jre/lib/rt.jar!/
java/util/ResourceBundle.class]
at
com.netscape.cmscore.apps.CMSEngine.getLogMessage(CMSEngine.java:1217)
[unknown]
at
com.netscape.cmscore.apps.CMSEngine.getLogMessage(CMSEngine.java:1297)
[unknown]

at com.netscape.certsrv.apps.CMS.getLogMessage(CMS.java:700) [unknown]

 at com.netscape.cms.logging.LogFile.shutdown(LogFile.java:866)
[unknown]
at
com.netscape.cms.logging.RollingLogFile.shutdown(RollingLogFile.java:144)
[unknown]
at com.netscape.cmscore.logging.LogQueue.shutdown(LogQueue.java:67)
[unknown]
at
com.netscape.cmscore.logging.LogSubsystem.shutdown(LogSubsystem.java:174)
[unknown]
at
com.netscape.cmscore.apps.CMSEngine.shutdownSubsystems(CMSEngine.java:1692)
[unknown]
at com.netscape.cmscore.apps.CMSEngine.shutdown(CMSEngine.java:1639)
[unknown]

at com.netscape.cmscore.apps.CMSEngine$1.run(CMSEngine.java:278)
[unknown]

environ:
KI_INSTANCE_PATH=/var/lib/pki/pki-tomcat
KI_UNSECURE_PORT=8080
KI_GROUP=pkiuser
KI_LOCKFILE=/var/lock/pki/tomcat/pki-tomcat
KI_PIDFILE=/var/run/pki/tomcat/pki-tomcat.pid
:CATALINA_BASE=/var/lib/pki/pki-tomcat
:NAME=pki-tomcat
KI_LOCKDIR=/var/lock/pki/tomcat
KI_PIDDIR=/var/run/pki/tomcat
KI_INSTANCE_INITSCRIPT=/var/lib/pki/pki-tomcat/pki-tomcat
:TOMCAT_GROUP=pkiuser
ATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
:TOMCAT_USER=pkiuser
:_=/usr/lib/jvm/jre/bin/java
WD=/usr/share/tomcat
:LANG=en_US.UTF-8
:TOMCAT_PIDFILE=/var/run/pki/tomcat/pki-tomcat.pid
:SERVICE_NAME=pki-tomcat
:RESTART_SERVER=/var/lib/pki/pki-tomcat/conf/restart_server_after_configuration
KI_USER=pkiuser
:TOMCAT_PROG=pki-tomcat
:SHLVL=3
:CATALINA_PID=/var/run/pki/tomcat/pki-tomcat.pid
KI_WEB_SERVER_TYPE=tomcat
:TOMCAT_LOCKFILE=/var/lock/subsys/pki-tomcat
KI_INSTANCE_ID=pki-tomcat

jvm_environment:
:sun.java.command : org.apache.catalina.startup.Bootstrap start
:sun.java.launcher : SUN_STANDARD
:java.home :
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x86_64/jre
:java.class.path : /usr/share/tomcat/bin/bootstrap.jar:/usr/share
/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
:java.library.path :
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
:sun.boot.class.path : /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2
.6.el7.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.
4.2.6.el7.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.
6.el7.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.
4.2.6.el7.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.
2.6.el7.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6
.el7.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2
.6.el7.x86_64/jre/lib/netx.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6
.el7.x86_64/jre/lib/plugin.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6
.el7.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.
el7.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7
.x86_64/jre/classes
:sun.boot.library.path :
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2.6.el7.x86_64/jre/lib/amd64
:java.ext.dirs : /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.40-2.4.2
.6.el7.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
:java.endorsed.dirs :
:cwd : /usr/share/tomcat
:java.vm.version : 24.0-b56
:java.vm.name : OpenJDK 64-Bit Server VM
:java.vm.info : mixed mode, sharing
:java.vm.vendor : Oracle Corporation
:java.vm.specification_name : Java Virtual Machine Specification
:java.vm.specification.vendor : Oracle Corporation
:java.vm.specification.version : 1.7


master: 3b2b7ea239fe85c0b90169402e0d1480122d20cc

branch 10.0: 2df3cad81c04c8d0fdbb28b619eace642b07fa62

Metadata Update from @nkinder:
- Issue assigned to edewata
- Issue set to the milestone: 10.0.6

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

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