![]() |
![]() |
We are currently migrating this forum over to our HelpSystems domain. Please post all new threads in our new HelpSystems Community Portal. |
![]() |
|
![]() |
AutoMate Discussion | ![]() |
Topic Title: Remote BPA Agent offline - attempting reconnection to localhost Topic Summary: Why is the agent host set to 'localhost'? Created On: 06/18/2014 03:26 PM Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
||||||||||
We have a main BPA server that contains the SMC. We have 2 more servers that have agents installed on them. They used to be connected to the main BPA server but now show offline in the SMC. When I log in to each of the agent servers the Automate task bar icon shows red (offline) and when I hover over the icon it says "Automate BPA Agent <AgentHostname> trying to reconnect to localhost". We've not tried to (re)install the agents or modify the registry entry to point to localhost. It seems to have done this on it's own. We are currently running v9.0.3. Is this an issue that is fixed in the latest version? I read about this same issue on this forum post: http://forums.networkautomation.com/forum/messageview.cfm?catid=51&threadid=10254&highlight_key=y&keyword1=Attempting%20reconnection%20to%20localhost
|
||||||||||
|
||||||||||
![]() |
||||||||||
Paul,
if they say "trying to reconnect to localhost". That must be for some reason the registry entry points to loacalhost instead of pointing to the real BPA server. Usually editing the registry does repair it. I should wait until full resolution of the 9.0.5.4 CPU problem before upgrading to that version.
------------------------- Jean Delfosse - Automate Beta Tester Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4 ![]() |
||||||||||
|
||||||||||
![]() |
||||||||||
We have a main BPA server that contains the SMC. We have 2 more servers that have agents installed on them. They used to be connected to the main BPA server but now show offline in the SMC. When I log in to each of the agent servers the Automate task bar icon shows red (offline) and when I hover over the icon it says "Automate BPA Agent We've not tried to (re)install the agents or modify the registry entry to point to localhost. It seems to have done this on it's own. We are currently running v9.0.3. Is this an issue that is fixed in the latest version? I read about this same issue on this forum post: http://forums.networkautomation.com/forum/messageview.cfm?catid=51&threadid=10254&highlight_key=y&keyword1=Attempting%20reconnection%20to%20localhost Paul, Please check the Windows Event Viewer and provide any messages that reference the Agent. It does look like it's trying to connect to the localhost but let's make sure that is all that is occurring with the Agent.
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
It appears that the reason the agents changed to localhost was because they could not connect to the main BPA server with the SMC on it. This is the event log entries where the agent switched to localhost. I can tell you that we had a major network outage during the time the event log entries occurred. So perhaps it switched to localhost because it could not connect?
Log Name: Application Description:
Description:
Log Name: Application
Log Name: Application Description:
Log Name: Application Source: AutoMate BPA Agent 9 Date: 6/7/2014 12:43:50 PM Event ID: 0 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: H2-VABPACIX01 Description:
|
||||||||||
|
||||||||||
![]() |
||||||||||
Paul,
I see the incident is now two weeks old (June 7). Is it resolved now ? Your assumption of the agents tring o connect to localhost as a fallback due to network outage makes sense. Although I did not know of that automatic fallback capability.
------------------------- Jean Delfosse - Automate Beta Tester Win7 Pro 64 bits -Win XP Pro SP3 32 bits - AM8, AM7, BPA10, BPA9, BPA8, BPA7, AM6 Enterprise, AM4 ![]() |
||||||||||
|
||||||||||
![]() |
||||||||||
I resolved the issue yesturday by changing the HOST registry value to the name of the main BPA server and then restarting the agent service. We really don't have many jobs currently on our BPA server so the issue wasn't noticed until yesturday. I do not understand why the software would change the HOST registry value to LOCALHOST for any reason. The main BPA server software is not installed on these agent only servers so those agents won't be able to connec to LOCALHOST at all.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Paul,
The software does not change the host name. The only methods to change the host name would be manually through registry editor or the agent was installed locally and the host name was not updated during the installation process. The installer populates the host name field to localhost if not updated.
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
Yes, I'm trying to say that the cause for this incident on our agent servers is unkonwn. We did not manually change the HOST registry entry or try to install an agent locally... The only thing that happened was the servers with the agent on them could not connect to the main BPA server due to a network outage. This seemed to have caused the agents to change the value for HOST in the registry to LOCALHOST.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Paul,
The software does not change the registry setting in any circumstance. I'm stating that the host name information was changed in some other fashion. Either way, you have solved the issue and are back up and running.
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
Hello again, You can see by the Windows event logs that one second the agent was trying to connect to the main BPA host (H2-VABPA01) then the next second it was trying to connect to LOCALHOST. This happened when our network outage (issue with hardware) occurred. No one was installing an agent or making manual changes to the HOST value in the registry for it. No one was able to access the server at this time becuase the network was down. Yes, the issue is currently resolved. We have not seen this issue reoccur. I will post in this topic again if it does...
|
||||||||||
|
||||||||||
![]() |
||||||||||
I have been having this same issue lately with one of the agents. The registry values resets to localhost, when the agent is rebooted, mostly after a outage. Manually editing the registry fixes it, but is there any way of preventing it from happen?
|
||||||||||
|
||||||||||
![]() |
||||||||||
Antony,
The agent does not update the registry to point elsewhere. If you see the agent registry keys changing, then someone is deploying an agent or installing an agent on that machine with the incorrect host information. If you can cause this to occur when restarting the agent service, please open a ticket with automate.support@helpsystems.com so we can schedule a remote session to see this occur.
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
Sorry for the late reply. But this is not a scenerio I can re-create. Well it happened again today, from what I've observed so far, this happens when the agent runs out of memory coz no one from the network team manually edits the registry.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Sorry for the late reply. But this is not a scenerio I can re-create. Well it happened again today, from what I've observed so far, this happens when the agent runs out of memory coz no one from the network team manually edits the registry.
|
||||||||||
|
||||||||||
![]() |
||||||||||
And when it runs out of memory. we start receiving this error mesasge as well, Task 'XXXXX' running on agent 'YYYY' failed because: A problem occurred while initializing the AutoMate 9 Task Interpreter: Attempt to get interface to the AutoMate 9 Task Interpreter has failed. (0x800705af)(Step 1) which gets resolved on a reboot. Is there any workaround?
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Antony, It would be best to upgrade to the latest version of BPA at this point as it's the most stable and we can rule out any issues with the installation.
------------------------- ![]() Devin Cannon | Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
we are in the process of migrating from 9 to 10. But we get the same error in 10 (10.4.2.1) when the agents run out of memory.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hello Antony,
Is this a virtual machine? IF so, is it possible to add more memory to the machine to prevent the agent from running out of memory?
------------------------- ![]() Alex Escalante | Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
||||||||||
![]() |
||||||||||
Update: We did get this fixed by upgrading the memory.
|
||||||||||
|
||||||||||
![]() |
||||||||||
Hi Antony, I'm glad it's working and thank you for following up on the thread with the fix.
------------------------- ![]() Devin Cannon | Support Analyst AutoMate | Division of HelpSystems HelpSystems, LLC | T: +1.213.738.1700 | F: +1.213.738.7665 |
||||||||||
|
FuseTalk Enterprise Edition v4.0 - © 1999-2021 FuseTalk Inc. All rights reserved.