Project

General

Profile

Bug #10306

Incorrect IPsec service status

Added by Viktor Gurov 8 months ago. Updated 7 months ago.

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

100%

Estimated time:
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

Associated revisions

Revision 60e34dde (diff)
Added by Viktor Gurov 8 months ago

Incorrect IPsec service status. Issue #10306

History

#1 Updated by Viktor Gurov 8 months ago

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

#2 Updated by Jim Pingle 8 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#3 Updated by Renato Botelho 8 months 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!

#4 Updated by Viktor Gurov 7 months 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

Also available in: Atom PDF