Project

General

Profile

Actions
Copy link

Bug #16450

closed

Breaks remote logging and integration with centralized log management (Wazuh, Graylog, rsyslog, etc.). This was previously working in 2.7.x.

Added by Ernesto Naraloni 30 days ago. Updated 30 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
System Logs
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.9.x
Affected Architecture:

Description

Summary:
On pfSense CE 2.8.1, enabling remote logging via GUI (Status > System Logs > Settings) has no effect: no configuration file is created under /var/etc/syslog.d/, and syslogd is not restarted with the required parameters.

Steps to reproduce:
1. Go to Status > System Logs > Settings
2. Enable "Remote Logging"
3. Set a valid remote syslog IP and port (e.g. 192.168.90.195:514, UDP)
4. Save and Apply

Expected:
A file like /var/etc/syslog.d/remote.conf should be created and syslogd should be restarted with `-f /etc/syslog.conf`, which includes the syslog.d directory.

Actual:
- No file is created under /var/etc/syslog.d/
- syslogd runs with default arguments, does not include any remote target
- No log is sent to remote servers
- Even `logger` does not emit packets unless syslogd is manually restarted with `-f`

Actions
Copy link
 #1

Updated by Jim Pingle 30 days ago

  • Status changed from New to Rejected
  • Priority changed from High to Normal

I can't reproduce this as stated. It works fine here when enabled. It generates /var/etc/syslog.d/pfSense.conf and the server is receiving log messages.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum .

See Reporting Issues with pfSense Software for more information.

Actions
Copy link

Also available in: Atom PDF