Problems with SpringSource AMS

[tsouza]

Hi,

I've been trying SpringSource AMS and tc Server, but I'm having the following problem: Yesterday, first, I tried AMS with no tc running, everything was working fine, but today, I was about to try AMS with a tc Server instance configured, although AMS auto-discovering worked fine, it couldn't be registered. Here is the error message:

Unable to import platform : org.hyperic.hq.appdef.shared.AIQApprovalException: Error connecting or communicating with agent Unable to connect to 192.168.0.25:2144: Connection timed out: connect

I suppose the problem is that my IP changed from .25 (yesterday) to .12 (today). Here is the AutoInventory IPs:

id	version_col	aiq_platform_id	address	netmask	mac_address	queuestatus	diff	ignored	ctime	mtime
10005	0	10002	192.168.0.25	255.255.255.0	00:1C:C0:67:5F:B4	3	0	false	1241634037389	1241634037389
10009	0	10002	192.168.0.12	255.255.255.0	00:1C:C0:67:5F:B4	1	0	false	1241634037389	1241634037389
10006	1	10002	192.168.21.1	255.255.255.0	00:50:56:C0:00:08	1	0	false	1241634037389	1241635765748
10007	1	10002	192.168.91.1	255.255.255.0	00:50:56:C0:00:01	1	0	false	1241634037389	1241635765748
10008	1	10002	127.0.0.1	255.0.0.0	00:00:00:00:00:00	1	0	false	1241634037389	1241635765748

The first row is yesterday's ip, the second is today's ip, the rest I can't even imagine where it came from (except, of course, the loopback). What's strange is that, even though AMS autodiscovers my host with fqn (which resolves to the correct IP), it keeps insisting with the old IP. The only thing I haven't tried is reinstalling everything, but I believe this should be a last resource action.

I tried removing the platform registration, but the problem continues. When I tried latest Hyperic, I remember somewhere an option to purge data tables, but I can't find it in AMS.

BTW, how are the plans on upgrading to latest Hyperic? I'm quite interested in it's SQL Server support (it could even detect my sql express instance).

Regards,
Thiago Souza

[Jason Konicki]

Hi,

I've been trying SpringSource AMS and tc Server, but I'm having the following problem: Yesterday, first, I tried AMS with no tc running, everything was working fine, but today, I was about to try AMS with a tc Server instance configured, although AMS auto-discovering worked fine, it couldn't be registered. Here is the error message:

Unable to import platform : org.hyperic.hq.appdef.shared.AIQApprovalException: Error connecting or communicating with agent Unable to connect to 192.168.0.25:2144: Connection timed out: connect

I suppose the problem is that my IP changed from .25 (yesterday) to .12 (today). Here is the AutoInventory IPs:

id	version_col	aiq_platform_id	address	netmask	mac_address	queuestatus	diff	ignored	ctime	mtime
10005	0	10002	192.168.0.25	255.255.255.0	00:1C:C0:67:5F:B4	3	0	false	1241634037389	1241634037389
10009	0	10002	192.168.0.12	255.255.255.0	00:1C:C0:67:5F:B4	1	0	false	1241634037389	1241634037389
10006	1	10002	192.168.21.1	255.255.255.0	00:50:56:C0:00:08	1	0	false	1241634037389	1241635765748
10007	1	10002	192.168.91.1	255.255.255.0	00:50:56:C0:00:01	1	0	false	1241634037389	1241635765748
10008	1	10002	127.0.0.1	255.0.0.0	00:00:00:00:00:00	1	0	false	1241634037389	1241635765748

The first row is yesterday's ip, the second is today's ip, the rest I can't even imagine where it came from (except, of course, the loopback). What's strange is that, even though AMS autodiscovers my host with fqn (which resolves to the correct IP), it keeps insisting with the old IP. The only thing I haven't tried is reinstalling everything, but I believe this should be a last resource action.

I tried removing the platform registration, but the problem continues. When I tried latest Hyperic, I remember somewhere an option to purge data tables, but I can't find it in AMS.

BTW, how are the plans on upgrading to latest Hyperic? I'm quite interested in it's SQL Server support (it could even detect my sql express instance).

Regards,
Thiago Souza

That issue should be resolved when AMS is upgraded to the latest HQ version.

The easiest way to resolve this right now is to re-register your agent, by deleting your <agent-home>/data directory and restarting the agent to re-register with the server.

-Jason

[tsouza]

Hi,

I tried it, but I got other errors, but It's good to know that it has been resolved, any plans on next release date?

Regards,
Thiago Souza