ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk" <aonis...@hortonworks.com>
Subject Re: Review Request 40801: Ambari fails to start with posgres DB on Suse
Date Mon, 30 Nov 2015 20:39:27 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40801/#review108389
-----------------------------------------------------------



ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py (line 426)
<https://reviews.apache.org/r/40801/#comment167837>

    Can we add str(ex) to this one. So the reason can be investigated easily if it occurs.


- Andrew Onischuk


On Nov. 30, 2015, 8:08 p.m., Vitalyi Brodetskyi wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40801/
> -----------------------------------------------------------
> 
> (Updated Nov. 30, 2015, 8:08 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14119
>     https://issues.apache.org/jira/browse/AMBARI-14119
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> {code}zypper install -y ambari-server"
> Loading repository data...
> Reading installed packages...
> Resolving package dependencies...
> 
> The following NEW packages are going to be installed:
>   ambari-server libpq5 postgresql94 postgresql94-server postgresql-init postgresql-server

> 
> The following packages are not supported by their vendor:
>   ambari-server libpq5 postgresql94 postgresql94-server postgresql-init postgresql-server

> 
> 6 new packages to install.
> Overall download size: 394.6 MiB. After the operation, additional 433.1 MiB will be used.
> Continue? [y/n/?] (y): y
> Retrieving package libpq5-9.4.5-5.1.x86_64 (1/6), 168.0 KiB (461.0 KiB unpacked)
> Retrieving: libpq5-9.4.5-5.1.x86_64.rpm [done]
> Retrieving package postgresql-init-9.4-46.5.noarch (2/6), 10.0 KiB (8.0 KiB unpacked)
> Retrieving: postgresql-init-9.4-46.5.noarch.rpm [done]
> Retrieving package postgresql94-9.4.4-6.1.x86_64 (3/6), 1.2 MiB (4.2 MiB unpacked)
> Retrieving: postgresql94-9.4.4-6.1.x86_64.rpm [done]
> Retrieving package postgresql94-server-9.4.4-6.1.x86_64 (4/6), 3.9 MiB (16.5 MiB unpacked)
> Retrieving: postgresql94-server-9.4.4-6.1.x86_64.rpm [done]
> Retrieving package postgresql-server-9.4-4.1.noarch (5/6), 4.0 KiB (1.0 KiB unpacked)
> Retrieving: postgresql-server-9.4-4.1.noarch.rpm [done]
> Retrieving package ambari-server-2.1.3.0-493.x86_64 (6/6), 389.4 MiB (412.0 MiB unpacked)
> Retrieving: ambari-server-2.1.3.0-493.x86_64.rpm [..done (151.6 MiB/s)]
> Installing: libpq5-9.4.5-5.1 [.done]
> Additional rpm output:
> warning: /var/cache/zypp/packages/HOSTED SLES11_3/server_database_postgresql/x86_64/libpq5-9.4.5-5.1.x86_64.rpm:
Header V3 DSA signature: NOKEY, key ID 05905ea8
> 
> 
> Installing: postgresql-init-9.4-46.5 [.done]
> Additional rpm output:
> warning: /var/cache/zypp/packages/HOSTED SLES11_3/server_database_postgresql/noarch/postgresql-init-9.4-46.5.noarch.rpm:
Header V3 DSA signature: NOKEY, key ID 05905ea8
> Updating etc/sysconfig/postgresql...
> 
> 
> Installing: postgresql94-9.4.4-6.1 [..done]
> Additional rpm output:
> warning: /var/cache/zypp/packages/HOSTED SLES11_3/server_database_postgresql/x86_64/postgresql94-9.4.4-6.1.x86_64.rpm:
Header V3 DSA signature: NOKEY, key ID 05905ea8
> 
> 
> Installing: postgresql94-server-9.4.4-6.1 [.....done]
> Additional rpm output:
> warning: /var/cache/zypp/packages/HOSTED SLES11_3/server_database_postgresql/x86_64/postgresql94-server-9.4.4-6.1.x86_64.rpm:
Header V3 DSA signature: NOKEY, key ID 05905ea8
> 
> 
> Installing: postgresql-server-9.4-4.1 [.done]
> Additional rpm output:
> warning: /var/cache/zypp/packages/HOSTED SLES11_3/server_database_postgresql/noarch/postgresql-server-9.4-4.1.noarch.rpm:
Header V3 DSA signature: NOKEY, key ID 05905ea8
> 
> 
> Installing: ambari-server-2.1.3.0-493 [....................................................................................................................................................................................................done]
> Additional rpm output:
> insserv: warning: script 'ambari-server' missing LSB tags
> insserv: warning: script 'ambari-server' missing LSB tags
> insserv: Default-Start undefined, assuming default start runlevel(s) for script `ambari-server'
> ambari-server             0:off  1:off  2:off  3:on   4:off  5:on   6:off
> 
> 
> Installing DB
> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -q -i /grid/0/jenkins/workspace/Run-Ambari-Setup@8/build-utils/openstack-utils/accounts/hw-qe-keypair.pem
root@172.22.109.230 "ambari-server setup --java-home=/usr/jdk64/jdk1.7.0_67 -s"
> Using python  /usr/bin/python2
> Setup ambari-server
> Checking SELinux...
> WARNING: Could not run /usr/sbin/sestatus: OK
> Customize user account for ambari-server daemon [y/n] (n)? 
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> SuSEfirewall2: SuSEfirewall2 not active
> 
> Checking JDK...
> WARNING: JAVA_HOME /usr/jdk64/jdk1.7.0_67 must be valid on ALL hosts
> WARNING: JCE Policy files are required for configuring Kerberos security. If you plan
to use Kerberos,please make sure JCE Unlimited Strength Jurisdiction Policy Files are valid
on all hosts.
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)? 
> Configuring database...
> Default properties detected. Using built-in database.
> Configuring ambari database...
> Checking PostgreSQL...
> Running initdb: This may take upto a minute.
> About to start PostgreSQL
> ERROR: Exiting with exit code 1. 
> REASON: Unable to start PostgreSQL server. Exiting
> Set skip.service.checks=true ambari properties file on the Server host
> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -q -i /grid/0/jenkins/workspace/Run-Ambari-Setup@8/build-utils/openstack-utils/accounts/hw-qe-keypair.pem
root@172.22.109.230 "sed -i 's/skip.service.checks=false/skip.service.checks=true/' /etc/ambari-server/conf/ambari.properties"
> ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -q -i /grid/0/jenkins/workspace/Run-Ambari-Setup@8/build-utils/openstack-utils/accounts/hw-qe-keypair.pem
root@172.22.109.230 "export AMBARI_JVM_ARGS="-Xms512m -Xmx2048m -XX:PermSize=1024m -XX:MaxPermSize=1024m";
ambari-server start" &
> bash: line 0: export: `-Xmx2048m': not a valid identifier
> bash: line 0: export: `-XX:PermSize=1024m': not a valid identifier
> bash: line 0: export: `-XX:MaxPermSize=1024m': not a valid identifier
> Using python  /usr/bin/python2
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Running initdb: This may take upto a minute.
> About to start PostgreSQL
> ERROR: Exiting with exit code 1. 
> REASON: Unable to start PostgreSQL server. Status None. . Exiting{code}
> 
> {code}/var/lib/pgsql/data # cat postmaster.log 
> 2015-11-26 11:39:43 UTC   FATAL:  could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock":
No such file or directory
> 2015-11-26 11:39:59 UTC   FATAL:  could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock":
No such file or directory
> 2015-11-26 12:01:34 UTC   FATAL:  could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock":
No such file or directory
> 2015-11-26 12:04:30 UTC   FATAL:  could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock":
No such file or directory
> {code}
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/python/ambari_server/dbConfiguration.py ae7d280 
>   ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py 933113e 
>   ambari-server/src/test/python/TestAmbariServer.py bc23402 
> 
> Diff: https://reviews.apache.org/r/40801/diff/
> 
> 
> Testing
> -------
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message