[
https://issues.apache.org/jira/browse/AMBARI-26560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
guluo resolved AMBARI-26560.
----------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
> Unable to execute alert because of mistakenly ambari-agent cache_dir
> --------------------------------------------------------------------
>
> Key: AMBARI-26560
> URL: https://issues.apache.org/jira/browse/AMBARI-26560
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Reporter: guluo
> Assignee: guluo
> Priority: Major
> Fix For: 3.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ambari-agent periodically fails to execute several alerts, and the following
> error appears in /var/log/ambari-agent/ambari-alert.log
> ERROR 2025-05-07 16:00:21,537 base_alert.py:141 -
> [Alert][ambari_agent_ulimit] Unable to execute alert. Unable to find
> 'alert_ulimit.py' as an absolute path or part of /tmp/stacks or
> /tmp/host_scripts
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/alerts/base_alert.py", line
> 120, in collect
> res = self._collect()
> File "/usr/lib/ambari-agent/lib/ambari_agent/alerts/script_alert.py", line
> 96, in _collect
> cmd_module = self._load_source()
> File "/usr/lib/ambari-agent/lib/ambari_agent/alerts/script_alert.py", line
> 176, in _load_source
> self.path, self.stacks_dir, self.host_scripts_dir
>
> The Reason:
> ambari-agent.ini defines a custom cache_dir, but ambari-agent does not
> correctly update this value when loading configuration in AmbariConfig.py.
> As a result, the agent always falls back to the default cache directory
> (/tmp), causing script lookup failures.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
