Bug #3423: Rudder-agent does not configure syslog correctly on RHEL5 - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #3423

closed

Rudder-agent does not configure syslog correctly on RHEL5

Added by Dennis Cabooter over 11 years ago. Updated over 7 years ago.

Status:

Rejected

Priority:

Assignee:

Dennis Cabooter

Category:

System integration

Target version:

3.1.19

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Please add rsyslog as a dependency on RHEL/CentOS systems. At the moment I have to tell kickstart to install rsyslog, enable rsyslog at boot, disable syslog at boot, shutdown syslog and start rsyslog. In my opinion all this should be handled by the rudder-agent installation.

History
Notes
Property changes

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Project changed from Rudder to 34
Status changed from New to Discussion
Assignee set to Dennis Cabooter

Dennis, I agree that rudder-agent package should make all changes necessary itself.

However, rsyslog is not required for rudder-agent to function. It can use plain syslog or syslog-ng too. Why do you choose to install rsyslog? Are you having problems with the native syslog or do you prefer some functionality in rsyslog?

Actions

Copy link

Updated by Dennis Cabooter over 11 years ago

Without modifying anything on the Rudder server (in our case Ubuntu Precise), and without rsyslog on a Rudder RHEL/CentOS client, all reports will show "no answer". Ubuntu machines have rsyslog installed by default, so that's no problem. I think It's by far most easy to install rsyslog on a RHEL/CentOS client by default to resolve the issue.

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Project changed from 34 to Rudder
Status changed from Discussion to 8
Assignee changed from Dennis Cabooter to Matthieu CERDA
Priority changed from N/A to 2
Target version set to 2.3.12

So this might be a bug in our syslogd configuration maybe, it should normally work out of the box. I'll investigate.

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Status changed from 8 to Discussion
Assignee changed from Matthieu CERDA to Dennis Cabooter

Actually, I tried installing a vanilla CentOS 6.2, and rsyslog is bundled in. Installing rudder-agent on this machine at install time (with Cobbler) made it work out of the box.

Do you restrict the groups installed in your Kickstart templates ? (especially the Base group)

Actions

Copy link

Updated by Dennis Cabooter over 11 years ago

We use CentOS 5.x and we can't upgrade to 6.x for now.

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Target version changed from 2.3.12 to 2.3.13

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.3.13 to 84

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 84 to 2.4.7

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Target version changed from 2.4.7 to 2.4.8

Actions

Copy link

#10

Updated by François ARMAND about 11 years ago

Assignee changed from Dennis Cabooter to Matthieu CERDA

Actions

Copy link

#11

Updated by François ARMAND about 11 years ago

REasssigning to Matthieu as it was the last involved before Denis answered his question.

Actions

Copy link

#12

Updated by François ARMAND about 11 years ago

Status changed from Discussion to 8

Actions

Copy link

#13

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.8 to 2.4.9

Actions

Copy link

#14

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.9 to 2.4.10

Actions

Copy link

#15

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.10 to 2.4.11

Actions

Copy link

#16

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.11 to 2.4.12

Actions

Copy link

#17

Updated by Nicolas PERRON about 11 years ago

Target version changed from 2.4.12 to 2.4.13

Actions

Copy link

#18

Updated by Vincent MEMBRÉ almost 11 years ago

Target version changed from 2.4.13 to 2.6.11

Since 2.4 is not maintained anymore, retargeting to branch 2.6

Actions

Copy link

#19

Updated by Matthieu CERDA over 10 years ago

Subject changed from Add rsyslog on CentOS to Rudder-agent does not configure syslog correctly on RHEL5

Actions

Copy link

#20

Updated by Vincent MEMBRÉ over 10 years ago

Target version changed from 2.6.11 to 2.6.12

Actions

Copy link

#21

Updated by Vincent MEMBRÉ over 10 years ago

Target version changed from 2.6.12 to 2.6.13

Actions

Copy link

#22

Updated by Vincent MEMBRÉ over 10 years ago

Target version changed from 2.6.13 to 2.6.14

Actions

Copy link

#23

Updated by Jonathan CLARKE over 10 years ago

Target version changed from 2.6.14 to 2.6.16

Actions

Copy link

#24

Updated by Jonathan CLARKE over 10 years ago

Target version changed from 2.6.16 to 2.6.17

Actions

Copy link

#25

Updated by Nicolas PERRON over 10 years ago

Target version changed from 2.6.17 to 2.6.18

Actions

Copy link

#26

Updated by Matthieu CERDA about 10 years ago

Target version changed from 2.6.18 to 2.6.19

Actions

Copy link

#27

Updated by Vincent MEMBRÉ about 10 years ago

Target version changed from 2.6.19 to 2.6.20

Actions

Copy link

#28

Updated by François ARMAND almost 10 years ago

Category set to System integration
Assignee changed from Matthieu CERDA to Dennis Cabooter
Target version changed from 2.6.20 to 2.10.10

Wow, this one was stuck under a bunch of dust.

Denis, sorry to summon you on such an old ticket, but please, could you tell us:

- if you are still experiencing the problem ?
- if you remember what was the version of centos on which you saw it, so that we have better chance at replicating it ?

Thanks, and sorry again

Actions

Copy link

#29