Date: Thu, 28 Mar 2024 23:21:32 +0000 (UTC) Message-ID: <328685125.5545.1711668092225@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5544_467149306.1711668092224" ------=_Part_5544_467149306.1711668092224 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The following error typically occurs when an agent on a Solaris = or Linux system is not returning data or cannot be added to Uptime Infrastr= ucture Monitor:
uptime agent daemon.error: Permission denied
This problem may also be detected by the presence of the following log m= essage in the /var/adm/messages or /var/log/messages files:
Oct 30 = 10:48:07 hostname inetd[6402]: [ID 388736 daemon.error] execv /opt/uptime-a= gent/bin/uptmagnt: Permission denied
This error is generally caused by inetd attempting to run the uptmagnt b= inary as one user when the binary is owned by another user. In the ex= ample above, we can find that the /opt/uptime-agent/bin/uptmagnt file is ow= ned by nobody:
# ls -l= /opt/uptime-agent/bin/uptmagnt -rwxr--r-- 1 nobody nobody 62736 Oct 2 16:0= 8 uptmagnt
However, the inted.conf file shows that the uptmagnt is to be run as the= uptime user:
# grep = uptmagnt /etc/inetd.conf # *** Installed by the up.time pkgadd command (uptmagnt) uptmagnt stream tc= p nowait uptime /opt/uptime-agent/bin/uptmagnt
By changing the inetd.conf line to run the uptmagnt as nobody i= nstead of uptime and then restarting inetd, the agent should start= responding normally.