Thread Summary: WiP
There's two issues here that have been co-mingled. They may or may not be related. Still trying to work that out.
Issue 1 - Running the GV Trunks update code on my Wazo install after upgrading from 17.13 to 17.14 broke my setup by causing the Asterisk service to fail to start.
Issue 1.1 - Found that issue 1 happens also on a fresh 17.14 install - all is well until I go through ./add-gvtrunk then Asterisk refuses to start. This leads me to believe that issue 1 was not unique to my install but something related to the GV trunk code.
[RESOLVED] Issue 2 - Getting a recursive view in the new admin add-ons view combined with a 500 server error. This occurs too on fresh virgin install. Can't say if it was happening on my old install pre-upgrade.
Issue discussed (and possibly solved) with Francois here: https://projects.wazo.community/boards/1/topics/11728?r=11767
-------------------------
Ok, looks like I screwed the pooch. After the fix above upgrade seems to have gone well. After, I inadvertently ran the second part (for when Asterisk version changes) and now Asterisk won't start.
How bad did I screw this up and can I/how do I get it back?
Output:
There's two issues here that have been co-mingled. They may or may not be related. Still trying to work that out.
Issue 1 - Running the GV Trunks update code on my Wazo install after upgrading from 17.13 to 17.14 broke my setup by causing the Asterisk service to fail to start.
Issue 1.1 - Found that issue 1 happens also on a fresh 17.14 install - all is well until I go through ./add-gvtrunk then Asterisk refuses to start. This leads me to believe that issue 1 was not unique to my install but something related to the GV trunk code.
I have successfully installed 17.09 and created trunks, installed 17.13 and created trunks, then upgraded that 17.13 to 17.14 and trunks kept working.
In contrast to my first upgrade from 17.13 to .14 where after the upgrade to .14 I ran teh xmpp update code and Asterisk refused to restart from there forward.
Another user reports same symptoms on a clean install of 17.14 whereby after install and running add-gvtrunk, Asterisk refuses to start.
In contrast to my first upgrade from 17.13 to .14 where after the upgrade to .14 I ran teh xmpp update code and Asterisk refused to restart from there forward.
Another user reports same symptoms on a clean install of 17.14 whereby after install and running add-gvtrunk, Asterisk refuses to start.
[RESOLVED] Issue 2 - Getting a recursive view in the new admin add-ons view combined with a 500 server error. This occurs too on fresh virgin install. Can't say if it was happening on my old install pre-upgrade.
Issue discussed (and possibly solved) with Francois here: https://projects.wazo.community/boards/1/topics/11728?r=11767
The IncrediblePBX script, after it runs and completes and presents you with the final screen of info (your knock.faq, etc.) requires another reboot and login to finish running scripts. IPBX does not prompt you to reboot nor does it indicate a reboot is needed anywhere however without it the new admin (and idk what else) is broken till then.
-------------------------
Ok, looks like I screwed the pooch. After the fix above upgrade seems to have gone well. After, I inadvertently ran the second part (for when Asterisk version changes) and now Asterisk won't start.
How bad did I screw this up and can I/how do I get it back?
Output:
2017-10-11 14:17:14 root@pbx:~# wazo-service restart all
Closing port 5060.
Waiting for services to stop successfully...
Waiting for services to start successfully...
starting rabbitmq-server ... OK
starting consul ... OK
starting [email protected] ... OK
starting nginx ... OK
starting mongooseim ... OK
starting dahdi ... OK
starting wazo-admin-ui ... OK
starting wazo-plugind ... OK
starting wazo-webhookd ... OK
starting xivo-sysconfd ... OK
starting xivo-confgend ... OK
starting xivo-confd ... OK
starting wazo-auth ... OK
starting xivo-dxtora ... OK
starting xivo-provd ... OK
starting xivo-agid ... OK
starting asterisk ...Job for asterisk.service failed. See 'systemctl status asterisk.service' and 'journalctl -xn' for details.
NOK
Opening port 5060.
Closing port 5060.
Waiting for services to stop successfully...
Waiting for services to start successfully...
starting rabbitmq-server ... OK
starting consul ... OK
starting [email protected] ... OK
starting nginx ... OK
starting mongooseim ... OK
starting dahdi ... OK
starting wazo-admin-ui ... OK
starting wazo-plugind ... OK
starting wazo-webhookd ... OK
starting xivo-sysconfd ... OK
starting xivo-confgend ... OK
starting xivo-confd ... OK
starting wazo-auth ... OK
starting xivo-dxtora ... OK
starting xivo-provd ... OK
starting xivo-agid ... OK
starting asterisk ...Job for asterisk.service failed. See 'systemctl status asterisk.service' and 'journalctl -xn' for details.
NOK
Opening port 5060.
2017-10-11 14:25:16 root@pbx:~# systemctl status asterisk
● asterisk.service - Asterisk PBX
Loaded: loaded (/lib/systemd/system/asterisk.service; enabled)
Active: failed (Result: resources) since Wed 2017-10-11 14:19:41 EDT; 8min ago
Process: 6430 ExecStartPost=/bin/bash -c for i in {1..10}; do /usr/sbin/asterisk -rx "core waitfullybooted" &>/dev/null && exit 0; sleep 1; done; exit 1 (code=exited, status=0/SUCCESS)
Process: 6408 ExecStart=/usr/sbin/asterisk -g -U asterisk (code=exited, status=0/SUCCESS)
Main PID: 6410 (code=exited, status=127)
Oct 11 14:19:36 pbx systemd[1]: Starting Asterisk PBX...
Oct 11 14:19:37 pbx systemd[1]: asterisk.service: main process exited, code=exited, status=127/n/a
Oct 11 14:19:37 pbx systemd[1]: PID 6410 read from file /var/run/asterisk/asterisk.pid does not exist or i...ombie.
Oct 11 14:19:41 pbx systemd[1]: asterisk.service never wrote its PID file. Failing.
Oct 11 14:19:41 pbx systemd[1]: Failed to start Asterisk PBX.
Oct 11 14:19:41 pbx systemd[1]: Unit asterisk.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
2017-10-11 14:28:33 root@pbx:~# journalctl -xn
-- Logs begin at Wed 2017-10-11 14:11:48 EDT, end at Wed 2017-10-11 14:28:35 EDT. --
Oct 11 14:26:46 pbx python3[6175]: 2017-10-11 14:26:46,957 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:26:46 pbx systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Oct 11 14:26:46 pbx systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 11 14:27:01 pbx CRON[10595]: (root) CMD (/root/ipchecker > /dev/null 2>&1)
Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session closed for user root
Oct 11 14:27:13 pbx python3[6175]: 2017-10-11 14:27:13,993 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:27:41 pbx python3[6175]: 2017-10-11 14:27:41,013 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:28:08 pbx python3[6175]: 2017-10-11 14:28:08,030 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:28:35 pbx python3[6175]: 2017-10-11 14:28:35,049 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
2017-10-11 14:29:21 root@pbx:~#
● asterisk.service - Asterisk PBX
Loaded: loaded (/lib/systemd/system/asterisk.service; enabled)
Active: failed (Result: resources) since Wed 2017-10-11 14:19:41 EDT; 8min ago
Process: 6430 ExecStartPost=/bin/bash -c for i in {1..10}; do /usr/sbin/asterisk -rx "core waitfullybooted" &>/dev/null && exit 0; sleep 1; done; exit 1 (code=exited, status=0/SUCCESS)
Process: 6408 ExecStart=/usr/sbin/asterisk -g -U asterisk (code=exited, status=0/SUCCESS)
Main PID: 6410 (code=exited, status=127)
Oct 11 14:19:36 pbx systemd[1]: Starting Asterisk PBX...
Oct 11 14:19:37 pbx systemd[1]: asterisk.service: main process exited, code=exited, status=127/n/a
Oct 11 14:19:37 pbx systemd[1]: PID 6410 read from file /var/run/asterisk/asterisk.pid does not exist or i...ombie.
Oct 11 14:19:41 pbx systemd[1]: asterisk.service never wrote its PID file. Failing.
Oct 11 14:19:41 pbx systemd[1]: Failed to start Asterisk PBX.
Oct 11 14:19:41 pbx systemd[1]: Unit asterisk.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
2017-10-11 14:28:33 root@pbx:~# journalctl -xn
-- Logs begin at Wed 2017-10-11 14:11:48 EDT, end at Wed 2017-10-11 14:28:35 EDT. --
Oct 11 14:26:46 pbx python3[6175]: 2017-10-11 14:26:46,957 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:26:46 pbx systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Oct 11 14:26:46 pbx systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 11 14:27:01 pbx CRON[10595]: (root) CMD (/root/ipchecker > /dev/null 2>&1)
Oct 11 14:27:01 pbx CRON[10594]: pam_unix(cron:session): session closed for user root
Oct 11 14:27:13 pbx python3[6175]: 2017-10-11 14:27:13,993 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:27:41 pbx python3[6175]: 2017-10-11 14:27:41,013 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:28:08 pbx python3[6175]: 2017-10-11 14:28:08,030 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
Oct 11 14:28:35 pbx python3[6175]: 2017-10-11 14:28:35,049 [6175] (INFO) (urllib3.connectionpool): Starting new HTT
2017-10-11 14:29:21 root@pbx:~#
Last edited: