Bug #5242
IPsec debug log settings not applied after stop/start or restart
0%
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.
Associated revisions
Fix up strongswan logging levels. Remove charondebug since strongswan.conf settings take precedence. Set logging levels in strongswan.conf to match what's set on a running system via 'ipsec stroke loglevel', and remove log levels that were hard coded in strongswan.conf. Ticket #5242
only use daemon and not auth for strongswan logging. As it was, all logs were duplicated. Ticket #5242
only use daemon and not auth for strongswan logging. As it was, all logs were duplicated. Ticket #5242
Disable strongswan logging under auth since it's all logged under daemon,
so nothing is duplicated. Ticket #5242
Disable strongswan logging under auth since it's all logged under daemon,
so nothing is duplicated. Ticket #5242
History
#1
Updated by Chris Buechler over 4 years ago
Updated by - Status changed from Confirmed to Feedback
should be fixed, leaving for review.
#2
Updated by Chris Buechler over 4 years ago
- Assignee set to Chris Buechler
#3
Updated by Chris Buechler over 4 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.
#4
Updated by Chris Buechler over 4 years ago
- Status changed from Feedback to Confirmed
still has some duplication of logs, looks like auth levels need to be set to silent.
#5
Updated by Chris Buechler over 4 years ago
- Status changed from Confirmed to Feedback
log duplication fixed
Fix up strongswan logging levels. Remove charondebug since strongswan.conf settings take precedence. Set logging levels in strongswan.conf to match what's set on a running system via 'ipsec stroke loglevel', and remove log levels that were hard coded in strongswan.conf. Ticket #5242