Actions
Bug #11727
closed
Rudder installation fails on SLES12
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
109
Name check:
Fix check:
Regression:
Description
This is due the ldap service not being started properly:
(5/9) Installing: rudder-inventory-ldap-1398866025:4.1.8.release-1.SLES.12.x86_64 ......................................................................[done] Additional rpm output: INFO: Setting rudder-slapd as a boot service... Done INFO: Reloading syslogd... Done INFO: Restarting rudder-slapd...rudder-slapd is neither service nor target!? Done
Inside the rpm's scripts:
# Need to restart to take schema changes into account echo -n "INFO: Restarting rudder-slapd..." service rudder-slapd restart >/dev/null echo " Done"
Trying to execute that on SLES12 SP2:
# service rudder-slapd restart rudder-slapd is neither service nor target!?
Updated by Nicolas CHARLES about 7 years ago
I can confirm this issue:
( 1/35) Installing: ncf-1398866025:1.1.0.201710230115-1.SLES.12.noarch ................................................................................................[done]
( 2/35) Installing: rudder-agent-1398866025:4.1.8.release-1.SLES.12.x86_64 ............................................................................................[done]
Additional rpm output:
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.
If you want to list systemd services use 'systemctl list-unit-files'.
To see services enabled on particular target use
'systemctl list-dependencies [target]'.
rudder 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ok: Rudder agent is now disabled.
INFO: Ensuring correct permissions on the keys directory... Done.
INFO: Creating keys for CFEngine agent... Done.
ok: Rudder agent has been enabled but not started, wait for next cron run.
********************************************************************************
rudder-agent has been installed (not started). This host can be a Rudder node.
To get started, configure your Rudder server's hostname and launch the agent:
# echo 'rudder.server' > /var/rudder/cfengine-community/policy_server.dat
# rudder agent start
This node will then appear in the Rudder web interface under 'Accept new nodes'.
********************************************************************************
( 3/35) Installing: rudder-inventory-ldap-1398866025:4.1.8.release-1.SLES.12.x86_64 ...................................................................................[done]
Additional rpm output:
INFO: Setting rudder-slapd as a boot service... Done
INFO: Reloading syslogd... Done
INFO: Restarting rudder-slapd...rudder-slapd is neither service nor target!?
Done
( 4/35) Installing: rudder-techniques-1398866025:4.1.8.release-1.SLES.12.noarch .......................................................................................[done]
( 5/35) Installing: postgresql-init-9.4-17.8.1.noarch .................................................................................................................[done]
Additional rpm output:
Updating /etc/sysconfig/postgresql...
( 6/35) Installing: python-enum34-1.0-2.1.noarch ......................................................................................................................[done]
( 7/35) Installing: python-idna-2.0-1.1.noarch ........................................................................................................................[done]
( 8/35) Installing: python-ipaddress-1.0.14-1.1.noarch ................................................................................................................[done]
( 9/35) Installing: python-pyasn1-0.1.8-1.1.noarch ....................................................................................................................[done]
(10/35) Installing: python-pycparser-2.10-3.7.noarch ..................................................................................................................[done]
(11/35) Installing: python-six-1.9.0-9.7.1.noarch .....................................................................................................................[done]
(12/35) Installing: libapr1-1.5.1-2.7.x86_64 ..........................................................................................................................[done]
(13/35) Installing: liblua5_2-5.2.2-4.2.x86_64 ........................................................................................................................[done]
(14/35) Installing: libpq5-9.4.5-4.1.x86_64 ...........................................................................................................................[done]
(15/35) Installing: python-cffi-1.1.0-1.2.x86_64 ......................................................................................................................[done]
(16/35) Installing: libapr-util1-1.5.3-1.77.x86_64 ....................................................................................................................[done]
(17/35) Installing: lua-5.2.2-4.2.x86_64 ..............................................................................................................................[done]
Additional rpm output:
update-alternatives: using /usr/bin/lua5.2 to provide /usr/bin/lua (lua) in auto mode
(18/35) Installing: rsyslog-module-pgsql-8.4.0-8.3.x86_64 .............................................................................................................[done]
(19/35) Installing: postgresql94-9.4.5-4.5.x86_64 .....................................................................................................................[done]
(20/35) Installing: python-cryptography-1.0-2.7.x86_64 ................................................................................................................[done]
(21/35) Installing: apache2-utils-2.4.16-5.1.x86_64 ...................................................................................................................[done]
(22/35) Installing: javapackages-tools-2.0.1-6.10.x86_64 ..............................................................................................................[done]
(23/35) Installing: postgresql94-server-9.4.5-4.5.x86_64 ..............................................................................................................[done]
(24/35) Installing: python-pyOpenSSL-0.14-1.7.noarch ..................................................................................................................[done]
(25/35) Installing: apache2-2.4.16-5.1.x86_64 .........................................................................................................................[done]
Additional rpm output:
Updating /etc/sysconfig/apache2...
(26/35) Installing: java-1_8_0-openjdk-headless-1.8.0.65-1.13.x86_64 ..................................................................................................[done]
Additional rpm output:
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk/bin/java to provide /usr/bin/java (java) in auto mode
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk to provide /usr/lib64/jvm/jre-openjdk (jre_openjdk) in auto mode
update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk to provide /usr/lib64/jvm/jre-1.8.0 (jre_1.8.0) in auto mode
(27/35) Installing: apache2-prefork-2.4.16-5.1.x86_64 .................................................................................................................[done]
(28/35) Installing: rudder-reports-1398866025:4.1.8.release-1.SLES.12.noarch ..........................................................................................[done]
Additional rpm output:
* postgresql.service - LSB: Start the PostgreSQL master daemon
Loaded: loaded (/etc/init.d/postgresql; bad; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
INFO: Setting PostgreSQL as a boot service... Done
INFO: Waiting for PostgreSQL to be up... Done
INFO: Creating Rudder PostgreSQL user... Done
INFO: Creating Rudder PostgreSQL database... Done
(29/35) Installing: rudder-jetty-1398866025:4.1.8.release-1.SLES.12.noarch ............................................................................................[done]
Additional rpm output:
Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.
If you want to list systemd services use 'systemctl list-unit-files'.
To see services enabled on particular target use
'systemctl list-dependencies [target]'.
rudder-jetty 0:off 1:off 2:off 3:off 4:off 5:off 6:off
(30/35) Installing: apache2-mod_wsgi-4.5.2-59.1.x86_64 ................................................................................................................[done]
Additional rpm output:
warning: /var/cache/zypp/packages/Rudder/x86_64/apache2-mod_wsgi-4.5.2-59.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID bd6d129a: NOKEY
(31/35) Installing: rudder-inventory-endpoint-1398866025:4.1.8.release-1.SLES.12.noarch ...............................................................................[done]
Additional rpm output:
INFO: Launching script to check if a migration is needed
INFO: End of migration script
INFO: Restarting syslogd ... Done
(32/35) Installing: rudder-server-relay-1398866025:4.1.8.release-1.SLES.12.x86_64 .....................................................................................[done]
Additional rpm output:
INFO: Creating group rudder... Done
INFO: Creating the rudder user... Done
INFO: Setting Apache HTTPd as a boot service... Done
INFO: Stopping Apache HTTPd... Done
INFO: No usable SSL certificate detected for Rudder HTTP/S support, generating one automatically... Done
INFO: Starting Apache HTTPd...Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
INFO: rudder-server-relay setup complete.
*****************************************************************************************
INFO: Now run on your root server:
INFO: '/opt/rudder/bin/rudder-node-to-relay 30d3a3f7-a627-41e1-9b7d-384705029e40
INFO: Please look at the documentation for details (Section 'Relay servers')
*******************************************************************i*********************
(33/35) Installing: ncf-api-virtualenv-1398866025:4.1.8.release-1.SLES.12.noarch ......................................................................................[done]
Additional rpm output:
INFO: Creating the ncf-api-venv user... Done
warning: group ncf-api-venv does not exist - using root
INFO: Restarting Apache HTTPd... Done
(34/35) Installing: rudder-webapp-1398866025:4.1.8.release-1.SLES.12.noarch ...........................................................................................[done]
Additional rpm output:
rudder-jetty is neither service nor target!?
INFO: Setting Apache HTTPd as a boot service... Done
INFO: Restarting syslog... Done
INFO: Stopping Apache HTTPd... Done
INFO: Adding ncf-api-venv to the rudder group... Done
INFO: Starting Apache HTTPd... Done
Initialized empty shared Git repository in /var/rudder/configuration-repository/.git/
INFO: Launching script to check if a migration is needed
INFO: Checking if rudder-web.properties database access credentials are all right... LDAP OK, SQL OK
INFO: Checking if inventory-web.properties database access credentials are all right... LDAP OK, SQL skipped
INFO: Alternative source path added: /var/rudder/configuration-repository/ncf
INFO: Checking PostgreSQL service status... OK
INFO: Checking LDAP service status............ FAILED
LDAP service verification failed after 10 tries.
ERROR: The migration has failed in some steps. Check previous error messages.
Please restart the failed service(s), and start the migration script again.
(on a single Rudder server, try service rudder restart)
Once it is working, run:
# /opt/rudder/bin/rudder-upgrade
INFO: End of migration script
rudder-jetty is neither service nor target!?
warning: %post(rudder-webapp-1398866025:4.1.8.release-1.SLES.12.noarch) scriptlet failed, exit status 1
(35/35) Installing: rudder-server-root-1398866025:4.1.8.release-1.SLES.12.noarch ......................................................................................[done]
Additional rpm output:
5a0c16cb mdb_db_open: database "cn=rudder-configuration" cannot be opened: No such file or directory (2). Restore from backup!
5a0c16cb backend_startup_one (type=mdb, suffix="cn=rudder-configuration"): bi_db_open failed! (2)
slap_startup failed
************************************************************
Rudder is now installed but not configured.
Please run /opt/rudder/bin/rudder-init
************************************************************
Command systemctl list-unit-files does not contain rudder
Updated by Nicolas CHARLES about 7 years ago
Running systemctl daemon-reload solves the issue
Updated by Nicolas CHARLES about 7 years ago
- Assignee set to Benoît PECCATTE
- Target version set to 4.1.9
- Effort required set to Small
- Priority changed from 94 to 109
Updated by Benoît PECCATTE about 7 years ago
- Status changed from New to In progress
Updated by Benoît PECCATTE about 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1406
Updated by Benoît PECCATTE about 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|e10fa06b5ac19c5f19d9b707ae81c1d19019cf72.
Updated by Vincent MEMBRÉ about 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.9 and 4.2.3 which were released today.
- 4.1.9: Announce Changelog
- 4.2.3: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions