FYI Incredible on Alpharacks

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
I’ve installed Incredible PBX a number of times and never had a problem like this:

I am Hosted on Alpharacks and they have added the 1gb swap drive

[[email protected] ~]# ./create-swapfile-DO
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB) copied, 7.59614 s, 141 MB/s
mkswap: /swapfile: warning: don’t erase bootbits sectors
on whole disk. Use -f to force.
Setting up swapspace version 1, size = 1048572 KiB
no label, UUID=3546bda6-7acf-4fe7-9d48-738c75199aab
swapon: /swapfile: swapon failed: Operation not permitted
error: permission denied on key ‘vm.swappiness’

total used free shared buffers cached
Mem: 1.0G 1.0G 13M 2.5M 0B 991M
-/+ buffers/cache: 18M 1.0G
Swap: 1.0G 2.9M 1.0G
30​

My first attempt to install at AR failed- Asterisk was never installed. So this time through, I am watching the install closely. I am following Ward's excellent instructions.

Thank you for any pointers or links to articles that could help.
 

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
14,846
Reaction score
2,548
You can't install a swap file on an OpenVZ (VPS) container. That's why you had to open a ticket and ask them to provide it.
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
Thank you, Ward. So I will just skip that step and go right into the Phase I install. Hopefully, I have more luck that when I tried the other day.
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
I am wondering if there might be some kind of block at Alpharacks. When going from my local PC I can get to this just fine- but it times out ..


http://mirror.dc2.hackingand.coffee/centos/6.10/os/x86_64/Packages/GConf2-2.28.0 -7.el6.x86_64.rpm: [Errno 12] Timeout on http://mirror.dc2.hackingand.coffee/cen tos/6.10/os/x86_64/Packages/GConf2-2.28.0-7.el6.x86_64.rpm: (28, 'connect() time d out!')
Trying other mirror.​

"trying other mirror" seems to always try the same mirror.

using wget manually fails with a timeout also- after trying over and over it seems to skip and go to the next step. I suspect I will need a ticket with AR for this one... but if anyone has any advice I'd be happy to read it.
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
I can confirm I am getting error after error related to resolving and getting files from mirrors.
For example:

tar: Error is not recoverable: exiting now
./IncrediblePBX-13-13.sh: line 591: cd: Asterisk-Flite*: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
--2019-01-11 21:11:45-- http://sourceforge.net/projects/mpg123/files/mpg123/1.16.0/mpg123-1.16.0.tar.bz2/download
Resolving sourceforge.net... failed: Temporary failure in name resolution.
wget: unable to resolve host address `sourceforge.net'
mv: cannot stat `download': No such file or directory
tar (child): mpg123*: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
./IncrediblePBX-13-13.sh: line 602: cd: mpg123*/: No such file or directory
./IncrediblePBX-13-13.sh: line 603: ./configure: No such file or directory
dahdi: unrecognized service
asterisk: unrecognized service
sed: can't read /etc/php.d/mcrypt.ini: No such file or directory
asterisk: unrecognized service
chown: cannot access `/var/run/asterisk': No such file or directory
chown: cannot access `/etc/asterisk': No such file or directory
chown: cannot access `/var/lib/asterisk': No such file or directory
chown: cannot access `/var/log/asterisk': No such file or directory
chown: cannot access `/var/spool/asterisk': No such file or directory
chown: cannot access `/usr/lib64/asterisk': No such file or directory



Has anyone been successful on AlphaRacks?
 

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
14,846
Reaction score
2,548
@Hal_1: We have several working VPS deployments on AlphaRacks. Without DNS resolution, you're never going to get a reliable build. I'd open a ticket and ask them to move you to another server.

Just curious. What do you show in /etc/resolv.conf??

It should be:
Code:
nameserver 8.8.8.8
nameserver 8.8.4.4
If not, change it and then chattr +i /etc/resolv.conf and reboot.
 
Last edited:

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
I have been informed by AlphaRacks support that this is because they are in China and the government has blocked IP addresses... and in order to make it work I need to pay them an additional $10 a month to have my IP address "rotated" to a working block and that it will lose connectivity regularly...

