Sng_freepbx_debian_install failure

I’m using the script at GitHub - FreePBX/sng_freepbx_debian_install: FreePBX 17 Installation Script attempting to install on an AWS instance running Debian 12.5.

The installation script runs as expected for quite a while before failing to complete…

The last ~10 lines from the script output are:
2024-05-28 14:13:51 - Installing FreePBX packages
2024-05-28 14:13:51 - Installing ionCube packages.
2024-05-28 14:13:51 - Installing ioncube-loader-82 …
2024-05-28 14:14:13 - ioncube-loader-82 installed successfully…
2024-05-28 14:14:13 - Installing sysadmin17 …
2024-05-28 14:15:10 - sysadmin17 installed successfully…
2024-05-28 14:15:11 - Installing sangoma-pbx17 …
2024-05-28 14:16:50 - sangoma-pbx17 installed successfully…
2024-05-28 14:16:50 - Installing ffmpeg …
2024-05-28 14:17:29 - ffmpeg installed successfully…
2024-05-28 14:17:29 - Enabling modules.
2024-05-28 14:17:30 - Restating fail2ban
2024-05-28 14:17:32 - Installing FreePBX 17
2024-05-28 14:17:33 - Installing freepbx17 …
Timeout, server 35.92.209.30 not responding.
$ _

And the last ~dozen lines from /var/log/pbx/freepbx17-install-2024.05.28-13.38.08.log are:
2024-05-28 14:17:33 - Installing freepbx17 …
Reading package lists…
Building dependency tree…
Reading state information…
The following NEW packages will be installed:
freepbx17
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 188 MB of archives.
After this operation, 598 MB of additional disk space will be used.
Get:1 http://deb.freepbx.org/freepbx17-prod bookworm/main amd64 freepbx17 amd64 17.1-1.sng12 [188 MB]
Fetched 188 MB in 31s (6100 kB/s)
Selecting previously unselected package freepbx17.
(Reading database … 107054 files and directories currently installed.)
Preparing to unpack …/freepbx17_17.1-1.sng12_amd64.deb …
Unpacking freepbx17 (17.1-1.sng12) …
Timeout, server 35.92.209.30 not responding.
$ _

At this point the server is unreachable by any means (but it is still running). It seems as though there’s some firewall restrictiction that’s blocking the ssh connection.

I’ve tried this installation process three times now, with the exact same result each time.

Before I dive deeply into the script to see what’s what, has anyone else ever experienced this behavior?

Try to add some Public DNS servers (8.8.8.8 or 1.1.1.1) and hit again.

Following up on my own post… I’ve stood up a standalone machine and this is where it dies:

(from the install log):
The following NEW packages will be installed:
freepbx17
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 188 MB of archives.
After this operation, 598 MB of additional disk space will be used.
Get:1 http://deb.freepbx.org/freepbx17-prod bookworm/main amd64 freepbx17 amd64 17.1-1.sng12 [188 MB]
Fetched 188 MB in 13s (14.0 MB/s)
Selecting previously unselected package freepbx17.
(Reading database … 107054 files and directories currently installed.)
Preparing to unpack …/freepbx17_17.1-1.sng12_amd64.deb …
Unpacking freepbx17 (17.1-1.sng12) …
dpkg-deb: error: subprocess was killed by signal (Killed)
dpkg: error processing archive /var/cache/apt/archives/freepbx17_17.1-1.sng12_amd64.deb (–unpack):
cannot copy extracted data for ‘./home/asterisk/.npm/_cacache/content-v2/sha512/dd/59/915c4b70ed164a01ffb84efd589bd0067a8f2bf3e0a30e2dbac7eed26108a5d54aada9d6a8921ce8109a21aa5cedd26e6469c2520e1250906fcb5a1a5107’ to ‘/home/asterisk/.npm/_cacache/content-v2/sha512/dd/59/915c4b70ed164a01ffb84efd589bd0067a8f2bf3e0a30e2dbac7eed26108a5d54aada9d6a8921ce8109a21aa5cedd26e6469c2520e1250906fcb5a1a5107.dpkg-new’: unexpected end of file or stream
Errors were encountered while processing:
/var/cache/apt/archives/freepbx17_17.1-1.sng12_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
2024-05-28 15:10:49 - Exiting script

So it looks like the .deb file freepbx17_17.1-1.sng12_amd64.deb is corrupted?

Any suggestions on how to resolve this? Or fall back to a previous version?

PS: I’m a total noobie on FreePBX so if you talk to me like I’m an idiot you won’t be too far off. :slight_smile:

@shahin - Did that. Virgin server build, but changed the resolver to 1.1.1.1 and 8.8.4.4 and no difference.

See my other reply; it looks like the .deb file for v17 is corrupt.

I appreciate you taking time to respond to me as I learn!

tried just now in freshly built debian VM on Vultr and it worked fine.
freepbx17 package is quite big in size so may be some issue from your end to download the package.

How much memory does the system have? What does “dmesg” show for output (such as dpkg-deb getting killed due to being out of memory)

Yep – It was out of memory. I couldn’t grep dmesg because I nuked the instance soon after it failed.

But I’ve (through iterations) determined that the smallest AWS Debian instance that will successfully install is a 2GB / 2vCPU instance.

I appreciate the help; thanks!

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.