Actions
Bug #16517
closed
Rudder Jetty not starting on CentOS 8 after fresh install
Added by Samuel Chesnel almost 5 years ago. Updated almost 5 years ago.
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
94
Name check:
To do
Fix check:
To do
Regression:
Description
Hello,
I tried to make a fresh install of a CentOS 8 server on which i installed Rudder 6 with the script given on the installation page :
curl https://repository.rudder.io/tools/rudder-setup | bash -s setup-server 6.0
Just after that, the rudder-jetty service doesn't start. I tried to uninstall the server and reinstall it, on a CentOS7 server, the result is the same with Rudder 6 :
/opt/rudder/bin/rudder-jetty.sh start Setting umask to 0007 Starting Jetty: . . . . . . . . . . . . . . . FAILED Thu Jan 9 16:33:01 CET 2020
I have nothing in the logs except :
journalctl -xe Jan 09 17:01:51 cfg.itsense.cloud rudder-jetty.sh[14318]: Starting Jetty: . . . . . . . . . . . . . . . FAILED Thu Jan 9 17:01:51 CET 2020 Jan 09 17:01:51 cfg.itsense.cloud systemd[1]: rudder-jetty.service: Control process exited, code=exited status=1 Jan 09 17:01:51 cfg.itsense.cloud systemd[1]: rudder-jetty.service: Failed with result 'exit-code'. Jan 09 17:01:51 cfg.itsense.cloud systemd[1]: Failed to start Jetty Web Application Server. -- Subject: Unit rudder-jetty.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit rudder-jetty.service has failed. -- -- The result is RESULT. Jan 09 17:01:51 cfg.itsense.cloud cf-agent[14196]: CFEngine(agent) rudder Finished command related to promiser '/bin/systemctl --no-ask-password start rudder-jetty.service' -- an error occur> Jan 09 17:01:51 cfg.itsense.cloud cf-agent[14196]: CFEngine(agent) rudder Completed execution of '/bin/systemctl --no-ask-password start rudder-jetty.service' Jan 09 17:01:51 cfg.itsense.cloud cf-agent[14196]: CFEngine(agent) rudder R: [INFO] Executing start on rudder-jetty using the systemctl method
Do you have any idea ?
Thank you,
Pierre Renard.
Updated by François ARMAND almost 5 years ago
Hello,
We had several problems with 6.0.1 and we are in the process of releasing 6.0.2 to correct them. You can try that version with "ci/6.0.2" in place of "6.0" command you posted.
Nonetheless, we would be sure that you didn't hit one we didn't know. Is there anything in /var/log/rudder/webapp/2020_01_09.stderrout.log ?
Also, most problem were related to SELinux. Can you test "setenforce 0" ?
Updated by Samuel Chesnel almost 5 years ago
- Assignee changed from Nicolas CHARLES to François ARMAND
curl https://repository.rudder.io/tools/rudder-setup | bash -s setup-server ci/6.0.2
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 29260 100 29260 0 0 164k 0 --:--:-- --:--:-- --:--:-- 164k
Rudder 6.0.2 Repository 0.0 B/s | 0 B 00:30
Error: Failed to synchronize cache for repo 'Rudder'
You can find the logs attached to this message.
After your answer I tried setenforce 0 but it still doesn't work.
Thank you for your answer.
Updated by François ARMAND almost 5 years ago
OK, I'm looking for that. Do you have any errors in aformentionned log files ?
Updated by François ARMAND almost 5 years ago
The version should be: 6.0-nightly, sorry!
Updated by Samuel Chesnel almost 5 years ago
Sorry, apparently the logile didn't load .. I rebooted the server and now i got a huge log file. Anyway here it is :
2020-01-09 17:32:25.149:INFO:oejs.SetUIDListener:main: Setting umask=07
2020-01-09 17:32:25.153:INFO:oejs.Server:main: jetty-9.4.11.v20180605; built: 2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm 1.8.0_232-b09
2020-01-09 17:32:25.172:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:///opt/rudder/share/webapps/] at interval 1
2020-01-09 17:32:27.855:INFO:oejw.StandardDescriptorProcessor:main: NO JSP Support for /rudder, did not find org.eclipse.jetty.jsp.JettyJspServlet
Use configuration file defined by JVM property -Dlogback.configurationFile : /opt/rudder/etc/logback.xml
2020-01-09 17:32:28.406:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
2020-01-09 17:32:28.406:INFO:oejs.session:main: No SessionScavenger set, using defaults
2020-01-09 17:32:28.407:INFO:oejs.session:main: node0 Scavenging every 600000ms
[2020-01-09 17:32:28+0100] INFO application - Rudder starts with PID 22495 on 4 cores
[2020-01-09 17:32:29+0100] INFO application - Use configuration file defined by JVM property -Drudder.configFile : /opt/rudder/etc/rudder-web.properties
[2020-01-09 17:32:29+0100] INFO application - Global exception handler configured to stop Rudder on: java.lang.Error
[2020-01-09 17:32:29+0100] INFO application - Property 'rudder.batch.delete.software.interval' is missing or empty in rudder.configFile. Default to 24 hours.
[2020-01-09 17:32:29+0100] INFO application - Starting Rudder 6.0.1 web application [build timestamp: 2019-12-19T16:41:16Z]
[2020-01-09 17:32:30+0100] ERROR com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Exception during pool initialization.
org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:280)
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
at org.postgresql.Driver.makeConnection(Driver.java:458)
at org.postgresql.Driver.connect(Driver.java:260)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:353)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:473)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:562)
at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115)
at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.liftedTree1$1(RudderDatasourceProvider.scala:78)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.datasource$lzycompute(RudderDatasourceProvider.scala:76)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.datasource(RudderDatasourceProvider.scala:76)
at bootstrap.liftweb.RudderConfig$.doobie$lzycompute(RudderConfig.scala:1787)
at bootstrap.liftweb.RudderConfig$.doobie(RudderConfig.scala:1787)
at bootstrap.liftweb.RudderConfig$.logRepository$lzycompute(RudderConfig.scala:1240)
at bootstrap.liftweb.RudderConfig$.logRepository(RudderConfig.scala:1239)
at bootstrap.liftweb.RudderConfig$.woLdapRuleRepository$lzycompute(RudderConfig.scala:1499)
at bootstrap.liftweb.RudderConfig$.woLdapRuleRepository(RudderConfig.scala:1494)
at bootstrap.liftweb.RudderConfig$.<init>(RudderConfig.scala:511)
at bootstrap.liftweb.RudderConfig$.<clinit>(RudderConfig.scala)
at bootstrap.liftweb.LiftInitContextListener.contextInitialized(LiftInitContextListener.scala:127)
at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:953)
at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:558)
at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:918)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:370)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:848)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:505)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:151)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:453)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:579)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:240)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
at org.eclipse.jetty.server.Server.start(Server.java:419)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at org.eclipse.jetty.server.Server.doStart(Server.java:386)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1572)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1512)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:220)
at org.eclipse.jetty.start.Main.start(Main.java:486)
at org.eclipse.jetty.start.Main.main(Main.java:77)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at org.postgresql.core.PGStream.<init>(PGStream.java:75)
at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:91)
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:192)
... 67 common frames omitted
[2020-01-09 17:32:30+0100] ERROR com.normation.rudder.repository.jdbc.RudderDatasourceProvider - Could not initialise the access to the database
[2020-01-09T17:32:30.287+01:00] ERROR FATAL An error happen during Rudder boot. Rudder will stop now.
java.lang.ExceptionInInitializerError
at bootstrap.liftweb.LiftInitContextListener.contextInitialized(LiftInitContextListener.scala:127)
at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:953)
at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:558)
at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:918)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:370)
at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:848)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:192)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:505)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:151)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:453)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:610)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:529)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:392)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:579)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:240)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
at org.eclipse.jetty.server.Server.start(Server.java:419)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113)
at org.eclipse.jetty.server.Server.doStart(Server.java:386)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1572)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1512)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:220)
at org.eclipse.jetty.start.Main.start(Main.java:486)
at org.eclipse.jetty.start.Main.main(Main.java:77)
Caused by: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
at com.zaxxer.hikari.pool.HikariPool.throwPoolInitializationException(HikariPool.java:597)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:576)
at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115)
at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.liftedTree1$1(RudderDatasourceProvider.scala:78)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.datasource$lzycompute(RudderDatasourceProvider.scala:76)
at com.normation.rudder.repository.jdbc.RudderDatasourceProvider.datasource(RudderDatasourceProvider.scala:76)
at bootstrap.liftweb.RudderConfig$.doobie$lzycompute(RudderConfig.scala:1787)
at bootstrap.liftweb.RudderConfig$.doobie(RudderConfig.scala:1787)
at bootstrap.liftweb.RudderConfig$.logRepository$lzycompute(RudderConfig.scala:1240)
at bootstrap.liftweb.RudderConfig$.logRepository(RudderConfig.scala:1239)
at bootstrap.liftweb.RudderConfig$.woLdapRuleRepository$lzycompute(RudderConfig.scala:1499)
at bootstrap.liftweb.RudderConfig$.woLdapRuleRepository(RudderConfig.scala:1494)
at bootstrap.liftweb.RudderConfig$.<init>(RudderConfig.scala:511)
at bootstrap.liftweb.RudderConfig$.<clinit>(RudderConfig.scala)
... 45 more
Caused by: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:280)
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
at org.postgresql.Driver.makeConnection(Driver.java:458)
at org.postgresql.Driver.connect(Driver.java:260)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:353)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:201)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:473)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:562)
... 58 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at org.postgresql.core.PGStream.<init>(PGStream.java:75)
at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:91)
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:192)
... 67 more
Thank you, I'll try with nightly.
Updated by Samuel Chesnel almost 5 years ago
With nightly :
Rudder 6.0-nightly Repository 93 kB/s | 202 kB 00:02
Package rudder-server-root-1398866025:6.0.1.release-1.EL.8.noarch is already installed.
Error:
Problem: cannot install the best candidate for the job
- nothing provides rudder-webapp > 1398866025:6.0.3.rc1.git000000000000 needed by rudder-server-root-1398866025:6.0.3.rc1.git202001090225-1.EL.8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Updated by François ARMAND almost 5 years ago
Arf, sorry for the nightly one, we are in the middle of releasing, so nightly package are breaken right now...
For the other problem, it looks like https://issues.rudder.io/issues/16450 which is corrected in 6.0.2. Can you try rudder agent run and see if it correct it?
Updated by Samuel Chesnel almost 5 years ago
I think the problem is about postgresql which does not work well with rudder, but I don't know why :
service rudder-relayd status Redirecting to /bin/systemctl status rudder-relayd.service ● rudder-relayd.service - Rudder Relay Daemon Loaded: loaded (/usr/lib/systemd/system/rudder-relayd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2020-01-10 09:27:12 CET; 3min 33s ago Process: 32453 ExecStart=/opt/rudder/bin/rudder-relayd (code=exited, status=3) Main PID: 32453 (code=exited, status=3) Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: ERROR r2d2: FATAL: Ident authentication failed for user "rudder" Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: ERROR r2d2: FATAL: Ident authentication failed for user "rudder" Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: ERROR r2d2: FATAL: Ident authentication failed for user "rudder" Jan 10 09:27:07 cfg.itsense.cloud rudder-relayd[32453]: Jan 10 09:27:12 cfg.itsense.cloud rudder-relayd[32453]: ERROR rudder_relayd: database pool error: timed out waiting for connection: FATAL: Ident authentication failed for user "rudder" Jan 10 09:27:12 cfg.itsense.cloud systemd[1]: rudder-relayd.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED Jan 10 09:27:12 cfg.itsense.cloud systemd[1]: rudder-relayd.service: Failed with result 'exit-code'.
rudder agent run
Rudder agent 6.0.1.release
Node uuid: root
Start execution with config [0]
M| State Technique Component Key Message
E| compliant Common ncf Initialization Configuration library initialization was correct
E| compliant Common Security parameters The internal environment security is acceptable
E| compliant Common CRON Daemon Cron daemon status was correct
error: Finished command related to promiser '/opt/rudder/bin/run-inventory --local=/var/rudder/tmp/inventory/cfg-root.ocs' -- an error occurred, returned 2
E| error Inventory inventory Could not execute the inventory
error: Method 'fusionAgent' failed in some repairs
error: Method 'doInventory_always' failed in some repairs
error: Method 'doInventory' failed in some repairs
E| compliant server-roles Check logrotate configur| The logrotate configuration is correct
E| compliant server-roles Check relayd process relayd service running was correct
E| compliant server-roles Check relayd boot script relayd service enabled was correct
E| compliant server-roles Relayd service configura| rudder-relayd configration was correct
E| compliant server-roles Check postgresql process postgresql service running was correct
E| compliant server-roles Check postgresql boot sc| postgresql service enabled was correct
E| compliant server-roles Check LDAP in rudder-web| Web interface configuration files (checked LDAP password) was correct
E| compliant server-roles Check LDAP credentials OpenLDAP configuration file (rootdn password) was correct
E| compliant server-roles Check rudder-passwords.c| Presence and permissions of Rudder password file was correct
E| compliant server-roles Check pgpass file Presence and permissions of pgsql password file was correct
error: Finished command related to promiser '/usr/bin/psql --no-password -q -c "ALTER USER rudder WITH PASSWORD 'e08a357632b8c2d48211'"' -- an error occurred, returned 1
E| compliant server-roles Check SQL in rudder-weba| Web interface configuration files (SQL password) was correct
E| error server-roles Check SQL credentials PostgreSQL user account's password could not be repaired
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 properties Rudder WebDAV properties was correct
E| compliant server-roles Check WebDAV credentials Apache WebDAV user and password are OK
E| compliant server-roles Check apache process apache service running was correct
E| compliant server-roles Check apache boot script apache service enabled was correct
warning Common Check jetty process rudder-jetty Check if the service rudder-jetty is started could not be repaired
error: Finished command related to promiser '/bin/systemctl --no-ask-password start rudder-jetty.service' -- an error occurred, returned 1
error: Method 'ncf_services' failed in some repairs
warning Common Check jetty process rudder-jetty Run action start on service rudder-jetty could not be repaired
error: Method 'service_action' failed in some repairs
warning Common Check jetty process rudder-jetty Start service rudder-jetty could not be repaired
error: Method 'service_start' failed in some repairs
warning Common Check jetty process rudder-jetty Ensure that service rudder-jetty is running could not be repaired
error: Method 'service_started' failed in some repairs
E| error server-roles Check jetty process jetty service running could not be repaired
E| compliant server-roles Check jetty boot script jetty service enabled was correct
error: Method 'rudder_generic_service' failed in some repairs
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
error: Finished command related to promiser '/usr/bin/curl --proxy '' -s http://localhost:8080/rudder/api/techniqueLibrary/reload |/bin/grep -q OK' -- an error occurred, returned 1
warning server-roles Check Technique library | The Technique library failed to reload. Will try again next time.
error: Method 'root_technique_reload' failed in some repairs
error: Finished command related to promiser '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/rudder/api/status |/bin/grep -q OK' -- an error occurred, returned 1
error: Finished command related to promiser '/bin/systemctl --no-ask-password restart rudder-jetty.service' -- an error occurred, returned 1
error: Method 'ncf_services' failed in some repairs
warning Common Check rudder status rudder-jetty Run action restart on service rudder-jetty could not be repaired
error: Method 'service_action' failed in some repairs
warning Common Check rudder status rudder-jetty Restart service rudder_jetty if 'any' condition defined could not be repaired
error: Method 'service_restart_if' failed in some repairs
E| error Common Check rudder status rudder-jetty Restart service rudder-jetty could not be repaired
error: Method 'service_restart' failed in some repairs
E| error server-roles Check rudder status The http://localhost:8080/rudder/api/status web interface failed to respond for the second time. Restarting jetty NOW!
error: Method 'generic_alive_check' failed in some repairs
E| compliant server-roles Check slapd process slapd service running was correct
E| compliant server-roles Check slapd boot script slapd service enabled was correct
error: Method 'root_component_check' failed in some repairs
## Summary #####################################################################
29 components verified in 5 directives
=> 29 components in Enforce mode
-> 24 compliant
-> 5 error
Execution time: 128.70s
################################################################################
I guess there is some issue in a cfg file, but I don't know which.
Thank you for your support !
Updated by Alexis Mousset almost 5 years ago
The problem very is very likely the one we also have on CentOS 7.7. The problem is a bug in the rudder-reports postinst script that prevents it from initializing the database when it is installed before rudder-agent.
An easy workaround is to run yum reinstall rudder-reports after server installation.
Updated by Samuel Chesnel almost 5 years ago
Great ! I solved the problem by using these commands :
yum reinstall rudder-reports yum reinstall rudder-webapp
The first one solved the problems with the database and the second one solved the problems with jetty.
Thank you very much
Updated by Alexis Mousset almost 5 years ago
- Status changed from New to Rejected
Good! Closing as duplicate of #16519.
Updated by Alexis Mousset almost 5 years ago
- Is duplicate of Bug #16519: rudder reports installation fails on CentOS 7.7 because /var/log/rudder/install directory does not exist added
Actions