Date: Thu, 28 Mar 2024 16:38:44 +0000 (UTC) Message-ID: <1779952815.5417.1711643924433@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5416_1733787804.1711643924428" ------=_Part_5416_1733787804.1711643924428 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This article describes how to address the condition that causes = a large number of messages, similar to those shown below, to appear in Linu= x or UNIX log files.
Jan 28 = 16:50:24 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagent[7325]= from 165.4.9.253 53672 Jan 28 16:50:28 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagen= t[7676] from 165.4.9.253 53707 Jan 28 16:50:31 agent-host inetd[259]: [ID 317013 daemon.notice] uptimeagen= t[7870] from 165.4.9.253 53732
Details
These 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 tim= e 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= .
Workaround
Prevent the system from logging at this level of detail by choosing one = of the following options:
log_typ= e =3D SYSLOG authpriv emerg This option will only log emerg messages to the log file instead of the opt= ion set in the /etc/syslog.conf file.
On Solaris 10 systems, the uptimeagent SMF may need to be updated. V=
erify if tcp_trace is set to TRUE by running the following command: inetadm=
-l network/uptimeagent/tcp.
If the tcp_trace value is set to TRUE, set it to false with the following =
command:
inetadm= -m network/uptimeagent/tcp tcp_trace=3DFALSE.