active rma

Eggers2 · Post by **Eggers2** » Wed Jan 16, 2008 1:26 am

----------------------
sorry, should not be a new topit, should be a reply topic of "Errors in 7.06 beta"
------------------------

Hi Alex,

I´m still trying with this active rma.

I installed it on a clean and fresh win2003 without any firwall or AV.
The active rma run 5 day and 12 hours. This morning it lost the connection.

When I log in the log.txt it says:
[10.01.2008 10:09] test-server Connection error: Wrong reply packet received
[11.01.2008 07:17] test-server Agent "test-server" already connected!
[11.01.2008 07:17] test-server Agent "test-server" already connected!
[12.01.2008 07:17] test-server Agent "test-server" already connected!
[12.01.2008 07:17] test-server Agent "test-server" already connected!
[12.01.2008 07:18] test-server Agent "test-server" already connected!
[13.01.2008 07:17] test-server Decode error: Cannot read data. An existing connection was forcibly closed by the remote host.
[13.01.2008 07:17] test-server Agent "test-server" already connected!
[15.01.2008 07:17] test-server Agent "test-server" already connected!

There is no entry from this morning (16.01.2008).

It just looks like the active rma hangs up.

When I restart the service everything is ok (for the next some days).

It seems to me that the AV programm does not matter. The other active rma clients (4 real customer servers) have the same behaviour. They all run (with 3.03 beta) some days till connections hangs up.

Sorry,
Alex

KS-Soft · Post by **KS-Soft** » Fri Jan 18, 2008 6:04 am

Could you please check connection status between HostMonitor and Active RMA usign some 3rd party utility (e.g. you may use our IP-Tools, Windows' netstat -a command or SysInternal's TCPView)?
When RMA starts to report "Agent "test-server" already connected!" error, please check is HostMonitor and RMA really connected. Check connection status several times within 40 sec. If there is stable connection between agent and HM, this means there is some error in agent's code (it "thinks" connection has been lost). Otherwise there is some mistake in HostMonitor (it "thinks" agent is connected while connection was dropped).
There is another posibility - you are running another RMA somewhere using the same name. But I don't think its a true for 4 different agents.

IMHO there is mistake in HostMonitor's code, we are looking for it.

Regards
Alex

KS-Soft · Post by **KS-Soft** » Fri Jan 18, 2008 9:02 am

H'm, interesting log...
Why your system loses connection once a day at 07:17, everyday except January 14?? There must be some external problem.

Regards
Alex

KS-Soft · Post by **KS-Soft** » Fri Jan 18, 2008 2:57 pm

Looks like nothing wrong in HostMonitor's code. I just optimized it a little...
I think "Agent NNN already connected" message appears because connection was not closed by software, there is some hardware break. HostMonitor detects this break just a little later than RMA. That's why RMA cannot connect right away, however after several seconds RMA repeats TCP request and HostMonitor accepts it.

So, I see 2 problems
1a) something breaks your network connection everyday at 07:17.
1b) or may be you have setup HostMonitor or some another application started on the same system to perform some heavy operations at 07:17? System (HostMonitor) slows down and does not respond to RMA within specified timeout. That's why agent "thinks" connection lost and tries to reconnect while HostMonitor "thinks" everything is fine (it simply does not have enough processor time to "think").
Could you please check both theories?

2) sometimes Active RMA hangs. May be as result of such connection break. Unfortunately we still cannot reproduce this...

PS. I think we may release HostMonitor 7 and keep Active RMA as Beta a little longer

Regards
Alex

Eggers2 · Post by **Eggers2** » Tue Jan 22, 2008 12:49 am

HI,

yes, there is a hardware-break always once a day. As I told you earlier in germany the providers always have a internetconnection cut once a day. They stop the internetconnection from customer to internet. The customer-router is programmed to restart the connection immediatly. But there is a cut for about 5-10 seconds once a day. often at the same time.

I checked the other four servers logs and they had a different time.
As you can see the first days the rma client succesfully reconnects to hostmonitor. But some day it stops to reconnect...

Right now I´m very busy but I will have a look at it next days...

Thanks,
Alex

greyhat64 · Post by **greyhat64** » Thu May 08, 2008 8:27 am

I'm having the exact same problem. I don't see any posted resolution or followup - what became of this issue?

KS-Soft Europe · Post by **KS-Soft Europe** » Thu May 08, 2008 8:59 am

greyhat64 wrote:I'm having the exact same problem. I don't see any posted resolution or followup - what became of this issue?

Could you provide more information, please?
- What version of HostMonitor do you use?
- What version of RMA do you use?
We recommend to use Active RMA ver 3.08, that is supplied with version 7.20

Regards,
Max

greyhat64 · Post by **greyhat64** » Mon May 12, 2008 9:55 pm

HostMonitor 7.20
Active RMA 3.06a
What's interesting is that RMA Manager connects without issue.
Could this have anything to do with trying to run Active RMA as a service?
I'll try 3.08 & report back.

KS-Soft · Post by **KS-Soft** » Tue May 13, 2008 5:41 pm

We made some changes in Active RMA version 3.06 Beta in order to fix this problem but I am not sure everything was done in 3.06 Beta.
Yes, please try version 3.08, it should work fine. If not, there must be some other problem

BTW: its bad idea to use software components from different packages (e.g. HostMonitor 7.20 and RMA 3.06). Please use all components from the same package: HostMonitor, RCC, Web Service, RMA Manager, etc.

Regards
Alex

greyhat64 · Post by **greyhat64** » Sat May 17, 2008 1:36 am

I installed the new 7.22c w/RMA 3.10 and Viola! My active RMA problems are resolved.

One thing I forgot to mention earlier, though - I'm having trouble with RCC.

I've set admin user with no IP restrictions (0.0.0.0) and yet I get the error

Connecting... Failed. Connection error. An invalid argument was supplied.

What am I missing here?

KS-Soft Europe · Post by **KS-Soft Europe** » Sat May 17, 2008 11:20 am

greyhat64 wrote:Connecting... Failed. Connection error. An invalid argument was supplied.

You just should execute following command from the command line prompt on the machine, where you start RCC:

Code: Select all

netsh winsock reset

Please note: reboot is required after this command.

Regards,
Max

greyhat64 · Post by **greyhat64** » Sun May 18, 2008 11:37 pm

RCC now works. Thanks. What's behind that?

KS-Soft Europe · Post by **KS-Soft Europe** » Mon May 19, 2008 1:22 am

greyhat64 wrote:RCC now works.

Glad to hear that.

greyhat64 wrote:What's behind that?

Looks like some Winsock corruption on your system. This issue might be caused by some third party software, for instance, we know exactly "NOD32" antivirus leads to this problem in some circumstances. "netsh winsock reset" command just resets the winsock catalogue.
http://technet.microsoft.com/en-us/libr ... 57156.aspx

Regards,
Max