For all of those people that are still having issues do you have other repos installed on your machines? @chaser @judcompbx @asteriskadmin
Paste the output of:
ls -l /etc/yum.repos.d/
As requested:
[root@freepbx boot]# ls -l /etc/yum.repos.d/
total 28
-rw-r--r-- 1 root root 1359 Jul 20 16:46 CentOS-Sources.repo
-rw-r--r-- 1 root root 1478 Jul 20 16:46 Sangoma-Base.repo
-rw-r--r-- 1 root root 316 Jul 20 16:46 Sangoma-Commercial.repo
-rw-r--r-- 1 root root 1323 Jul 20 16:46 Sangoma-CR.repo
-rw-r--r-- 1 root root 290 Jul 20 16:46 Sangoma-fasttrack.repo
-rw-r--r-- 1 root root 588 Jul 20 16:46 Sangoma-Media.repo
-rw-r--r-- 1 root root 486 Jul 20 16:46 Sangoma-Sources.repo
[root@freepbx boot]#
Iāve installed the dependencies listed by @asteriskadmin and this has stopped the gui module admin page from crashing out, but I then run into the Transaction Check Error issue that I posted about earlier.
donāt seem to have any issues. same ls -l as @chaser
I also have āSet Module Admin to Edge modeā set to āNoā in advanced config ; not sure how this affects things now
Do you both still have transaction checks?
try:
yum clean all
yum upgrade[root@freepbx ~]# yum clean all
Loaded plugins: fastestmirror, versionlock
Cleaning repos: sng-base sng-epel sng-extras sng-pkgs sng-updates
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors
[root@freepbx ~]# yum upgrade
Loaded plugins: fastestmirror, versionlock
sng-base | 3.6 kB 00:00:00
sng-epel | 4.3 kB 00:00:00
sng-extras | 3.4 kB 00:00:00
sng-pkgs | 3.4 kB 00:00:00
sng-updates | 3.4 kB 00:00:00
(1/8): sng-epel/7/x86_64/group_gz | 170 kB 00:00:00
(2/8): sng-base/7/x86_64/group_gz | 156 kB 00:00:00
(3/8): sng-epel/7/x86_64/updateinfo | 833 kB 00:00:00
(4/8): sng-extras/7/x86_64/primary_db | 112 kB 00:00:00
(5/8): sng-updates/7/x86_64/primary_db | 2.7 MB 00:00:00
(6/8): sng-pkgs/7/x86_64/primary_db | 455 kB 00:00:00
(7/8): sng-epel/7/x86_64/primary_db | 4.8 MB 00:00:01
(8/8): sng-base/7/x86_64/primary_db | 5.7 MB 00:00:01
Determining fastest mirrors
No packages marked for update
[root@freepbx ~]#
You have no packages marked for update. This issue seems resolved?
yes. still getting those transaction errors. even after updating the dependencies (I also just edited my earlier post to show this)
yum removed the fail2ban & fail2ban server packages (not sure I should have actually done that!), and now only get the transaction errors for the two firmware files.
So remove the packages for the firmware.
yum remove ql2400-firmware
yum remove ql2500-firmware
Did you both use the distro upgrade script?
Removing packages now.
Yes. I upgraded to FreePBX14 using the upgrade script.
total 28
-rw-r--r-- 1 root root 1359 Jul 21 01:46 CentOS-Sources.repo
-rw-r--r-- 1 root root 1478 Jul 21 01:46 Sangoma-Base.repo
-rw-r--r-- 1 root root 316 Jul 21 01:46 Sangoma-Commercial.repo
-rw-r--r-- 1 root root 1323 Jul 21 01:46 Sangoma-CR.repo
-rw-r--r-- 1 root root 290 Jul 21 01:46 Sangoma-fasttrack.repo
-rw-r--r-- 1 root root 588 Jul 21 01:46 Sangoma-Media.repo
-rw-r--r-- 1 root root 486 Jul 21 01:46 Sangoma-Sources.repo```A couple of things.
Firstly we donāt install āfail2ban-serverā we utilize āfail2ban-fpbxā I assume the upgrade script added āfail2ban-serverā
Furthermore the conflicting firmware files are marked with āel6_5ā because they came from the older distro. In our newer upgrade scripts we remove these, you probably upgraded before we did this.
1 Like
Now that Iāve fixed the transaction errors (I also had to delete a file from /boot, because I didnāt have enough space), yum upgrade is now running. Looks like it might take quite a while, though (currently at step 136/622)!
Edit: Ok. Update complete, and all working well again. Itās even solved my non starting DAHDi issue 
Hi Andrew!
Unfortunately this breaks things royally for meā¦
Wanpipe no longer worksā¦
(Even if I revert the fix dicko had suggested but anyway I donāt think it has anything to do with my problemā¦)
Thereās something I want to try before creating a ticket, I just need to dig up the right commandā¦
I will keep you postedā¦
Have a nice day!
Nick
OK, I was hope running weak-modules --add-kernel would work but it didnātā¦
I get this when fwconsole tries to start the Wanpipe drivers for my Sangoma A200.
########################################################################
# Sangoma Wanpipe #
# Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script #
# v2.51 #
# Sangoma Technologies Inc. #
# Copyright(c) 2016. #
########################################################################
Warning: Dahdi modules not found: Wanpipe not build for DAHDI
Error: Dahdi and/or Zaptel modules not found! Please install DAHDI and compile Wanpipe for DAHDI!
Starting WAN Router...
wanrouter: Wanpipe Module: sdladrv not found !!!!
WANPIPE drivers must be compiled as modules
Check kernel configuration in /usr/src/linux/.config:
CONFIG_WAN_ROUTER=m
CONFIG_VENDOR_SANGOMA=m
Error Output:
================
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.eth0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
modinfo: ERROR: Module sdladrv not found.
modinfo: ERROR: Module sdladrv not found.
All of this over a RED background (if you ever see it you will see why I put it in capsā¦ 
)
sdladrv doesnāt exist for that kernel (and weak-modules --add-kernel probably consider this kernel different enough that it doesnāt want to do the symlinks).
I will see what i can do about starting the box with a kernel that has the necessary modules and hope thing workā¦
Have a nice day!
Nick
Maybe the drivers are installed in the wrong directory?
This guy had the same problem in the past:
Hi!
Thank you but they are actually missing this timeā¦ I even reindex the index used by locate to make sure of thatā¦
With the previous kernels it was an easy fix with weak-modules --add-kernel but not this timeā¦
Have a nice day!
Nick
OK, editing the grub config file to choose the previous kernel offered worksā¦
I donāt have time to debug this more tonight to see if anything can be doneā¦
Those Sangoma Wanpipe drivers are apparently provided by kmod-wanpipe. The version I had currently is 7.0.20-9.sng7ā¦
Have a nice day!
Nick
Hi!
I created the following ticket: Latest system updates (October 2017) breaks Wanpipe drivers.
Have a nice day!
Nick
Hi!
I guess I should add more information as to how I was able to update considering I ran the earliest available distro upgrade āscriptā so it was to be expected that without helping things somewhat I would get conflictsā¦
I had already cleaned up a long time ago packages such as the ql* ones which I knew were from the preceding distro.
I had to remove the fail2ban-server package to allow for the installation of the fail2ban-fpbx oneā¦ That is unfortunate because the fail2ban-server package (which came from the sng-epel repo) is of a more recent version than the fail2ban-fpbx oneā¦
After that I was able to update the packagesā¦
I got a few warning about. rpnnew files being created (I will have to check what is different between the ones I have and the new ones) and a few other warnings one of them about some sort of secure kernel configuration but unrelated to the Wanpioe driversā¦
I was actually looking forward to the kernel update which is breaking things for me because I was aware of some of the vulnerabilities it fixes (one of which is Blueborne which just got patched on my mobile phone as wellā¦)ā¦ I am hoping that a matching kmod-wanpipe package will soon be releasedā¦
Have a nice day!
Nick