Actions
Bug #5242
closed
IPsec debug log settings not applied after stop/start or restart
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.
Updated by Chris Buechler about 9 years ago
- Status changed from Confirmed to Feedback
should be fixed, leaving for review.
Updated by Chris Buechler about 9 years ago
this seems to be fine, works on 2.2.5 and 2.3 after reboot and a stop/start. Asked mgsmith to double check.
Updated by Chris Buechler about 9 years ago
- Status changed from Feedback to Confirmed
still has some duplication of logs, looks like auth levels need to be set to silent.
Updated by Chris Buechler about 9 years ago
- Status changed from Confirmed to Feedback
log duplication fixed
Actions