[
https://issues.apache.org/jira/browse/AMBARI-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-18427:
---------------------------------
Description:
I hit this issue yesterday after upgrading ambari-agent:
{code}
Verifying Python version compatibility...
Using python /usr/bin/pythonChecking for previously running Ambari Agent...
Starting ambari-agentVerifying ambari-agent process status...
ERROR: ambari-agent start failed. For more details, see
/var/log/ambari-agent/ambari-agent.out:
====================
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/ambari_agent/AmbariAgent.py", line
24, in <module> from Controller import AGENT_AUTO_RESTART_EXIT_CODE
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 41,
in <module> from ambari_agent.ActionQueue import ActionQueue
File "/usr/lib/python2.6/site-packages/ambari_agent/ActionQueue.py", line
37, in <module> from ambari_commons.str_utils import split_on_chunks
ImportError: cannot import name split_on_chunks
====================
{code}
I'm not the first person to have encountered it, see:
https://community.hortonworks.com/questions/55968/ambari-agent-start-failed-2.html
Considering this is an existing cluster the solution of rm -rf'ing the entire
python2.6 site-packages seems excessive...
was:
I hit this issue yesterday after upgrading ambari-agent:
{code}
Verifying Python version compatibility...
Using python /usr/bin/pythonChecking for previously running Ambari Agent...
Starting ambari-agentVerifying ambari-agent process status...
ERROR: ambari-agent start failed. For more details, see
/var/log/ambari-agent/ambari-agent.out:
====================
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/ambari_agent/AmbariAgent.py", line
24, in <module> from Controller import AGENT_AUTO_RESTART_EXIT_CODE
File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 41,
in <module> from ambari_agent.ActionQueue import ActionQueue
File "/usr/lib/python2.6/site-packages/ambari_agent/ActionQueue.py", line
37, in <module> from ambari_commons.str_utils import split_on_chunks
ImportError: cannot import name split_on_chunks
====================
{code}
I'm not the first person to have encountered it, see:
https://community.hortonworks.com/questions/55968/ambari-agent-start-failed-2.html
Considering this is an existing cluster the solution of rm -rf'ing the entire
python2.6 site-packages seems excessive
> Agent 2.4.0.1 start error "cannot import name split_on_chunks" after upgrade
> ----------------------------------------------------------------------------
>
> Key: AMBARI-18427
> URL: https://issues.apache.org/jira/browse/AMBARI-18427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.4.0
> Environment: HDP 2.3
> Reporter: Hari Sekhon
> Priority: Blocker
>
> I hit this issue yesterday after upgrading ambari-agent:
> {code}
> Verifying Python version compatibility...
> Using python /usr/bin/pythonChecking for previously running Ambari Agent...
> Starting ambari-agentVerifying ambari-agent process status...
> ERROR: ambari-agent start failed. For more details, see
> /var/log/ambari-agent/ambari-agent.out:
> ====================
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/AmbariAgent.py", line
> 24, in <module> from Controller import AGENT_AUTO_RESTART_EXIT_CODE
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 41, in <module> from ambari_agent.ActionQueue import ActionQueue
> File "/usr/lib/python2.6/site-packages/ambari_agent/ActionQueue.py", line
> 37, in <module> from ambari_commons.str_utils import split_on_chunks
> ImportError: cannot import name split_on_chunks
> ====================
> {code}
> I'm not the first person to have encountered it, see:
> https://community.hortonworks.com/questions/55968/ambari-agent-start-failed-2.html
> Considering this is an existing cluster the solution of rm -rf'ing the entire
> python2.6 site-packages seems excessive...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
