Got it....it was the load balancing agent.
<!-- Return IP addresse as defined in the first line of hostname command -->
<variable name="IP">
<command>ip route get 1.2.3.4 | awk 'NR>1{exit};1{print
$NF}'</command>
Above is the relevant part of the config. The comment describes what
it's going to do and then it goes and does something else.
Works with:
<command>hostname -i</command>
Peter
On Wed, Sep 7, 2011 at 6:16 PM, Peter Hartmann <ascensiont...@gmail.com> wrote:
> I'm new to the ltsp-cluster thing. While tracking down a problem with
> localdev ,I noticed that on the clients the LDM_SERVER value is
> showing the wrong ip address, that of another nic in the application
> server. I also see in the Cluster Control Center> Terminal Logs the
> same wrong address shows up in the column for Application Server
> Address.
>
> When I specify the LDM_SERVER as the ip address of my app-server01 it
> gets picked up by the clients. When change it back to %LOADBALANCER%
> it goes back to the wrong ip of the app-server01.
>
> In /etc/ltsp/lbsconfig.xml I changed from hostname to ip address for
> the node...no change. /etc/hosts were good on both cluster-root and
> app-server01 anyway. Does anybody know why the load balancer would
> give out that LDM_SERVER? Is that what's happening?
>
>
> Brain hurts now.
>
>
> Thanks for any help in advance.
>
> Peter
>
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
