very thanks for your explanations!
i send you an output of utgstatus. I don't understand why i see norvegian machines in 
my status!?
host           flags    interface     flags    interface     flags    interface     
flags    interface     flags    interface     flags    interface     flags    
interface     flags    interface     flags
                        193.50.130.0/24        147.94.0.0/16          192.168.128.0/24 
      147.94.64.0/24         129.241.15.0/24        129.241.107.0/24       
129.241.113.0/24       129.241.162.0/23   
--------------------    -------------------    -------------------    
-------------------    -------------------    -------------------    
-------------------    -------------------    -------------------
serengheti        TN    193.50.130.5    U--    147.94.64.5     U--    192.168.128.1   
UAM                                                                                    
                               
mombasa           TN                                                  192.168.128.2   
UAM    147.94.64.14    U--                                                             
                               
serveurbd         -N                                                                   
      147.94.64.9     U--                                                              
                              
atarnajuat        -N    193.50.130.120  UA-                                            
                                                                                       
                              
abel.math.ntnu.no -N                                                  192.168.128.1   
-AM                           129.241.15.50   U--                                      
                               
eos.idi.ntnu.no   -N                                                                   
                                                    129.241.107.66  UAM                
                              
eik.idi.ntnu.no   -N                                                                   
                                                    129.241.107.90  -A-    
129.241.113.20  -A-    129.241.162.32  -A-


i try to execute /opt/SUNWut/sbin/utrestart, but yesterday, i did also 
/etc/init.d/utsvc stop/start, perhaps it's the same thing, in 
/var/opt/SUNWut/log/messages, i see the same messages:
Jun 21 17:28:37 mombasa utkiosk[10942]: [ID 702911 user.info] Error in ut_getCon
tByTypeAndName(): Object not found
Jun 21 17:28:37 mombasa UTPOLICY: [ID 702911 user.info] # Reading policy file: /
etc/opt/SUNWut/policy/utpolicy # Current Policy: /opt/SUNWut/lib/utgenpolicy -a
-g -t clear -t add:IEEE802.0003ba2fdbbd -z both
Jun 21 17:28:37 mombasa utauthd: [ID 396523 user.info] main NOTICE: SmartCardCon
figData: LDAP contains no smartcard configuration files
Jun 21 17:28:37 mombasa utauthd: [ID 255168 user.info] main NOTICE: SmartCardCon
figData: read 19 smartcard configuration files from directory file: /etc/opt/SUN
Wut/smartcard/probe_order.conf
Jun 21 17:28:37 mombasa utauthd: [ID 474606 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/JavaBadgeCAC.cfg: 643 tokens processed
Jun 21 17:28:37 mombasa utauthd: [ID 587751 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/JavaBadge-Citibank.cfg: 144 tokens processed

and
Jun 22 09:39:19 mombasa UTPOLICY: [ID 702911 user.info] # Reading policy file: /
etc/opt/SUNWut/policy/utpolicy # Current Policy: /opt/SUNWut/lib/utgenpolicy -a
-g -t clear -t add:IEEE802.0003ba2fdbbd -z both
Jun 22 09:39:19 mombasa utauthd: [ID 396523 user.info] main NOTICE: SmartCardCon
figData: LDAP contains no smartcard configuration files
Jun 22 09:39:19 mombasa utauthd: [ID 255168 user.info] main NOTICE: SmartCardCon
figData: read 19 smartcard configuration files from directory file: /etc/opt/SUN
Wut/smartcard/probe_order.conf
Jun 22 09:39:19 mombasa utauthd: [ID 474606 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/JavaBadgeCAC.cfg: 643 tokens processed
Jun 22 09:39:19 mombasa utauthd: [ID 587751 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/JavaBadge-Citibank.cfg: 144 tokens processed
Jun 22 09:39:19 mombasa utauthd: [ID 353254 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/Payflex-All.cfg: 237 tokens processed
Jun 22 09:39:19 mombasa utauthd: [ID 462772 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/CyberflexAccess.cfg: 104 tokens processed
Jun 22 09:39:19 mombasa utauthd: [ID 409033 user.info] main NOTICE: SmartCardCon
figData: /etc/opt/SUNWut/smartcard/CyberflexAccessDeveloper32K.cfg: 144 tokens 

Today, i'm not in my lab, so i can't do tests to verify what's happening
i post new response tomorrow

and again, very thanks for your help


On Tue, Jun 22, 2004 at 04:27:21AM +0000, [EMAIL PROTECTED] wrote:
> Gerard Henry <[EMAIL PROTECTED]> wrote:
> > i have two sun ray servers configured in a failover group (sol9, SRS2.0)
> > They have been rebooted, but the slave first the master, and now, there is no 
> > session on slave!
> 
> That's a little unusual.  Are you sure that Sun Ray services on the slave are 
> running correctly
> and that the master agrees that the slave is a member of the failover group?  What 
> does
> 'utgstatus' say on the master?
> 
> > Here is error message:
> > 
> > Jun 18 20:23:18 mombasa utpulld[527]: [ID 224068 daemon.error] Error: ldap_sasl_
> > bind (host serengheti, DN cn=admin,o=utdata) returned: Can't contact LDAP server
> > Jun 18 20:23:18 mombasa utpulld[527]: [ID 428662 daemon.error] utpulld: terminat
> > ing normally
> > 
> > serengheti is master, mombasa is slave
> 
> That's OK, it just means that when the slave booted it was unable to contact the 
> master
> (because the master was still down) and it therefore couldn't pull any datastore 
> updates
> from the master.  When the master comes up it should push the updates to the slave.
> The "pull on reboot" attempt above is just trying to get the slave into sync with 
> the master
> as quickly as possible.
> 
> > What 's the best way to do :
> > - reboot slave mombas
> > or do something like /etc/init.d/ut... restart?
> 
> Rebooting won't cause any sessions to move to the slave.  If you want to restart Sun
> Ray services on the slave (which should be OK because there are no sessions there
> anyway) then use '/opt/SUNWut/sbin/utrestart'.  However, the sessions that are 
> already
> on the master will stay there unless some event happens to cause the master and slave
> to negotiate the placement of a new session.  That will happen whenever a new session
> is requested, for instance when someone inserts a smartcard, someone attempts a
> non-smartcard login, someone logs out, someone hits the 'Start Over' button on the 
> login
> greeter, or someone power-cycles a Sun Ray
> 
> > And i don't understand why slave needs master to work, i thought "failover" did 
> > all the job?!
> 
> The slave only needs the master when there are datastore updates that need to be
> performed.  Updates are always performed on the master first and then copied to the
> slaves.  After a simple reboot it shouldn't matter.  Whatever the reason why the 
> slave
> didn't get any sessions, that reason has nothing to do with data store replication.  
> It's
> more likely the result of a misconfiguration or a network fault.
> 
> OttoM.
> __
> ottomeister
> 
> Disclaimer: These are my opinions.  I do not speak for my employer.
> 
> -- 
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
> 
> 
> _______________________________________________
> 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

Reply via email to