Related Documentation | \nVersion of up.time Affected | \nAffected Platforms | \n
\n | All | \nLinux, UNIX | \n
This article describes how to address the condition that causes a large number of messages, similar to those shown below, to appear in Linux or UNIX log files.
\n \n\nJan 28 16:50:24 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagent[7325] from 165.4.9.253 53672 \nJan 28 16:50:28 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagent[7676] from 165.4.9.253 53707 \nJan 28 16:50:31 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagent[7870] from 165.4.9.253 53732 \n\n \n
Details
\n \nThese errors appear because the syslog tool on the agent system has been configured to log daemon.notice messages. This level of logging registers every connection to the agent system (i.e. the messages are logged each time the monitoring station polls the agent). For example, with a five-minute polling frequency, a message will appear in the log file every five minutes.
\n \nWorkaround
\n \nPrevent the system from logging at this level of detail by choosing one of the following options:
\n \n\nlog_type = SYSLOG authpriv emerg \n\n \n
This option will only log emerg messages to the log file instead of the option set in the /etc/syslog.conf file.
\n