active RMA agent update fails

losisoft · Post by **losisoft** » Mon May 12, 2008 9:16 am

Hi,

I try to upgrade my 5 active RMA agent from version 3.06 beta to version 3.08 with RMA manager. (Hostmon 7.18 )

From the 5 agent I could only update one agent without problem.
I got the following error with the other agents:
Sending request to AGENTNAME .. Error: Error

I tried to isolate the problem:

From the Agent side I only see that it create a file named: rma$a.upd
it doesn't do anything else. The size of the file is 0 byte.
If I restart the agent service, then the rma$a.upd file grows in size, around 70-90 bytes. But it contains only garbage.

As I see it doesn't transfer the new agent content to the agent server.

I tried the latest RMA_manager, and RMA client from version 7.22 to use.
It's better, but still get similar errors. Even with a upgrade from the agent 3.08 to 3.09.

Any idea, how to troubleshoot this error?
Is there any log file?

KS-Soft Europe · Post by **KS-Soft Europe** » Mon May 12, 2008 9:37 am

Could you provide more information, please?
- What Windows is installed on the machine, where RMA is running?
- Is RMA started as a service or as an application?
- What account do you use to start RMA if it is started as a service?

Probably, you have selected running agent to be transfered on remote site? We do not recommend to do that. We suggest you to copy new version of RMA into separate folder and select this RMA for update.

Regards,
Max

losisoft · Post by **losisoft** » Mon May 12, 2008 11:20 am

- What Windows is installed on the machine, where RMA is running?
Windows server 2003, SP2
- Is RMA started as a service or as an application?
Service
- What account do you use to start RMA if it is started as a service?
It's a windows user, which is a local admin on that machine.

>Probably, you have selected running agent to be transfered on remote site?
Nope. I used the file which is residing on the hostmonitor server itself.
And that machine doesn't have any agent installed locally.

KS-Soft · Post by **KS-Soft** » Mon May 12, 2008 3:02 pm

H'm, we were able to reproduce this problem on one system, while on other systems everything works just fine.
We need more time to investigate this issue....

Regards
Alex

losisoft · Post by **losisoft** » Tue May 13, 2008 1:50 am

KS-Soft wrote:H'm, we were able to reproduce this problem on one system, while on other systems everything works just fine.
We need more time to investigate this issue....

Regards
Alex

No problem, just let me know, if I can help you in the investigation.

losisoft · Post by **losisoft** » Thu May 29, 2008 7:26 pm

Did you manage to find anything, why it fails?
Could you narrow down the problem?

KS-Soft · Post by **KS-Soft** » Sun Jun 01, 2008 10:28 pm

Sorry for delay. I think we fixed the problem.
Could you please try the following update: www.ks-soft.net/download/actrma318.zip

BTW
This version supports IPv6 for for IP related test methods, such as Ping, TCP, UDP, NTP, SMTP, Radius, DICOM, SMTP Get, etc
You may use IPv4 or IPv6 addresses to specify target host, also you may use hostname (just like before) PLUS you may use hostname with ::ipv6 and ::ipv4 suffixes.
E.g.
- fe50::910c:51ff:9d:fe44
- 10.10.1.100
- primary.mailserver.com
- primary.mailserver.com::ipv4
- primary.mailserver.com::ipv6
When you specify hostname without suffix (primary.mailserver.com), RMA tries to resolve name using IPv4. If this is impossible, it tries to use IPv6.
If TCP/IP protocol version 6 in not installed, RMA uses IP version 4 as before. Also, IPv6 is not supported on Windows NT, 2000 (even if you have installed it on your Windows 2000 system). It works on Windows XP SP2, Windows 2003, Vista, Windows 2008

DNS, Trace, DHCP test methods do not support IPv6 yet.

Regards
Alex

losisoft · Post by **losisoft** » Tue Jun 03, 2008 3:21 am

Hi,

Thanks, I have updated the clients with the new version.
And then I tried to update them with the RMA manager with the same version.

And the results are not good. Only 3 of the 11 agent could update them self.

edit:
The 3.18 beta agents are always showing as operable client. Not connected, as the 3.09. Is this by design?

Is there a new rma manager what I need to use for the new agent?

Edit2:
I see in the log:
[6/3/2008 3:00 PM] active-machine.domain.int Connection error: Invalid password(?) (RMA Manager)
[
But the same machine with the old RMA agent work's fine.

The RMA manager is version: 3.03

KS-Soft · Post by **KS-Soft** » Tue Jun 03, 2008 4:31 pm

Ok, there is another version at www.ks-soft.net/download/actrma319.zip
I hope it works. At least it works fine on all our systems - we done update operation over 100 times...

Regards
Alex

losisoft · Post by **losisoft** » Wed Jun 04, 2008 9:50 am

I will update the agents tomorrow, I will let you know about the results.

losisoft · Post by **losisoft** » Mon Jun 09, 2008 11:24 am

Hi,

I have manually updated the agents to the 3.19 beta version.
Then I tried to update them to the same version.
I got all the time: Error: Error.
If I try to update to an older version, then I can update some of the client some not.

Can it not be that the RMA manager is old? I got 3.03

KS-Soft · Post by **KS-Soft** » Mon Jun 09, 2008 12:24 pm

RMA Manager 3.03 is latest version. Do you see 'Done" message after "Error"?
RMa Manager could show 1st error message because it cannot request updated information about agent while agent is rebooting however update process should work fine.

Regards
Alex

losisoft · Post by **losisoft** » Tue Jun 10, 2008 2:56 am

Hi,

I get this error:
Sending request to active-machine1 .. Error: Error
Sending request to active-machine2 .. Error: Error
Sending request to active-machine3 .. Error: Error
Done

It created a rma$a.upd file on the client. But nothing else. It's 0 byte long. And locked by the service. I need to restart it, to be able to delete it.

KS-Soft · Post by **KS-Soft** » Tue Jun 10, 2008 5:34 am

Sorry, we cannot reproduce the problem.
I don't know what is wrong

Could you try to start and update RMA in application mode?

Regards
Alex