Hi Stassen, What issue did you find in repos?
I’ve got a second FPBX distro that I’m trying to build as an Advanced Recovery partner for the install that’s currently got Modules GUI problems, and this other distro install is doing just fine. So I checked files in etc/yum.repos.d and the files are identical to those in the broken build.
I had a look at the RPM-GPG-KEY-Sangoma-7 file mentioned in the repos and that’s the same across both installs too. See
What did you see that was broken in the repos?
In the screen shot at the top of the thread, I clicked the link to create a report to the PBX bug tracker.
Their response restated what the screen shot error messaging said (delete the contents of yumwrapper) which I’d already done, and I had mentioned above that I’d already done it.
However, I just followed their instruction just now and deleted the contents again (4 .log files), but this time I didn’t bother with the clean/upgrade/reinstall operations for yum. I checked back to the Module Admin page ------- and it’s working!
So I’m thinking that I read too much into the problem from other posts w.r.t yum, and carried out operations that interfered somehow.
Whatever the situation, and whatever the problem was, we’re back in Module business, which is great.
In my situation I saw a difference in repo’s between the 2 instances. I’m not aware that I manually changed something in that area, but because 1 instance could be upgraded, I used the repo definition as a basis for the instance with an issue
I had the same issue right after updating from version 15 to 16 earlier today, deleting the /dev/shm/yumwrapper didn’t work, I did it and retried, but every time I got the same error. I even tried to delete, reboot and try again.
So I ended up using the terminal: I did a “yum update”, updated some packages and received a very interesting warning about old references (while I was upgrading I remember selecting an option to update the sources) so I decided to do “yum history new” to refresh references, and it did the trick for me, I hope it doesn’t break anything but so far it’s working and I don’t get the error while doing the update on the web anymore.