Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.

This article describes the issue of report generation failure, due to an application error.

 

When reports are generated, NSM displays the following error:
 

Job abandoned due to application error. Please verify the status of following server processes and retry:
- gproGDH
- gproDDH
- devServerManager

In the gproGDM log, you can see the Can't connect to X11 window server using ':991.0 error, when generating the report.

2011/11/29-17:24:31.611 notice [GDH-16:356-0] 356-0 is now RUNNING...
Exception in thread "GDH-16:356-0" java.lang.InternalError: Can't connect to X11 window server 
using ':991.0' as the value of the DISPLAY variable.
	at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
	at sun.awt.X11GraphicsEnvironment.access$100(X11GraphicsEnvironment.java:52)
	at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:155)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:131)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:169)
	at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
	at sun.awt.X11.XToolkit.(XToolkit.java:89)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:169)
	at java.awt.Toolkit$2.run(Toolkit.java:834)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:826)
	at java.awt.KeyboardFocusManager.initPeer(KeyboardFocusManager.java:399)
	at java.awt.KeyboardFocusManager.(KeyboardFocusManager.java:395)
	at java.awt.DefaultKeyboardFocusManager.(DefaultKeyboardFocusManager.java:47)
	at java.awt.KeyboardFocusManager.getCurrentKeyboardFocusManager(KeyboardFocusManager.java:165)
	at java.awt.KeyboardFocusManager.getCurrentKeyboardFocusManager(KeyboardFocusManager.java:156)
	at java.awt.Component.getFocusTraversalKeys_NoIDCheck(Component.java:7069)
	at java.awt.Component.setFocusTraversalKeys_NoIDCheck(Component.java:7039)
	at java.awt.Container.setFocusTraversalKeys(Container.java:2927)
	at javax.swing.JComponent.setFocusTraversalKeys(JComponent.java:4123)
	at javax.swing.JTable.(JTable.java:591)
	at javax.swing.JTable.(JTable.java:553)
	at com.netscreen.devicecomm.LogReport$ReportChartTable.(LogReport.java:2397)
	at com.netscreen.devicecomm.LogReport$ReportChartTable.(LogReport.java:2377)
	at com.netscreen.devicecomm.LogReport.init(LogReport.java:611)
	at com.netscreen.devicecomm.LogReport.(LogReport.java:246)
	at com.netscreen.devicecomm.GuiDirectiveHandler.getReport(GuiDirectiveHandler.java:2418)
	at com.netscreen.devicecomm.GuiDirectiveHandler.processReports(GuiDirectiveHandler.java:2394)
	at com.netscreen.devicecomm.GuiDirectiveHandler.doRunLogBasedReports(GuiDirectiveHandler.java:2173)
	at com.netscreen.devicecomm.GuiDirectiveInterface.processDirective(GuiDirectiveInterface.java:112)
	at com.netscreen.devicecomm.WorkerThread.run(WorkerThread.java:185)

On checking the process, Xvfb is not running.

[root@NSMXpress errorLog]# ps auxww | grep Xvfb
root      7592  0.0  0.0  5100  648 pts/1    S+   23:35   0:00 grep Xvfb

Make sure to install the necessary system update file, before upgrading NSM. Execute /usr/X11R6/bin/Xvfb -pn :991.0 &.

Verify if Xvfb is running:

[root@NSMXpress errorLog]# ps auxww | grep Xvfb
root 7592 0.0 0.0 5100 648 pts/1 S+ 23:35 0:00 grep Xvfb
nsm 27973 0.0 0.0 9072 3504 ? S Jan08 0:00 /usr/X11R6/bin/Xvfb -pn :991.0

Reboot the NSM server, if you have upgraded or installed NSM.
 

2020-10-09: Archived article.

2020-11-21 :Tagged article for EOL/EOE