# Thinc VSM Agent connection refused **URL:** \ **Category:** Community Support\ **Tags:** tlserver, thinlinc\ **Created:** [7 March 2022 11:55 UTC](https://community.thinlinc.com/t/thinc-vsm-agent-connection-refused/325 "2022-03-07T11:55:31Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![s0p4L1n](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@s0p4L1n](https://community.thinlinc.com/u/s0p4L1n)\ **Post date:** [7 March 2022 11:55 UTC](https://community.thinlinc.com/t/thinc-vsm-agent-connection-refused/325/1 "2022-03-07T11:55:31Z")
Hello since one week, one of my VSM agent is marked as down and I can’t find what is the issue. The Virtual Machine is up, the DNS is working, the network is working also. I can ping the host from my both HA Thinlinc nodes, I can SSH from them. ![image](https://europe1.discourse-cdn.com/flex005/uploads/thinlinc/original/1X/66a029c76090d170cf36a0b73a065716af37f368.png) The log in _/var/log/vsmserver.log_ tells me that: ```auto WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:00:43 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:01:23 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:02:03 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:02:43 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:03:23 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:04:03 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:04:43 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:05:24 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:06:04 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:06:44 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:07:24 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:08:04 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:08:44 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:09:24 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. 2022-03-06 00:10:04 WARNING vsmserver.loadinfo: [Errno 111] Connection refused talking to VSM Agent tl-agent-1:904 in request for loadinfo. Marking as down. ``` It is Thinlinc v12.1, the configuration is the same than last year, I did not change anything in the configuration, except than changing the localectl language from French to English on the agent. Is anyone have an idea ? ---
**Author:** ![pewo](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/pewo/32/46_2.png) [@pewo](https://community.thinlinc.com/u/pewo)\ **Post date:** [8 March 2022 20:57 UTC](https://community.thinlinc.com/t/thinc-vsm-agent-connection-refused/325/2 "2022-03-08T20:57:20Z")
Is vsmagent running on the agent server ? % systemctl status vsmagent If you run it on the tl-agent-1 server ? What is the result of: % nc -zv tl-agent-1 904 If you run it on the thinlinc master server ---
**Author:** ![s0p4L1n](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@s0p4L1n](https://community.thinlinc.com/u/s0p4L1n)\ **Post date:** [14 March 2022 23:06 UTC](https://community.thinlinc.com/t/thinc-vsm-agent-connection-refused/325/3 "2022-03-14T23:06:50Z")
Hello, The issue for my agent node is closed. I am migrating to a bigger hardware cluster. But it appears I have the same situation on a fresh cluster (2 nodes with 2 socket of 20/40 C/T and 512 GB RAM) **Corosync / Pacemaker cluster healthy:** ```auto root@tl-alpha-d11:/var/log# crm configure show node 1: tl-alpha-d11 node 2: tl-beta-d11 primitive cluster_ip IPaddr2 \ params cidr_netmask=24 ip=10.1.15.2 \ op monitor interval=30s \ op start timeout=20s interval=0s \ op stop timeout=20s interval=0s primitive fence_tl-alpha-d11 stonith:fence_virsh \ params ipaddr=10.1.15.2 port=VMtl-alpha-d11 action=off login=root passwd=" ******" \ op monitor interval=60s primitive fence_tl-beta-d11 stonith:fence_virsh \ params ipaddr=10.1.15.2 port=VMtl-beta-d11 action=off login=root passwd=" ******" delay=15 \ op monitor interval=60s location l_fence_tl-alpha-d11 fence_tl-alpha-d11 -inf: tl-alpha-d11 location l_fence_tl-beta-d11 fence_tl-beta-d11 -inf: tl-beta-d11 property cib-bootstrap-options: \ have-watchdog=false \ dc-version=2.0.5-ba59be7122 \ cluster-infrastructure=corosync \ cluster-name=debian \ stonith-enabled=yes \ no-quorum-policy=ignore \ last-lrm-refresh=1647291235v ``` nc -zv tl-alpha-d11 904 ```auto root@tl-alpha-d11:/var/log# nc -zv tl-beta-d11 904 Connection to tl-beta-d11 (10.1.15.4) 904 port [tcp/*] succeeded! root@tl-alpha-d11:/var/log# nc -zv tl-alpha-d11 904 Connection to tl-alpha-d11 (10.1.15.3) 904 port [tcp/*] succeeded! ``` - Connexion to the server expired, check your settings When I check the /var/log/vsmserver/agent at the same time, i get: ![image](https://europe1.discourse-cdn.com/flex005/uploads/thinlinc/original/1X/647fe38ce06d98962a0a7bfcf16c8b4d07371ce4.png) The no route to host in the log was because i had 127.0.0.1 linked to the DNS name in /etc/hosts (fixed) I have exact same configuration than my previous setup on Debian 10, now I’m on Debian 11. ---
**Author:** ![s0p4L1n](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@s0p4L1n](https://community.thinlinc.com/u/s0p4L1n)\ **Post date:** [15 March 2022 09:16 UTC](https://community.thinlinc.com/t/thinc-vsm-agent-connection-refused/325/4 "2022-03-15T09:16:53Z")
This morning I tested again, and it is working now ! I did not change anything in the configuration. Maybe it was an DNS propagation issue ? I tried to find what was the issue but nothing appear in my investigation.