Open stumbaumr opened 3 months ago
restart executes this:
should be the same from the gui restart button if I'm not mistaken, could help you further analyse your problem.
It might make sense to open another ticket for the dropdown, it's more or less logical that it tries to stick to the dialog, but doesn't look very nice when the item is at the bottom of the form.
Found a work around...
Just doing the restart 3 minutes later again starts the service again...
Maybe that onestop
command does not wait till the service is completey stopped - so the -c ipsec
can not start it yet...
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
I use the System-> Settings-> Cron funktionality to restart the IPsec service everyday at 01:05 to empty the virtual pools. The restart just only stops the IPsec service - the start does not work and I end up with a stopped IPsec service and no VPN functionality.
Since I upgraded from 22.7.11 to 24.1.8 in one go (as soon as the new way of doing IPsec was usable to me) using opnsense-revert to identify at what point it broke is rather impossible. So I deleted the cron config and rebuilt it and it is still broken in 24.1.8.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Restart just restart and not stop and not start the IPsec service
Describe alternatives you considered
I turned that cron job off now and to a manual restart in the morning or evening with informing my users beforehand...
Screenshots
Relevant log files
Service being shutdown but not started again - then at 07:11 doing a manual start...
Additional context
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1.8-amd64 FreeBSD 13.2-RELEASE-p11 OpenSSL 3.0.13 Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz (8 cores, 16 threads)