You have to run uttscadm -c -g <group>
This step is documented in the how to upgrade SRWC section of the doc.
On 3/2/11 3:20 AM, Mika A wrote:
Back at work..
On Tuesday 01 March 2011 14:42:00 [email protected] wrote:
You need to rerun uttscadm again.
I did run "uttscadm -r" and while I don't see uttsc syntax errors anymore in
the log, I now see these:
Mar 2 12:55:45 sunvdi-broker-03 kioskcritd[18515]: [ID 190395 user.info]
kioskcritd started
Mar 2 12:55:45 sunvdi-broker-03 kiosk:vda[18593]: [ID 702911 user.error]
/opt/SUNWuttsc/bin/uttsc exited with error code 1 - exiting
Mar 2 12:55:45 sunvdi-broker-03 Sun Ray Connector proxy:[2329]: [ID 297250
user.warning] SRDS access by peer process denied
Mar 2 12:55:45 sunvdi-broker-03 kiosk:vda[17992]: [ID 702911 user.notice]
Unable to connect to Sun Ray Connector Proxy. Please ensure uttscadm has been
run before launching the Sun Ray Connector.
Mar 2 12:55:45 sunvdi-broker-03 kiosk:vda[18666]: [ID 702911 user.error]
/opt/SUNWuttsc/bin/uttsc exited with error code 1 - exiting
Mar 2 12:55:45 sunvdi-broker-03 Sun Ray Connector proxy:[2329]: [ID 297250
user.warning] SRDS access by peer process denied
Mar 2 12:55:45 sunvdi-broker-03 kiosk:vda[18293]: [ID 702911 user.notice]
Unable to connect to Sun Ray Connector Proxy. Please ensure uttscadm has been
run before launching the Sun Ray Connector.
So obviously at least now I need to run uttscadm but since I already ran it
with "uttscadm -r" and that didn't help, should I now run it with "uttscadm -c
-g<group>"? And since I've never done anything like that, is the group this
one (from /etc/group):
srwcgrp::88000:
Thanks!
.mika
PS. As a sidenote, regarding the system as a whole, I am once again amazed how
fragile the thing is. We have a fully supported VDI system to which I did an
upgrade following the Update Installation document and the end result was a
total blackout for users, which has now lasted for two days.. These things can
happen but these happen way too often and they last for WAY too long..
.mika
On Mar 1, 2011, at 1:22 AM, Mika A<[email protected]> wrote:
Joop,
we upgraded our standard, Sun/Oracle supported environment from VDI
3.2 to VDI
3.2.2 and after the upgrade NONE of our DTUs can connect to their
desktops
(Windows VMs on VBox hosts).
The problem seems to have something to do with uttsc, as we get
quite a lot of
these in messages-log:
Mar 1 11:10:44 sunvdi-broker-02 Sun Ray Connector proxy:[18237]:
[ID 855542
user.error] Child closed socket prematurely, session shutdown
Mar 1 11:10:44 sunvdi-broker-02 Sun Ray Connector proxy:[18277]:
[ID 855542
user.error] Child closed socket prematurely, session shutdown
Mar 1 11:10:44 sunvdi-broker-02 kiosk:vda[18586]: [ID 702911
user.error]
/opt/SUNWuttsc/bin/uttsc exited with error code 1 - exiting
Mar 1 11:10:44 sunvdi-broker-02 kiosk:vda[18650]: [ID 702911
user.error]
/opt/SUNWuttsc/bin/uttsc exited with error code 1 - exiting
Mar 1 11:10:45 sunvdi-broker-02 Sun Ray Connector proxy:[19023]:
[ID 855542
user.error] Child closed socket prematurely, session shutdown
Mar 1 11:10:45 sunvdi-broker-02 kiosk:vda[19269]: [ID 702911
user.error]
/opt/SUNWuttsc/bin/uttsc exited with error code 1 - exiting
Mar 1 11:10:46 sunvdi-broker-02 Sun Ray Connector proxy:[20988]:
[ID 855542
user.error] Child closed socket prematurely, session shutdown
Oracle Support is currently wondering the thing but I was wondering
if someone
had seen this this before?
The upgrade itself went perfectly, no problems there, and the system
works
otherwise normally.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
