10 Replies Latest reply on Oct 26, 2016 10:01 AM by Vasileios Michos

    Can't access host Connection timed out

      Hi,

       

      I am getting connection timeout error while accessing target server, but some times I am able to connect successfully. I am able to ping server as well as telnet to 4750 without any error. Also checked service is running, I checked using netstat command and it is showing 4750 port listening.

       

      agentinfo command output -

       

      PRDBBSA01# agentinfo 180.179.67.76

      180.179.67.76:

        Agent Release   : 8.3.00.115

        Hostname        : PBX2

        Operating System: WindowsNT 6.2 (x86_64)

        User Permissions: BladeLogicRSCD@MOMPBX2->mmpladmin@MOMPBX2:PrivilegeMapped (Identity via trust)

        Security        : Protocol=5, Encryption=TLS1

        Host ID         : 28312A08

        # of Processors : 32

        License Status  : Licensed for NSH/CM

       

      So sometimes agent is responding and sometimes not, it is like something is closing connection continuously. This is domain controler, OS is windows 2012. I have also checked event viewer where I can see error regarding DReplay Controler, I am not sure whether this is causing the problem.

       

      Also I would like to mention 180.179.67.76 is puclic IP and natted on firewall, actual server IP is different.

       

      Regards,

      Omkar

        • 1. Re: Can't access host Connection timed out
          John O'Toole

          Hi Omkar,

           

          Is this happening in the context of a BSA Job? Or some client activity such as a live browse etc?

           

          Is this a multi apppserver environment? If it is, have you noticed any pattern around the connection working from appserver a but not from appserver b?

           

          If not, can we test to see if we can reproduce the intermittent connectivity issue outside of BSA. You mentioned that "telnet 4750" works from the appserver? Can you rerun that telnet command ten or so times in a row to see if any of them throw an error as well?

           

          Thanks,

           

          John

          • 2. Re: Can't access host Connection timed out

            Hi John,

             

            Its single app server environment. This happening in Job, Browsing as well as while doing agentinfo. I am able to do telnet continuously there is no error.

             

            Regards,

            Omkar

            • 3. Re: Can't access host Connection timed out
              John O'Toole

              Thanks. I wonder if this is an intermittent performance issue and sometimes access to this server is slow enough that it hits the default timeout? (which, if we think this might be it, is something we can increase).

               

              Lets focus on agentinfo for now since it sounds like it can be reproduced, albeit intermittently, from there.

               

              Can you run agentinfo ten times against this server? How many of those runs succeeded and how many timed out?

              Can you include the exact text of one of those agentinfo timeouts?

              Also, when it times out, how long does it seem to take?. 30 seconds? When it succeeds, how long does it take?

               

              Thanks,

               

              Joh

              • 4. Re: Can't access host Connection timed out

                Thanks John, I did the same. when it times out it took around 20-30 seconds to throw an error. I did agentinfo 15 times with 5 seconds of interval and I observed connection time out twice in between after 4-5 successful execution.

                at the same time I also execute "netstat -a | findstr 4750" at target server. output is as below -


                here 180.179.103.21 is my application server IP

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:53373   ESTABLISHED

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38783   ESTABLISHED

                  TCP    192.168.100.5:4750     180.179.103.21:53373   CLOSE_WAIT

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38783   ESTABLISHED

                  TCP    192.168.100.5:4750     180.179.103.21:53373   CLOSE_WAIT

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38802   ESTABLISHED

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38802   ESTABLISHED

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38802   CLOSE_WAIT

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38811   ESTABLISHED

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38811   CLOSE_WAIT

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                 

                C:\Users\bmcagent>netstat -a | findstr 4750

                  TCP    0.0.0.0:4750           PBX2:0                 LISTENING

                  TCP    192.168.100.5:4750     180.179.103.21:38827   ESTABLISHED

                 

                Regards,

                Omkar

                • 5. Re: Can't access host Connection timed out
                  John O'Toole

                  Thanks. I am sure everything is ok on the agent side.

                   

                  For the agentinfo commands which do work – how quickly do they come back? In a couple of seconds or longer? (10+ seconds)

                   

                  Thanks,

                   

                  John

                  • 6. Re: Can't access host Connection timed out

                    Hi John,

                     

                    agentinfo command get back quickly. I am also sure that there is no issue with RSCD agent or application server, neither network issue. This is something with OS. What I have observed is request from appserver always reach to target server but it throws error while responding. I tried below thing

                    180.179.67.76 is target server IP here.

                    I executed -  nexec 180.179.67.76 CMD /c "mkdir C:\test"

                    here test folder got created on C:\ but I got response - nexec: Error accessing host 180.179.67.76: Connection timed out

                    later I executed - nexec 180.179.67.76 CMD /c "dir C:\""

                    I got response -

                     

                    Volume in drive C has no label.

                    Volume Serial Number is 2831-2A08

                     

                    Directory of C:\

                     

                    01/30/2014  05:19 PM    <DIR>          compaq

                    01/30/2014  04:32 PM    <DIR>          cpqsystem

                    01/30/2014  05:19 PM    <DIR>          hp

                    01/30/2014  03:37 AM    <DIR>          inetpub

                    08/22/2013  09:22 PM    <DIR>          PerfLogs

                    01/31/2014  05:37 PM    <DIR>          Program Files

                    01/31/2014  10:45 PM    <DIR>          Program Files (x86)

                    01/30/2014  04:21 PM             2,944 smh_installer.log

                    02/06/2014  11:19 AM    <DIR>          test

                    02/05/2014  11:37 AM    <DIR>          Users

                    01/30/2014  05:32 PM    <DIR>          utility

                    02/05/2014  11:36 AM    <DIR>          Windows

                                   1 File(s)          2,944 bytes

                                  11 Dir(s)  205,870,071,808 bytes free

                     

                    You can see test directory is created on target server. So what I am thinking here is target OS is sometimes failing to bind dynamic port during response to application server request. But still don't have strong evidence to say this. nothing is there in system or application event log. What do you think ?

                     

                    Regards,

                    Omkar

                    • 7. Re: Can't access host Connection timed out
                      Joe Piotrowski

                      Omkar, did you get a resolution to this? Have you opened a Support ticket?

                      • 8. Re: Can't access host Connection timed out

                        Hi Joe,

                         

                        No I haven't raised support ticket as this issue I am facing on production server, which belongs to end customer. Customer want Compliance and Audit report on the server which we have provided doing it manually (using traditional process that customer was following) . Customer is not allowing to work on respective server to troubleshoot as this is live server. I also tried to re-produce issue but no luck.

                        For time being marking this as assumed answered. Will update this thread in case I face same issue.

                         

                        Regards,

                        Omkar

                        • 9. Re: Can't access host Connection timed out
                          Wayne Wollesen

                          Not sure if this will be helpful or not, but we are having what sounds like the exactly same issue with some AIX database servers. I opened an incident with BMC support today, so if they come back with anything I'll put it here and maybe it will help out.

                           

                          Please let me know if you figure anything out on your end. I know it's Windows vs. AIX but maybe it will have a similar fix.

                          • 10. Re: Can't access host Connection timed out
                            Vasileios Michos

                            I'm facing the same issue. After a failed USP on target Agent.

                            If we manually restart the Agent there will be no problem but I need to know why this is happening.

                            After reading troubleshooting I ran agentinfo and get the same message.

                            can't access host : connection timed out.