Project

General

Profile

Actions
Copy link

Bug #4436

closed

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

Added by Nicolas CHARLES about 10 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
1
Assignee:
Nicolas CHARLES
Category:
System integration
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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

Actions
Copy link
 #1

Updated by Dennis Cabooter about 10 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
 #2

Updated by Nicolas CHARLES about 10 years ago

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

Actions
Copy link
 #3

Updated by Nicolas PERRON about 10 years ago

  • Priority changed from N/A to 1

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
 #4

Updated by Nicolas CHARLES about 10 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
 #5

Updated by Nicolas PERRON about 10 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
 #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions
Copy link
 #9

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions
Copy link
 #10

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions
Copy link
 #11

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions
Copy link
 #12

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions
Copy link
 #14

Updated by François ARMAND about 9 years ago

  • Target version changed from 2.6.20 to 2.10.10
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #18

Updated by François ARMAND about 9 years ago

  • Category set to System integration
  • Assignee set to Nicolas CHARLES
  • Reproduced set to No

Nico, is this still the case ?

It doesn't seem so, but I can't confirm it.

Actions
Copy link
 #19

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #37

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #39

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #40

Updated by François ARMAND about 7 years ago

  • Status changed from New to Rejected
  • Priority set to 0

This is not the case anymore (at least since 3.1.x )

Actions
Copy link

Also available in: Atom PDF