SOLVED No CLI output after updating through Module Admin

[Rrrr]

PBX2020.1 fresh install
CentOs 7
16.12.0
iPBX 15.0.12.17

I see a few other threads with issues using Module Admin: here and here.
This seems different: I just want to warn people not to use Module Admin.

With a fresh install, I updated three vulnerable modules and applied settings.
After that I went back to the CLI to find out that there is no more verbose output despite standard verbose settings (3).

Reports
ModuleVersionPublisherLicenseStatusTrack

Asterisk Info15.0.10StableSangoma Technologies CorporationGPLv3+Enabled and up to date

Asterisk Logfiles13.0.10.8StableSchmooze Com. Inc.GPLv3+Online upgrade available (15.0.4)Vulnerable, Requires: 13.0.10.10

Asternic CDR Reports1.6.3StableAsternic.bizEnabled; Not available online

CDR Reports15.0.17.1StableSangoma Technologies CorporationGPLv3+Online upgrade available (15.0.17.2)Vulnerable, Requires: 15.0.17.2

Call Event Logging15.0.15.8StableSangoma Technologies CorporationGPLv3+Online upgrade available (15.0.15.10)Vulnerable, Requires: 15.0.15.10

 

[billsimon]

Many threads on this. It’s just a bug. Fix the Logfile settings which got set to “off.” No need to “warn” people about module admin.

 

[wardmundy]

If you had rebooted or logged out and back in after the fresh install, the Automatic Update Utility would have straightened all of this out. Or, from the Linux CLI...

fwconsole ma upgradeall
fwconsole reload
/root/sig-fix
/root/sig-fix

 

[Rrrr]

Thank you.

1. I rolled back to an image after the install completed and logged back in: the three modules were not updated by the automatic update utility.

Retrieving... lastupdate2020
Updates available as of Sun Aug 23 17:18:18 IDT 2020: 18
Checking for update20201. INSTALLED: Automatic Update Utility is working
Checking for update20202. INSTALLED: Patches for Incredible PBX 2020.3 Raspbian
Checking for update20203. INSTALLED: ClearlyIP repo configured for updates
Checking for update20204. INSTALLED: Incredible PBX 2020.3 Raspbian CDR patch
Checking for update20205. INSTALLED: Incredible PBX 2020.3 AsteriDex patch
Checking for update20206. INSTALLED: FreePBX GPG Key Refresh
Checking for update20207. INSTALLED: halt and reboot scripts added
Checking for update20208. INSTALLED: timezone-setup update for Raspbian 10
Checking for update20209. INSTALLED: TM3 add-fqdn update for IPv6 use
Checking for update202010. INSTALLED: Raspbian 10 Incredible Fax installer update
Checking for update202011. INSTALLED: Incredible PBX 2020.3 pbxstatus LAN port patch
Checking for update202012. INSTALLED: NV-Weather-ZIP patch for 0 zip codes
Checking for update202013. INSTALLED: Incredible PBX 2020.3 amd.conf patch
Checking for update202014. INSTALLED: LAME aadded for voicemail processing
Checking for update202015. INSTALLED: watson-test STT script added to /usr/local/sbin
Checking for update202016. INSTALLED: Wolfram Alpga AGI script updated
Checking for update202017. INSTALLED: Asterisk 16 update script patched
Checking for update202018. INSTALLED: Removed Asterisk duplicate logging
Updates and notifications completed.

2. Running Ward's code from the Linux CLI I updated the modules (much easier!), but, like the GUI update, caused the asterisk CLI to show no output.

fwconsole ma upgradeall
fwconsole reload
/root/sig-fix
/root/sig-fix

3. I logged out and in again (SSH), making sure the automatic update utility ran: to no avail.

4. As per @billsimon I found this and checked Settings -> Asterisk Logfile Settings -> Log Files which were indeed all set to off. I set them as follows:
console => debug,error,notice,verbose,warning
full => debug,error,notice,verbose

All good, thank you for your help.

 

[wardmundy]

All sorted out now. Apparently different versions of Incredible PBX had the logging set in different ways. So now update202018 checks the FreePBX settings before deleting the custom file. If the logging is not configured in FreePBX, then it leaves it set up in the logger custom file. Otherwise, it deletes what would be duplicate logging entries.

If you make changes to the logging setup in FreePBX, just remember to adjust logger_logfiles_custom.conf accordingly.