Thanks Reuti, I did some more reading, and considering the complexity of our network, it looks like I really need to set up DNS for the cluster specifically. I am pretty sure this will clear up all problems.
Dan On Wed, 2014-01-01 at 01:08 +0100, Reuti wrote: > Hi, > > Am 31.12.2013 um 21:02 schrieb Daniel R. Gore: > > > I have to configure gridengine to run on a non-standard cluster where > > the all nodes (head node included) have multiple interfaces. I need to > > run gridengine over an interface the is not associated with the nodes > > (head node included) FQDN. I have followed the instructions here > > http://gridscheduler.sourceforge.net/howto/multi_intrfcs.html , but > > unfortunately this does not work. > > > > SGE can resolve all hostnames with > > SGE_ROOT/utilbin/lx26-amd64/gethostbyname -aname "name associated with > > alternate interface". But when I change the > > SGE_ROOT/SGE_CELL/common/act_qmaster to read the masters' grid engine > > interface rather than the hostname, the sgemaster fails to start > > indicating that this is not a master host. > > Better is to use the -all option. As stated in the `man gethostname` page: > > $ gethostname -all > Hostname: extern_name.mydomain > SGE name: gridmaster > Aliases: loghost gridmaster > > it should show both known names. > > -- Reuti > > > > Obviously SGE master tightly correlates to hostname > > in /etc/sysconfig/network. Is there anyway to get around this? > > > > Thanks. > > > > Dan > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > > > _______________________________________________ > > users mailing list > > [email protected] > > https://gridengine.org/mailman/listinfo/users > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
