You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2018/05/07 14:51:00 UTC
[jira] [Updated] (AMBARI-23781) Ambari 2.6.2 server start/stop
throws warning about unable to load _posixsubprocess.so
[ https://issues.apache.org/jira/browse/AMBARI-23781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Di Li updated AMBARI-23781:
---------------------------
Description:
This was for Ambari 2.6.2-135 for PPC build
This is the err from my print out that I added to /usr/lib/ambari-server/lib/ambari_commons/subprocess32.py
_UserWarning: _posixsubprocess /usr/lib/ambari-server/lib/ambari_commons/_posixsubprocess.so: cannot open shared object file: No such file or directory_
The file existed with 644 permission owned by root ( also the user for Ambari install)
Ambari server also timed out on start up right after the Ambari upgrade. (complained server was not up after 50 seconds)
was:
This is the err from my print out that I added to /usr/lib/ambari-server/lib/ambari_commons/subprocess32.py
_UserWarning: _posixsubprocess /usr/lib/ambari-server/lib/ambari_commons/_posixsubprocess.so: cannot open shared object file: No such file or directory_
The file existed with 644 permission owned by root ( also the user for Ambari install)
> Ambari 2.6.2 server start/stop throws warning about unable to load _posixsubprocess.so
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-23781
> URL: https://issues.apache.org/jira/browse/AMBARI-23781
> Project: Ambari
> Issue Type: Bug
> Reporter: Di Li
> Priority: Major
>
> This was for Ambari 2.6.2-135 for PPC build
> This is the err from my print out that I added to /usr/lib/ambari-server/lib/ambari_commons/subprocess32.py
> _UserWarning: _posixsubprocess /usr/lib/ambari-server/lib/ambari_commons/_posixsubprocess.so: cannot open shared object file: No such file or directory_
> The file existed with 644 permission owned by root ( also the user for Ambari install)
> Ambari server also timed out on start up right after the Ambari upgrade. (complained server was not up after 50 seconds)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)