I found what the problem was:

In the latest release of Solaris 10 it doesn't like how Sunray Server 3.1 writes the following line in /etc/inet/inetd.conf

utrcmd stream tcp nowait,trusted root /opt/SUNWut/lib/in.utrcmdd in.ut
rcmdd

Running inetconv I would get the following
# inetconv
inetconv: Notice: Service manifest for 100235/1 already generated as /var/svc/manifest/network/rpc/100235_1-rpc_ticotsord.xml, skipped inetconv: Notice: Service manifest for tftp already generated as /var/svc/manifest/network/tftp-udp6.xml, skipped inetconv: Error /etc/inet/inetd.conf line 37 invalid wait-status: nowait,trusted

So I edited that file and changed the line to look like this:

utrcmd  stream  tcp     nowait  root    /opt/SUNWut/lib/in.utrcmdd in.ut
rcmdd

inetconv then ran and added that service to svcs. I did this on both servers and then re-ran utreplica and everything works now. Not sure if removing the "trusted" part is best solution, but failover group is working now.

------------------------------


All,
  I saw one post about this but no solution was presented. I'm having
the following problem.  I'm setting up two Sunray servers running
Solaris 10 05/08 with version 3.1.  Both servers have fresh install of
Solaris 10.  Install of software all went smoothly on both servers.  I
have run utconfig and utadm on both servers.  I set both up for failover
group with same password key.  DTU's are getting login screens from both
of the two servers.  Problem I'm having is now trying to run the
utreplica to setup the failover group.  This is what I'm getting:

On the master:

# ./utreplica -l

Sun Ray server 3.1
Administration Failover Configuration


No replica context for this server

# ./utreplica -p suntest2

Sun Ray server 3.1
Administration Failover Configuration

Converting Administration Standalone Server to Administration Primary
suntest2.engr.colostate.edu: Connection refused
utreplica: Warning, Incompatible secondary server suntest2:
        Unable to determine the replication status of suntest2.

### updating the SRDS config file
        ...done
Stopping Sun Ray Data Store daemon
Sun Ray Data Store daemon stopped
Starting Sun Ray Data Store daemon .
Tue Jul  8 09:10 : utdsd starting
Starting utpushd daemon

Restarting Sun Ray server ...
stopping authentication manager
starting session manager
starting device manager
starting printer service
starting serial service
starting authentication manager
starting Apache web server

Configuration of Failover Administration has completed.
Please check the log file,
/var/adm/log/utreplica.2008_07_08_09:10:36.log, for errors.

On the Slave:

# ./utreplica -l

Sun Ray server 3.1
Administration Failover Configuration


No replica context for this server

# ./utreplica -s suntest1

Sun Ray server 3.1
Administration Failover Configuration

utreplica: Warning, Unable to determine the replication status of suntest1.

Error message from suntest1:
suntest1.engr.colostate.edu: Connection refused

Unable to retrieve the SRDS port from the primary.  Please make sure
that the SunRay software is installed/configured on the primary
server.

You may continue with the setup by choosing the software release
running on the primary.


Continue? ([y]/n)? n
utreplica: Abort, Administration Failover Configuration Aborted


Is there something I missed in setup?  Running utreplica -l shows
everything is fine on the master.  On the slave I did answer yes to
continue and utreplica on that showed everything is fine. But on the Web
GUI It will give internal error when trying to view sessions on the
slave server.


--
C. J. Keist                     Email: [EMAIL PROTECTED]
UNIX/Network Manager            Phone: 970-491-0630
Engineering Network Services    Fax:   970-491-5569
College of Engineering, CSU
Ft. Collins, CO 80523-1301

All I want is a chance to prove 'Money can't buy happiness'

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to