This makes absolutely no sense to me- but that is what they are claiming.

Alpharacks seems like a non-choice at this point.
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
The latest update for those who might be paying attention. I (again) did a reinstall of CentOS and I am doing the install again. This time a different mirror was selected and things seem to be progressing normally.
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
Install died here:

--2019-01-15 12:55:44-- http://sourceforge.net/projects/mpg123/files/mpg123/1.16.0/mpg123-1.16.0.tar.bz2/download
Resolving sourceforge.net... 216.105.38.13
Connecting to sourceforge.net|216.105.38.13|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://sourceforge.net/projects/mpg123/files/mpg123/1.16.0/mpg123-1.16.0.tar.bz2/download [following]
--2019-01-15 12:55:44-- https://sourceforge.net/projects/mpg123/files/mpg123/1.16.0/mpg123-1.16.0.tar.bz2/download
Connecting to sourceforge.net|216.105.38.13|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://downloads.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2?r=&ts=1547574945&use_mirror=iweb [following]
--2019-01-15 12:55:45-- https://downloads.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2?r=&ts=1547574945&use_mirror=iweb
Resolving downloads.sourceforge.net... 216.105.38.13
Connecting to downloads.sourceforge.net|216.105.38.13|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://iweb.dl.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2 [following]
--2019-01-15 12:55:45-- https://iweb.dl.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2
Resolving iweb.dl.sourceforge.net... 192.175.120.182, 2607:f748:10:12::5f:2
Connecting to iweb.dl.sourceforge.net|192.175.120.182|:443... failed: Connection timed out.
Connecting to iweb.dl.sourceforge.net|2607:f748:10:12::5f:2|:443... failed: Connection timed out.
Retrying.

--2019-01-15 12:57:52-- (try: 2) https://iweb.dl.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2
Connecting to iweb.dl.sourceforge.net|192.175.120.182|:443... failed: Connection timed out.
Connecting to iweb.dl.sourceforge.net|2607:f748:10:12::5f:2|:443... failed: Connection timed out.
Retrying.

--2019-01-15 13:00:00-- (try: 3) https://iweb.dl.sourceforge.net/project/mpg123/mpg123/1.16.0/mpg123-1.16.0.tar.bz2
Connecting to iweb.dl.sourceforge.net|192.175.120.182|:443... failed: Connection timed out.
Connecting to iweb.dl.sourceforge.net|2607:f748:10:12::5f:2|:443...
 

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
Ward- I tried yet again, because there doesn't seem to be a way to recover from a failure, and it failed earlier. It just seems like they block a lot of mirrors there. This step worked last time.


--2019-01-15 13:33:15-- http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Resolving download.fedoraproject.org... 67.203.2.67, 152.19.134.142, 8.43.85.67, ...
Connecting to download.fedoraproject.org|67.203.2.67|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://mirror.nodesdirect.com/epel/6/x86_64/epel-release-6-8.noarch.rpm [following]
--2019-01-15 13:33:15-- http://mirror.nodesdirect.com/epel/6/x86_64/epel-release-6-8.noarch.rpm
Resolving mirror.nodesdirect.com... 23.92.92.94, 2604:4600::175c:5c5e
Connecting to mirror.nodesdirect.com|23.92.92.94|:80... failed: Connection timed out.
Connecting to mirror.nodesdirect.com|2604:4600::175c:5c5e|:80...
 

geopeterwc

Guru
Joined
Aug 17, 2010
Messages
249
Reaction score
57
Location
SF Bay Area - Go Giants!
@Hal_1 ... There is no convenient "recovery" for a failed installation - best to start over with a fresh install of CentOS 64-bit O/S. I know, as I've been down this path a couple of times in the past few days, mostly because of my own mis-steps on the journey. Anything that has been added, ie., swap file, increased storage, bandwidth, etc. will be preserved when your VPS is 'rebooted.'

Use the VPS Control Panel for your AlphaRacks VPS, and select the option to REINSTALL the CentOS-6-x86_64-minimal option for CentOS on your VPS. Give it ten to fifteen minutes to reinstall, and you'll have a 'virgin' system to build your iPBX. Though I haven't tried CentOS 7, I have had very good results (and @wardmundy continues to recommend) CentOS 6 for iPBX installations.

