FreePBX 14 Module Admin throws Exception

Hey all,

I’m new to FreePBX 13 so I don’t have all the tabs memorized just yet.

I was using the FreePBX V 13 Module Admin page and I selected one of the other tabs. It was the tab where you can check for updates to the asterisk/linux side of things. The command took some time to complete but when it did, I now get an exception when I go to Modules Admin.

Here is the basic output:


RPM command errored, tried to run '/usr/bin/rpm -q --queryformat “%{VERSION}.%{RELEASE}\n” alsa-lib.x86_64 asterisk-version-switch.noarch asterisk13.x86_64 asterisk13-addons.x86_64 asterisk13-addons-bluetooth.x86_64 asterisk13-addons-core.x86_64 asterisk13-addons-mysql.x86_64 asterisk13-addons-ooh323.x86_64 asterisk13-core.x86_64 asterisk13-curl.x86_64 asterisk13-dahdi.x86_64 asterisk13-doc.x86_64 asterisk13-flite.x86_64 asterisk13-odbc.x86_64 asterisk13-ogg.x86_64 asterisk13-resample.x86_64 asterisk13-voicemail.x86_64 audit.x86_64 audit-libs.x86_64 authconfig.x86_64 bash.x86_64 bind-libs.x86_64 bind-libs-lite.x86_64 bind-license.noarch bind-utils.x86_64 binutils.x86_64 biosdevname.x86_64 bluez-libs.x86_64 boost-filesystem.x86_64 boost-program-options.x86_64 boost-system.x86_64 boost-thread.x86_64 btrfs-progs.x86_64 ca-certificates.noarch cairo.x86_64 chkconfig.x86_64 chrony.x86_64 copy-jdk-configs.noarch cpio.x86_64 cpp.x86_64 cronie.x86_64 cronie-noanacron.x86_64 cryptsetup.x86_64 cryptsetup-libs.x86_64 cups-libs.x86_64 curl.x86_64 cyrus-sasl-lib.x86_64

There are more listed but you get the idea.

Stack shows:

4 Exception


3 FreePBX\Builtin\SystemUpdates getInstalledRpmVersions


2 FreePBX\Builtin\SystemUpdates parseUpdates


1 FreePBX\Builtin\SystemUpdates getPendingUpdates


0 include


I’m not sure where to even start with this one…


Sounds very similar to the issue reported for FreePBX 14:

The solution probably won’t be the same, but try a yum update, and see if you get any Transaction Errors. That may then guide you towards incompatible packages that may need to be removed.

Thanks, your search foo is better than mine. I’ll give them a shot.

So I just did a ‘yum update’ and then rebooted the system. When I went back to Module Admin and then went to the tab ‘System Updates’ all was well with the world.

Thanks for the tip on the other postings and I was able to resolve the issue without having to remove any software first.