From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Feedback on the branch openvpn-rebase
Date: Sun, 29 Jun 2025 13:35:04 +0200 [thread overview]
Message-ID: <04f4a94e-56a2-42fb-9d1d-913e829b5a8b@ipfire.org> (raw)
In-Reply-To: <a6a432dd-f7ef-47e0-b405-2d5aedb4b52d@ipfire.org>
Hi All,
Have found out why the openvpn-authenticator shows up as not running when being stopped. In the initscript stop section there is
openvon-authenticator
instead of
openvpn-authenticator
Regards,
Adolf
On 29/06/2025 12:51, Adolf Belka wrote:
> Hi All,
>
> Tested out the latest openvpn-rebase branch from @ms using the link to the iso that he provided from the latest fixes.
>
> The disable and enable checkbox now works. If you enable the checkbox and save then the box is enabled and if you then disable and save it the checkbox now is disabled so that previous issue is fixed.
>
>
> Unfortunately the start and stop issue is still present.
>
> When I start the system running with the openvpn server running and then I disable the server then it shows the server as stopped.
>
> If I then enable the server and save then the checkbox is enabled but the server stays stopped.
>
> On the command line the status shows
>
> /usr/sbin/openvpn is not running but /var/run/openvpn-rw.pid exists.
>
> So the server stopped but the pid was not removed.
>
> If I boot the system and the server was checked as enabled then everything starts properly.
>
> The boot screen shows
>
> Starting OpenVPN Roadwarrior Server... OK
> Starting OpenVPN Authenticator... OK
> Starting OpenVPN N2N connection 'ipfirenet2net'... OK
>
> then if I straight away reboot the shutdown screen shows
>
>
> Stopping OpenVPN Authenticator... Not running WARN
> Stopping OpenVPN Roadwarrior Server... FAIL
> Stopping OpenVPN N2N connection 'ipfirenet2net'... OK
>
>
> The N2N connection starts and stops correctly and the pid is removed.
>
> I believe that this might be due to the variable PIDFILE being used for both the authenticator and the rw daemons and when the openvpn-rw daemon is being shutdown it has the authenticator pid in the PIDFILE variable and not the openvpn-rw.pid file name.
>
> I have tried various ways to change this in the openvpn-rw initscript but I ended up fixing it for one thing but then creating a problem for another one. Basically I think because I don't understand how the whole initscript and pid process is running in IPFire.
>
> Regards,
> Adolf.
next prev parent reply other threads:[~2025-06-29 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 10:51 Adolf Belka
2025-06-29 11:35 ` Adolf Belka [this message]
2025-06-30 8:47 ` Michael Tremer
2025-06-30 8:40 ` Michael Tremer
2025-06-30 8:46 ` Michael Tremer
2025-06-30 9:55 ` Adolf Belka
2025-06-30 10:04 ` Michael Tremer
2025-06-30 10:13 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04f4a94e-56a2-42fb-9d1d-913e829b5a8b@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox