SOLVED Anyone else's Module Admin confused this morning?

[ostridge]

Settings > Advanced Settings, check the branding field

Oops - no such section "Settings > Advanced Settings, - Branding # on RPi iPBX 2020.3
and with ' Display Readonly Settings = Yes '

System hang while doing upgrade all from cli​

Upgrading module 'clearlytrunking' from 13.0.9.9 to 13.0.9.13.6
Starting module download from https://mirror.clearlyip.com/modules/clearlytrunking/clearlytrunking-13.0.9.13.6.tgz ...
Processing
Downloading...
 304297/304297 [============================] 100%
Finished downloading
Extracting...Done
Module https://mirror.clearlyip.com/modules/clearlytrunking/clearlytrunking-13.0.9.13.6.tgz 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 warningFound npm-cache v0.7.0
Running installation..
[npm-cache] [INFO] using /home/asterisk/.package_cache as cache directory
[npm-cache] [INFO] [composer] Dependency config file /var/www/html/admin/modules/clearlytrunking/node/composer.json does not exist. Skipping install
[npm-cache] [INFO] [npm] using package-lock.json instead of package.json
[npm-cache] [INFO] [npm] config file exists
[npm-cache] [INFO] [npm] cli exists
[npm-cache] [INFO] [npm] hash of /var/www/html/admin/modules/clearlytrunking/node/package-lock.json: 4077aaf763ae3613e90ff166836923d9
[npm-cache] [INFO] [npm] running [npm install]...
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

> [email protected] install /var/www/html/admin/modules/clearlytrunking/node/node_modules/websocket
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/var/www/html/admin/modules/clearlytrunking/node/node_modules/websocket/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o



## apparent system hung; or taking forever.

make: Entering directory '/var/www/html/admin/modules/clearlytrunking/node/node_modules/websocket/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o

 

