Skip to content

Troubleshooting

Jump to bottom
haedri edited this page Feb 12, 2021 · 5 revisions

ProbeServlet is privileged and cannot be loaded...

An issue with the yum package for Tomcat 6 on RHEL 6 may prevent privileged apps from working correctly (see #243). You may need to create /etc/tomcat6/Catalina/localhost/probe.xml manually, similar to a Fully Manual Deployment.

Error on first request

Probe uses ServerInfo to determine what server it's running on. If you've changed this property on your server or if you are using an unsupported server, Probe may give an error when you try to access it. This is not possible to bypass this issue at the moment.

Graphs do not display

Run AWT in Headless Mode on UNIX

Some users have experienced problems (see #64) with graph images not displaying properly, especially when running Tomcat on Sun's JDK for UNIX. If you see a stack trace for a java.lang.NoClassDefFoundError thrown by a class in the org.jfree.chart package, add the following JVM command line option:

-Djava.awt.headless=true

Debian 9/ Ubuntu with OpenJDK

On Debian 9 with openjdk8 (as a debian package) the graphics did not display even though -Djava.awt.headless=true was already set. The stacktrace shows java.lang.NoClassDefFoundError thrown by a class in the org.jfree.chart.

Commenting out the assistive_technologies line in /etc/java-8-openjdk/accessibility.properties solved it. Alternativly add -Djavax.accessibility.assistive_technologies=" " to the JVM start options.

Taken from here

No fonts found in OpenJDK

Some users have experienced problems (see #161) when running OpenJDK, causing java.lang.Error: Probable fatal error:No fonts found. If switching to the Sun/Oracle JDK is not an option, consider installing a font package.

JNDI DataSource not listed

If you have configured a global JNDI DataSource in Tomcat's server.xml file or an application JNDI DataSource in the applications context.xml file (META-INF/context.xml or conf/Catalina//.xml files), but cannot see it in Psi-Probe, it might be possible that your application holds a tomcat-jdbc jar file. In this case, resolving the JNDI DataSource details does not work in Psi-Probe due to Class-Loader isolation. You can fix this by either:

  • adding <Loader delegate="true"/> to your application's context.xml file. This enforces the usage of existing jar files from Tomcat's lib directory in your application, and not to use the deployed, conflicting jar files.
  • or remove tomcat-jdbc.jar from your applications WEB-INF/lib directory

SSL at tomcat/conf/web.xml doesn't work

Earlier versions of tomcat before 8.5.x do not support fully merging web.xml items. As such if you wish to configure security constraints at tomcat level, you will need to also add the auth-constraint so that psi probe works. You will otherwise receive a message about insufficient privileges. Example of this is as follows.

Tomcat 7.0.x & 8.0.x requires

   	<security-constraint>
		<display-name>No anonymous access</display-name>
		<web-resource-collection>
			<web-resource-name>All areas</web-resource-name>
			<url-pattern>/*</url-pattern>
		</web-resource-collection>
		<auth-constraint>
			<role-name>probeuser</role-name>
			<role-name>poweruser</role-name>
			<role-name>manager</role-name>
			<role-name>manager-gui</role-name>
			<role-name>poweruserplus</role-name>
		</auth-constraint>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint>

While tomcat 8.5.x needs no auth constraint

   	<security-constraint>
		<display-name>No anonymous access</display-name>
		<web-resource-collection>
			<web-resource-name>All areas</web-resource-name>
			<url-pattern>/*</url-pattern>
		</web-resource-collection>
		<user-data-constraint>
			<transport-guarantee>CONFIDENTIAL</transport-guarantee>
		</user-data-constraint>
	</security-constraint>

My problem wasn't listed here

I have to ask: are you using the latest version of Probe? Your issue might be fixed already.

Someone might have reported the same problem, but it wasn't actually a problem with PSI Probe. Check the invalid issues to see if there's a way to fix it on your end.

No fix available? You might not be alone. Search open issues and subscribe to your issue to stay informed.

Still no luck? Please file a new issue and provide as much information as you can.

Clone this wiki locally