Project

General

Profile

Actions

Bug #8613

closed

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

Added by Nicolas CHARLES almost 5 years ago. Updated about 3 years ago.

Status:
Released
Priority:
3
Category:
Documentation
Target version:
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

Actions #1

Updated by François ARMAND almost 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.24 to 308
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 308 to 3.1.14
Actions #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #9

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #10

Updated by Benoît PECCATTE about 4 years ago

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

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #12

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Alexis MOUSSET)
Actions #13

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #14

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #15

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 5 to 18
Actions #16

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.25 to 387
Actions #20

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
Actions #21

Updated by Alexis MOUSSET over 3 years ago

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

Updated by Alexis MOUSSET over 3 years 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
Actions #23

Updated by Alexis MOUSSET over 3 years ago

  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
Actions #24

Updated by Alexis MOUSSET over 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #25

Updated by Vincent MEMBRÉ about 3 years 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.

Actions

Also available in: Atom PDF