article Suppress Connection Warnings from the Agent in /var/adm/messages

In some Linux / Unix / Solaris configurations, you may notice that the up.time agent is repeatedly logging connection warnings in the /var/adm/messages log.  This is usually normal behaviour as xinetd/inetd is set up to log any connections from it's services by default.

 

In the case of the up.time agent, this practice can result in very large log files, as every time the Monitoring Station polls the agent or runs a Service Monitor, the connection will be logged.
 
If you want to disable this logging for the up.time agent service, there are a couple of different approaches to take.  The option to use depends on the platform's OS, and how it's xinetd/inetd/syslogd settings are configured.  So please make sure you are using the appropriate option for your environment.
  1. Disable or suppress warning level messages via the appropriate config file for your Operating System's logging tool, and how your agent is currently running (i.e. xinet.d, init.d or deamon mode).
  2. Edit the /etc/xinetd.d/uptimeagent file and change the log type to only log EMERG level messages, which will suppress the warning level connection messages (i.e. log_type = SYSLOG authpriv emerg).
  3. Edit the /etc/xinetd.d/uptimeagent file, and change the the log_type to FILE, and either log to an uptime agent only log, or /dev/null to suppress the logging completely (i.e. log_type: FILE /dev/null or log_type: FILE /var/tmp/uptimeagent.log).

Related Articles


Suppress Linux agent inetd uptmagnt connection warnings

RatingViews
article

This solution adds further detail to the following article that describes how to suppress agent daemon messages: http://support.uptimesoftware.com/article.php?id=308 Use the following steps to...

By: uptime Support | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 549

  2248

/var/adm/messages: inetd uptmagnt connection warnings

RatingViews
article

On some UNIX or Linux servers you may notice repeated messages like the ones below in your messages log once you start monitoring the server with up.time. Jul 2 14:43:27 hostname inetd[486]:...

By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 308

  3277

Resolving uptimeagent Daemon Messages

RatingViews
article

By: uptime Support | Date Created: 6-13-2006 | Last Modified: 10-28-2011 | Index: 081

  5699

Understanding your Oracle Connection Settings

RatingViews
article

This article outlines how you can use the information in the Oracle TNS connection string to populate database-specific fields that need to be set in the uptime.conf file.

By: uptime Support | Date Created: 2-27-2007 | Last Modified: 6-30-2011 | Index: 146

  6095

Problems adding an Agent to up.time

RatingViews
article

By: uptime Support | Date Created: 6-15-2006 | Last Modified: 8-9-2011 | Index: 083

  7973

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement