Error when using upgrade-10.13.66-18.sh and upgrade-10.13.66-19.sh

I had 10.13.66-17, i ran the upgrade-10.13.66-18.sh - it showed the error below when updating, trying to recover i thought about running it again, but the script had updated the system to 10.13.66-18 so i ran upgrade-10.13.66-19.sh - giving the same error below - it seems like freepbx-13.0.191.4-1.shmz65.1.54.noarch has a dependancy of mongodb-server-2.4.14-4.el6.i686 - this fails becuase it and all its dependancies are also for i686 but the system is actually x86_64 - why is freepbx which is noarch requesting mongodb-server-2.4.14-4.el6.i686 - is there a way of recovering from this.

Resolving Dependencies
–> Running transaction check
—> Package freepbx.noarch 0:13.0.190.19-1.shmz65.1.53 will be updated
—> Package freepbx.noarch 0:13.0.191.4-1.shmz65.1.54 will be an update
–> Processing Dependency: php-soap for package: freepbx-13.0.191.4-1.shmz65.1.54.noarch
–> Processing Dependency: mongodb-server for package: freepbx-13.0.191.4-1.shmz65.1.54.noarch
—> Package ssh_keys.noarch 0:3.0-4.shmz65.1.93 will be updated
—> Package ssh_keys.noarch 0:3.0-5.shmz65.1.97 will be an update
–> Running transaction check
—> Package mongodb-server.i686 0:2.4.14-4.el6 will be installed
–> Processing Dependency: v8 for package: mongodb-server-2.4.14-4.el6.i686
–> Processing Dependency: libv8.so.3 for package: mongodb-server-2.4.14-4.el6.i686

further investigating shows the following…

Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:

     1. You have an upgrade for libstdc++ which is missing some
        dependency that another package requires. Yum is trying to
        solve this by installing an older version of libstdc++ of the
        different architecture. If you exclude the bad architecture
        yum will tell you what the root cause is (which package
        requires what). You can try redoing the upgrade with
        --exclude libstdc++.otherarch ... this should give you an error
        message showing the root cause of the problem.

     2. You have multiple architectures of libstdc++ installed, but
        yum can only see an upgrade for one of those arcitectures.
        If you don't want/need both architectures anymore then you
        can remove the one with the missing update and everything
        will work.

     3. You have duplicate versions of libstdc++ installed already.
        You can use "yum check" to get yum show these errors.

   ...you can also use --setopt=protected_multilib=false to remove
   this checking, however this is almost never the correct thing to
   do as something else is very likely to go wrong (often causing
   much more problems).

   Protected multilib versions: libstdc++-4.4.7-11.el6.i686 != libstdc++-4.4.7-17.el6.x86_64

Error: Protected multilib versions: libgcc-4.4.7-11.el6.i686 != libgcc-4.4.7-17.el6.x86_64

We are not requiring a i686. Something on your system is confused as it appears you have both 32bit and 64bit packages installed.

Thanks Tony

It seems that mongodb-server is a dep for freepbx-13.0.191.4-1.shmz65.1.54.noarch?

–> Processing Dependency: mongodb-server for package: freepbx-13.0.191.4-1.shmz65.1.54.noarch

repoquery --requires freepbx.noarch
/bin/sh
httpd
icu
libicu-devel
mongodb-server

however

there is no x86_64 package in the repo for mongodb-server

[root@larynx ~]# yum info mongodb-server
Loaded plugins: fastestmirror, kmod, security
Loading mirror speeds from cached hostfile
Available Packages
Name : mongodb-server
Arch : i686
Version : 2.4.14
Release : 4.el6
Size : 5.1 M
Repo : pbx
Summary : MongoDB server, sharding server and support scripts
URL : http://www.mongodb.org
License : AGPLv3 and zlib and ASL 2.0
Description : This package provides the mongo server software, mongo sharding server
: software, default configuration files, and init scripts.

i only have FreePBX.repo in the yum.repos.d folder.

When i “info” the mongo db server on a centos system installed via a centos ISO it gives me

[root@backbone ~]# yum info mongodb-server
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile

when i run yum info mogo-server on another FreePBX system installed from the distrib FreePBX iso it gives me

[root@orbital yum.repos.d]# yum info mongodb-server
Loaded plugins: fastestmirror, kmod, security
Determining fastest mirrors
base | 2.0 kB 00:00
extras | 1.3 kB 00:00
pbx | 2.9 kB 00:00
pbx/primary_db | 1.6 MB 00:03
schmooze-commercial | 2.9 kB 00:00
schmooze-commercial/primary_db | 101 kB 00:01
updates | 1.3 kB 00:00
Available Packages
Name : mongodb-server
Arch : i686
Version : 2.4.14
Release : 4.el6
Size : 5.1 M
Repo : pbx
Summary : MongoDB server, sharding server and support scripts
URL : http://www.mongodb.org
License : AGPLv3 and zlib and ASL 2.0
Description : This package provides the mongo server software, mongo sharding server
: software, default configuration files, and init scripts.

so as
–> Processing Dependency: mongodb-server for package: freepbx-13.0.191.4-1.shmz65.1.54.noarch

i guess it is trying to install the only mongodb server it can find.

Is this line of enquiry sensible or have i missed something?

i have updated the system using

“yum upgrade -x freepbx.noarch”

Which has completed without error.

Are there supposed to be any other *.repo files in the default setup (I installed from one of the installer ISOs)
When i run

rpm -qa --queryformat ‘%{NAME} %{ARCH}\n’

it ONLY gives me x86_64 packages (i can post the output if you like)

just to check if i have any i686 installed i ran…

rpm -qa --queryformat ‘%{NAME} %{ARCH}\n’ | grep -v x86_64

gives me.

python-sssdconfig noarch
perl-Convert-ASN1 noarch
perl-XML-Filter-BufferText noarch
fedora-usermgmt noarch
dahdi-firmware-te133 noarch
dahdi-firmware-oct6114-032 noarch
system-config-firewall-base noarch
mysql-log-rotate noarch
sgml-common noarch
ql2500-firmware noarch
yum noarch
gpg-pubkey (none)
perl-HTML-Tagset noarch
fedora-usermgmt-default-fedora-setup noarch
crontabs noarch
perl-XML-SAX-Writer noarch
redhat-rpm-config noarch
asterisk-sounds-core-en-gsm noarch
dahdi-firmware-a8a noarch
sysadmin noarch
aic94xx-firmware noarch
ca-certificates noarch
jpackage-utils noarch
ql2100-firmware noarch
asterisk-sounds-extra-en-ulaw noarch
yum-kmod noarch
schmooze-dahdi noarch
autoconf noarch
perl-Digest-HMAC noarch
webmin noarch
fail2ban noarch
dahdi-firmware-oct6126-128 noarch
urw-fonts noarch
moh-sounds noarch
basesystem noarch
ql2400-firmware noarch
ql23xx-firmware noarch
asterisk-sounds-core-en-alaw noarch
yum-plugin-fastestmirror noarch
libX11-common noarch
kbd-misc noarch
perl-LDAP noarch
mailcap noarch
gpg-pubkey (none)
dahdi-firmware-hx8 noarch
dahdi-firmware-te435 noarch
dahdi-firmware-a8b noarch
easyrsa3 noarch
bfa-firmware noarch
php-pear-DB noarch
asterisk-sounds-extra-en-alaw noarch
dahdi-firmware noarch
hal-info noarch
perl-Module-Find noarch
automake noarch
dracut noarch
perl-Authen-SASL noarch
perl-URI noarch
perl-Git noarch
dahdi-firmware-tc400m noarch
dahdi-firmware-oct6114-064 noarch
dahdi-firmware-oct6114-128 noarch
system-config-network-tui noarch
mysql-init-fixer noarch
hwdata noarch
xorg-x11-fonts-Type1 noarch
hicolor-icon-theme noarch
php-pear noarch
setup noarch
asterisk-version-switch noarch
rootfiles noarch
iSymphonyServerV3-fpbx noarch
tzdata-java noarch
perl-XML-SAX noarch
dracut-kernel noarch
fedora-usermgmt-core noarch
kernel-firmware noarch
dahdi-firmware-a4b noarch
dahdi-firmware-oct6114-256 noarch
dahdi-firmware-te436 noarch
redhat-logos noarch

I suppose i could add the epel repo and get the MongoDB server that way, which would probably pull down any of its deps, but i am a bit wary of doing that as i want to keep the FreePBX as clean and as near to the distro as possible as i have just had to sort out the mess surrounding the death of PIAF by migrating to a clean FreePBX.

Were you able to resolve this? I’m stuck on the same problem, using epel packages doesnt clear, freepbx still wants the i686 version installed.

Hm… i guess i must have but i cannot remember what i did… i just ran an update and it worked fine… my apologies for not documenting whatever it was i did.

And NOW - i have completely dealt with it by upgrading to #14 of FreePBX - the upgrade is worth it, many improvements not the least that this is completely gone - i opted for a fresh install and rebuild as this new version will deal with its own upgrades.