Project

General

Profile

Actions
Copy link

Bug #10306

closed

Incorrect IPsec service status

Added by Viktor Gurov about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
IPsec
Target version:
2.5.0
Start date:
02/29/2020
Due date:
% Done:

100%

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

Description

If you do some changes on the IPsec Mobile or IPsec Advanced tab and press apply,
Strongswan daemon restarted, but you can see 'start service' button in top right corner
although the service is actually running

It seems that get_service_status() tries to check charon daemon status by is_pid_running() with using outdated charon.pid file

Actions
Copy link
 #1

Updated by Viktor Gurov about 4 years ago

This PR adds extra charon process checking:
https://github.com/pfsense/pfsense/pull/4215

Actions
Copy link
 #2

Updated by Jim Pingle about 4 years ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0
Actions
Copy link
 #3

Updated by Renato Botelho about 4 years ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

Actions
Copy link
 #4

Updated by Viktor Gurov about 4 years ago

  • Status changed from Feedback to Resolved

Renato Botelho wrote:

PR has been merged. Thanks!

works as expected on 2.5.0.a.20200331.2303

Actions
Copy link

Also available in: Atom PDF