Can't connect to X11 window server using ':10.0' as the value of the DISPLAY variable.
Hi,
I am using LDOM in Solaris Server. Below are the the system information: Code:
# uname -a I've installed Weblogic usng Generic Installer with GUI. During this installation I've enabled X11 and connect via putty without any issue. Below is the system scenario before installation: (weblogic is installed as "oracle" local user) Code:
After installation, when I am trying to run the weblogic configuration script it encounter below error and unable to open GUI window. I've also tried with VNC and still same: ERROR: Code:
Any help will be highly appreciated Thanks rh.mahfuz |
Code:
xhost + |
Quote:
Code:
firefox & |
Quote:
All it does is allow ANYONE on the system access to the X server.... basically, turning off all security. Normally the client system is using domain sockets, not TCP sockets, thus xhost will NOT suddenly permit connections. It is sshd on the remote system that controls the limited TCP socket (normally only using localhost connections). Now, for the problem. firefox is one of the applications that attempts to direct an existing firefox process to open windows. If firefox is running on Windows, being directed to open an X window may fail (I don't have a Windows box to try this on, so this part is conjecture). The problem with weblogic, however, is different - weblogic on the remote system is NOT running as the user. I believe it running as the oracle user, which may not have access to the Xauthorization file, and not as the user login. This depends on how the putty login to the server is done, and how X forwarding is configured on the server (it is possible for it to be disabled for specific users via the "AllowUsers" options). You might have to run the weblogic configuration tool in console mode. |
xhost has everything to do it if native X feature is used for remote application execution. Of course, if SSH is used for X forwarding xhost is not needed.
|
Quote:
Xhost is worthless. All it really does is disable security. The standard installation does not enable TCP connections to the X server, and hasn't for almost 15 years. Even when TCP connections were used routinely, xhost was bad security, and it was easy enough to transfer X authentication across the net. Been doing that ever since X11 release 2. |
Well, I'm using it almost daily. Not over the internet, of course. I see no reason not to use it on trusted LAN. Besides, you can use xhost to enable just one IP address / hostname.
|
There is no such thing as a "trusted lan". Specially when it includes a Windows based system.
Even "just one" allows anyone on that "one" (or anyone attached to the wire/wireless) to capture everything. Been there, done that (well, actually, it was done to me). The X protocol doesn't inherently support any security whatsoever. Originally, it included encryption - but the US export ban on encryption blocked that - so it had to be removed. Along with any comments/hooks/ whatever that could be used to support encryption. All authentication/passwords/messages are sent in clear text, available to any thing to capture. ssh has been the best alternative - and it works. Some side benefits as well since the ssh protocol combines multiple X packets and compresses them, it reduces the traffic (more beneficial for long distance). One last thing, the op reported that firefox worked fine over the connection. |
@jpollard & @Emerson Thanks both of you for the reply.
I've logged into the system as oracle user and tring to run the configuration script as oracle user Before I run the configuration script, I'd installed Weblogic using GUI and during GUI installation I'd logged in as oracle user and ran the installation script as oracle user. To run installation script I used below command Code:
oracle$ java -jar weblogic-installer.jar Code:
root# ls -al .Xauthority I am confused..... is it X11 display problem or something wrong with server/software version compatibility issue?? :( :( Thanks. |
Its tricky but I've got the solution:
Its not X11/Display issue. I've changed some thing inside "config.sh file as below: I've deleted "${JVM_D64}" form the below line: before Code:
JVM_ARGS="-Dpython.cachedir=/tmp/cachedir ${JVM_D64} ${UTILS_MEM_ARGS} ${SECURITY_JVM_ARGS} ${CONFIG_JVM_ARGS}" Code:
JVM_ARGS="-Dpython.cachedir=/tmp/cachedir ${JVM_D64} ${UTILS_MEM_ARGS} ${SECURITY_JVM_ARGS} ${CONFIG_JVM_ARGS}" I can complete the configuration without any issue but Weblogic 12.2.1.0 required JDK 1.8 to run ./startWeblogic.sh or to open the administrative console http://hostname:7001/console So I install JAVA 1.8 and then try to run the ./config.sh but getting same Display error (no matter whether I add or remove ${JVM_D64} ) To solve this I edit the config file to specify the JAVA_HOME location for JDK 1.7 : Code:
JAVA_HOME=/usr/jdk/jdk1.7.0_80 Thats all and solved my issue. |
Hi,
I hit this same issue during WebLogic upgrades, and didn't want to be switching Java versions. After a lot of investigation we found that there is a Solaris issue that causes this behaviour. See below for details of Oracle documentation on this. Once we applied the recommend patch, the problems were resolved. Hope this saves someone the days of work it took to get this sorted for us!! Regards, Adrian https://support.oracle.com/epmos/fac...1&id=1545998.1 (may require support login) APPLIES TO: Oracle WebLogic Server - Version 10.3.1 to 12.1.2.0.0 SunOS SYMPTOMS The below error message could occur when using the configuration wizard in GUI mode on Solaris 10 update 10 by running <WLS_HOME>/common/bin/config.sh. Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using 'xxx.xxx.xxx.xxx:0.0' as the value of the DISPLAY variable. at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65) at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:110) at java.security.AccessController.doPrivileged(Native Method) at sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:74) CHANGES This worked but some Solaris patches have been installed then. CAUSE The installation of the "Patch #119059 revision 62" was the cause of this error. This problem corresponds to unpublished defect 16226141 - CAN'T CONNECT TO X11 WINDOW SERVER AFTER APPLYING PATCH #119059-61 OR ABOVE SOLUTION Apply Solaris OS Patch #119059-64. |
Where I can download that patch, it's not available in the oracle downloads.
|
Quote:
|
|
All times are GMT -5. The time now is 11:14 PM. |