MonitorWare Knowledge Base

by **Jackson** » Wed Mar 26, 2003 8:34 am

I established the client-server system as the way which described in the article "How to setup Windows NT centralized Monitoring - MonitorWare". But when I checked the result which generated by the MoniLog, I found it's only collected few records of the Remote client system(less than 10), and the local records have been completely gathered.

For this, I check the Application Logs with EventViewer on the Remote Client System, and I found a lot of record says "Error, Event ID:114 Describe: Error sending MIAP server message: Remote system closed socket communication while we were expecting data".

I am using Windows2000 Server Chinese Version on both Client and Server as OS.

I'm not sure where is the problem and how to solve this, can anyone help me out? In case I can't get back here and check, please also send me an e-mail at zzl@cic.tsinghua.edu.cn when you reply me.

Thanks in Advance.

by **alorbach** » Wed Mar 26, 2003 12:02 pm

Hi,

from your description, it looks like that there are communication problems between the Client Server systems.

So I need to ask some other things first.
Which MWAgent Version are you using? (Please note that 1.2 is the latest one).
Are you using the default ports for SETP?
How is the connection quality between your server and clients?

by **Guest** » Thu Mar 27, 2003 1:10 am

Thanks for reply.

I am using Adiscon MonitorWare Agent Version 1.2.127 Client Version 1.2.314.

Yes, I'm using default port 5432. And our network is 1000MHz Ethernet, all the client and server are in the same segment. The connections between them are good enough to do MonitorWare's job.

by **alorbach** » Thu Mar 27, 2003 10:21 am

Agreed

, that Bandwidth should be definitely enough

In order to find the problem, could enable debug logging (See MWAgent Client, there is a point debug options) with Full Debug output on the machine that has the SETP Server.

Then restart the MWAgent, and let it run for approx 30 minutes. After this, please pack the debug file with ZIP or RAR and send it to support@adiscon.com.

Then I can take a deeper look to it, and analyze the problem here.

by **tosh** » Wed Apr 30, 2003 5:45 pm

I've also had this error, but this was on servers sending event log info across the internet to a collector.

When I first installed the agent, it sends everything in the event log as a big flood - this usually causes these errors. If you leave the agent alone, it starts back up again, and eventually gets through all the records.

Once the server is in production, and only a few events are being sent, I don't see these errors normally.

Hope that helps

by **tosh** » Thu May 01, 2003 11:45 am

Hi

Can someone from Adiscon explain if events will ever be lost due to poor network connectivity? I'm getting these errors in my logs every day, and I'm assuming its due to poor Internet connectivity, but have ignored them so far...

Regards

by **Guest** » Fri May 02, 2003 8:30 am

Hello,

If you forward the data using the SETP protocol (only present in MWAgent so far), then the messages will not get lost becuase it is TCP based but if you are using Syslog Protocol, then the messages can get lost because of network traffic

Best Regards
Wajih-ur-Rehman
Adiscon

by **tosh** » Fri May 02, 2003 2:21 pm

I am only using the SETP protocol not syslog...

by **alorbach** » Fri May 02, 2003 2:32 pm

If you use SETP, you will not loose messages. MWAgent keeps retrying if it could not send a message until it succeeds

.

by **tosh** » Fri May 02, 2003 2:42 pm

thanks for the clarification

MonitorWare Knowledge Base

Can't gather all of the records!?

Can't gather all of the records!?

RE:

Google Ads

Who is online