SOLVED XiVO install problems on Vultr and Virtualbox

[sirdotcom]

Hi,
I have installed XiVO a number of times, and sometimes it goes well. But for some reason it seems to "deteriorate" over time. But despite that, I'm trying a fresh install on Vultr, and here's the python stuff I get:

Configuring XiVO. Please wait...
Login to web interface as root with web password.
Traceback (most recent call last):
  File "./wizard.py", line 12, in <module>
    if c.wizard.get()['configured'] != True:
  File "/usr/lib/python2.7/dist-packages/xivo_confd_client/commands/wizard.py", line 33, in get
    response = self.session.get(url)
  File "/usr/lib/python2.7/dist-packages/xivo_confd_client/session.py", line 57, in get
    response = self.session.get(url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 469, in get
    return self.request('GET', url, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 457, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 569, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 407, in send
    raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(111, 'Connection refused'))
Please verify no errors shown above in XiVO configuration step.

To continue with installation, press ENTER. Or press Ctrl-C to abort.^C

I don't know anything about python, but it seems like it's just installing .debs more or less ... also if I try to browse to it I get a proxy error: xivo-confd must be running: Failed to connect to 127.0.0.1 port 9487: Connection refused

Has anyone had this problem on a fresh install? This is at least the third time and there's not much you can do to mess it up

Thanks,
Steve

 

[Sylvain Boily]

What the script are you using to install xivo?

 

[sirdotcom]

Hi,
I'm using IncrediblePBX13-XiVO.sh ... from the tutorial at http://nerdvittles.com/?page_id=18907
Thanks,
Steve

 

[wardmundy]

@Sylvain Boily: Looks like xivo-confd is failing to start and /etc/xivo-confd/config.yml is missing:

● xivo-confd.service - xivo-confd server
   Loaded: loaded (/lib/systemd/system/xivo-confd.service; disabled)
   Active: failed (Result: exit-code) since Sat 2016-11-05 07:43:48 EDT; 1min 29s ago
  Process: 23458 ExecStart=/usr/bin/xivo-confd (code=exited, status=1/FAILURE)
  Process: 23457 ExecStartPre=/usr/bin/install -d -o www-data -g www-data /var/run/xivo-confd (code=exited, status=0/SUCCESS)

Nov 05 07:43:47 vultr.guest systemd[1]: Starting xivo-confd server...
Nov 05 07:43:48 vultr.guest xivo-confd[23458]: Could not read config file /etc/xivo-confd/config.yml: [Errno ...yml'
Nov 05 07:43:48 vultr.guest systemd[1]: xivo-confd.service: control process exited, code=exited status=1
Nov 05 07:43:48 vultr.guest systemd[1]: Failed to start xivo-confd server.
Nov 05 07:43:48 vultr.guest systemd[1]: Unit xivo-confd.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

 

[wardmundy]

Looks like Vultr has broken something in their Debian 8 build. We will report it. For the time being, use Digital Ocean and follow the tutorial carefully and be sure to set hostname to xivo.incrediblepbx.com when you build the VPS.

 

[sirdotcom]

Thanks ... yes apparently there's a problem with Debian on Vultr. Thanks for the heads up.

 

[wardmundy]

@sirdotcom Can't reproduce a problem with VirtualBox. Did you follow the tutorial?

 

[wardmundy]

Working through the XiVO build problem on Vultr this morning. Luckily, Vultr supports installs from your own ISOs so it was fairly easy to pinpoint where the problem was.

1. We uploaded our own Debian 8/64 image from IncrediblePBX.com (Servers -> ISO -> + Add):

http://incrediblepbx.com/debian-8.6.0-amd64-netinst.iso

2. Then we created the standard $5 VPS using the new ISO instead of the Debian 8/64 image at Vultr.

3. From the console window for the VPS, we went through the base install of Debian using xivo for hostname, incrediblepbx.com for host domain, accepting all the defaults, and disabling all Debian components except SSH and base utilities (last 2 options only). When the final prompt appears saying it's time to reboot, we removed the ISO image (in Settings) so that the VPS would boot from the newly installed system.

4. Logged back in from the console and enabled remote SSH access in /etc/ssh/sshd_config and then restarted ssh.

5. Logged into the VPS using SSH and performed the standard Incredible PBX for XiVO install following our Vultr tutorial.

Everything installed and works fine.

That tells me the Vultr folks broke something when they created the latest Debian 8/64 image. We will report it. In the meantime, you can follow the steps above if you need a working server on Vultr in a hurry.

 

[wardmundy]

The Vultr folks have identified the problem. They updated their image last week and removed the cloud-init package which included a number of python dependencies upon which XiVO depends. In the minimal net-install of XiVO, these are automatically included; however, Vultr now is using a subset of the minimal Debian 8 platform by default.

We now have added cloud-init to the latest Incredible PBX for XiVO installer, and everything is working again. Just download the latest installer and follow the Nerd Vittles Vultr installation tutorial and all will be well in XiVO land.

Thanks for the heads up, @sirdotcom.

FYI to @Sylvain Boily: Perhaps cloud-init should be a dependency in the XiVO build since its dependencies include numerous python components that XiVO needs to successfully install:

iso-codes python-apt python-apt-common python-boto python-cheetah python-configobj python-json-pointer python-jsonpatch python-oauth python-prettytable python-serial python-software-properties python3-apt unattended-upgrades