Issues noted with in-place upgrade, 14->15->16

FreePBX Installation / Upgrade
1

We’ve done several of these over the last couple months and in all cases the upgrade process resulted in:

  • SangomaConnect being partially broken: Adding, removing, reactivating users non-functional. The only solution we have found is to remove all users and the module entirely and start from scratch.
  • Backup jobs lose their destination.
  • Backup schedule appears intact but doesn’t run.

I know the push is on to do backup/restore to v17, but I’m sure others are proceeding with caution, like us, and for them these notes might be helpful.

2

Curious what destination you were using ?

When it broke, was it on the last leg ie. 16 → 17 ? Or earlier ?

Backup/Restore should work - have you considered opening a backup issue on GitHub ?

3

FTP.

I don’t know.

13->14->15 causes it to break.
14->15 also.

I long ago gave up filing bug reports because they just turned into stupid, pointless efforts where I was told it wasn’t a bug and basically told to prove it or shut up. I post here so others know. If you want to fix it knock yourself out. But you should fix the two-years broken SangomaConnect license renewal system first. And yes, THAT is still broken. I had to call yesterday to get a renewal purchase fixed. If the wiki says it’s fixed, the wiki is wrong.

1 Like
4

Added a bug for the Backup jobs and schedules issues at [bug]: Backup/Restore failing on 14->15->16->17 - bad destinations and schedules · Issue #539 · FreePBX/issue-tracker · GitHub

Where on the wiki does it say that Sangoma Connect was broken but is now fixed ?

5

The person who fixed the license issue yesterday told me, “There’s a new wiki on this that says it’s fixed.”

I didn’t go looking for it. No idea where it is. I told him it’s decidedly not fixed.

The head doesn’t appear to know what the tail is doing.

2 Likes
6

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.