SOLVED Sysadmin won't update

jeff.h

Guru
Joined
Dec 1, 2010
Messages
502
Reaction score
71
The module will update in Module Admin, but Webmin keeps telling me there is a package update as well, however it keeps giving an error about freepbx being required.

It is doing this on 4 physical machines and one VM. Three physical machines and were installed from PIAF 2.0.6.4 64bit the other physical and the VM are from 2.0.6.5 32 bit. All are updated to the latest versions of everything.

I uninstalled via YUM then tried to reinstall and it gives the same error and now I am without the package completely.

root@pbx:~ $ yum install sysadmin
Loaded plugins: fastestmirror, refresh-packagekit
Repository schmooze-commercial is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: mirror.linux.duke.edu
* extras: mirror.linux.duke.edu
* piaf64: 192.210.137.132
* updates: mirror.linux.duke.edu
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package sysadmin.noarch 0:2.7.0-178_centos6 will be installed
--> Processing Dependency: freepbx for package: sysadmin-2.7.0-178_centos6.noarch
--> Processing Dependency: apcupsd for package: sysadmin-2.7.0-178_centos6.noarch
--> Running transaction check
---> Package apcupsd.i686 0:3.14.10-1.el6 will be installed
---> Package sysadmin.noarch 0:2.7.0-178_centos6 will be installed
--> Processing Dependency: freepbx for package: sysadmin-2.7.0-178_centos6.noarch
--> Finished Dependency Resolution
Error: Package: sysadmin-2.7.0-178_centos6.noarch (schmooze-commercial)
Requires: freepbx
You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest
 
Hi,

You should report that to freepbx through the bug tracker, there is indeed an added dependency in the latest sysadmin RPM (sysadmin-2.7.0-178_centos6.noarch) that was published 2 days ago.
The previous version (sysadmin-2.6.1-177_centos6.noarch) doesn't have this dependency.

So in the mean time you should be able to install the previous version with:
Code:
yum install sysadmin-2.6.1-177*
Which is probably what you had before you uninstalled it.
(You don't say what version of the package you had before you uninstalled it...)

Webmin will continue to say there is a more recent version... indeed 2.7 is newer but contain the unresolvable dependency...

I haven't look further, it's probably the case that this dependency is valid under the freepbx distro but under PIAF, freepbx is not delivered through RPM and this dependency can't be fulfilled.
Either they maintain 2 sysadmin package and some error was made, or only one sysadmin package is maintained and it should not depend on the freepbx package that is only applicable to freepbx distro. I'm not blaming anyone or anything, just surfing on the issue at 60K feet, trying to help.

Like I said, haven't checked a lot, so a lot could be wrong but in the mean time you should have no problem with the proposed solution and ignoring further webmin notices.

reconwireless phoneguy
 
This would have to mean that PIAF installation performed for the last 2 days would have faced the same issue, trying to load the latest sysadmin module with the unresolvable dependency?
darmock wardmundy
 
Since we started using the schmooze repo for freepbx stuff as was suggested by the freepbx folks instead of using our own static repo we have in essence turned over control to them for the freepbx stuff. So if there is an error in dependencies it needs to be addressed by them. Stuff happens when it is out of direct PIAF control......


Have a great day


Tom
 
Thanks folks. I used the previous version as Hykos had suggested and that's returned the functionality.
 
So if there is an error in dependencies it needs to be addressed by them.

Thanks folks. I used the previous version as Hykos had suggested and that's returned the functionality.

Opening bug tickets is a great way to give back to the project and make it better, We can't really help those that don't help themselves, it literally takes about 30 seconds to open a bug ticket, like darmock said if something needs to be addressed by the FreePBX development team, you need to open a ticket.
 
Hyksos if you have not used that account since august when we migrated it takes about 30 minutes or so for the usernames and passwords to sync over, you should be good now.
 
Great, Looks like the issue is now fixed, resolved by the FreePBX development staff in about 30 minutes, on a Saturday night once the ticket was submitted. Now back to your regularly scheduled weekend.
 
Hey, thanks guys, I was working from my iPhone earlier today when I got it fixed on my box and was going to submit a bug when I got back home, but it looks like you all got it handled already. Thanks!
 

Members online

No members online now.

Forum statistics

Threads
26,688
Messages
174,412
Members
20,259
Latest member
Fadeek86
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top