Hi! I have a production Elastix 4 setup, that I want to upgrade to Issabel. The forum entries seem to give fragmented information on how to do this. I'm by no means an expert, so this are all trial-and-error, works-on-my-machine ideas.
Why not just fresh install from DVD? Because my system is in production, I want to continue using it but now with Issabel, without having to reconfigure everything. So I setup a "lab" machine, installed Elastix 4, updated everything (yum update, yum upgrade), imported part of my production setup (extensions) just to make sure it has something inside, and then tried:
cd /etc/yum.repos.d
mkdir old
mv elastix.repo old/
mv commercial-addons.repo old/
curl http://repo.issabel.org/issabel/4/Issabel.repo
chmod 766 Issabel.repo
yum update
(all this has been described in other posts)
Probably a
yum clean
would be a good idea, before the update.
Somewhere in the way I tried
yum remove elastix elastix-framework
But I'm not really sure this had any real effect.. After updates and everything yum update gives me an error (also posted before, I write this in spanish):
Paquete issabel-endpointconfig2.noarch 0:4.0.0-1 debe ser instalado
Procesando dependencias: issabel-agenda >= 4.0.0-1 para el paquete issabel-endpointconfig2-4.0.0-1.noarch
...
Paquete elastix-endpointconfig2-4.0.0-3.noarch (@elastix-updates)
Necesita: elastix-agenda-4.0.0-3.noarch (@anaconda)
...
Obsoleto por: issabel-agenda-4.0.0-1.noarch (issabel-base)
No encontrado
So it seems that issabel-agenda is needed, it points to elastix-agenda, which is not available. And this goes in a loop, so you can't remove this problem and you can't install agenda.
Aftere several trials I was finally able to install agenda and get rid of the error, now it seems that Issabel (Elastix 4 upgraded to Issabel 4) is running smoothly. What I did was simple:
cd /tmp
curl http://repo.issabel.org/issabel/4/base/x86_64/RPMS/issabel-agenda_4.0.0-1.noarch.rpm
yum -i --force --nodeps issabel-agenda_4.0.0-1.noarch.rpm
And that did the trick: agenda is working and no more yum update errors. I'm pretty sure this is not the best way, and there's an error somewhere, but it got Issabel working ok. I probably didn't need to download the RPM, the --force and --nodeps could have done the same, but that's what I did...
Also, my passwords were messed up (couldn't web login). Running issabel-admin-passwords got stuck since it couldn't connect to MySQL (MariaD
. So I did:
vim /etc/issabel.conf
Edited mysqlrootpwd=[TO MY ORIGINAL PASSWORD]
And now issabel-admin-passwords --change ran ok and I was able to update all my passwords.
So I'm all happy with an Elastix 4 -> Issabel 4 upgraded system (lab, not production) all running! Still, I'm going to repeat the whole process again before I try it on the real production PBX.
Since I knocked my head quite a few times with this, I thought some of this might be usefull... hope it does.
Regards, Gonzalo.
