Project

General

Profile

Bug #8613

Missing documentation about InputTCPMaxSessions and when to change its value in rsyslog

Added by Nicolas CHARLES almost 2 years ago. Updated 4 months ago.

Status:
Released
Priority:
3
Category:
Documentation
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
18

Description

If there are plenty of nodes, the number of incoming reports from nodes may flood the rsyslog, resulting in "too many tcp sessions - dropping incoming request" messages in logs
we need to document when and how to configure this value, for differents number of nodes

Associated revisions

Revision 24764e8e (diff)
Added by Alexis MOUSSET 6 months ago

Fixes #8613: Missing documentation about InputTCPMaxSessions and when to change its value in rsyslog

History

#1 Updated by François ARMAND almost 2 years ago

  • Assignee set to Alexis MOUSSET
  • Priority changed from N/A to 3

#2 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#3 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.24 to 308

#4 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 308 to 3.1.14

#5 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.14 to 3.1.15

#6 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.15 to 3.1.16

#7 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.16 to 3.1.17

#8 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.17 to 3.1.18

#9 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#10 Updated by Benoît PECCATTE about 1 year ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority set to 5

#11 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.19 to 3.1.20

#12 Updated by Jonathan CLARKE about 1 year ago

  • Assignee deleted (Alexis MOUSSET)

#13 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#14 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#15 Updated by Benoît PECCATTE 12 months ago

  • Priority changed from 5 to 18

#16 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.22 to 3.1.23

#17 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.23 to 3.1.24

#18 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 3.1.24 to 3.1.25

#19 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 3.1.25 to 387

#20 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 387 to 4.1.10

#21 Updated by Alexis MOUSSET 6 months ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#22 Updated by Alexis MOUSSET 6 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/390

#23 Updated by Alexis MOUSSET 6 months ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE

#24 Updated by Alexis MOUSSET 6 months ago

  • Status changed from Pending technical review to Pending release

#25 Updated by Vincent MEMBRÉ 4 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Also available in: Atom PDF