MonitorWare Knowledge Base

I am running MWAgent 2.1.224 on a Winows 2003 server but every now and again (once a day on average) get about 10 logs within the space of a few seconds which are:

Error while applying an action - skipping this action. Error is 'Unknown error while sending data (TCP)'.

Followed by:

Numerous runtime events were encountered .
This is usually caused by configuration or network problems.
From now, there will no more events logged for this hour.

Anyone else seen this or care to comment. I've turned on full logging in case that sheds any light on the problem and am awaiting a repro - hopefully tomorow

Hi,

are you using Syslog over TCP or SETP Action?
This error can happen when the target Server (Syslog or SETP) is offline.


best regards,
Andre Lorbach

Neither - we just send e-mails

Oh ok
Does it happen randomly?
Or did the Email Action not work yet?

Every thing works fine, we get the e-mails for the various services we have set up e.g. diskfull, services, events. Just now and again we get 10 e-mails through with these error logs in and then sometimes have to restart the service.

What is odd is that one of our rules/services sends an e-mail when an ERROR is logged in the event log and we DO get the e-mails for these ERRORs raised by MonitorWareAgent to the errors are probably not related to sending e-mails. But then those are the only actions that woudl use the network???

From the error message a TCP based connection did not succeed.
The following actions (can) use the TCP protocol:

- Syslog
- SETP
- SendEmail

As you only use SendEmail, it is related to this action.
In order to found out more, can you enable debug logging on one of this servers and set it to Full DebugOutput? Let it run for a while and then send me the debug logfile to alorbach AT adiscon.com

OK, will do although I suspect it wont be until after the weekend now.

Many thanks

Sorry for the delay in getting back to you - I have now sent the trace file as requested

Many thanks,
Phil.

np...for all others reading this thread, we are currently handling this case via email. If the problem is solved, the solution will be posted here.