I have shutdown the firewall completely (one advantage of being in a 
stand-alone network).  It was causing issues with originally getting them to 
connect.  It was also blocking them attempting to update the firmware.
      From: "Clift, Tom CIV NSWCDD, K55" <robert.cl...@navy.mil>
 To: Tim Gaudet <tim_gau...@yahoo.com>; SunRay-Users mailing list 
<sunray-users@filibeto.org> 
 Sent: Monday, January 26, 2015 4:36 PM
 Subject: RE: [SunRay-Users] Didn't survive a reboot code 26 D
   
Try "service iptables stop"



Tom Clift

540-653-8023

DSN  249-8023

________________________________
From: sunray-users-boun...@filibeto.org [sunray-users-boun...@filibeto.org] on 
behalf of Tim Gaudet [tim_gau...@yahoo.com]
Sent: Monday, January 26, 2015 3:34 PM
To: sunray-users@filibeto.org
Subject: [SunRay-Users] Didn't survive a reboot code 26 D

About my system:  I am running rhel 6.4 on a stand-alone network and using 
sunray 3 plus.  I actually had the sunrays working.  I had opened a ticket with 
Oracle and we managed to get them working just fine, then Oracle closed the 
ticket.  I got to a point where it was time for a reboot and voila the sunrays 
no longer work.  The network portion still works since I can see the 
information on the screen and I can ping the sunray.  However I am getting an 
error message saying:
utxinit@dpy12<mailto:utxinit@dpy12>: Could not connect to Session Manager!
utxinit@dpy12:<mailto:utxinit@dpy12:> utxexec ERROR: Cannot open display :12


utxexec: utxexec ERROR: Cannot open display :12
root: utxinit ERROR: Client XOpenDisplay failed, display 12

So now I am dead in the water.  Please if anyone can help me figure out what I 
had running that I now don't

Tim

  
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to