Project

General

Profile

Actions
Copy link

Bug #4981

closed

Remote logging not active after reboot

Added by Lars Jorgensen over 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Logging
Target version:
-
Start date:
08/18/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.4
Affected Architecture:
amd64

Description

I have configured the remote syslog feature of pfSense. After a reboot it doesn't send logs to the remote syslog server until I go to Status -> System Logs -> Settings and click "save".

Actions
Copy link
 #1

Updated by Chris Buechler over 8 years ago

  • Status changed from New to Feedback

where is the server you're logging to, local, over VPN, or?

Actions
Copy link
 #2

Updated by Lars Jorgensen over 8 years ago

I'm logging to two servers. A regular syslog server and a Nagios Log server. They are both on the same subnet as the interface selected in "Source Address" under "Remote Logging Options".

I "Remote Syslog Contents" I have only selected "Firewall events".

Actions
Copy link
 #3

Updated by Lars Jorgensen over 7 years ago

Any news on this? Still an issue in the latest 2.3.1_p5 release. I'm also logging to a Nagios Log Server now, and both of them stop receiving anything after a reboot of pfSense. If I go into Status -> System Logs -> Settings and just click "save", loggin starts up again. It's a hasle, though, and I usually forget it.

Actions
Copy link
 #4

Updated by Jim Pingle over 4 years ago

  • Status changed from Feedback to Closed

As far as I'm aware this isn't currently an issue any longer.

Actions
Copy link

Also available in: Atom PDF