SOLVED Install fails on Vultr

[Jerry3716]

Tried the install, twice, for IncrediblePBX-Xivo on Vultr - failed with error codes about rabbitmq.

Tried a clean install of just Xivo on a Debian instance, similar errors.

Attempted install of just rabbitmq -

Hit http://http.us.debian.org jessie/main amd64 Packages
Hit http://http.us.debian.org jessie/main Translation-en
Ign http://www.rabbitmq.com testing/main Translation-en_US
Ign http://www.rabbitmq.com testing/main Translation-en
Fetched 8,144 B in 2s (3,891 B/s)
Reading package lists... Done
root@p2:/var/lib/rabbitmq# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up rabbitmq-server (3.6.3-1) ...
Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing package rabbitmq-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looked at the service, as described in the error message, and ports cannot be opened.

Installed webmin - a firewall was not even installed. (As expected.) Installed iptables with the correct ports open.

Same error.

Anyone else have the same experience? Or, suggestions?

 

[Jerry3716]

I should have searched more before posting -

Looks like a hostname other than xivo.incrediblepbx.com will result in this error.

 

[Jerry3716]

Now, all sorts of errors, after the restart. Best guess is that the ISO is out-of-date already. Giving up, for now.

 

[wardmundy]

@Jerry3716 Works fine if you follow the tutorial. New article on Vultr will be available on Nerd Vittles this coming Monday.

 

[Jerry3716]

Very cool!! Much easier than the ISO. One small item popped up -


Login to web interface as root with web password.

Wizard already configured...

Traceback (most recent call last):

File "./wizard.py", line 21, in <module>

"timezone": discover['timezone'],

NameError: name 'discover' is not defined

Please verify no errors shown above in XiVO configuration step.


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


First time that I received the error, I had changed the host name from vultr to my own. Second time, I left the host name alone. An entry is required in the domain name - used incrediblepbx.com

Based upon a thread at XiVO, I went ahead and finished the install.

The rest of the install went well!!!!

Later today and tomorrow, going to attempt to put Xivo's High Availability in place between this VULTR instance and an on-premise Intel NUC. The NUC has 35 extensions currently and I setup with software raid SSDs. (I have given the VULTR instance plenty of resources.) Your excellent tutorials made this project manageable!! Thank you!!!!

 

[wardmundy]

Still not sure what you are doing. If you complete the Incredible PBX install from the command line BEFORE you access the GUI in the web, there should be no problems. Just built another one less than an hour ago.

 

[Ahron]

Thank you for all the wonderful tutorials and assistance!

I tried three times to install Incredible PBX at VULTR from the ISO. I have reread the instructions over and over again to look for mistakes. Although the entire install seems to work as per instructions (http://nerdvittles.com/?tag=google-voice), I am left with two issues. One, when using the SSH to login as root, the Incredible PBX status page shows both Asterisk and Fail2Ban services in the red DN status. Two, when logging into the web interface of the Incredible GUI, the Asterisk Manager Interface shows a ‘failure’ status.


Any suggestions of where my mistake lies would be greatly appreciated!

 

[wardmundy]

@Ahron: Two suggestions. Make another attempt this morning. Incredible PBX loads components from dozens of providers, and weekends can be problematic when servers go down without a babysitter on site. If it still fails for you, set up a Vultr VM with CentOS 6 or Ubuntu 14 and use the Incredible PBX installer for the platform of your choice to load everything. You'll end up with the same product.

 

[Ahron]

Thank you kindly! I'll try your suggestions later on in the day.

 

[Jerry3716]

@Ahron Just did a VULTR VM at New Jersey site without any errors. The command 'pbxstatus' showed green across the board. Was then able to login to the web configuration panel and showed green except for the CTI daemon which needs configuration for your environment. Make sure that you complete the command line installation before logging into the web configuration panel. During script, some of the components say to login to complete the installation. Hit enter through those until the end which looks like this -

IMPORTANT TO-DO LIST TO COMPLETE YOUR SETUP:

1. Add Speech Recog Key on line 72: /var/lib/asterisk/agi-bin/speech-recog.agi

Tutorial available here: http://nerdvittles.com/?p=14612#app2

2. For DISA support, modify /root/disa-xivo.txt and copy to dialplan.

Tutorial available here: http://nerd.bz/28Xkt3Z

3. Obtain Line Credentials using XiVO web interface @ IPBX Settings:Lines.

Use these to configure a SIP phone and AsteriDex Click-to-Dial.

AsteriDex tutorial available here: http://nerd.bz/244Mfyl

4. Add some SIP Trunks and Routes to support outgoing and incoming calls.

Tutorials available here: http://nerdvittles.com/?page_id=18324

5. Download AsteriDex SpeedDial Code Generator: http://nerd.bz/28LJNJK

6. Check the status of XiVO at any time: pbxstatus

7. PortKnocker credentials for emergency access: /root/knock.FAQ

8. Restart your firewall with this command ONLY: iptables-restart

9. Login to XiVO using this alternate PPTP address: 172.16.16.100

 

[Ahron]

Mission accomplished! I ended up installing Incredible PBX for XiVO in the Vultr Cloud. It looks like all systems go except for two things. 1) Why is the Consul setting is red and 'DN'? 2) I tried getting my PortKnocker credentials by entering /root/knock.FAQ in PuTTY. Instead of seeing my ports that need to be knocked, I get the following message, "Permission denied". What did I do wrong?

Thanx for the assistance!

 

[wardmundy]

knock.FAQ is a text file. You display it with...

cat /root/knock.FAQ