Upgrade from 13 to 14 Error on phase 2

[dicko]

lsof -i :96```

[digitalb]

Both reported back blank

[GameGamer43 (Bryan Walters)]

Try running the following to get apache back

mv /etc/httpd/conf.d/schmoozecom.conf /etc/httpd/conf.d/schmoozecom.conf.bak
service httpd restart

[Michael1490 (Michael Kreg)]

Running this command also got me past the loop.

yum remove asterisk-sounds-core-en-gsm-1.4.25-94_centos5.noarch

Now when I run the distro-upgrade, it stops at these dependencies.

Resolving Dependencies
→ Running transaction check
—> Package preupgrade-assistant.x86_64 0:1.0.2-36.0.1.el6.centos will be installed
→ Processing Dependency: python(abi) = 2.6 for package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64
→ Processing Dependency: librpmio.so.1()(64bit) for package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64
→ Processing Dependency: librpm.so.1()(64bit) for package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64
→ Processing Dependency: libpcre.so.0()(64bit) for package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64
—> Package preupgrade-assistant-contents.noarch 0:0.5.14-1.el6.centos will be installed
→ Finished Dependency Resolution
Error: Package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64 (upgrade)
Requires: libpcre.so.0()(64bit)
Error: Package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64 (upgrade)
Requires: librpm.so.1()(64bit)
Error: Package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64 (upgrade)
Requires: librpmio.so.1()(64bit)
Error: Package: preupgrade-assistant-1.0.2-36.0.1.el6.centos.x86_64 (upgrade)
Requires: python(abi) = 2.6
Installed: python-2.7.5-48.el7.x86_64 (installed)
python(abi) = 2.7
python(abi) = 2.7
Available: python34-3.4.5-4.el7.x86_64 (sng-epel)
python(abi) = 3.4
Available: python36u-3.6.1-2.ius.centos7.x86_64 (sng-pkgs)
python(abi) = 3.6
python(abi) = 3.6
You could try using --skip-broken to work around the problem
** Found 3 pre-existing rpmdb problem(s), ‘yum check’ output follows:
mysql-init-fixer-1.0.0-4_centos6.noarch has missing requires of mysql-server
mysql-log-rotate-1.0.0-1.shmz65.5.7.noarch has missing requires of mysql-server
2:vim-enhanced-7.4.258-1.shmz65.1.4.x86_64 has missing requires of perl(:MODULE_COMPAT_5.10.1)

[digitalb]

That did it thank you.

[BlazeStudios (Tom Ray)]

@tonyclewis

The reason you need to use the upgrade scripts is FreePBX requires PHP 5.6 that is only available on SNG7 and not the old unsupported SHMZ OS 6 so we need to first upgrade the OS and all the packages.

I’m just looking for clarification on this statement since @tm1000 stated about two weeks ago that the FreePBX 13 Distro is supported for the next four releases. Your statement is saying that the FreePBX 13 Distro is unsupported. Which is it?

[cynjut (Dave Burgess)]

@BlazeStudios

Your statement is saying that the FreePBX 13 Distro is unsupported.

I’m not clear how you got from “PHP 5.6 is only available on SNG7” to “FreePBX Distro is unsupported”. The Distro is the distro - it’s a package deal.

[BlazeStudios (Tom Ray)]

@cynjut

I’m not clear how you got from “PHP 5.6 is only available on SNG7” to “FreePBX Distro is unsupported”. The Distro is the distro - it’s a package deal.

First, FreePBX 13 and FreePBX 14 are two different versions of the Distro. There is an ISO that will install only version 13 and an ISO that will install only 14. Additionally, each version is “packaged” with a different underlying OS for them.

So in order for both to be supported the development/support of the code for each version has to be maintained. For example, if there is a bug found in the IVRs module and it impacts both those using FreePBX 13 and FreePBX 14 now if FreePBX 13 is still supported a fix will be released that applies to each VERSION, because they are different. If FreePBX 13 is not support then the fix will only be released for FreePBX 14. Anyone that is still on FreePBX 13 will be told the fix is to “upgrade to 14”.

Your logic of the “Distro is the Distro” would imply that versions such as 2.8, 2.9, 2.10, etc are still supported because they are “Distro” and that would be utterly and completely wrong.

And since FreePBX 13 is running a different OS and the modules run under an old version of PHP 5.3 asking how long it has support is a valid question because that will require maintaining a separate support channel for the v13 distro/modules. As it stands right now there is no released documentation that I have found that shows the End of Life timeline for FreePBX 13 or even if/when FreePBX 13 moves to a Security Fix Only status.

[tm1000 (Andrew Nagy)]

@BlazeStudios

I’m just looking for clarification on this statement since @tm1000 stated about two weeks ago that the FreePBX 13 Distro is supported for the next four releases.

I never said this. What I did say is freepbx 13 is supported for security fixes for 4 releases back. So when freepbx 17 is out 13 is still security fixes.

Freepbx is also supported in bug fixes two versions back. So when 15 is out 13 will still be supported.

You asked about how long the distro is supported and you said I said that distro 13 is supported for four releases. I never said anything like that about the distro. Distro 6 is unsupported like Tony said. Meaning the distro. Not freepbx. They are separate.

[BlazeStudios (Tom Ray)]

Thanks, answers my question.

Distro 6 : 10.33.66-20 <-- Last update to be expected. Makes sense.
v13 Modules: Supported until v16 release than SFO until v18 release