[
https://issues.apache.org/jira/browse/VCL-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth reassigned VCL-1027:
-------------------------------
Assignee: Andy Kurth
Fix Version/s: 2.5
Description:
I have seen this occur on server requests when multiple users are added in a
short amount of time. The ext_sshd service is restarted every time a user is
added. There is some threshold in systemd that prevents this, causing the
service to stop and not restart without waiting for a few seconds.
This is the error:
{noformat}
[root@bn17-97 ~]# service ext_sshd restart
Redirecting to /bin/systemctl restart ext_sshd.service
[root@bn17-97 ~]# service ext_sshd restart
Redirecting to /bin/systemctl restart ext_sshd.service
[root@bn17-97 ~]# service ext_sshd restart
Redirecting to /bin/systemctl restart ext_sshd.service
[root@bn17-97 ~]# service ext_sshd restart
Redirecting to /bin/systemctl restart ext_sshd.service
[root@bn17-97 ~]# service ext_sshd restart
Redirecting to /bin/systemctl restart ext_sshd.service
Job for ext_sshd.service failed because start of the service was attempted too
often. See "systemctl status ext_sshd.service" and "journalctl -xe" for details.
To force a start use "systemctl reset-failed ext_sshd.service" followed by
"systemctl start ext_sshd.service" again.
{noformat}
When this occurs, users can't connect to the reservation. There is currently no
code that detects or corrects this.
Options could be added to the systemd service file created in
{{systemd.pm::add_ext_sshd_service}}. Two potential additions under the
\[Service\] section:
* Restart=on-failure
* RestartSec=3s
Summary: External SSH service under systemd fails to restart if
several restarts are rapidly attempted (was: SSH)
> External SSH service under systemd fails to restart if several restarts are
> rapidly attempted
> ---------------------------------------------------------------------------------------------
>
> Key: VCL-1027
> URL: https://issues.apache.org/jira/browse/VCL-1027
> Project: VCL
> Issue Type: Improvement
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> I have seen this occur on server requests when multiple users are added in a
> short amount of time. The ext_sshd service is restarted every time a user is
> added. There is some threshold in systemd that prevents this, causing the
> service to stop and not restart without waiting for a few seconds.
> This is the error:
> {noformat}
> [root@bn17-97 ~]# service ext_sshd restart
> Redirecting to /bin/systemctl restart ext_sshd.service
> [root@bn17-97 ~]# service ext_sshd restart
> Redirecting to /bin/systemctl restart ext_sshd.service
> [root@bn17-97 ~]# service ext_sshd restart
> Redirecting to /bin/systemctl restart ext_sshd.service
> [root@bn17-97 ~]# service ext_sshd restart
> Redirecting to /bin/systemctl restart ext_sshd.service
> [root@bn17-97 ~]# service ext_sshd restart
> Redirecting to /bin/systemctl restart ext_sshd.service
> Job for ext_sshd.service failed because start of the service was attempted
> too often. See "systemctl status ext_sshd.service" and "journalctl -xe" for
> details.
> To force a start use "systemctl reset-failed ext_sshd.service" followed by
> "systemctl start ext_sshd.service" again.
> {noformat}
> When this occurs, users can't connect to the reservation. There is currently
> no code that detects or corrects this.
> Options could be added to the systemd service file created in
> {{systemd.pm::add_ext_sshd_service}}. Two potential additions under the
> \[Service\] section:
> * Restart=on-failure
> * RestartSec=3s
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
