From 531b1d0dddaa74a1b993ab589a3a7fa41494cbf1 Mon Sep 17 00:00:00 2001 From: A Holt Date: Wed, 4 Aug 2021 12:26:26 -0400 Subject: [PATCH 1/3] Asterisk fails to start reliably: can freepbx.service's fwconsole work?? --- roles/pbx/tasks/enable-or-disable.yml | 39 +++++++++++++++++---------- 1 file changed, 25 insertions(+), 14 deletions(-) diff --git a/roles/pbx/tasks/enable-or-disable.yml b/roles/pbx/tasks/enable-or-disable.yml index 53d83fd9f..638b06957 100644 --- a/roles/pbx/tasks/enable-or-disable.yml +++ b/roles/pbx/tasks/enable-or-disable.yml @@ -1,18 +1,29 @@ -- name: Enable & (Re)start 'asterisk' systemd service (if pbx_enabled) - systemd: - daemon_reload: yes - name: asterisk - enabled: yes - state: restarted - when: pbx_enabled +# 2021-08-04: This stanza commonly causes systemd error "Asterisk is already +# running. /etc/init.d/asterisk will exit now" (initial installs especially?) +# +# Also 'systemctl restart freepbx' all alone during initial install -- is +# likewise unreliable -- as confirmed on both Ubuntu 20.04 and Debian 11 :/ +# +# Yes /etc/systemd/system/freepbx.service is supposed to run 'fwconsole stop' +# then 'fwconsole start' reliably, as many web posts recommend, But No Dice :/ +# +# Do we need something like 'RestartSec=3' in freepbx.service ?? +# +#- name: Enable & (Re)start 'asterisk' systemd service (if pbx_enabled) +# systemd: +# daemon_reload: yes +# name: asterisk +# enabled: yes +# state: restarted +# when: pbx_enabled -- name: Disable & Stop 'asterisk' systemd service (if not pbx_enabled) - systemd: - daemon_reload: yes - name: asterisk - enabled: no - state: stopped - when: not pbx_enabled +#- name: Disable & Stop 'asterisk' systemd service (if not pbx_enabled) +# systemd: +# daemon_reload: yes +# name: asterisk +# enabled: no +# state: stopped +# when: not pbx_enabled - name: Enable & (Re)start 'freepbx' systemd service (if pbx_enabled) From f3626b4fde08d38ed6282d4541aa32709e429265 Mon Sep 17 00:00:00 2001 From: A Holt Date: Wed, 4 Aug 2021 12:28:02 -0400 Subject: [PATCH 2/3] Asterisk fails to start reliably: can 'RestartSec=3' in freepbx.service's fwconsole help?? --- roles/pbx/templates/freepbx.service.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/pbx/templates/freepbx.service.j2 b/roles/pbx/templates/freepbx.service.j2 index 50a23eea8..676abf88c 100644 --- a/roles/pbx/templates/freepbx.service.j2 +++ b/roles/pbx/templates/freepbx.service.j2 @@ -7,6 +7,7 @@ Type=oneshot RemainAfterExit=yes ExecStart=/usr/sbin/fwconsole start ExecStop=/usr/sbin/fwconsole stop +RestartSec=3 [Install] WantedBy=multi-user.target From 1c05a05b6426c3a5307a748a717bf3873e6519bf Mon Sep 17 00:00:00 2001 From: A Holt Date: Wed, 4 Aug 2021 12:36:53 -0400 Subject: [PATCH 3/3] pbx/tasks/enable-or-disable.yml: Asterisk starting snafu --- roles/pbx/tasks/enable-or-disable.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/pbx/tasks/enable-or-disable.yml b/roles/pbx/tasks/enable-or-disable.yml index 638b06957..e60921b59 100644 --- a/roles/pbx/tasks/enable-or-disable.yml +++ b/roles/pbx/tasks/enable-or-disable.yml @@ -1,11 +1,11 @@ -# 2021-08-04: This stanza commonly causes systemd error "Asterisk is already +# 2021-08-04: Stanza below commonly causes systemd error "Asterisk is already # running. /etc/init.d/asterisk will exit now" (initial installs especially?) # -# Also 'systemctl restart freepbx' all alone during initial install -- is -# likewise unreliable -- as confirmed on both Ubuntu 20.04 and Debian 11 :/ +# But without this stanza, 'systemctl restart freepbx' all alone during initial +# install ALSO fails to start Asterisk reliably, on Ubuntu 20.04 & Debian 11 :/ # # Yes /etc/systemd/system/freepbx.service is supposed to run 'fwconsole stop' -# then 'fwconsole start' reliably, as many web posts recommend, But No Dice :/ +# then 'fwconsole start' reliably, as many web posts recommend, But No Dice! # # Do we need something like 'RestartSec=3' in freepbx.service ?? #