How to Upgrade FreePBX Distro 13 to 14

[Marbled (Nicolas Riendeau)]

Hi!

@psdk

So SNG7 has problem with NIC on VMWare and doesn’t detect any network adapter?
Because I install FreePBX 14 from .iso, and it doesn’t detect NIC too.

Right now there are like 3 (known) problems that can cause loss of network connectivity.

• Running under a VM with a VMware specific NIC. I would not be surprised you could have the same problem with other VM solutions though…
• Having some types of DAHDI hardware. The ones which seem to be causing problems right now are the ones who appear like network cards to the system once their drivers are loaded.
• In some situations having IPv6 activated on your system.

@psdk

I hope Sangoma guys solve this problem as soon as possible.

I don’t think it’s that easy in this case since this problem was reported early on by one of the early testers (ie @waldrondigital) over a month ago.

I was one of those early testers and had the loss of network connectivity problem but in my case early on it seemed to be related to my DAHDI card which, once it’s drivers are loaded, appears like a network card.

(I could not say with certainty until very recently…)

Back when I ran the distro upgrade “script” there were other issues with those DAHDI drivers and the ones specific to my card (Wanpipe drivers for my Sangoma A200) and it looks like this might actually have helped in some ways because I think it might be once those DAHDI drivers got updated/moved out of the way that my system network connectivity was restored.

I still had a problem which was causing a slow but for me but lost of network connectivity for others which I thought I fixed this week but I had a weird problem today so I am not sure anymore.

Each time someone reports a network connectivity problem my first two questions are “Are you running a VM and do you have DAHDI hardware?” because, early on, this seemed to be what was tying those network connectivity problems together…

(It’s actually me who referred @mattbratt to the post he referred you too like a day or two ago… )

I believe the network connectivity test is actually in response to the network connectivity problems @waldrondigital and me had that this test was added to stop the upgrade as soon as the problem was noticed…

I have not played with VMs in quite a while but Iwould not be surprised it would a missing driver thing and that they might not be allowed to distribute the VMware one or something like that…

What I guess they could do is try to detect your network card is setup like this and tell you to change before allowing the script to run further.

As for IPv6, someone reported having IPv6 activated was causing him DNS issues and those tend to look like network connectivity problems even though it is something only name resolution problems…

Of those problems, as an early tester, I only had one but had quiiiiite a few others, most of which have been fixed…

Good luck and have a nice day!

Nick

[Marbled (Nicolas Riendeau)]

Hi!

@mattbratt

FWIW, in my experience, I wouldn’t migrate to FreePBX 14 from a prior version if it is a production system. As noted before, the script is currently in beta.

As I said here:

How to Upgrade FreePBX Distro 13 to 14

Hi! The distro upgrade “script” is available but still beta… Some people barely had any problems (or problems which were easy to solve) while others had problems which required restoring and going back to FreePBX 13… I ran it about a month ago when it was first made available and it broke my system. However I was able, with help from the FreePBX devs, to get it back to working order without requiring a reinstall… Some people were not so lucky… There wasn’t only thing that got broken but mu…

Only consider running it if you have a looooooooot of time on your hands which is something usually not possible in Production…

@mattbratt

All seemed fine until later I discovered CDR not working, dependencies not correct, and could not install system updates because of that.

CDR, when lost during the upgrade, are usually caused by one of two things…

• odbc.ini got moved out of the way into odbc.ini.rpmsave…

re:

UCP data stopped after upgrade to FreepBX 14

Hi! Does CDR and CEL work at all from the Dashboard? (edit: by at all I mean do you see anything added to it or is it just stale data from before the upgrade?) After the upgrade that no longer worked for me, see https://issues.freepbx.org/browse/FREEPBX-15491?focusedCommentId=108408&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-108408 (and the next 2 messages that follow it). I had to recopy odbc.ini (in /etc I believe), as it was no longer present. I had …

• Somehow the proper asterisk*-odbc package was not installed…

re:

CDR not working after FreePBX 13 to 14 upgrade

Bonjour Jacques! (Hi Jacques!) Now things are starting to make sense… Can you do yum install asterisk13-odbc (if you are running Asterisk 13) or yum install asterisk14-odbc (if you are running Asterisk 14) and post the results back? Do you get any error message, warnings about missing depencies, etc…? If it installs properly, can you retry reloading the module (it might require a reboot but I don’t think so, at least to try to load it). Good luck and have a nice day! Nick

(and the message after it)…

I actually opened a ticket for it even though I did not have this specific problem, see FREEPBX-1581.

Unfortunately since I did not have that problem I cannot provide the logs @GameGamer43 is asking for in that ticket… If anyone encounters this problem please upload your logs to this ticket so he can track down the problem…

If you mentioned this problem on the forums and I did not suggest this (or if it did not work), I am sorry…

As for dependencies, this type of problem or something different?

Sangoma 7 upgrade script failing

Hi and thank you for your input! Did it complete successfully? I see the same problem in the logs I put in the ticket, ie Error: nodejs-docs conflicts with 2:nodejs-8.1.4-2.14.x86_64 Error: Package: 2:nodejs-devel-8.1.4-2.14.x86_64 (sng-pkgs) Requires: nodejs(x86-64) = 8.1.4-2.14 Removing: 2:nodejs-6.9.5-1.7.x86_64 (installed) nodejs(x86-64) = 2:6.9.5-1.7 Updated By: 2:nodejs-8.1.4-2.14.x86_64 (sng-pkgs) nodejs(x86-64) = 2:8.1.4-…

By the way, I did remove those conflicts manually after…

The only one which needed special treatment was kmod-dahdi IIRC…

@mattbratt

Once in, I did a few minor adjustments, like disabling IPv6, etc…then restored my settings from my botched 14 migrated system.

I did consider that once my system started working but I wanted to see if I could figure out how to fix all the issues I had and report them if it seemed like it was unlikely it was fixed…

Have a nice day!

[Marbled (Nicolas Riendeau)]

Hi!

@ecarlseen

I kind of expected something along those lines if we migrated now, but we weren’t sure about the ramifications of holding off and were trying to figure out what to do. I think that at this point we’ll wait it out.

Chances are, if your system is relatively stock and

• Not running on a VM.
• Not using some type of DAHDI hardware.

You might not have problems or have problems which are easy to fix and already have documented fixes…

Problem is you might not notice them immediately (like non-working CDR) and once you do it might be too late and you might have lost information you had to keep (like those CDR entries…).

One person had a non-working Fax Pro module and IIRC it was down for days until it was found his system was missing a package because the content of one package was split into two on the new distro upstream (It’s Centos based)…

The Fax Pro module might be commercial I believe you kind of say your (official) commercial support goodbye until it is out of beta…

Hopefully he doesn’t use much faxes anymore but still needed this to work…

You might also have the weirdest of problems we have not encountered before of don’t have easy and documented fixes and go back to FreePBX 13 and restore from a backup.

I ran the distro upgrade “script” on a system you could call “Production” but it’s the system I use for my home phone…

If things don’t work quite right there is an automatic failover of the most important phone line(s) to mobile phones and I can temporarily setup something (I did setup an ATA as a temporary solution) if things take too much time to resolve…

Even though it’s the system which handles my home phone it’s also a test system as well with multiple DIDs, VoIP providers, outbound routes, etc… Not exactly a company phone system but definitely more than an home phone system…

I made sure I had backups, time and was willing to have downtime if it turned out to be necessary but there were while for you acceptable downtime might be like 4 hours, mine was more than 4 days (of course after having setup that ATA…).

Good luck and have a nice day!

Nick