Project

General

Profile

Actions
Copy link

Bug #9510

closed

Failed connexion to Postgres on a fresh Debian 7 install

Added by François ARMAND about 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System integration
Target version:
4.0.0
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On a fresh debian 7 install, I'm getting:

...
Caused by:
com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: FATAL: password authentication failed for user "rudder" 
>-at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:516)
>-at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:118)
>-at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:71)
>-at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.liftedTree1$1(RudderDatasourceProvider.scala:80)

Running:

root@server:/home/vagrant# rudder agent run
Rudder agent 4.0.0~rc2-wheezy0 (CFEngine Core 3.7.4)
Node uuid: root
Start execution with config [0]
...
E| repaired      server-roles              Check SQL credentials                        The Rudder PostgreSQL user account's password has been changed
..

And then:

root@server:/home/vagrant# /etc/init.d/rudder-jetty restart
Stopping Jetty: OK
Setting umask to 0007
Starting Jetty: . . . . . OK Mon Oct 24 13:40:25 UTC 2016

Solve the problem.

Actions
Copy link
 #1

Updated by François ARMAND about 8 years ago

Hum, in fact something went wrong during the installation:

2016-10-24 13:40:18] ERROR application - There is some required entries missing in the LDAP directory: ou=Pending Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Accepted Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Removed Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Rudder, cn=rudder-configuration (no error message)
[2016-10-24 13:40:18] ERROR net.liftweb.http.provider.HTTPProvider - Failed to Boot! Your application may not run properly
javax.servlet.UnavailableException: There is some required entries missing in the LDAP directory: ou=Pending Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Accepted Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Removed Inventories, ou=Inventories, cn=rudder-configuration (no error message) | ou=Inventories, cn=rudder-configuration (no error message) | ou=Rudder, cn=rudder-configuration (no error message)
Actions
Copy link
 #2

Updated by François ARMAND about 8 years ago

OK, so, this seems not OK

...
==> debian7_server: apache2: Syntax error on line 265 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/conf.d/ncf-api-virtualenv.conf: No such file or directory
...

...
==> debian7_server: Setting up rudder-agent (4.0.0~rc2-wheezy0) ...
==> debian7_server: ok: Rudder agent is now disabled.
==> debian7_server: rudder-agent[8665]: [ALERT] can't execute cf-serverd
==> debian7_server: error: service rudder-agent could not be stoped
...

...
==> debian7_server: Running rudder-init.sh...
==> debian7_server: ldap_add: No such object (32)
==> debian7_server: adding new entry "apiAccountId=a92b486d-379a-4e96-b2e8-b1ac6f7fd4a5,ou=API Accounts,ou=Rudder,cn=rudder-configuration" 
[[[END]]]
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 321 to 4.0.0~rc3

Same on debian 8 here.

postgres seems to repair by itself (rudder agent sets good value) but ldap still seems to be empty

Actions
Copy link
 #4

Updated by François ARMAND about 8 years ago

  • Target version changed from 4.0.0~rc3 to 321

So the problem is that /opt/rudder/bin/rudder-init.sh is not done.

If we exec that script by end, everything come back to normal.

Most likelly a bug with http://www.rudder-project.org/redmine/issues/9269 ?

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 321 to 4.0.0~rc3
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 4.0.0~rc3 to 4.0.0~rc4
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 4.0.0~rc4 to 4.0.0~rc5
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 4.0.0~rc5 to 4.0.0
Actions
Copy link
 #9

Updated by Nicolas CHARLES about 8 years ago

I have the same error messages in the rudder-jetty log, but this is expected.
Once a debian package is installed, it starts automatically, so jetty starts even before we get a chance to configure it, and then even before we get a chance to run rudder-init

Once it is run, it works as expected

Actions
Copy link
 #10

Updated by François ARMAND about 8 years ago

  • Status changed from New to Rejected

The problem was that everything was broken in debian in rc3 (package problem). It was corrected in more recent rcs.

Actions
Copy link

Also available in: Atom PDF