[
https://issues.apache.org/jira/browse/IMPALA-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer updated IMPALA-13802:
-------------------------------------
Summary: bootstrap_system.sh can fail in the middle in dirty environment
(was: bootstrap_system.sh cam fail in the middle in dirty environment)
> bootstrap_system.sh can fail in the middle in dirty environment
> ---------------------------------------------------------------
>
> Key: IMPALA-13802
> URL: https://issues.apache.org/jira/browse/IMPALA-13802
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Csaba Ringhofer
> Priority: Major
>
> This comes up regularly when building on reused RHEL8 build instances:
> {code}
> 00:00:28.224 + sudo service postgresql initdb
> 00:00:28.241 Hint: the preferred way to do this is now
> "/usr/bin/postgresql-setup --initdb --unit postgresql"
> 00:00:28.302 * Initializing database in '/var/lib/pgsql/data'
> 00:00:28.303 ERROR: Data directory /var/lib/pgsql/data is not empty!
> 00:00:28.303 ERROR: Initializing database failed, possibly see
> /var/lib/pgsql/initdb_postgresql.log
> {code}
> this leads to prematurely exiting the script at:
> https://github.com/apache/impala/blob/ce9b927d547ac4290275fede4843288bbf97a429/bin/bootstrap_system.sh#L399
> surprisingly this doesn't seem to cause subsequent issues - probably it is
> enough that the rest of script already ran once
> If already touching this area, it would be nice to move logic related to
> IMPALA_HOME to another script, as it is not needed in automatic tests and can
> be a nuisance in personal builds as it messes with .bashrc
> https://github.com/apache/impala/blob/ce9b927d547ac4290275fede4843288bbf97a429/bin/bootstrap_system.sh#L518
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
