Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMatthew Harmsen
2016-03-22 23:48:53 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/2226
KRA setup over LDAPS fails with a NullPointerException in ProxyRealm.findSecurityConstraints.
https://fedorahosted.org/freeipa/ticket/5570https://www.redhat.com/archives/pki-devel/2016-February/msg00100.html
== curl ==
{{{
# curl http://master1.ipa.test:8080/ca/admin/ca/getStatus
<!DOCTYPE html><html><head><title>Apache Tomcat/8.0.26 - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 500 - </h1><div class="line"></div><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>exception</b></p><pre>java.lang.NullPointerException
com.netscape.cms.tomcat.ProxyRealm.findSecurityConstraints(ProxyRealm.java:114)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1526)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1482)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:745)
</pre><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/8.0.26 logs.</u></p><hr class="line"><h3>Apache Tomcat/8.0.26</h3></body></html>
}}}
== journalctl ==
{{{
# journalctl -f -u pki-tomcatd
...
Mar 01 12:10:31 master1.ipa.test server[8061]: Mar 01, 2016 12:10:31 PM org.apache.catalina.core.ContainerBase backgroundProcess
Mar 01 12:10:31 master1.ipa.test server[8061]: WARNING: Exception processing realm com.netscape.cms.tomcat.ProxyRealm@65ac2207 background process
Mar 01 12:10:31 master1.ipa.test server[8061]: java.lang.NullPointerException
Mar 01 12:10:31 master1.ipa.test server[8061]: at com.netscape.cms.tomcat.ProxyRealm.backgroundProcess(ProxyRealm.java:109)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1127)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:5554)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1377)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)
Mar 01 12:10:31 master1.ipa.test server[8061]: at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1349)
Mar 01 12:10:31 master1.ipa.test server[8061]: at java.lang.Thread.run(Thread.java:745)
}}}
{{{
# rpm -qa tomcat pki-ca freeipa-server
pki-ca-10.2.6-15.fc23.noarch
freeipa-server-4.3.90-0.fc23.x86_64
tomcat-8.0.26-2.fc23.noarch
}}}
tduehr reported in the ticket:
I'm seeing this exception in a FreeIPA server as well. KRA installation worked fine but this seems to be preventing the CMS from starting properly resulting in all CA operations to fail. Using the CA/KRA master for CA operations works without a problem.