<div dir="ltr">After disabling HA it started working.<div><br></div><div>After re-enabling it got back to same strange on/off behavior.</div><div><br></div><div>vsmserver.log</div><div>2014-04-23 15:09:10 INFO vsmserver: VSM Server version 4.1.1 build 4137 started<br>
2014-04-23 15:09:10 INFO vsmserver.license: Updating license data from disk to memory<br>2014-04-23 15:09:10 INFO vsmserver.license: License summary: 10 concurrent users. Hard limit of 11 concurrent users. <br>2014-04-23 15:09:10 INFO vsmserver.session: Loaded 0 sessions for 0 users from file</div>
<div>...<br>2014-04-23 15:09:50 WARNING vsmserver: Timeout getting load from VSM Agent EXTERNAL_IP1:904, marking as down<br>2014-04-23 15:09:50 WARNING vsmserver: Timeout getting load from VSM Agent EXTERNAL_IP2:904, marking as down<br>
2014-04-23 15:11:10 WARNING vsmserver: Timeout getting load from VSM Agent EXTERNAL_IP1:904, marking as down<br>2014-04-23 15:11:10 WARNING vsmserver: Timeout getting load from VSM Agent EXTERNAL_IP2:904, marking as down<br>
</div><div><br></div><div>We really wanted to HA the vsmservers.</div><div><br></div><div>Any tips?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 1:41 PM, Peter Astrand <span dir="ltr"><<a href="mailto:astrand@cendio.se" target="_blank">astrand@cendio.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi, comments below:<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Currently, we have a centralized FreeNX scenario with 2 frontend servers and 29 backend servers, supporting +500 users, all running in the LAN, on old server hardware.<br>
This scenario has been running for 4 years. We created message queuing and remote tasks to alleviate our stupid day to day sysadmin jobs, ...<br>
More info, on this 2 year old presentation (sorry, portuguese)<br>
<br>
<a href="http://www.slideshare.net/rui_lapa/desktop-linux-na-tranquilidade-portolinux-presentation?qid=a331b942-8a98-4ae9-aea0-c02698e698b4&v=default&b=&from_search=1" target="_blank">http://www.slideshare.net/rui_<u></u>lapa/desktop-linux-na-<u></u>tranquilidade-portolinux-<u></u>presentation?qid=a331b942-<u></u>8a98-4ae9-aea0-c02698e698b4&v=<u></u>default&b=&from_search=1</a><br>
<br>
At the moment, we are evolving the solution to "crazy", so we want to provide a desktop to external "entities" and shops without internal network access, while still providing internal linux desktops.<br>
The crazy is, that the external desktops servers will run on a cloud provider.<br>
In the future, we plan to ONLY use cloud servers, while keeping the 2 vsmservers on the DMZ.<br>
</blockquote>
<br></div>
I agree that this is crazy :-) As I mentioned, the VSM servers should be located where the VSM agents are. There are several reasons for this, security being one of them.<div class=""><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
At this time we are doing our final test, where we have 2 DMZ vsmservers, 3 LAN agents and 2 Cloud agents.<br>
<br>
The datacenter has 4 dedicated internet circuits, with 1 IP each, in a in/output load balancing scenario. (F5 BigIp).<br>
<br>
The cloud agents are getting 4 (tcp/904) pollings from each external ip of each circuit.<br>
Due to this, we configured cloud agents "/vsmagent/allowed_clients" mapped to the 4 external NAT IP's.<br>
Unfortunately, even though, we get the tcpdump from each IP to TCP/904 and see the replies, the vsmservers webadmin status load page keeps considering these servers one cycle up, the next up/down, randomly.<br>
The internal vsmserver have the "/vsmserver/terminalservers", with the external cloud ip's and the internal lan ips.<br>
<br>
But, is there anything more we need to do?<br>
</blockquote>
<br></div>
The web interface communicate with the VSM Server, so apparently the VSM server(s) loses contact with the cloud agents now and then. It's difficult to tell why. You could start with one single VSM server, ie disable HA, until the agent communication works reliably. Also, check out vsmserver.log. tcpdump/Wireshark can probably also tell you what's going on.<br>
<br>
Regards, ---<div class="HOEnZb"><div class="h5"><br>
Peter Astrand ThinLinc Chief Developer<br>
Cendio AB <a href="http://cendio.com" target="_blank">http://cendio.com</a><br>
Teknikringen 8 <a href="http://twitter.com/ThinLinc" target="_blank">http://twitter.com/ThinLinc</a><br>
583 30 Linkoping <a href="http://facebook.com/ThinLinc" target="_blank">http://facebook.com/ThinLinc</a><br>
Phone: <a href="tel:%2B46-13-214600" value="+4613214600" target="_blank">+46-13-214600</a> <a href="http://google.com/+CendioThinLinc" target="_blank">http://google.com/+<u></u>CendioThinLinc</a><br>
</div></div></blockquote></div><br></div>