Environment
Novell Sentinel 6.1 RD
Situation
After rebooting the Sentinel RD server, users can no longer run reports using the Web UI. The Web UI reports the following errors;
"Can't connect to X11 window server using ':0.0' as the value of the DISPLAY
variable"
and
"Error Could not initialize class sun.awt.X11GraphicsEnvironment"
When running the sentinel.sh stop command, the "tomcat" and "activemq" processes are not stopped completely thus when you restart sentinel, sentinel.sh start, these processes remain and you get the above errors due to the already open connections.
The X11 errors seem to occur when the DISPLAY env variable is set for the default novell user before the novell user calls the sentinel.sh start command to start the processes. Exactly why the processes are not stopped is still under investigation.
"Can't connect to X11 window server using ':0.0' as the value of the DISPLAY
variable"
and
"Error Could not initialize class sun.awt.X11GraphicsEnvironment"
When running the sentinel.sh stop command, the "tomcat" and "activemq" processes are not stopped completely thus when you restart sentinel, sentinel.sh start, these processes remain and you get the above errors due to the already open connections.
The X11 errors seem to occur when the DISPLAY env variable is set for the default novell user before the novell user calls the sentinel.sh start command to start the processes. Exactly why the processes are not stopped is still under investigation.
Resolution
To resolve this issue follow these steps as a workaround:
1: su - novell
2: cd $APP_HOME/bin
3: sentinel.sh stop
4: ps -ef | grep novell
if necessary manually kill the "tomcat" and "activemq" processes
5: Ensure that your novell user does NOT have the DISPLAY environment variable set, env | grep DISPLAY
If the DISPLAY env is set, issue this command;
unset DISPLAY
6: Restart sentinel, sentinel.sh start
Allow a few minutes to restart before logging back into the web UI and verify that you can now run reports.
1: su - novell
2: cd $APP_HOME/bin
3: sentinel.sh stop
4: ps -ef | grep novell
if necessary manually kill the "tomcat" and "activemq" processes
5: Ensure that your novell user does NOT have the DISPLAY environment variable set, env | grep DISPLAY
If the DISPLAY env is set, issue this command;
unset DISPLAY
6: Restart sentinel, sentinel.sh start
Allow a few minutes to restart before logging back into the web UI and verify that you can now run reports.