./upgrade-10.13.66-22.sh
Check to make sure this is a FreePBX Distro system before executing
This appears to be a FreePBX Distro system as it has a Distro Version of 10.13.66-22
Your FreePBX Distro System is being upgraded to 10.13.66-22. Please standby...
STAGE 1 STARTING - GUI Modules
Machine not activated
Loaded plugins: fastestmirror, kmod
Setting up Update Process
Loading mirror speeds from cached hostfile
No Packages marked for Update
Upgrade All FreePBX GUI Modules
[AMPSBIN] changed from previous value: [/usr/local/sbin] to new value: [/usr/sbin]
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions...
Setting base permissions...Done
Setting specific permissions...
18341 [============================]
Finished setting permissions
No repos specified, using: [standard] from last GUI settings
Up to date.
Installing: pm2, ucpnode, xmpp
Downloading & Installing pm2...
Starting pm2 download..
Processing pm2
Verifying local module download...Verified
Extracting...Done
Module pm2 successfully downloaded
Installing/Updating Required Libraries. This may take a while...The following messages are ONLY FOR DEBUGGING. Ignore anything that says 'WARN' or is just a warning
Running installation..
Session terminated, killing shell...The process "runuser 'asterisk' -s '/bin/bash' -c 'cd /var/www/html/admin/modules/pm2/node && mkdir -p /home/asterisk/.pm2 && mkdir -p /var/www/html/admin/modules/pm2/node/logs && export HOME=/home/asterisk && export PM2_HOME=/home/asterisk/.pm2 && export ASTLOGDIR=/var/log/asterisk && export ASTVARLIBDIR=/var/lib/asterisk && export PATH=$HOME/.node/bin:$PATH && export NODE_PATH=$HOME/.node/lib/node_modules:$NODE_PATH && export MANPATH=$HOME/.node/share/man:$MANPATH && npm install --only=production'" exceeded the timeout of 600 seconds.
Finished updating libraries!
[Symfony\Component\Process\Exception\ProcessFailedException]
The command "runuser 'asterisk' -s '/bin/bash' -c 'cd /var/www/html/admin/modules/pm2/node && mkdir -p /home/asterisk/.pm2 && mkdir -p /var/www/html/admin/modules/pm2/node/logs && export HOME=/home/asterisk && export PM2_HOME=/home/asterisk/.pm2 && export ASTLOGDIR=/var/log/asterisk && export ASTVARLIBDIR=/var/lib/asterisk && export PATH=$HOME/.node/bin:$PATH && export NODE_PATH=$HOME/.node/lib/node_modules:$NODE_PATH && export MANPATH=$HOME/.node/share/man:$MANPATH && /var/www/html/admin/modules/pm2/node/node_modules/pm2/bin/pm2 ping'" failed.
Exit Code: 1(General error)
Output:
================
Error Output:
================
module.js:338
throw err;
^
Error: Cannot find module 'debug'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.<anonymous> (/var/www/html/admin/modules/pm2/node/node_modules/pm2/constants.js:7:14)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
you can imagine what happens when it tries the other modules which require pm2
fping -C 10 151.101.52.162 163.172.101.189
151.101.52.162 : [0], 84 bytes, 174 ms (174 avg, 0% loss)
163.172.101.189 : [0], 84 bytes, 316 ms (316 avg, 0% loss)
151.101.52.162 : [1], 84 bytes, 176 ms (175 avg, 0% loss)
163.172.101.189 : [1], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [2], 84 bytes, 174 ms (175 avg, 0% loss)
163.172.101.189 : [2], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [3], 84 bytes, 174 ms (175 avg, 0% loss)
163.172.101.189 : [3], 84 bytes, 318 ms (317 avg, 0% loss)
151.101.52.162 : [4], 84 bytes, 175 ms (175 avg, 0% loss)
163.172.101.189 : [4], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [5], 84 bytes, 175 ms (175 avg, 0% loss)
163.172.101.189 : [5], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [6], 84 bytes, 175 ms (175 avg, 0% loss)
163.172.101.189 : [6], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [7], 84 bytes, 175 ms (175 avg, 0% loss)
163.172.101.189 : [7], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [8], 84 bytes, 174 ms (175 avg, 0% loss)
163.172.101.189 : [8], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : [9], 84 bytes, 174 ms (175 avg, 0% loss)
163.172.101.189 : [9], 84 bytes, 317 ms (317 avg, 0% loss)
151.101.52.162 : 174.81 176.59 174.96 174.82 175.48 175.69 175.09 175.48 174.81 174.87
163.172.101.189 : 316.78 317.29 317.82 318.03 317.80 317.03 317.94 317.83 317.98 317.49
so there shouldn’t be any connectivity issues there.
npm i debug
this just sits at the loading rotating bar thing and does nothing for approximately forever
the firewall can see connectivity from the server to 151.101.28.162, which I assume is the alternative here, but this doesn’t have issues either.
Yet another day spent on this product that I really need to spend elsewhere in the business. Nothing should take this much administration effort and time just for simple updates. Unfortunately, I’m stuck with it for the forseeable future due to other infrastructure that requires it. Any help really appreciated so I can stop spending time on this &^%)&^*& thing.