Project

General

Profile

Actions

Bug #14750

closed

If postgresql is down, agent tried to fix password before checking that its up an running

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

If I stop postgresql, i get the following out from agent

E| compliant     server-roles              Check rudder-passwords.c|                    Rudder passwords file is present and secure
rudder     info: Executing 'no timeout,uid=26' ... '/usr/bin/psql --no-password -q -c "ALTER USER rudder WITH PASSWORD '74b3530a1bbc'"'
   error: Finished command related to promiser '/usr/bin/psql --no-password -q -c "ALTER USER rudder WITH PASSWORD '74b3530a1bbc'"' -- an error occurred, returned 2
  notice: Q: "...r/bin/psql --no": psql: could not connect to server: No such file or directory
Q: "...r/bin/psql --no":     Is the server running locally and accepting
Q: "...r/bin/psql --no":     connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
rudder     info: Last 3 quoted lines were generated by promiser '/usr/bin/psql --no-password -q -c "ALTER USER rudder WITH PASSWORD '74b3530a1bbc'"'
rudder     info: Completed execution of '/usr/bin/psql --no-password -q -c "ALTER USER rudder WITH PASSWORD '74b3530a1bbc'"'
E| compliant     server-roles              Check SQL in rudder-weba|                    Web interface configuration files are OK (checked SQL password)
E| error         server-roles              Check SQL credentials                        PostgreSQL user account's password could not be changed!
   error: Method 'root_password_check_psql' failed in some repairs
E| compliant     server-roles              Check allowed networks c|                    Allowed networks configuration is correct
E| compliant     server-roles              Check WebDAV credentials                     Apache WebDAV user and password are OK
R: [INFO] Executing is-active-process on httpd using the systemctl method
   info          server-roles              Check apache process      httpd              Check if the service httpd is started using ps was correct
   info          server-roles              Check apache process      httpd              Ensure that service httpd is running was correct
   info          server-roles              Check apache process      httpd              Ensure that service httpd is running was correct
E| compliant     server-roles              Check apache process                         Check apache process running was correct
R: [INFO] Executing is-enabled on httpd using the systemctl method
   info          server-roles              Check apache boot script  httpd              Check if service httpd is started at boot was correct
   info          server-roles              Check apache boot script  httpd              Ensure service httpd is started at boot was correct
   info          server-roles              Check apache boot script  httpd              Ensure service httpd is started at boot was correct
E| compliant     server-roles              Check apache boot script                     Check apache boot starting parameters was correct
R: [INFO] Executing is-active-process on .*java.*/opt/rudder/jetty/start.jar using the systemctl method
   info          server-roles              Check jetty process       .*java.*/opt/rudd| Check if the service .*java.*/opt/rudder/jetty/start.jar is started using ps was correct
   info          server-roles              Check jetty process       rudder-jetty       Ensure that service rudder-jetty is running was correct
   info          server-roles              Check jetty process       rudder-jetty       Ensure that service rudder-jetty is running was correct
E| compliant     server-roles              Check jetty process                          Check jetty process running was correct
   info          server-roles              Check jetty process       /var/rudder/cfeng| Symlink /var/rudder/cfengine-community/ppkeys/root-MD5=3bbcb07144f5cad97a558e0184a3079a.pub targeting /var/rudder/cfengine-community/ppkeys/localhost.pub was correct
   info          server-roles              Check jetty process       /var/rudder/cfeng| Symlink /var/rudder/cfengine-community/ppkeys/root-MD5=3bbcb07144f5cad97a558e0184a3079a.pub targeting /var/rudder/cfengine-community/ppkeys/localhost.pub was correct
   info          server-roles              Check jetty process       /var/rudder/cfeng| Symlink /var/rudder/cfengine-community/ppkeys/root-MD5=3bbcb07144f5cad97a558e0184a3079a.pub targeting /var/rudder/cfengine-community/ppkeys/localhost.pub (without overwrite) was correct
E| compliant     server-roles              Check configuration-repo|                    The /var/rudder/configuration-repository directory is present
E| compliant     server-roles              Check configuration-repo|                    The /var/rudder/configuration-repository git lock file is not present or not older than 5 minutes
rudder     info: Executing 'no timeout' ... '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/rudder/api/status |/bin/grep -q OK'
rudder     info: Automatically promoting context scope for 'site_ok' to namespace visibility, due to persistence
rudder     info: Completed execution of '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/rudder/api/status |/bin/grep -q OK'
E| compliant     server-roles              Check rudder status                          The http://localhost:8080/rudder/api/status web interface is running
rudder     info: Executing 'no timeout' ... '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/endpoint/api/status |/bin/grep -q OK'
rudder     info: Automatically promoting context scope for 'site_ok' to namespace visibility, due to persistence
rudder     info: Completed execution of '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/endpoint/api/status |/bin/grep -q OK'
E| compliant     server-roles              Check endpoint status                        The http://localhost:8080/endpoint/api/status web interface is running
R: [INFO] Executing is-active-process on /opt/rudder/libexec/slapd using the systemctl method
   info          server-roles              Check slapd process       /opt/rudder/libex| Check if the service /opt/rudder/libexec/slapd is started using ps was correct
   info          server-roles              Check slapd process       rudder-slapd       Ensure that service rudder-slapd is running was correct
   info          server-roles              Check slapd process       rudder-slapd       Ensure that service rudder-slapd is running was correct
E| compliant     server-roles              Check slapd process                          Check slapd process running was correct
E| compliant     server-roles              Check PostgreSQL configu|                    There is no need of specific PostgreSQL configuration on this system
R: [INFO] Executing is-active-process on postgres:.*writer using the systemctl method
   warning       server-roles              Check postgresql process  postgres:.*writer  Check if the service postgres:.*writer is started using ps could not be repaired
rudder     info: Executing 'no timeout' ... '/bin/systemctl --no-ask-password start postgresql-11.service'
rudder     info: Completed execution of '/bin/systemctl --no-ask-password start postgresql-11.service'
R: [INFO] Executing start on postgresql-11 using the systemctl method
   info          server-roles              Check postgresql process  postgresql-11      Run action start on service postgresql-11 was repaired
   info          server-roles              Check postgresql process  postgresql-11      Start service postgresql-11 was repaired
   info          server-roles              Check postgresql process  postgresql-11      Ensure that service postgresql-11 is running was repaired
   info          server-roles              Check postgresql process  postgresql-11      Ensure that service postgresql-11 is running was repaired
E| repaired      server-roles              Check postgresql process                     Check postgresql process running was repaired
R: [INFO] Executing is-enabled on postgresql-11 using the systemctl method
   info          server-roles              Check postgresql boot sc| postgresql-11      Check if service postgresql-11 is started at boot was correct
   info          server-roles              Check postgresql boot sc| postgresql-11      Ensure service postgresql-11 is started at boot was correct
   info          server-roles              Check postgresql boot sc| postgresql-11      Ensure service postgresql-11 is started at boot was correct
E| compliant     server-roles              Check postgresql boot sc|                    Check postgresql boot starting parameters was correct
   error: Method 'root_component_check' failed in some repairs

it should try to fix password after checking the component


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #15589: If slapd is down, the agent tries to restart rudder-jetty before rudder-slapdRejectedActions
Actions

Also available in: Atom PDF