Project

General

Profile

Actions

Bug #13714

closed

Our rsyslog configuration uses deprecated syntax and must be updated

Added by Nicolas CHARLES over 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
42
Name check:
Fix check:
Regression:

Description

On "modern" syslog, rsyslog complains about deprecated entry.
It is highly possible that in the future our rsyslog config won't be supported anymore

Oct 23 18:42:55 server liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="403" x-info="http://www.rsyslog.com"] start
Oct 23 18:42:55 server liblogging-stdlog: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.24.0 try http://www.rsyslog.com/e/2307 ]
Oct 23 18:42:55 server liblogging-stdlog: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.24.0 try http://www.rsyslog.com/e/2307 ]
Oct 23 18:42:55 server liblogging-stdlog: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.24.0 try http://www.rsyslog.com/e/2307 ]
Oct 23 18:42:55 server liblogging-stdlog: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.24.0 try http://www.rsyslog.com/e/2307 ]
Actions #1

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.3.6 to 4.3.7
Actions #2

Updated by François ARMAND over 5 years ago

  • Subject changed from deprecation warning in rsyslog to our rsyslog configuration uses deprecated syntaxe and must be updated
  • Effort required set to Small

We need to check that the new syntax is available on all supported OS and update it.

Actions #3

Updated by Alexis Mousset over 5 years ago

  • Subject changed from our rsyslog configuration uses deprecated syntaxe and must be updated to Our rsyslog configuration uses deprecated syntax and must be updated
Actions #4

Updated by Alexis Mousset over 5 years ago

It seems not to be available in rsyslog 7.

Actions #6

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.3.7 to 4.3.8
Actions #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.3.8 to 4.3.9
Actions #8

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 4.3.9 to 4.3.10
Actions #9

Updated by François ARMAND over 5 years ago

  • Target version changed from 4.3.10 to 4.3.11
Actions #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.3.11 to 4.3.12
Actions #11

Updated by Benoît PECCATTE over 5 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 45
Actions #12

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.3.12 to 4.3.13
  • Priority changed from 45 to 44
Actions #13

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.3.13 to 4.3.14
Actions #14

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.3.14 to 587
  • Priority changed from 44 to 43
Actions #15

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 587 to 4.3.14
  • Priority changed from 43 to 42
Actions #16

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from New to Rejected

In 5.1 we will have a new protocol to use for reporting, not based on syslog, And i fear fixing warning in syslog configration will not be a priority and would cost us too much effort

Rejecting this issue

Actions

Also available in: Atom PDF