Julo Chrobak wrote:
Sorry for incorrect information. I am using SRSS 3.1.1 and I realize
it is not supported on SLES 10. The problem is, that it is supported
only on SLES9 with SP3 and SLES9 is available for trial without SP3 :(
So, I am trying to use higher version of SLES...
Anyway, here is the output of "/etc/opt/SUNWut/jre/bin/java -version" :
linux:~ # /etc/opt/SUNWut/jre/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
Well, there's your problem. During utinstall it asked something like
"Please enter a path to a Java 1.4 JRE" and you pointed it at
a 1.6 JRE. I recommend you install the JRE in the Supplemental
area of the SRSS CD image (say to "/usr/j2se"), and do the following:
# rm /etc/opt/SUNWut/jre
# ln -s /usr/j2se /etc/opt/SUNWut/jre
# /opt/SUNWut/sbin/utrestart
That just might solve your problem. I'm not *aware* of any
issues with SLES 10 and SRSS 3.1.1 offhand - others on this
list may well have recipes to get it working.
-Bob
Thanks for your help.
Julius Chrobak
Bob Doolittle wrote:
Can you please send us the output of:
/etc/opt/SUNWut/jre/bin/java -version
Are you using the Sun-supplied version of Java,
or the one supplied with SuSE 10? We have found
issues (not yet root caused) when using other vendors'
versions of Java.
I'm sure you realize that only SuSE 8 is actually supported
with SRSS 3.1, so you are trying ground that is untested
by Sun... It looks like our next release well bump support
up to SuSE 9, but not 10.
-Bob
Opinions expressed above are mine, not my employers.
Julo Chrobak wrote:
utauthd seems to be running:
=====================================================
== ps aux | grep auth
=====================================================
root 4701 0.1 0.8 26228 18212 tty7 Ss+ 11:17 0:08
/usr/X11R6/bin/X -br vt7 -auth
/var/lib/xdm/authdir/authfiles/A:0-2kUBg5
root 5011 0.0 0.0 1592 472 ? Ss 11:17 0:00
/opt/SUNWut/lib/utsessiond -r -c /etc/opt/SUNWut/auth.permit
root 5013 0.0 0.0 1624 656 ? Ss 11:17 0:00
/opt/SUNWut/lib/utdevmgrd -r -c /etc/opt/SUNWut/auth.permit
root 5016 0.0 0.8 219120 16772 ? Sl 11:17 0:00
/etc/opt/SUNWut/jre/bin/java auth.utauthd.utauthd
root 5017 0.0 0.0 1676 604 ? S 11:17 0:00
/bin/ksh -p /opt/SUNWut/lib/utlog -o /var/opt/SUNWut/log/auth_log
root 5055 0.0 0.0 2304 1140 ? S 11:17 0:00
/opt/SUNWut/lib/utsessiond -r -c /etc/opt/SUNWut/auth.permit
root 5056 0.0 0.0 2864 1652 ? S 11:17 0:00
/opt/SUNWut/lib/utdevmgrd -r -c /etc/opt/SUNWut/auth.permit
root 5921 0.0 0.0 1860 644 pts/0 S+ 12:32 0:00
grep auth
AND file /var/opt/SUNWut/log/auth_log is empty ...
Julo Chrobak.
P.S.M. Swamiji wrote:
Julo Chrobak wrote:
Here are some helpful informations:
=====================================================
== utcapture command after conntecting DTU
=====================================================
linux:/opt/SUNWut/sbin # ./utcapture
# TERMINALID TIMESTAMP TOTAL PACKET TOTAL LOSS BYTES SENT
PERCENT LOSS LATENCY
No desktops found
No desktops found
No desktops found
No desktops found
No desktops found
No desktops found
No desktops found
Authentication Manager timeout
=====================================================
== utgstatus after conntecting DTU
=====================================================
linux:/opt/SUNWut/sbin # ./utgstatus
Error: Could not get gstatus information from server linux
From this message, I suspect utauthd is not running.
If authd is not running then DTUs won't come up.
See utrestart resolves the issue. If not. provide the
auth_log contents that may have info like why authd is
not coming up.
Thanks
P.S.M.Swamiji
Note: These are my personal opinions, nothing to do with my employer
=====================================================
== /var/log/messages after connecting DTU
=====================================================
Mar 9 09:48:10 linux dhcpd: DHCPDISCOVER from 00:14:4f:0e:92:47
via eth0
Mar 9 09:48:11 linux dhcpd: DHCPOFFER on 192.168.0.19 to
00:14:4f:0e:92:47 via eth0
Mar 9 09:48:11 linux dhcpd: DHCPREQUEST for 192.168.0.19
(192.168.0.1) from 00:14:4f:0e:92:47 via eth0
Mar 9 09:48:11 linux dhcpd: DHCPACK on 192.168.0.19 to
00:14:4f:0e:92:47 via eth0
Mar 9 09:48:13 linux utauthd: Worker3 NOTICE: CLAIMED by
TerminalId.m0 NAME: TerminalId.00144f0e9247 PARAMETERS:
{terminalIPA=192.168.0.19, type=pseudo,
fw=3.1_120879-05_2006.09.20.12.31, state=disconnected,
cause=insert, doamgh=true, barrierLevel=310, rawId=00144f0e9247,
MTU=1500, tokenSeq=1, firstServer=c0a80001, namespace=IEEE802,
ddcconfig=0, id=00144f0e9247,
clientRand=D.bvr1UKMZH5KwMqgHaSQ8mCNof7n6s2inajIr4FxMe,
realIP=c0a80013, useReal=true, event=insert, pn=39364,
sn=00144f0e9247, rawType=pseudo, hw=SunRayP8, initState=1, _=1}
Mar 9 09:48:13 linux utauthd: Worker3 NOTICE: CONNECT
IEEE802.00144f0e9247, TerminalId.00144f0e9247, explicit grant
Mar 9 09:48:13 linux utauthd: Worker3 NOTICE: MTU = 1500
Mar 9 09:48:13 linux utauthd: Worker3 NOTICE:
SessionManager.getSessionManager: Initiate callback to utsessiond
at localhost:7007
Mar 9 09:48:13 linux utauthd: Worker3 NOTICE:
SessionManager.initiateCallback localhost:7010 established
communication
Mar 9 09:48:31 linux utcapture: getAuthMgrRecords(): poll timed out
Mar 9 09:49:17 linux usersession: getAuthMgrRecords(): poll timed
out
Mar 9 09:49:17 linux usersession: set_state(): failed to contact
authd (Authentication Manager timeout)
Mar 9 09:49:40 linux status: get_current_list(): poll timed out
Mar 9 09:49:45 linux status: get_current_list(): poll timed out
Mar 9 09:49:51 linux status: getAuthMgrRecords(): poll timed out
Mar 9 09:49:51 linux status: set_state(): failed to contact authd
(Authentication Manager timeout)
Mar 9 09:50:12 linux utgstatus: get_gstatus(): Poll timed out
Mar 9 09:50:27 linux utsession: getAuthMgrRecords(): poll timed out
Mar 9 09:50:27 linux utsession: set_state(): failed to contact
authd (Authentication Manager timeout)
SO! It seems that DHCP server works fine, without any problem.
When I check the DHCP status it returns the following information:
=====================================================
== utquery command after connecting DTU
=====================================================
linux:/opt/SUNWut/sbin # ./utquery -d 192.168.0.19
terminalID=00144f0e9247
terminalIPA=192.168.0.19
model=SunRayP8
Subnet=255.255.255.0
Router=192.168.0.1
MTU=1500
Broadcst=192.168.0.255
LeaseTim=86400
DHCPServer=192.168.0.1
AuthSrvr=192.168.0.1
AuthPort=7009
LogHost=192.168.0.1
FwSrvr=192.168.0.1
NewTVer=3.1_120879-05_2006.09.20.12.31
parmsVersion=3.1_120879-05_2006.09.20.12.31
parmsBarrier=310
currentAuth=192.168.0.1
currentFW=3.1_120879-05_2006.09.20.12.31
currentBarrier=310
currentBarrierLevel=310
AltAuth=192.168.0.1,255.255.255.255
dname=site
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://node1.filibeto.org/mailman/listinfo/sunray-users
