You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a problem with the "respawn forever" feature of procd in relation with processes which dies right after they were started.
How to reproduce:
Create an openvpn config section like this
config openvpn 'test'
option enabled '1'
Of course, this is not sufficient for a working openvpn instance.
Start the openvpn instance
/etc/init.d/openvpn start test
Now you can see in syslog that the instance ist tried to be established in a infinite loop:
Wed Nov 28 10:25:29 2018 daemon.err openvpn(test)[13977]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf
Wed Nov 28 10:25:29 2018 daemon.warn openvpn(test)[13977]: Use --help for more information.
Wed Nov 28 10:25:34 2018 daemon.err openvpn(test)[14024]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf
Wed Nov 28 10:25:34 2018 daemon.warn openvpn(test)[14024]: Use --help for more information.
Wed Nov 28 10:25:39 2018 daemon.err openvpn(test)[14360]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf
Wed Nov 28 10:25:39 2018 daemon.warn openvpn(test)[14360]: Use --help for more information.
ubus call service list '{"name":"openvpn"}' shows this:
{
"openvpn": {
"instances": {
"test": {
"running": false,
"command": [
"\/usr\/sbin\/openvpn",
"--syslog",
"openvpn(test)",
"--status",
"\/var\/run\/openvpn.test.status",
"--cd",
"\/var\/etc",
"--config",
"openvpn-test.conf"
],
"term_timeout": 5,
"respawn": {
"threshold": 3600,
"timeout": 5,
"retry": -1
}
}
}
}
}
Now this instance can't be stopped anymore. I've tried doing all of the following
/etc/init.d/openvpn stop test /etc/init.d/openvpn stop ubus call service delete '{"name":"openvpn","instance":"test"}'
How can we get this instances killed?
The text was updated successfully, but these errors were encountered:
ms:
There is a problem with the "respawn forever" feature of procd in relation with processes which dies right after they were started.
How to reproduce:
config openvpn 'test' option enabled '1'
Of course, this is not sufficient for a working openvpn instance.
/etc/init.d/openvpn start test
Now you can see in syslog that the instance ist tried to be established in a infinite loop:
Wed Nov 28 10:25:29 2018 daemon.err openvpn(test)[13977]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf Wed Nov 28 10:25:29 2018 daemon.warn openvpn(test)[13977]: Use --help for more information. Wed Nov 28 10:25:34 2018 daemon.err openvpn(test)[14024]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf Wed Nov 28 10:25:34 2018 daemon.warn openvpn(test)[14024]: Use --help for more information. Wed Nov 28 10:25:39 2018 daemon.err openvpn(test)[14360]: Options error: In [CMD-LINE]:1: Error opening configuration file: openvpn-test.conf Wed Nov 28 10:25:39 2018 daemon.warn openvpn(test)[14360]: Use --help for more information.
ubus call service list '{"name":"openvpn"}'
shows this:{ "openvpn": { "instances": { "test": { "running": false, "command": [ "\/usr\/sbin\/openvpn", "--syslog", "openvpn(test)", "--status", "\/var\/run\/openvpn.test.status", "--cd", "\/var\/etc", "--config", "openvpn-test.conf" ], "term_timeout": 5, "respawn": { "threshold": 3600, "timeout": 5, "retry": -1 } } } } }
Now this instance can't be stopped anymore. I've tried doing all of the following/etc/init.d/openvpn stop test
/etc/init.d/openvpn stop
ubus call service delete '{"name":"openvpn","instance":"test"}'
How can we get this instances killed?
The text was updated successfully, but these errors were encountered: