Ok guys it was my not using the FQDN which did it.

 My host files were ok but it was a good thought as it has bitten me before and 
I forgot to check in this instance.

 I used the FQDN to add the FOG members as suggested by CJ, and it worked.

 The relief!! (-:

 Thanks for your prompt tips.

----- Original Message -----
From: Craig Bender
Sent: 12/07/11 05:12 PM
To: SunRay-Users mailing list
Subject: Re: [SunRay-Users] FOG join failure

 Since this is Linux, I would second CJ's thoughts and look at the host file 
for naming problems. Standard RH style host files have the host name on the 
same line as the loopback. That breaks quite a few things. The web admin 
interface, utadm, and possible utreplica. Make sure that your host file has the 
host name on it's own line, here's how I would set mine up. 127.0.0.1 localhost 
locahost.localdomain 183.167.250.39 triceratops triceratops.here.ac.uk 
183.167.250.3 balur balaur.here.ac.uk On 12/7/11 8:17 AM, Cj wrote: > John, > 
Maybe the problem is host-naming related ? > Triceratops thinks it is a primary 
for balaur, not for balaur.here.ac.uk > (which is the name being output in the 
error message for the failed > utreplica -s command). > Maybe setting 
triceratops as the primary for balaur.here.ac.uk will > work ? Sometimes it is 
using names and sometimes IP addresses ? > Just a thought > > Cheers > Cj. > > 
-------------------------------------------------------------------!
 ----- > *From:* [email protected] > 
[mailto:[email protected]] *On Behalf Of *john halfpenny > 
*Sent:* 07 December 2011 14:45 > *To:* SunRay-Users mailing list > *Subject:* 
[SunRay-Users] FOG join failure > > Hi Everyone > > I have CentOS5 64-bit 
running srs5.2 working fine as a standalone. > > For the past few days I've 
been attempting to set up a FOG with no > success at all. I already had this 
working successfully on Ubuntu and my > steps so far haven't been so very 
different on CentOS, I've exhausted > all I can find and have explored all the 
avenues discovered. I'm > beginning to lose my mind. > > Ok, I get this on the 
primary (triceratops): > > [root@triceratops ~]# /opt/SUNWut/sbin/utreplica -l 
> > Sun Ray Server Software 4.3 > Administration Failover Configuration > > 
triceratops.here.ac.uk is a primary server for: > balaur > > [root@triceratops 
~]# /opt/SUNWut/sbin/utgstatus > > host flags interface flags > 
183.167.250.0/32 > -------!
 ------------------ ------------------- > triceratops.here.ac.uk TN 
183..167.250.39 UA- > balaur.here.ac.uk TN 183.167.250.3 UA- > > > But on the 
secondary (balaur) I get this: > > [root@balaur ~]# /opt/SUNWut/sbin/utgstatus 
> > host flags interface flags > 183.167.250.0/32 > ------------------------- 
------------------- > balaur.here.ac.uk TN 183.167.250.3 UA- > 
triceratops.here.ac.uk TN 183.167.250.39 UA- > > [root@balaur ~]# 
/opt/SUNWut/sbin/utreplica -s triceratops > > Sun Ray Server Software 4.3 > 
Administration Failover Configuration > > utreplica: Error, triceratops is not 
configured as a Primary for > balaur.here.ac.uk. > > > It makes no difference 
whether I use multicast with an outrageously high > TTL or fall back to 
broadcast, or even if I try to set the secondary > first. It always ends with 
the same result, and I end up doing utreplica > -u, then a utconfig -u and 
starting again after a reboot to have another go. > > Has anyone any clue where 
I could look just to understand where it is > failing? > > My secondary is a 
clone of the p!
 rimary, having all references of > hostname altered, and a utconfig 
uninstall/install cycle performed. > > Thanks for any advice! > > John > > > 
_______________________________________________ > 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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to