Bug #16526
closedfatal issue rudder-server-root installation
Description
Installing : 1398866025:rudder-reports-6.0.2.release-1.EL.7.noarch 14/81
/opt/rudder/share/package-scripts/rudder-reports-postinst: line 8: /var/log/rudder/install/rudder-reports-20200112183754.log: No such file or directory
warning: %post(rudder-reports-1398866025:6.0.2.release-1.EL.7.noarch) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package 1398866025:rudder-reports-6.0.2.release-1.EL.7.noarch
Complete!
Server status check failed after 60 seconds...
after rebbot server : Rudder is currently loading, please wait
rudder agent check
FINISH: Rudder agent check ran properly, please look at messages above to see if there has been any error.
Rudder jetty failed to start.
systemctl start rudder-jetty.service
Job for rudder-jetty.service failed because the control process exited with error code. See "systemctl status rudder-jetty.service" and "journalctl xe" for details. Subject: Unit rudder-jetty.service has begun start-up
[root@rudder-omr system]# journalctl -xe
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: @server-roles
@result_na@server-roles
@server-roles-directive@0
@Send metrics to rudder-project@None
@2020-01-13 08:12:10+00:00##root@#Sen
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder Method 'run_server_roles_directive' failed in some repairs
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: @Inventory
@result_success@inventory-all
@inventory-all@0
@inventory@None
@2020-01-13 08:12:10+00:00##root@#Next inventory scheduled betwe
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: @Common
@result_na@hasPolicyServer-root
@common-root@0
@Monitoring@None
@2020-01-13 08:12:10+00:00##root@#No Rudder monitoring information
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: @Common
@control@rudder
@run@0
@end@20200112-185603-7e6e1f0c
@2020-01-13 08:12:10+00:00##root@#End execution
Jan 13 09:15:00 rudder-omr polkitd825: Registered Authentication Agent for unix-process:5856:3521515 (system bus name :1.632 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyK
Jan 13 09:15:00 rudder-omr systemd1: Starting Jetty Web Application Server...
-
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rudder-jetty.service has begun starting up.
Jan 13 09:15:00 rudder-omr rudder-jetty.sh5862: Setting umask to 0007
Jan 13 09:15:01 rudder-omr systemd1: Started Session 247 of user root.
-- Subject: Unit session-247.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-247.scope has finished starting up.
--
-- The start-up result is done.
Jan 13 09:15:01 rudder-omr systemd1: Started Session 248 of user root.
-- Subject: Unit session-248.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-248.scope has finished starting up.
--
-- The start-up result is done.
Jan 13 09:15:01 rudder-omr CROND5952: (root) CMD (/opt/rudder/bin/rudder agent check q >> /var/log/rudder/agent-check/check.log 2>&1) Subject: Unit rudder-jetty.service has failed
Jan 13 09:15:01 rudder-omr CROND5951: (root) CMD (/opt/rudder/bin/relay-cleanup >/dev/null)
Jan 13 09:15:36 rudder-omr su6248: (to postgres) root on none
Jan 13 09:15:36 rudder-omr su6248: pam_unix(su-l:session): session opened for user postgres by (uid=0)
Jan 13 09:15:36 rudder-omr su6248: pam_unix(su-l:session): session closed for user postgres
Jan 13 09:16:01 rudder-omr rudder-jetty.sh5862: Starting Jetty: . . . . . . . . . . . . . . . FAILED Mon Jan 13 09:16:01 CET 2020
Jan 13 09:16:01 rudder-omr systemd1: rudder-jetty.service: control process exited, code=exited status=1
Jan 13 09:16:01 rudder-omr systemd1: Failed to start Jetty Web Application Server.
-
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rudder-jetty.service has failed.
--
-- The result is failed.
Jan 13 09:16:01 rudder-omr systemd1: Unit rudder-jetty.service entered failed state.
Jan 13 09:16:01 rudder-omr systemd1: rudder-jetty.service failed.
Jan 13 09:16:01 rudder-omr polkitd825: Unregistered Authentication Agent for unix-process:5856:3521515 (system bus name :1.632, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Accepting connection
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Accepting connection
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Failed to canonicalise filename '/var/rudder/share/515c9687-d91b-4b3a-b169-ee2ff5516a3b/rules/cfengine-community/rudder_promi
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Failed to canonicalise filename '/var/rudder/share/515c9687-d91b-4b3a-b169-ee2ff5516a3b/rules/cfengine-community/rudder_promises_gen
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Failed to canonicalise filename '/var/rudder/tools/rudder_tools_updated' (realpath: No such file or directory)
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Failed to canonicalise filename '/var/rudder/tools/rudder_tools_updated' (realpath: No such file or directory)
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Closing connection, terminating thread
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Closing connection, terminating thread
Updated by pascal legrand almost 5 years ago
Installing : 1398866025:rudder-reports-6.0.2.release-1.EL.7.noarch 14/81
/opt/rudder/share/package-scripts/rudder-reports-postinst: line 8: /var/log/rudder/install/rudder-reports-20200112183754.log: No such file or directory
warning: %post(rudder-reports-1398866025:6.0.2.release-1.EL.7.noarch) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package 1398866025:rudder-reports-6.0.2.release-1.EL.7.noarch
Complete!
Server status check failed after 60 seconds...
after rebbot server : Rudder is currently loading, please wait
rudder agent check
FINISH: Rudder agent check ran properly, please look at messages above to see if there has been any error.
Rudder jetty failed to start.
systemctl start rudder-jetty.service
Job for rudder-jetty.service failed because the control process exited with error code. See "systemctl status rudder-jetty.service" and "journalctl xe" for details.
[root@rudder-omr system]# journalctl xe Subject: Unit rudder-jetty.service has begun start-up
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: server-roles@result_na@server-roles@server-roles-directive@0@Send metrics to rudder-project@None@2020-01-13 08:12:10+00:00##root
#Sen
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder Method 'run_server_roles_directive' failed in some repairs
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: Inventory@result_success@inventory-all@inventory-all@0@inventory@None@2020-01-13 08:12:10+00:00##root
#Next inventory scheduled betwe
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: Common@result_na@hasPolicyServer-root@common-root@0@Monitoring@None@2020-01-13 08:12:10+00:00##root
#No Rudder monitoring information
Jan 13 09:14:16 rudder-omr cf-agent4798: CFEngine(agent) rudder R: Common@control@rudder@run@0@end@20200112-185603-7e6e1f0c@2020-01-13 08:12:10+00:00##root
#End execution
Jan 13 09:15:00 rudder-omr polkitd825: Registered Authentication Agent for unix-process:5856:3521515 (system bus name :1.632 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyK
Jan 13 09:15:00 rudder-omr systemd1: Starting Jetty Web Application Server...
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rudder-jetty.service has begun starting up.
Jan 13 09:15:00 rudder-omr rudder-jetty.sh5862: Setting umask to 0007
Jan 13 09:15:01 rudder-omr systemd1: Started Session 247 of user root.
-- Subject: Unit session-247.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-247.scope has finished starting up.
--
-- The start-up result is done.
Jan 13 09:15:01 rudder-omr systemd1: Started Session 248 of user root.
-- Subject: Unit session-248.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-248.scope has finished starting up.
--
-- The start-up result is done.
Jan 13 09:15:01 rudder-omr CROND5952: (root) CMD (/opt/rudder/bin/rudder agent check q >> /var/log/rudder/agent-check/check.log 2>&1)
Jan 13 09:15:01 rudder-omr CROND5951: (root) CMD (/opt/rudder/bin/relay-cleanup >/dev/null)
Jan 13 09:15:36 rudder-omr su6248: (to postgres) root on none
Jan 13 09:15:36 rudder-omr su6248: pam_unix(su-l:session): session opened for user postgres by (uid=0)
Jan 13 09:15:36 rudder-omr su6248: pam_unix(su-l:session): session closed for user postgres
Jan 13 09:16:01 rudder-omr rudder-jetty.sh5862: Starting Jetty: . . . . . . . . . . . . . . . FAILED Mon Jan 13 09:16:01 CET 2020
Jan 13 09:16:01 rudder-omr systemd1: rudder-jetty.service: control process exited, code=exited status=1
Jan 13 09:16:01 rudder-omr systemd1: Failed to start Jetty Web Application Server.
- Subject: Unit rudder-jetty.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rudder-jetty.service has failed.
--
-- The result is failed.
Jan 13 09:16:01 rudder-omr systemd1: Unit rudder-jetty.service entered failed state.
Jan 13 09:16:01 rudder-omr systemd1: rudder-jetty.service failed.
Jan 13 09:16:01 rudder-omr polkitd825: Unregistered Authentication Agent for unix-process:5856:3521515 (system bus name :1.632, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Accepting connection
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Accepting connection
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Failed to canonicalise filename '/var/rudder/share/515c9687-d91b-4b3a-b169-ee2ff5516a3b/rules/cfengine-community/rudder_promi
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Failed to canonicalise filename '/var/rudder/share/515c9687-d91b-4b3a-b169-ee2ff5516a3b/rules/cfengine-community/rudder_promises_gen
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Failed to canonicalise filename '/var/rudder/tools/rudder_tools_updated' (realpath: No such file or directory)
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Failed to canonicalise filename '/var/rudder/tools/rudder_tools_updated' (realpath: No such file or directory)
Jan 13 09:16:19 rudder-omr cf-serverd1140: rudder info: 192.168.122.150> Closing connection, terminating thread
Jan 13 09:16:19 rudder-omr cf-serverd1140: CFEngine(server) rudder 192.168.122.150> Closing connection, terminating thread
cat /var/log/rudder/agent-check/check.log
psql: n'a pas pu se connecter au serveur : Aucun fichier ou dossier de ce type
Le serveur est-il actif localement et accepte-t-il les connexions sur la
socket Unix « /var/run/postgresql/.s.PGSQL.5432 » ?
root: FATAL: Cannot connect to PostgreSQL - please check its status
Rudder agent 6.0.2.release
Node uuid: root
Start execution with config [0]
info Rudder agent was run on a subset of policies - not all policies were checked
- Summary #####################################################################
1 components verified in 3 directives
=> 1 components in Enforce mode
-> 1 compliant
Execution time: 2.94s ################################################################################
psql: n'a pas pu se connecter au serveur : Aucun fichier ou dossier de ce type
Le serveur est-il actif localement et accepte-t-il les connexions sur la
socket Unix « /var/run/postgresql/.s.PGSQL.5432 » ?
root: FATAL: Cannot connect to PostgreSQL - please check its status
rudder-cf-serverd: enabled
rudder-cf-execd: enabled
rudder-cf-serverd: enabled
rudder-cf-execd: enabled
systemctl status postgresql.service
● postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2020-01-12 23:28:18 CET; 9h ago
Process: 1162 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p ${PGPORT} -w -t 300 (code=exited, status=0/SUCCESS)
Process: 1137 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=0/SUCCESS)
Main PID: 1305 (postgres)
CGroup: /system.slice/postgresql.service
├─1305 /usr/bin/postgres -D /var/lib/pgsql/data -p 5432
├─1633 postgres: logger process
├─1641 postgres: checkpointer process
├─1642 postgres: writer process
├─1643 postgres: wal writer process
├─1644 postgres: autovacuum launcher process
├─1645 postgres: stats collector process
├─6428 postgres: rudder rudder ::1(50836) idle
├─6449 postgres: rudder rudder ::1(50902) idle
├─7039 postgres: rudder rudder ::1(51040) idle
├─7428 postgres: rudder rudder ::1(51268) idle
├─7523 postgres: rudder rudder ::1(51334) idle
├─7777 postgres: rudder rudder ::1(51464) idle
├─7788 postgres: rudder rudder ::1(51534) idle
├─8855 postgres: rudder rudder ::1(51984) idle
├─9050 postgres: rudder rudder ::1(52114) idle
├─9093 postgres: rudder rudder ::1(52180) idle
└─9577 postgres: rudder rudder ::1(35574) idle
Jan 12 23:28:16 rudder-omr systemd1: Starting PostgreSQL database server...
Jan 12 23:28:18 rudder-omr systemd1: Started PostgreSQL database server.
Updated by Félix DALLIDET almost 5 years ago
Hi, chekc this ticket https://issues.rudder.io/issues/16519 seems like you should create the directory /var/log/rudder/install before reinstalling rudder-reports
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from New to Rejected
Hi Pascal, the workaround in to run
yum reinstall rudder-reports
If you haven't initialized the database by yourself, if you have done it, we will see the correct workaround
The issue is corrected in #16519, I'm rejecting this issue, but you can still use it to discuss your problem