Project

General

Profile

Actions

Bug #10376

closed

Duplicate logs from charon

Added by Christian Ullrich about 4 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
03/26/2020
Due date:
% Done:

0%

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

Description

Intermittently the IPsec log receives every log line from charon twice, formatted slightly differently. The difference is that where there is a connection associated with the line, it appears in only one of the copies, while other lines are duplicated verbatim:

Mar 26 06:26:22 charon: 06[IKE] sending DPD request
Mar 26 06:26:22 charon: 06[IKE] <con6000|277> sending DPD request
Mar 26 06:26:32 charon: 10[IKE] sending DPD request
Mar 26 06:26:32 charon: 10[IKE] <con8000|279> sending DPD request
Mar 26 06:26:37 charon: 11[CFG] rereading secrets
Mar 26 06:26:37 charon: 11[CFG] rereading secrets
Mar 26 06:26:37 charon: 11[CFG] loading secrets from '/var/etc/ipsec/ipsec.secrets'
Mar 26 06:26:37 charon: 11[CFG] loading secrets from '/var/etc/ipsec/ipsec.secrets'
Mar 26 06:26:37 charon: 11[CFG]   loaded RSA private key from '/var/etc/ipsec/ipsec.d/private/cert-1.key'
Mar 26 06:26:37 charon: 11[CFG]   loaded RSA private key from '/var/etc/ipsec/ipsec.d/private/cert-1.key'
Mar 26 06:26:37 charon: 11[CFG]   loaded RSA private key from '/var/etc/ipsec/ipsec.d/private/cert-2.key'
Mar 26 06:26:37 charon: 11[CFG]   loaded RSA private key from '/var/etc/ipsec/ipsec.d/private/cert-2.key'

My log levels are currently set mostly to Audit, with a few on Control. This happens at the default levels, too.

I think it is sometimes possible to get the daemon out of this state by reloading it (apply changes). As you can see above, it did not work this time.

Actions #1

Updated by Christian Ullrich about 4 years ago

pfSense is 2.4.4-p3.

Actions #2

Updated by Jim Pingle about 4 years ago

  • Category set to IPsec
  • Status changed from New to Rejected

Fairly certain this has been solved on at least 2.5.0, if not also on 2.4.5. I used to see this regularly and haven't seen it anywhere in my lab in quite some time.

Actions #3

Updated by Christian Ullrich about 4 years ago

I don't know about 2.5.0, but I can assure you it is not fixed in 2.4.5.

Actions

Also available in: Atom PDF