TUTORIAL Incredible Wazo Upgrade to 17.17

Discussion in 'PIAF 3 Add-Ons' started by wardmundy, Aug 15, 2016.

  1. hawk#1

    hawk#1 Member

    Joined:
    Nov 3, 2015
    Messages:
    40
    Likes Received:
    15
    @wardmundy,

    I know you are a busy person, can you give us any idea when we should check back on Incredible PBX for Wazo?
     
  2. wardmundy

    wardmundy Nerd Uno

    Joined:
    Oct 12, 2007
    Messages:
    14,172
    Likes Received:
    2,391
    @Sylvain Boily has acknowledged there is a problem with Debian 9 "improvements" and Wazo 18.03. Once the Wazo team has addressed the issues and reports back, we'll give it another go. In the meantime, you can install Incredible PBX for Wazo 17.17 and go through the upgrade procedure to get to 18.03. Latest and greatest isn't always the best solution.
     
    hawk#1 likes this.
  3. hawk#1

    hawk#1 Member

    Joined:
    Nov 3, 2015
    Messages:
    40
    Likes Received:
    15
    I still need to decide if I'm going to run it on a local system or run it on a cloud.
     
  4. ZachG

    ZachG New Member

    Joined:
    Jan 7, 2015
    Messages:
    14
    Likes Received:
    3
  5. Jack Miller

    Jack Miller Member

    Joined:
    Jun 16, 2016
    Messages:
    33
    Likes Received:
    6
    We've been happy with the cheapest option on OVH. We ran on Linode for a while, but that was problematic. Upgrade to 18.03 went perfectly.
     
    wardmundy likes this.
  6. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    56
    Likes Received:
    3
    This has worked well for me so far too.

    The only "problem" I'm seeing after 6 months is the lack of a decent backup option for VPS SSD. Gotta move to VPS Cloud to get first decent backup option so about $15/mo ($8.xx/mo USD for the VPS and about $6.xx/mo for backups pkg)

    A bit much for my meager needs (compared to the less than $5/mo paying now) but still relatively cheap. Question I'm scared to ask so far is what's the migration path like from vps-ssd to vps-cloud...
    I don't expect the answer will be "oh just click here".. lol

    Will need to see a clear weekend and couple day afterbefore I can dive into that pool...

    What are you doing for backups?
     
  7. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    56
    Likes Received:
    3
    Hey Ward,
    I think these instructions should be incorporated somehow into (or at least referenced in) post #47.

    For example I'm upgrading from 17.14 to 17.17. Without reading through the thread, I would have missed these important steps for GV.

    EDIT -
    btw the file name in /etc/asterisk is xmpp_oauth.conf (note the xmpp part is first). At least that's how it is on my system.



     
    #147 JFrost, Mar 30, 2018
    Last edited: Mar 30, 2018
  8. Jack Miller

    Jack Miller Member

    Joined:
    Jun 16, 2016
    Messages:
    33
    Likes Received:
    6
    Manual, scripted backups to S3. Not nearly as easy as paying for them.
     
  9. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    56
    Likes Received:
    3
    Any chance you're willing to share?

    (could've used it last night :rolleyes:. Upgraded 17.14 -> 17.17 and not all is well yet...)
     
  10. JFrost

    JFrost Member

    Joined:
    Oct 1, 2016
    Messages:
    56
    Likes Received:
    3
    Ok. I'm getting nowhere. Upgraded 17.14 -> 17.17 per post #47. After `wazo-upgrade` step, Asterisk won't start with an error that "asterisk.service never wrote it's PID file. Failing"
    I think I have exhausted my google-fu.
    Need some help pls. Output below.
    Ty.


    Code:
    2018-03-30 14:04:22 vps120849:~# journalctl -xn
    -- Logs begin at Fri 2018-03-30 13:55:37 EDT, end at Fri 2018-03-30 14:04:20 EDT. --
    Mar 30 14:02:04 vps120849 systemd[1]: asterisk.service never wrote its PID file. Failing.
    Mar 30 14:02:04 vps120849 systemd[1]: Failed to start Asterisk PBX.
    -- Subject: Unit asterisk.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit asterisk.service has failed.
    --
    -- The result is failed.
    Mar 30 14:02:04 vps120849 systemd[1]: Unit asterisk.service entered failed state.
    Mar 30 14:02:05 vps120849 python3[634]: 2018-03-30 14:02:05,840 [634] (INFO) (urllib3.connectionpool): Star
    Mar 30 14:02:32 vps120849 python3[634]: 2018-03-30 14:02:32,852 [634] (INFO) (urllib3.connectionpool): Star
    Mar 30 14:02:59 vps120849 python3[634]: 2018-03-30 14:02:59,869 [634] (INFO) (urllib3.connectionpool): Star
    Mar 30 14:03:25 vps120849 monit[2564]: 'asterisk' failed to start (exit status 1) -- /usr/bin/wazo-service:
    Mar 30 14:03:26 vps120849 python3[634]: 2018-03-30 14:03:26,880 [634] (INFO) (urllib3.connectionpool): Star
    Mar 30 14:03:53 vps120849 python3[634]: 2018-03-30 14:03:53,891 [634] (INFO) (urllib3.connectionpool): Star
    Mar 30 14:04:20 vps120849 python3[634]: 2018-03-30 14:04:20,903 [634] (INFO) (urllib3.connectionpool): Star
    lines 1-18/18 (END)...skipping...
    -- Logs begin at Fri 2018-03-30 13:55:37 EDT, end at Fri 2018-03-30 14:04:20 EDT. --
    Mar 30 14:02:04 vps120849 systemd[1]: asterisk.service never wrote its PID file. Failing.
    Mar 30 14:02:04 vps120849 systemd[1]: Failed to start Asterisk PBX.
    -- Subject: Unit asterisk.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit asterisk.service has failed.
    --
    -- The result is failed.
    Mar 30 14:02:04 vps120849 systemd[1]: Unit asterisk.service entered failed state.
    Mar 30 14:02:05 vps120849 python3[634]: 2018-03-30 14:02:05,840 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    Mar 30 14:02:32 vps120849 python3[634]: 2018-03-30 14:02:32,852 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    Mar 30 14:02:59 vps120849 python3[634]: 2018-03-30 14:02:59,869 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    Mar 30 14:03:25 vps120849 monit[2564]: 'asterisk' failed to start (exit status 1) -- /usr/bin/wazo-service: Job for asterisk.service failed. See 'systemctl status asterisk.service' and 'journalctl -xn' for details.
    Mar 30 14:03:26 vps120849 python3[634]: 2018-03-30 14:03:26,880 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    Mar 30 14:03:53 vps120849 python3[634]: 2018-03-30 14:03:53,891 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    Mar 30 14:04:20 vps120849 python3[634]: 2018-03-30 14:04:20,903 [634] (INFO) (urllib3.connectionpool): Starting new HTTPS connection (1): localhost
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    ~
    and
    Code:
    2018-03-30 14:04:57 vps120849:~# systemctl status asterisk.service
    ● asterisk.service - Asterisk PBX
       Loaded: loaded (/lib/systemd/system/asterisk.service; enabled)
       Active: failed (Result: core-dump) since Fri 2018-03-30 14:10:18 EDT; 2min 9s ago
      Process: 8720 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: 8695 ExecStart=/usr/sbin/asterisk -g -U asterisk (code=exited, status=0/SUCCESS)
     Main PID: 8700 (code=dumped, signal=SEGV)
    
    Mar 30 14:10:18 vps120849 systemd[1]: Started Asterisk PBX.
    Mar 30 14:10:18 vps120849 systemd[1]: asterisk.service: main process exited, code=dumped, status=11/SEGV
    Mar 30 14:10:18 vps120849 systemd[1]: Unit asterisk.service entered failed state.
    2018-03-30 14:12:27 vps120849:~#
    

    EDIT-

    So still struggling with this. Asterisk console shows crashing with 'segmentation fault' and it appears to be shortly after parsing modules.conf. Don't know enough about modules to start including/removing stuff so could really use some help here. Per some other posts I've checked for res_xmpp.so ans res_xmpp_oauth.so and both are prefixed with noload => already.
    Posted this also at Wazo forums so will update outputs there.

    Have no phones at all now and GV fallback isn't even working quite right so dead in the water. Please help.

    https://projects.wazo.community/boards/1/topics/13224
     
    #150 JFrost, Mar 30, 2018
    Last edited: Mar 31, 2018
  11. Sylvain Boily

    Sylvain Boily Active Member

    Joined:
    Apr 30, 2016
    Messages:
    258
    Likes Received:
    143
    Hello,

    I just want to clarify something about incrediblepbx and professional support my company is offering, because it seems it's not clear for all. Wazo Inc (my company) don't offer business support. For us, incrediblepbx is an open source project on the top of wazo. We are happy to help people in the community if it possible, but we don't offer any commercial support. We don't develop any plugins Ward has created, so it's not possible for us to have commercial support for this distribution. This is exactly the same for the raspivo distribution, created by Iris Network.

    Sylvain
     
  12. Ramsey F

    Ramsey F New Member

    Joined:
    Feb 11, 2017
    Messages:
    24
    Likes Received:
    5
    I can successfully install and run Wazo 18.03 using instructions on the Wazo site, but I can't get any IncrediblePBX goodies.

    I cannot successfully install Wazo 17.17 using the script IncrediblePBX15-Wazo.sh. I have broken dependencies. Is there an easy edit to get around them?

    Code:
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:
    
    The following packages have unmet dependencies:
     xivo-base : Depends: wazo-auth but it is not going to be installed
                 Depends: wazo-service but it is not going to be installed
                 Depends: wazo-webhookd but it is not going to be installed
                 Depends: xivo-confd but it is not going to be installed
                 Depends: xivo-ctid-ng but it is not going to be installed
                 Depends: xivo-dird but it is not going to be installed
                 Depends: xivo-manage-db but it is not going to be installed
                 Depends: xivo-websocketd but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.
    Reading package lists...
    Building dependency tree...
    Reading state information...
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:
    
    The following packages have unmet dependencies:
     xivo : Depends: xivo-base (= 14:17.17~20171122.200523.92959c1) but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.
    wazo_install.sh: line 65: xivo-service: command not found
    
     

Share This Page