In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
asterisk ippbx not working after yum update
Dear Experts:
We have deployed asterisk ip-pbx for our sales operation with xorcom appliance other than default shipping this required custom coded from the developer done in PHP. eveything was working fine but recently after yum update the service affected. now that devloper still working to fix.
Developer said update was required for asterisk hence did yum update and this broke the code.
I think instead of using yum update could have used stand alone appliacation wise update.
Please tell me how to handle such sitation
1.Is it possible to undo the yum update process to restore to previous.
2. what measures the developer should take before going for yum update.
3. how to avoid yum update affecting astersik, php , freepbx and dhadi
Please suggest.
We have deployed asterisk ip-pbx for our sales operation with xorcom appliance other than default shipping this required custom coded from the developer done in PHP. eveything was working fine but recently after yum update the service affected. now that devloper still working to fix.
Developer said update was required for asterisk hence did yum update and this broke the code.
I think instead of using yum update could have used stand alone appliacation wise update.
Please tell me how to handle such sitation
1.Is it possible to undo the yum update process to restore to previous.
2. what measures the developer should take before going for yum update.
3. how to avoid yum update affecting astersik, php , freepbx and dhadi
Please suggest.
Asked:
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
http://www.tomvernon.co.uk/blog/2011/03/roll-back-rpm-packages-centosredhat/
I've never used it myself and just looked it up to see if it could be done. Since it's not default and it can suck up drive space I doubt it was enabled on the appliance setup.
Normally I would just be sure to have a backup before doing a update for a production system. Possibly going as far as pulling the drive and cloning it so I can switch it back really quickly by just putting the original drive back in.
Any chance you can get the original install back onto the appliance and go from there?
The catch with updates on systems that use binary packages - this means the programs are precompiled - is the the packages have to be built for the specific version of the system. So if you upgrade the core linux you must have a matching asterisk/dahdi/etc for the version you upgrade linux to.
If a system uses a source code package then you can recompile asterisk and its components for the new linux version. You can still have issues because sometimes things change and the compile will not run cleanly or the configuration is not exactly the same - but in general this works fine.
It can be hard to predict problems, like for example there was a bug fixed but your setup had a work around in place, so by fixing the bug the workaround may become a bug and the upgrade broke the setup.
Did asterisk completely stop or did the update only affect the developers changes?
The measures a developer should take is to test things before doing anything to a production system. Without knowing the details its hard to say if what has happened was somebody doing something stupid or it is some oddball problem. Any time there is customization doing a upgrade is more of a risk.
Just to be safe always have a full backup before tinkering with anything live. This way you know for sure you can always go back if something goes wrong. With appliance devices this is not always as easy as a drive clone, you may need prior firmware and configuration saves to restore a system.