| Author |
Message |
![[Post New]](/Sysforums/templates/default/images/icon_minipost_new.gif) 08/10/2009 11:53:16
|
adrian_gazibar
SysAider
Joined: 04/07/2008
Messages: 38
Offline
|
Trying to deploy the remote discovery service in one of the remote networks.
Downloaded it, installed it with the right settings (name, url, account id), started it, I am getting the following error messages in the snmpagent.log on the remote discovery machine:
Error on registering discovery service.org.apache.commons.httpclient.NoHttpResponseException: The server 10.21.1.75 failed to respond
Error on getting discovery service messages from sysaid server.org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 5000 ms
Because of this the remote discovery is not getting available on the discovery jobs page.
On the SysAid Server, there are no errors linked to this.
The interesting thing is, that I see the message when I connect to the SysAid server in the Asset Management/Network Discovery/Log
I am connecting from a completely different location, where i don't have direct connectivity to the remote discovery server.
Just so you understand:
- The SysAid Server is in Germany
- The Remote Discovery Server is in Cyprus
- I am presently connecting from Romania
From my place, I don't have a direct connection to Cyprus
But I do have a connection to Germany
And Cyprus also has a connection to Germany.
The connections work excellent. That was the first thing to test (for instance the SysAid Agent installed on the remote Discovery machine in Cyprus is communicating with the server in Germany.
Did anyone encountered issues with the remote discovery?
Is there a known issue with remote discovery?
Late edit: After 30 minutes of errors, the remote discovery has shown up in the SysAid Server. I suspect the server was busy doing something, or the registration is scheduled to be processed at a later time.
So it can be considered closed
This message was edited 1 time. Last update was at 08/10/2009 12:05:55
|
|
|
30/07/2010 14:40:08
|
Timmothy Green
SysAider
Joined: 21/10/2009
Messages: 38
Offline
|
Getting the same error, however, it has been 4 hours since the message below was logged and still not seeing the Remote Discovery server under Network Discovery.
Error on getting discovery service messages from sysaid server.org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 5000 ms
|
|
|
21/02/2011 15:58:13
|
KieranCork
SysAider
Joined: 11/10/2010
Messages: 24
Offline
|
I'm getting the same error on three remote sites where I've installed the 7.5 remote agent.
It's been between 30 minutes and five hours between installs but none have shown up yet. Any ideas about this one Sysaiders?
Thanks
Kieran
|
|
|
18/04/2011 14:35:42
|
Jeremy Phillips
SysAider
Joined: 04/09/2010
Messages: 17
Location: Davis, California, USA
Offline
|
I am also getting this error.
I installed the remote discovery service at one of our remote sites last week, and it worked with no problems.
Every other site I have tried to add subsequently results in this same error. When I start the remote discovery service, I do get the pop-up in SysAid indicating that the remote discover service has started, but then the service never shows up in the list of available services. All of the unsuccessful remote discovery services have been running for several days, and still do not show up in the list. I have restarted the remote services and the SysAid instance several times.
I am using version 7.5 of the remote discovery service.
I was about to submit a support request, but I figure I'll give this a chance first 
Thanks,
Jeremy.
This message was edited 2 times. Last update was at 18/04/2011 14:43:44
|
|
|
12/09/2011 18:17:04
|
Copenhague
SysAider
Joined: 28/06/2011
Messages: 5
Offline
|
Hello everyone,
I'm working with V8 and I have the same problem! have you found the solution?
Thank in advance
|
|
|
![[Up]](/Sysforums/templates/default/images/icon_up.gif){kind=icon}
![[WWW]](/Sysforums/templates/default/images/icon_www.gif){kind=icon}
