Bug #4436: /var/log/syslog is polluted by all rudder logs of nodes - 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 #4436

closed

/var/log/syslog is polluted by all rudder logs of nodes

Added by Nicolas CHARLES almost 11 years ago. Updated over 7 years ago.

Status:

Rejected

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

System integration

Target version:

3.1.19

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

when we use rdder , /var/log/syslog get all lot lot of rudder logs, by all nodes.
we should not store reports of node in /var/log/syslog when they are store in the rudder log, because it makes difficut to backup/store the syslog messages, or to look at what is happening

History
Notes
Property changes

Actions

Copy link

Updated by Dennis Cabooter almost 11 years ago

Do you mean only on the server or also on the nodes? I would like to see Rudder logging to /var/log/rudder.log instead of /var/log/{syslog,messages} on nodes as well.

Actions

Copy link

Updated by Nicolas CHARLES almost 11 years ago

I meant primarly on server, but if the node is polluted as well, we should fixe this

Actions

Copy link

Updated by Nicolas PERRON almost 11 years ago

Priority changed from N/A to 1 (highest)

It would be VERY VERY great to remove all the logs of RUdder into /var/log/{syslog,messages} get from cf-agent and crontab.

These messages are really polluting the useful messages, especially when we have to search for an old information. All the useful messages are hidden by the lines of rudder and cf-serverd.
- fail of cf-promises
- execution of cron
- sometimes Rudder reports
- Reports about tcdb eror
- Error about cf-serverd on reading public key
- warning about ldap indexes (on server-side)

Actions

Copy link

Updated by Nicolas CHARLES almost 11 years ago

Nicolas

I'm not sure I understand your last part. What you would like is to have all the compliance log in a specific file, and keep everything else in the syslog file ?

Actions

Copy link

Updated by Nicolas PERRON almost 11 years ago

Nicolas CHARLES wrote:

Nicolas

I'm not sure I understand your last part. What you would like is to have all the compliance log in a specific file, and keep everything else in the syslog file ?

No, I was listing what are the messages we don't want to have in syslog. A specific file should be more suitable, even if they are all mixed, but not in the syslog file.

Actions

Copy link