Follow the instructions found in the tutorial (http://nerdvittles.com/?p=27498). The instructions are mirrored in the other tutorial, but the summary instructions in this tutorial do get you to a working VPS system on AlphaRacks.

Once the OS has installed successfully, use PUTTY or another SSH terminal to log into your installation. Begin your installation according to the instructions in the above tutorial. Your VPS will automatically reboot after the first phase of the installation of iPBX 13-13, requiring you to use your SSH terminal to log in again to the VPS and launch the installation script a second time.

Follow the instructions to upgrade your CentOS6 installation to the latest (likely CentOS 6.10) and to install the required software tools.

I prefer a "LEAN" system, so my installation procedure ends before installing the Enchilada stuff ... and I'm not interested (at this time) in FAX through my PBX, so ... proceed at your own peril beyond the second run of the installation script.

I don't understand the reference to China, as the VPS installation locations are in Los Angeles and New York, and should not have "China" connections.

/Pete./
 
  • Like
Reactions: wardmundy

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
@geopeterwc

I don't get the China statement from them either. I don't think they really understand what I am saying.

I've been following the instructions on 27948. I am on my 5th install of the OS again... because each time I do this- one or more of the repos along the way fail and I can't move forward-- and have to start over.

From your VPS there can you hit the Mirrors shown in my posts?


reviewing the log the only thing that failed is my epel install the first time around- can I redo that or do I need to start over?

it looks like these are the commands to download and install (from the script:

wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
rpm -Uvh epel-release-6-8.noarch.rpm
yum -y install freetds freetds-devel​

I'll run them and hope for the best...
 
Last edited:

geopeterwc

Guru
Joined
Aug 17, 2010
Messages
249
Reaction score
57
Location
SF Bay Area - Go Giants!
@Hal_1 ... it looks to me that you're making this much more difficult than it needs to be. There is no need to access any of the Fedora project files to install iPBX 13-13. First step: ensure that you've reinstalled your preferred O/S (CentOS-6 64-bit). Takes about 10 minutes to complete this step.

When the Control Panel reports that the O/S is installed, launch PUTTY or another SSH client to log into the root account, and change the password using the 'passwd' command to set the root password to something you'll remember. (Alternatively, the root password can be changed using the VPS Control Panel's Serial Console option if you don't know the root password. BUT, don't perform any of the other installation steps using the Serial Console access to root.)

The first phase of the installation will take some time. Don't be impatient if it appears that the installation has stalled. The first phase , as well as the second phase of the installation can't be rushed. My installations have taken more than a half hour from beginning to completion of each phase. When the first phase completes, the server will automatically reboot - if you're using PUTTY, you'll see indication that the connection has closed.

When the server has rebooted, log in as root a second time, and launch the installation script again. This phase of the installation also takes multiple minutes, and there will be periods of time where it appears that the process has stopped.

There is no need for any 'unnatural acts' to be performed, ie., using wget to get any of the resources identified in the installation script. @wardmundy is a master at providing scripts that hide the 'ugliness' that might otherwise result by trying any manual process to accomplish the install.

Key to success using AlphaRacks: patience.

/Pete./
 
  • Like
Reactions: wardmundy

Hal_1

New Member
Joined
May 10, 2010
Messages
16
Reaction score
1
So I want to be clear here- I was running the scripts provided in the install package.

when I ran
./IncrediblePBX-13-13.sh
it tried to install a ton of things that failed- I just kept doing it over and over until it picked a mirror that it got through to.

I did not try to deviate AT ALL from @wardmundy 's script. I ran it as is. I promise.

unfortunately, the latest install had a problem when ./incrediblefax13.sh ran

Status says it's running- but the links don't appear I am currently trying to determine where the install log for that step is, as I don't see one in ~, to see what failed.

I really don't want to start over again.
 

Members online

Latest Posts

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,207
Messages
135,991
Members
14,459
Latest member
BinhMinh