Checking prerequsites…
Checking bitsize of machine [ ] - x86_64
Checking available disk space [ ] - 745G Available
Checking for outdated system [ ✘ ]
This machine has pending yum updates. This machine must be up to date before
the upgrade tool is run. To resolve this issue please run ‘yum update’. The
output of ‘yum check-update’ is below.
I take it it didn’t want to remove other packages when you tried it (or at least something important like some packages want to when you want to remove them).
Please keep us posted!
If it does seem to work, please check to see if CDR/CEL is working, this is one of them problem you could have and when the rest is working is one of the last to be noticed…
You meant the package or the repo? It sounds like you meant the repo and I didn’t think removing a repo removed the packages that came from it (and that package was already installed).
Just to be sure as to what you are saying there, was that third party repo added by @Bradbpw or did it used to be there for the FreePBX 13 distro?
Would it be possible for the distro upgrade “script” to detect when someone had added repos, tell them to preferably remove them and tell them which package should preferably be removed because they came from it?
Obviously this problem is not caused by the distro upgrade “script”, it would have been present even before trying to run it but when it’s the distro upgrade “script” which recommends doing a yum update could it possibly check for things like that?
I know the scripts remove the old distro repos and replaces them with Sangoma 7 ones but what does it do when there are other repos which were not distributed with the distro?
I know @nsumner had problems with mongodb back when I upgraded my home server…
re:
but that was during actual upgrade and not during an update and that problem was more than likely fixed by later scripts (it was the first one publicly made available…).
I hope @Bradbpw will have good news for us tomorrow…
Unfortunately, I don’t have great news. I got past the Mongo packages obstacle, but now I’m having the same issue as tim007 had in this post
I had to leave it for the night and plan to pick it back up again tomorrow. @Marbled, I see you were helping Tim007 with this problem. Based on the thread, it doesn’t look like a solution was found. Do you know of a fix to this to keep the update moving?
For others the network connectivity problem seemed to be related to the use of a VM or some DAHDI cards (like the Sangoma A200).
Are you using either?
We recently identified a problem with that (which might very well be present during upgrade) so if you tell me you have one there are a few things I would like you to do…
But first, please tell me if you are using a VM or a DAHDI card…
To the best of my knowledge (I’m a novice) I am not using a DAHDI or VM (virtual machine). My PBX is basically an old desktop computer with that I turned into a PBX. My internet connection is direct into my motherboard.
I attempted to look at my resolv.conf file to check DNS entries like tim007 did, but I can’t get a command line. I’m stuck at this screen below. I’ve tried ctrl+c and several other potential keys to get a command line. I even ran my hands over the keyboard in frustration, but can’t get a command line. Is there a trick to get a command line?
The computer is just an old desktop that we stuck in a server chassis. We plug right into the motherboard. I’ve been using it as our primary PBX with FreePBX for 4+ years.
Since Sangoma 7 is a Centos derivative it is most likely disabled there as well…
There is a chance that adding kmod-forcedeth from the http://elrepo.org repos might work but if you have a spare supported network card you could put in that system it would be a lot simpler and far less prone to causing more problems in the future…
Since you have no network connectivity it will also be a pain to get the driver there…
Is there any chance of adding a discrete network card?
I am unable to identify the chipset from the pictures but some people are complaining about lack of compatibility with quite a few OSes, including some version of Windows (which is surprising)…
] - x86_64
