CentOS 5.4 64 bit srss 4.2 troubles

Question

Hi have 3 sun ray 170 thin clients that used to work on an older sunfire v250, but now we have upgraded to a new IBM 3500 series running CentOS 5.4 64 bit. We are trying to get the thin 170s to work with the new 4.2 version of sun ray software. We had licensing for 3.1 as far as I read it won't work with RHEL 5 so I downloaded the free trial of 4.2.
I have tried for 4 days with no luck in getting it to work. I have installed all the prerequisites for RHEL 5 update 3 [Could it be it does not work on update 4????].
Except the JRE, CentOS 5 has 1.6 openjdk [mixed mode] and I just pointed to that during configuration.
When I ran utinstall I got no errors, everything installed great. I printed the installation log and no errors. utadm -A went fine too no problems the dhcpd.conf file was sent up and seems to be working fine. utconfig also went fine the first time I installed it I used tomcat5 that I can get for CentOS 5 but the web console did not work. I just get a blank page. I installed again this time I first installed the apache-tomcat that is downloaded with srss 4.2 and installed in /opt just like it says here
http://wikis.sun.com/display/SRSS4dot2/Home
Again I print out the logs and no errors and I just get a blank page on 1660 and 1661 nothing, maybe this needs to be running to configure the whole things. With 3.1 I just skip the web console because all I need is a thin client,.
I can't run utfwsync [it says to do this off the wiki] I get an error about not being able to get gstatus for the server ????whatever that is???
When I connect the 170s I see one of the dhcp range IPs and the MAC address for the 170 then the <-----> icon with 100F and the IP of the server at the bottom I get a code of 22D then the client resets and this goes on for ever.
No firewall or SELINUX is on or was on during installation.
I am running out of patience with this. Does anyone have any suggestions or have any additional info [logs, support, etc] regarding installing on CentOS 5.4 64 bit and why it does not work. Actually how can I tell everything is up? I mean I see a bunch of ut processes when I run ps but have no idea what should be up.
Also there is mention about using ldap and although all the ldap rpms are loaded I did not configure anything nor see instructions on having to do so.
Also any suggestions on any other software that can work with CentOS 5.4 64 bit using the sun ray 170 as thin clients besides srss4.2 would be welcome.
Thanks in advance

Answer 1

bdajames wrote:
I have tried for 4 days with no luck in getting it to work. I have installed all the prerequisites for RHEL 5 update 3 [Could it be it does not work on update 4????].While not officially qualified on that release, it worked for me. On a fresh install of 5.4 on an x64 platform I needed to install the 32-bit ndbm and libXfont packages in addition to the prerequisites listed for 5.3.
Except the JRE, CentOS 5 has 1.6 openjdk [mixed mode] and I just pointed to that during configuration.The JRE that was on your 64-bit Linux? That won't work. It needs a 32-bit JVM 1.6 that is fully compatible with Sun JNI. Not sure, if openjdk works - better use a 32-bit JRE from Sun.
When I ran utinstall I got no errors, everything installed great. I printed the installation log and no errors. utadm -A went fine too no problems the dhcpd.conf file was sent up and seems to be working fine. utconfig also went fine the first time I installed it I used tomcat5 that I can get for CentOS 5 but the web console did not work. I just get a blank page. I installed again this time I first installed the apache-tomcat that is downloaded with srss 4.2 and installed in /opt just like it says here
http://wikis.sun.com/display/SRSS4dot2/Home
Again I print out the logs and no errors and I just get a blank page on 1660 and 1661 nothing, maybe this needs to be running to configure the whole things. With 3.1 I just skip the web console because all I need is a thin client,.You can skip the web console, if you are fine with configuring everything from the CLI.
But I suspect this is also caused by using the wrong JRE.
I can't run utfwsync [it says to do this off the wiki] I get an error about not being able to get gstatus for the server ????whatever that is???This tells you that the utauthd daemon is not running. Probably caused by using the wrong JVM.
When I connect the 170s I see one of the dhcp range IPs and the MAC address for the 170 then the <-----> icon with 100F and the IP of the server at the bottom I get a code of 22D then the client resets and this goes on for ever.
No firewall or SELINUX is on or was on during installation.
I am running out of patience with this. Does anyone have any suggestions or have any additional info [logs, support, etc] regarding installing on CentOS 5.4 64 bit and why it does not work. Actually how can I tell everything is up? I mean I see a bunch of ut processes when I run ps but have no idea what should be up.The basic test that the utauthd process is up and running is to look at the group status (the 'gstatus' you wondered about):
  $ /opt/SUNWut/sbin/utgstatus.
If you get "Error: Could not get gstatus information", then the service is down on this server.
You can often find out more about what is going wrong, if you look at the following log files:
/var/opt/SUNWut/log/auth_log          - if the utauthd daemon fails (i.e no 'gstatus')
/var/opt/SUNWut/log/utwebadmin.log    - if the webconsole fails
/var/opt/SUNWut/log/messages          - if the daemons are up, but connection still fails
/var/log/gdm/<display>.log            - if everything else seems to work, but the DTU is stuck in status 26{code}
Also there is mention about using ldap and although all the ldap rpms are loaded I did not configure anything nor see instructions on having to do so.
LDAP is used internally by SRSS, but you usually don't need to deal with that directly in any way.
Also any suggestions on any other software that can work with CentOS 5.4 64 bit using the sun ray 170 as thin clients besides srss4.2 would be welcome.
There isn't really any other software for this.