Project

General

Profile

Actions
Copy link

Bug #16509

closed

On centos8 relay, service relayd is not started after installation

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

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Relay server or API
Target version:
6.0.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
To do
Regression:

Description

all seems ok, but journalctl says

Jan 09 10:37:32 relay rudder-relayd[15309]:  INFO relayd: Read configuration from "/opt/rudder/etc/relayd/" 
Jan 09 10:37:32 relay rudder-relayd[15309]:  ERROR rudder_relayd: I/O error: Permission denied (os error 13)

manually running /opt/rudder/bin/rudder-relayd seems to fix the permission, as all is good then

Subtasks 2 (0 open — 2 closed)

User story #16512: Set correct permissions on relayd configReleasedBenoît PECCATTEActions
Bug #16559: Rpm packages are missing some conffiles since /opt/rudder/etc is not included as filesReleasedAlexis MoussetActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 5 years ago

interestingly, first run fails because of OS, second one fails because of port

Jan 09 10:40:04 relay systemd[1]: Started Rudder Relay Daemon.
-- Subject: Unit rudder-relayd.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- 
-- Unit rudder-relayd.service has finished starting up.
-- 
-- The start-up result is RESULT.
Jan 09 10:40:04 relay cf-agent[16037]: CFEngine(agent) rudder Completed execution of '/bin/systemctl --no-ask-password start rudder-relayd.service'
Jan 09 10:40:04 relay cf-agent[16037]: CFEngine(agent) rudder R: [INFO] Executing start on rudder-relayd using the systemctl method
Jan 09 10:40:04 relay cf-agent[16037]: CFEngine(agent) rudder R: @@server-roles@@log_repaired@@server-roles@@server-roles-directive@@0@@Check relayd process@@rudder-relayd@@2020-01-09 10:40:>
Jan 09 10:40:04 relay rudder-relayd[16253]:  INFO relayd: Starting rudder-relayd 6.0.2
Jan 09 10:40:04 relay rudder-relayd[16253]:  INFO relayd: Read configuration from "/opt/rudder/etc/relayd/" 
Jan 09 10:40:04 relay rudder-relayd[16253]:  INFO relayd::data::node: Parsing nodes list from "/var/rudder/lib/relay/nodeslist.json" 
Jan 09 10:40:04 relay rudder-relayd[16253]:  INFO relayd::api: Starting API on 127.0.0.1:3030
Jan 09 10:40:04 relay rudder-relayd[16253]: thread 'tokio-runtime-worker-0' panicked at 'error binding to 127.0.0.1:3030: error creating server listener: Address already in use (os error 98)>
Jan 09 10:40:04 relay rudder-relayd[16253]: stack backtrace:
Jan 09 10:40:04 relay cf-agent[16037]: CFEngine(agent) rudder R: @@server-roles@@log_repaired@@server-roles@@server-roles-directive@@0@@Check relayd process@@rudder-relayd@@2020-01-09 10:40:>
Jan 09 10:40:05 relay cf-agent[16037]: CFEngine(agent) rudder R: @@server-roles@@log_repaired@@server-roles@@server-roles-directive@@0@@Check relayd process@@rudder-relayd@@2020-01-09 10:40:>
Jan 09 10:40:05 relay rudder-relayd[16253]:    0: backtrace::backtrace::libunwind::trace
Jan 09 10:40:05 relay rudder-relayd[16253]:              at ./cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/libunwind.rs:88
Jan 09 10:40:05 relay rudder-relayd[16253]:    1: backtrace::backtrace::trace_unsynchronized
Jan 09 10:40:05 relay rudder-relayd[16253]:              at ./cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.29/src/backtrace/mod.rs:66
Jan 09 10:40:05 relay rudder-relayd[16253]:    2: std::sys_common::backtrace::_print
Jan 09 10:40:05 relay rudder-relayd[16253]:              at src/libstd/sys_common/backtrace.rs:47
Jan 09 10:40:05 relay rudder-relayd[16253]:    3: std::sys_common::backtrace::print
Jan 09 10:40:05 relay rudder-relayd[16253]:              at src/libstd/sys_common/backtrace.rs:36
Jan 09 10:40:05 relay rudder-relayd[16253]:    4: std::panicking::default_hook::{{closure}}
Jan 09 10:40:05 relay rudder-relayd[16253]:              at src/libstd/panicking.rs:200

Actions
Copy link
 #2

Updated by Alexis Mousset almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #3

Updated by Alexis Mousset almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2182
Actions
Copy link
 #4

Updated by Alexis Mousset almost 5 years ago

  • Pull Request changed from https://github.com/Normation/rudder-packages/pull/2182 to https://github.com/Normation/rudder/pull/2708
Actions
Copy link
 #5

Updated by Alexis Mousset almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #6

Updated by Alexis Mousset almost 5 years ago

  • Name check changed from To do to Reviewed
Actions
Copy link
 #7

Updated by Alexis Mousset almost 5 years ago

  • Subject changed from on centos8 relay, service relayd is not started after installation to On centos8 relay, service relayd is not started after installation
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.3 which was released today.

Actions
Copy link

Also available in: Atom PDF