Problem Connecting to scalarizer Agent

Eliade Micu's Avatar

Eliade Micu

18 Dec, 2014 12:34 AM

Hi,

I get the following error when I attempt to open up the Extended Instance Information:

Unable to perform request to scalarizr: Couldn't connect to server; Failed to connect to 54.187.104.57 port 8010: Connection refused (http://54.187.104.57:8010/system)

This happens for 2 of my instances: clyde-farm-4 → clyde-app-server-3 #1 and clyde-farm-4 → clyde-app-server-3 #2, and it doesn't happen on other instances. The agent version on these instances is 2.10.11, on the others is 2.12.4. If I try to run a script on any of these instances, nothing seems to happen, and nothing gets logged.

This issue happened intermittently in the past, please help. As it stands, I am unable to run any maintenance scripts on these instances from the scalr interface. Thank you.

Eliade Micu

  1. Support Staff 1 Posted by Marat Komarov on 18 Dec, 2014 12:06 PM

    Marat Komarov's Avatar

    Agent is running fine and ready for connections, please check firewall and security group settings for tcp 8010 and 8013

    Regards,
    Marat

  2. 2 Posted by Eliade Micu on 18 Dec, 2014 03:35 PM

    Eliade Micu's Avatar

    Hi Marat,

     

    I don’t think it’s a permission issue, the Windows Firewall is off on those instances, and they run in the scalr.ip-pool ( <https://my.scalr.com/#/security/groups/sg-d7e421b2/edit?cloudLocation=us-west-2&platform=ec2> sg-d7e421b2) security group, just like the other instances that experience no issues. Interestingly, if I RDP into the instance <https://my.scalr.com/#/farms/view?farmId=19014> clyde-farm-4 → <https://my.scalr.com/#/farms/19014/roles/70213/view> clyde-app-server-3 # <https://my.scalr.com/#/servers/35e3c1d8-0e9d-4b57-9df8-8fc598b7ce15/view> 1 and type localhost:8010 in a Chrome browser window, nothing happens.

     

    Here is the output of netstat on this instance, there are a lot of CLOSE_WAITs, which is not good:

     

      Proto Local Address Foreign Address State

      TCP 172.31.32.200:3389 c-174-56-174-131:49978 ESTABLISHED

      TCP 172.31.32.200:3389 210.115.42.163:9096 ESTABLISHED

      TCP 172.31.32.200:8008 174:41351 TIME_WAIT

      TCP 172.31.32.200:8010 124:35009 CLOSE_WAIT

      TCP 172.31.32.200:8010 124:36302 CLOSE_WAIT

      TCP 172.31.32.200:8013 sl2-dal07:37064 CLOSE_WAIT

      TCP 172.31.32.200:8013 sl2-dal07:46253 CLOSE_WAIT

      TCP 172.31.32.200:8013 sl2-dal07:48525 CLOSE_WAIT

      TCP 172.31.32.200:8013 sl2-dal07:51545 CLOSE_WAIT

      TCP 172.31.32.200:8013 sl2-dal07:60577 CLOSE_WAIT

     

    If I try localhost:8010 on another instance, like <https://my.scalr.com/#/farms/view?farmId=19014> clyde-farm-4 → <https://my.scalr.com/#/farms/19014/roles/70226/view> clyde-mongo # <https://my.scalr.com/#/servers/2ad03f1a-b54a-45aa-b4bd-bb6e59535425/view> 1, I get back a response, like 'HTTP_X_SIGNATURE', so there’s something else going on. Anything else to look into? Thanks.

  3. Support Staff 3 Posted by Marat Komarov on 22 Dec, 2014 09:30 AM

    Marat Komarov's Avatar

    Port 8010 is owned by 2 processes, one of which is dead (8708). Seems that it was crashed, and Windows left socket owned by it. We'll find a way how to prevent this, but for now you need to reboot your server.

    netstat -ano
    ...
      TCP    0.0.0.0:8010           0.0.0.0:0              LISTENING       8708
      TCP    0.0.0.0:8010           0.0.0.0:0              LISTENING       6376
    ...
    
  4. Marat Komarov closed this discussion on 20 Jan, 2015 10:25 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac