I am so discouraged with just simple upgrades. I have upgraded the modules, i’ve run yum upgrade. i ran the versionupgrade --check, everything came back green. I use Vultr so I consoled into the backend and ran the upgrade. I am still getting this error after trying to install Freepbx16
have you did search in a Forum ?
Yes, I searched in the forums for relevant update related posts. Many people have had similar issues, unfortunately most of them aren’t commented on or don’t have a resolution on them. When this happens, I reboot and nothing will work and of course these are production PBXs so I cant leave them down while I open a ticket.
Upgrade all modules and then try again. You can do via Linux CLI,
fwconsole ma refreshsignatures
fwconsole ma upgradeall
fwconsole chown
fwconsole r --verbose
I’ve tried these. It wont let me run any fwconsole commands.
I’ll try again tonight and copy and paste the error. These upgrade failures are very easy to replicate
how ? you can’t run fwconsole
at all on your PBX?
When I try to run fwconsole commands, it often mentions things are deprecated. Sometimes they mention curly brackets. It’s almost like framework didn’t get upgraded but the other stuff did or something.
I can easily replicate it though because it’s on a vultr vps and I Can roll back the snapshot.
Can you please open a case in support ? I can take a look if you give me the case number.
https://help.sangoma.com/community/s/create-a-support-ticket
I had to create a new account and its flagged for review.
01796637 is the case number.
Perfect, I took the case, will be working with you.
I got my side configured. Please proceed
I just wanted to say thank you for getting my system upgraded and showing me what you were doing. I have another PBX and I’ll use the same commands and version and let you know the outcome.
Again, thank you!
It was a pleasure to work with you Jeremy, have a great week !
and the issues were???
Still trying to figure that out. Had another PBX die off tonight with the same Database issue.
I had issues recently with a 15 to 16 upgrade. It turned out to be a buggy EPM module that didn’t correctly create new database fields in one of the tables. I fixed it by creating them manually and then after the fact found out it was the EPM. I think it was @kgupta that told me about the known issue and directed me to an edge version of EPM.
For shits and giggles I’ll do an edge of EPM. Thanks.
I’m going on the assumption that didn’t resolve my issue as it’s still at “running transaction” and if I ssh into another instance, it’s back to the SQL STATE[HY000] error. Ugh. I hate failed updates.