Project

General

Profile

Actions
Copy link

Bug #14609

closed

When server syslog listen on another port than 514, it does not notify the agents with syslog

Added by Félix DALLIDET about 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
5.0.18
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

On an old ubuntu server, freshly upgraded in 5.0.9, the server still listen on 5514.
A newly accepted agent did not adapt its syslog conf to send the logs on the adequate port and was sending them on 514 instead.
It was on a Slackware, using syslog.

Actions
Copy link
 #1

Updated by Nicolas CHARLES about 5 years ago

it does work with rsyslog and syslog-ng
the issue is that syslogd dosn't support other port than 514

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #9

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #11

Updated by François ARMAND almost 4 years ago

  • Status changed from New to Resolved

I'm closing this one since it is resolved in 6.0 by not using syslog anymore and 5.0 is EOL.

Actions
Copy link

Also available in: Atom PDF