Bug #15178
closed
Katello Installer Error
Description
This error appears to have come about this week, as test installs last week didn't do this.
Main Config Menu
1. [â] Configure capsule
2. [â] Configure certs
3. [â] Configure foreman
4. [â] Configure foreman_plugin_bootdisk
5. [â] Configure foreman_plugin_chef
6. [â] Configure foreman_plugin_default_hostgroup
7. [â] Configure foreman_plugin_discovery
8. [â] Configure foreman_plugin_hooks
9. [â] Configure foreman_plugin_puppetdb
10. [â] Configure foreman_plugin_remote_execution
11. [â] Configure foreman_plugin_setup
12. [â] Configure foreman_plugin_tasks
13. [â] Configure foreman_plugin_templates
14. [â] Configure katello
15. [â] Configure katello_plugin_gutterball
16. Display current config
17. Save and run
18. Cancel run without Saving
Choose an option from the menu... 17
echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for :5432/postgres]/returns: change from notrun to 0 failed: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]:5432/postgres]: Failed to call refresh: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for @:5432/postgres]: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Gutterball::Database/Exec[migrate database]: Failed to call refresh: Could not find command 'gutterball-db'
/Stage[main]/Gutterball::Database/Exec[migrate database]: Could not find command 'gutterball-db'
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache:index]/Exec[foreman-rake-apipie:cache:index]: Failed to call refresh: /usr/sbin/foreman-rake apipie:cache:index returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache:index]/Exec[foreman-rake-apipie:cache:index]: /usr/sbin/foreman-rake apipie:cache:index returned 1 instead of one of [0]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pxaa2katello01m0.z2.linux.argosretailgroup.com]: Failed to call refresh: Proxy pxaa2katello01m0.z2.linux.argosretailgroup.com cannot be registered (Could not load data from https://pxaa2katello01m0.z2.linux.argosretailgroup.com
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pxaa2katello01m0.z2.linux.argosretailgroup.com]: Proxy pxaa2katello01m0.z2.linux.argosretailgroup.com cannot be registered (Could not load data from https://pxaa2katello01m0.z2.linux.argosretailgroup.com
Installing Done [100%] [...........................................................................................................................................................................................]
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/katello-installer/katello-installer.log
Full log attached.
Have tried including PostgreSQL as a service port to the firewalld with no effect, have also tested the connection afterwards via the postgres account, which seems fine.
su - postgres
Last login: Wed May 25 14:01:46 BST 2016 on pts/0
-bash-4.2$ /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres
postgres=# \du;
gutterball | | {}
postgres | Superuser, Create role, Create DB, Replication | {}
postgres=#
Files
Updated by Dominic Cleal almost 9 years ago
- Project changed from Foreman to Katello
- Category deleted (
47)
Updated by Eric Helms almost 9 years ago
- Status changed from New to Need more information
- Translation missing: en.field_release set to 144
Anything custom about your environment prior to running installation? Did you configure any options during the installation process outside of the default setup?
Updated by David Arnold almost 9 years ago
Installation options taken were as follows, we're currently using polipo to provide the http proxy.
katello-installer -i --katello-proxy-url "http://localhost" \
--katello-proxy-port "8123" \
--foreman-admin-password "passw0rd" \
--capsule-dns true \
--capsule-dns-interface "ens32" \
--capsule-dns-zone "z2.linux.argosretailgroup.com" \
--capsule-dns-reverse "168.192.in-addr.arpa" \
--capsule-dhcp true \
--capsule-dhcp-interface "ens32" \
--capsule-dhcp-range "192.168.124.152 192.168.124.160" \
--capsule-dhcp-gateway "192.168.124.1" \
--capsule-dhcp-nameservers "192.168.124.141" \
--capsule-tftp true \
--capsule-tftp-servername $(hostname) \
--certs-country "UK" \
--certs-state "County" \ # Masked
--certs-city "City" \ # Masked
--certs-org "Company" \ # Masked
--certs-org-unit "Zone2"
Updated by David Arnold almost 9 years ago
Other than base install, SELinux set to permissive, ntp is setup and firewall configured as follows:-
firewall-cmd --list-all
public (default, active)
interfaces: ens32
sources:
services: dhcp dhcpv6-client dns http https ldap postgresql ssh tftp
ports: 9090/udp 5000/udp 7911/tcp 8140/tcp 9090/tcp 5647/tcp 8140/udp 5432/tcp 5647/udp 7911/udp 5432/udp 5000/tcp
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
Updated by Eric Helms almost 9 years ago
Could the proxy be interfering if not firewalld?
Updated by David Arnold almost 9 years ago
Following setup for getting Repos and RPMs:-
26. Download the four Repo RPM files required for installing Katello.
curl -OJL --socks4 127.0.0.1:8888 http://fedorapeople.org/groups/katello/releases/yum/2.4/katello/RHEL/7Server/x86_64/katello-repos-latest.rpm
curl -OJL --socks4 127.0.0.1:8888 http://yum.theforeman.org/releases/1.10/el7/x86_64/foreman-release.rpm
curl -OJL --socks4 127.0.0.1:8888 http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
curl -OJL --socks4 127.0.0.1:8888 http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
27. Yum install the four Repos
yum localinstall katello-repos-latest.rpm
yum localinstall foreman-release.rpm
yum localinstall puppetlabs-release-el-7.noarch.rpm
yum localinstall epel-release-latest-7.noarch.rpm
28. Yum install the Foreman Release package
yum install foreman-release-scl
29. Yum install the Katello packages….there are a few dependencies (circa 477) as well.
yum install katello
Updated by Eric Helms almost 9 years ago
That aspect appears fine, but it is having issues connecting to postgres? Anything unique or custom about your postgres? If not, then our assumption is something is interfering with the ability to talk to postgres locally.
Updated by David Arnold almost 9 years ago
No, we're not making any changes to postgres outside the installer. Looking at the log we came to the same assumption, so tested connection after the installer failed. Though we were assuming it was the postgres account that was used so our test may be invalid. Connectivity appears successful post installer failing.
su - postgres
Last login: Wed May 25 14:01:46 BST 2016 on pts/0
-bash-4.2$ /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres
postgres=# \du;
gutterball | | {}
postgres | Superuser, Create role, Create DB, Replication | {}
postgres=#
Updated by David Arnold almost 9 years ago
Looking in the postgres log, it's trying to connect using the 'foreman' role, which from the above output hasn't been created.
I've just checked and test server we built last week are the 'foreman' role is present in that postgres database.
Any ideas on what creates the 'foreman' role within the postgres DB?
Updated by David Arnold almost 9 years ago
This is looking more like an environmental problem, rather than a software issue.
We've managed to do two other test installs without issues.
Please close this issue down.
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release changed from 144 to 168
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release changed from 168 to 171
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release deleted (
171)
Updated by Justin Sherrill almost 9 years ago
- Status changed from Need more information to Closed
- Translation missing: en.field_release set to 166
Closed as per request