Getting Started Errors
Im having some difficulty. I've installed Fedora Core 4 on a virtual server platform for testing and I have installed SGD just fine.
This invironment is at home, behind a linksys router. I've set the webserver on port 81.
I have tried all port forwarding, and even set the SGD server to be in the DMZ and still I am unable to get it to connect from outside my network. Well let me rephrase that, it does indeed connect to the webserver, but the graphical icon that says LOADING with the horizontal bar scrolling from left to right sits there forever. It prompts me to accept an install from Sun, and I do accept that, but it never takes me to the login screen.
Internally, however, It takes me right to the login screen and I can log in.
Problem 1... Now Problem 2, all the windows applications I publish work fine, but none of the applications that are hosted on the linux box will execute, EXCEPT the vt420 (servername)
The Array Manager, Session Manager, Gnome Terminal, and xclock all will not run.
advice?
[1055 byte] By [
henington] at [2007-11-26 8:04:36]

# 1
Here is an error im noticing when its trying to load one of the apps hosted on the linux box.
(gnome-session:20115): Gtk-WARNING **: cannot open display:
Connection to SYSTEMNAME closed.
and when running the array manager,
Connected
../.././bin/bin/ttaxset: unable to open display ""
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:159)
at java.awt.Window.<init>(Window.java:317)
at java.awt.Frame.<init>(Frame.java:419)
at java.awt.Frame.<init>(Frame.java:384)
at javax.swing.JFrame.<init>(JFrame.java:150)
at com.sco.tta.admin.gui.RunAdminGui$AdminFrame.<init>(RunAdminGui.java:260)
at com.sco.tta.admin.gui.RunAdminGui.<clinit>(RunAdminGui.java:68)
Connection to SERVERNAME closed.
# 2
Just a shot in the dark late this evening.
It appears you have two issues:
1) X services cannot acquire the display - I believe in your hmmmm - memory late this evening /etc/inet.d there is a Tarantella file. Contained within the file is a variable TTASSHCLIENT it is commented out, uncommon and modify to read
TTASSHCLIENT="/user/bin/ssh -X"; export TTASSHCLIENT
I found that information somewhere on the Internet when we were setting up the evaluation environment of SDG.
Hope that corrects the X issues experienced.
Second issue - 3144 need to be open on the firewall by default I'm way out there on this one as I do not have a very good handle overall of your configuration.
Me had many issues with the described symptom bars scrolling - set a trap and noticed 3144 was the requested port.
Hope this helps - if not let me know, we are running on FC4 and later this evening will go to FC5
# 3
I did try that,
I changed it to
TTASSHCLIENT="/user/bin/ssh -X"; export TTASSHCLIENT
and
TTASSHCLIENT="/usr/bin/ssh -X"; export TTASSHCLIENT
and
TTASSHCLIENT="/usr/bin/ssh -X" export TTASSHCLIENT
and still i get this error,
(gnome-terminal:30995): Gtk-WARNING **: cannot open display:
Connection to virtualhost closed.
This is the error when TTASSHCLIENT is commented out.
exec /usr/bin/gnome-terminal
(gnome-terminal:30948): Gtk-WARNING **: cannot open display:
I've put off messing with firewall stuff untill I can get it working internally... Any other ideas?
# 4
Just walking through the steps I took to achive the goal
1. Edit the sshd_config file and include the following:
X11Forwarding yes
2. Edit the ssh_config file and include the following:
ForwardAgent yes
ForwardX11 yes
3. Restart the SSH daemon.
If you already check and configured the above let me know
# 5
Just one other quick question do you have KDE loaded on the system?
# 6
Problem X applications run on the same machine as the Secure Global Desktop server fail to launch, reporting an error such as "Can't open display: unix:10" in the application launch dialog's Launch Details area. [514597]
Cause X applications built with the UDK on OpenServer may not work if the DISPLAY environment variable is set to "unix:n".
Solution In Object Manager, ensure that the Arguments For Command attribute of your X application object contains the following setting:
-display $ALTDISPLAY
# 7
Ok we just brought a fresh FC4 online.
1) In /etc/init.d/Tarantella one must set
TTASSHCLIENT="/usr/bin/ssh -X"; export TTASSHCLIENT
a) Restart Tarantella - notice if you use /opt/tarantella/bin/tarantella it is not the same script as /etc/init.d/Tarantella - I think I'll have to look again.
If you were successful with setting the variable - when you launch object manager the error witl now reference Cookies - yep the Tarantella under /etc/init.d is not the same as the one located in /opt/tarantella/bin/ - thus if you set the variable in Tarantella and use tarantella to restart - well......
2) /opt/tarantella/bin/tarantella config edit --security-xsecurity 0
3) If you are funning SE linux - there are issues with starting the services at boot time more later on that
That should get you running - later we will harden, once we are ready to expose the system to the Internet.
Drew
# 8
Thank you for trying to help Drew,
I changed the TTASSHCLIENT setting and restarted Tarantilla, I also set the security to 0, no love. Still sits at the Sun Secure Global Desktop... Loading forever.
As for the previous comments, with the changing the Display settings I have not done that yet. Right now just workign on the conenction, as our applications will be windows based anyways, not Unix.
So first problem, Not able to connect from outside the network :(
Any other ideas? I can give you the web address if that would help at all ?
# 9
Please post your /etc/sysconfig/selinux file here.
# 10
Also - lets just start connecting from the console and work out way to the network, it may take a few more steps.
# 11
Hey - let's take the communication out of the board. E-mail me at dfharwel@rdque.com once we nail the issues, looks as if we have with new information we can post the solution to the board. At times reading such a long interaction sends people away - defeats the purpose of the board.
# 12
> Im having some difficulty. I've installed Fedora
> Core 4 on a virtual server platform for testing and I
> have installed SGD just fine.
>
> This invironment is at home, behind a linksys
> router. I've set the webserver on port 81.
>
> I have tried all port forwarding, and even set the
> SGD server to be in the DMZ and still I am unable to
> get it to connect from outside my network. Well let
> me rephrase that, it does indeed connect to the
> webserver, but the graphical icon that says LOADING
> with the horizontal bar scrolling from left to right
> sits there forever. It prompts me to accept an
> install from Sun, and I do accept that, but it
> never takes me to the login screen.
>
> Internally, however, It takes me right to the login
> screen and I can log in.
>
> Problem 1... Now Problem 2, all the windows
> applications I publish work fine, but none of the
> applications that are hosted on the linux box will
> execute, EXCEPT the vt420 (servername)
>
> The Array Manager, Session Manager, Gnome Terminal,
> and xclock all will not run.
>
> advice?
Make sure, if you're running "ssh" that:
. X11 forwarding options are enable for __both__ the client (ssh_config) and the server (sshd_config). These files are under /etc/ssh
. make sure sshd starts with the "-4" option (amend the /etc/sysconfig/sshd file and add the OPTIONS="-4" line - then restart sshd)
. rename/remove the /etc/ssh/sshrc file
Hope this helps.
Best,
ROb
Rob_Z at 2007-7-6 20:40:00 >

# 13
SSh_config:
ForwardX11Trusted yes
SShd_config:
X11Forwarding yes
Everything else around that line is commented out...
[quote]. make sure sshd starts with the "-4" option (amend the /etc/sysconfig/sshd file and add the OPTIONS="-4" line - then restart sshd)[/quote]
Im not seeing a sshd file ?
# 14
> SSh_config:
> ForwardX11Trusted yes
>
> SShd_config:
> X11Forwarding yes
>
>
> Everything else around that line is commented out...
>
>
>
> [quote]. make sure sshd starts with the "-4" option
> (amend the /etc/sysconfig/sshd file and add the
> OPTIONS="-4" line - then restart sshd)[/quote]
>
> Im not seeing a sshd file ?
Create it.
Rob_Z at 2007-7-6 20:40:00 >

# 15
Corrected - port 3144 issue associated th X security see previous recomendation on X Security