Project

General

Profile

Actions
Copy link

Bug #5242

closed
CB CB

IPsec debug log settings not applied after stop/start or restart

Bug #5242: IPsec debug log settings not applied after stop/start or restart

Added by Chris Buechler almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
Chris Buechler
Category:
IPsec
Target version:
2.2.5
Start date:
10/02/2015
Due date:
% Done:

0%

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

Description

Debug log levels after a stop/start or restart rely on charondebug in ipsec.conf. But:
"Logger configurations in strongswan.conf have a higher priority than charondebug in ipsec.conf: If you define any loggers in strongswan.conf, charondebug does not have any effect at all."
https://wiki.strongswan.org/projects/strongswan/wiki/LoggerConfiguration

the debug log levels must be specified in strongswan.conf rather than as charondebug.

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #1

  • Status changed from Confirmed to Feedback

should be fixed, leaving for review.

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #2

  • Assignee set to Chris Buechler

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #3

this seems to be fine, works on 2.2.5 and 2.3 after reboot and a stop/start. Asked mgsmith to double check.

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #4

  • Status changed from Feedback to Confirmed

still has some duplication of logs, looks like auth levels need to be set to silent.

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #5

  • Status changed from Confirmed to Feedback

log duplication fixed

CB Updated by Chris Buechler almost 11 years ago Actions
Copy link
 #6

  • Status changed from Feedback to Resolved

fixed

Actions
Copy link

Also available in: Atom