[hawk#1]

@ostridge

sorry but I don't have a RPI on IPBX 2020.3 anymore so I did not know that setting did not exist then. I used ward's

Moving from Incredible PBX 2020 to 2021 on the Raspberry Pi​

from back in June, and upgraded. So when I checked my RPi system for that setting, it does exist.

 

[hawk#1]

Is the /root/sig-fix (bis) needed?

no it is not needed unless one of the update are for modules that are unsigned. I just wrote one script instead of having to run two scripts, guess I'm on the lazy side and prefer to just run one script.

 

[ostridge]

Pi3 2020.3
There is NO section "Settings/Advanced Settings/ - Branding
From CLI doing

following commands:

fwconsole ma upgradeall
rm -f /tmp/*
fwconsole reload
/root/sig-fix

root@incrediblepbx:~# fwconsole ma upgradeall
No repos specified, using: [standard,extended,unsupported] from last GUI settings

Module(s) requiring upgrades: api, blacklist, bulkhandler, core, framework, manager, tts, userman, voicemail, webrtc

Reached problems at clearlytrunking-13.0.9.13.6.tgz

Upgrading module 'clearlytrunking' from 13.0.9.9 to 13.0.9.13.6
Starting module download from https://mirror.clearlyip.com/modules/clearlytrunking/clearlytrunking-13.0.9.13.6.tgz ...
Processing
Downloading...
304297/304297 [============================] 100%
Finished downloading
Extracting...Done
Module https://mirror.clearlyip.com/modules/clearlytrunking/clearlytrunking-13.0.9.13.6.tgz 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 warningFound npm-cache v0.7.0
Running installation..
[npm-cache] [INFO] using /home/asterisk/.package_cache as cache directory
[npm-cache] [INFO] [composer] Dependency config file /var/www/html/admin/modules/clearlytrunking/node/composer.json does not exist. Skipping install
[npm-cache] [INFO] [npm] using package-lock.json instead of package.json
[npm-cache] [INFO] [npm] config file exists
[npm-cache] [INFO] [npm] cli exists
[npm-cache] [INFO] [npm] hash of /var/www/html/admin/modules/clearlytrunking/node/package-lock.json: 4077aaf763ae3613e90ff166836923d9
[npm-cache] [INFO] [npm] running [npm install]...
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

> [email protected] install /var/www/html/admin/modules/clearlytrunking/node/node_modules/websocket
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/var/www/html/admin/modules/clearlytrunking/node/node_modules/websocket/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o

At this point went to bed but in morning greeted with this and still running:-

The process "runuser 'asterisk' -s '/bin/bash' -c 'cd /var/www/html/admin/modules/clearlytrunking/node && mkdir -p /home/asterisk/.pm2 && mkdir -p /var/www/html/admin/modules/clearlytrunking/node/logs && export '\''NODE_ENV'\''='\''production'\'' && 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-cache install --only=production'" exceeded the timeout of 600 seconds.Failed updating libraries!

In modulefunctions.class.php line 700:

  PDOStatement::execute(): MySQL server has gone away


moduleadmin [-f|--force] [-d|--debug] [--edge] [--ignorecache] [--stable] [--color] [--skipchown] [-e|--autoenable] [--skipdisabled] [--snapshot SNAPSHOT] [--format FORMAT] [-R|--repo REPO] [-t|--tag TAG] [--skipbreakingcheck] [--sendemail] [--onlystdout] [--] [<args>]...

Killed
root@incrediblepbx:~# rm -f /tmp/*
rm: cannot remove '/tmp/par-726f6f74': Is a directory
rm: cannot remove '/tmp/systemd-private-2df9ee9db9644826b927377d73362a7e-apache2.service-Xr3PJn': Is a directory
rm: cannot remove '/tmp/systemd-private-2df9ee9db9644826b927377d73362a7e-haveged.service-iBSkoU': Is a directory
rm: cannot remove '/tmp/systemd-private-2df9ee9db9644826b927377d73362a7e-ntp.service-86NJIU': Is a directory
rm: cannot remove '/tmp/systemd-private-2df9ee9db9644826b927377d73362a7e-phpsessionclean.service-cB1Fpi': Is a directory
rm: cannot remove '/tmp/systemd-private-2df9ee9db9644826b927377d73362a7e-redis-server.service-uqcUs6': Is a directory
root@incrediblepbx:~# fwconsole reload
Killed

Server Hung at that point

Trunking Module 13.0.9.9 Stable Clearly IP Commercial Disabled; Pending Upgrade to 13.0.9.13.6

 

[dallas]

@ostridge rm -f /tmp/* is incorrect. Here's the full sequence of commands.

fwconsole ma upgradeall
rm -f -r /tmp/*
fwconsole reload
/root/sig-fix
/root/sig-fix

 

[ostridge]

RPi IncrediblePBX 2020.3 Branding module not installed.

Incredible PBX branding module

What is that module named?

Edit: Fixed this by using Module Admin to install the UCP to version 15.0.10, then used the linux CLI fwconsole script as above posts and @dallas recursive amendment

#!/bin/bash
## filename: /root/fwconsole-ma-upgradeall.sh
fwconsole ma upgradeall
rm -f -r /tmp/*
fwconsole reload
/root/sig-fix
/root/sig-fix

Just leaving these 2 as upgradeable for reasons herein:

Bulk Phone Restart   Stable   Sangoma Technologies Corporation  GPLv3+ Not Installed (Available online: 13.0.7)  Previously found to conflict with OSS End Point Manager.

XMPP Stable   Sangoma Technologies Corporation  AGPLv3 Not Installed (Available online: 15.0.6.12)    Failed install due apparently to no config.

 

[tbrummell]

The Incredible PBX branding module from ClearlyIP lets us manage versions of every FreePBX module. UCP was erroneously set to a specific version rather than the latest release. We have fixed it. Ordinarily, you are much safer leaving the Branding option in Advanced Settings set to 15.19.11.001 which lets us protect your platform from a dangerous module if one should appear down the road. The downside is what happened here where I forgot to unblock a locked version of UCP because the next version caused folks problems that were later fixed in a subsequent release. My apologies.

Yeah, I've been away and just came back this morning, upgraded (via GUI) just fine with no changes made to other parts as mentioned above.

 

[hawk#1]

Could anyone explain why the command rm -f /tmp/* works on all my IncrediblePBX 2021 for Debian and Raspberry Pi's, and for IncrediblePBX 2020 for CentOS 7 systems. Also that is what is published in the Nerdvittles guides for the systems listed above. I understand that the -r is to remove subdirectories, but why is only some having to remove sub-directories and others do not?

 

[dallas]

but why is only some having to remove sub-directories and others do not?

My guess is that the sub-directories don't exist on systems where rm -f /tmp/* works.
Could be something different in the script fwconsole-ma-upgradeall.sh.

 

[hawk#1]

My guess is that the sub-directories don't exist on systems where rm -f /tmp/* works.
Could be something different in the script fwconsole-ma-upgradeall.sh.

Thanks, or another reason is because they installed other things that left sub-directories in the tmp directory. Anyways, I added the -r to my script, figured there is nothing wrong with keeping the tmp directory empty of unnecessary crap