[torqueusers] Server not talking to MOMs at all

Garrick Staples garrick at usc.edu
Mon Aug 15 17:14:00 MDT 2005


> Earlier, my config file was
> #########################
> $restricted     192.168.1.254
> $restricted     fructose.cchmc.org
> $restricted     205.142.199.176
> $restricted     transferase.dmzcluster.cchmc.org
> $logevent       255
> 
> $clienthost     fructose
> $clienthost  transferase
> $clienthost  xylose
> ##############################
> 
> When I changed it to,
> ###################################
> $restricted     192.168.1.254
> $restricted     transferase.dmzcluster.cchmc.org
> $restricted     205.142.199.176
> $restricted     fructose.cchmc.org
> $logevent       255
> 
> $clienthost  transferase
> $clienthost     fructose
> $clienthost  xylose
> ####################################
> 
> everything started to work. Here, as you had guessed, fructose is the 
> name for the 205.142.199.* interface (public). transferase is the name 
> for the 192.*.*.* interface (private).  Why is this? Which of these 
> lines made the difference? I am dazzled. Could you explain it please? My 
> Masquerade is still working fine, just to note.

The first $clienthost listed identifies the "server" to the MOM.  It is the
only hostname that will receive status updates from the MOM.

This will change in a future TORQUE release when multi-server support is
finished.

-- 
Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20050815/5c6e5d2e/attachment.bin


More information about the torqueusers mailing list