Unimpressed - Auto update has left me with a broken system!

[leonp]

Hi,

Not very impressed at the moment.

It auto updated to V16 last weekend and now none of my Call Flow Designer Apps are working, taking out half of my phone system.

Why would it auto upgrade to V16 when features are in use which are not supported in it?

Really hope someone from 3CX contacts me ASAP. Tried contacting them, got redirected to a partner who want to redirect me to 3cx and round we go.

 

[leonp]

The thing bugging me the most about this on reflection - is that I'm not sure I even had auto updates enabled.

 

[cobaltit]

Oddly enough it auto-updates if you check the box to auto-update. Auto-update is designed to do one thing; check to see if there is a newer version and then automatically update if it finds one. It's not there to evaluate how you use the system. That's the job of the admin to be aware of the changes announced well ahead of time and then realize that maybe they should turn auto-updates off.

In the mean time you would simply take your v15.5 backup and then uninstall and reinstall. You may need to contact 3CX sales to have them flag your license for v15.5 . This is also documented in the forums as you are not the only person to be auto-updated.

 

[cobaltit]

The thing bugging me the most about this on reflection - is that I'm not sure I even had auto updates enabled.

If that is the case then that is unfortunate. Most folks with auto-updates off haven't had an issue but there have been a handful of folks mention (including partners) that they believed auto-updates was off but it still updated. I haven't seen any official 3CX confirmation that this is possible or proven.

 

[Evolute IT]

That's the job of the admin to be aware of the changes announced well ahead of time and then realize that maybe they should turn auto-updates off.

So many people are mad at 3CX for that. I saw about 25 posts just about CFD and another 10 about auto-update.

I just wish people would understand auto-update is a feature for a lab instance, not production. Who let Windows Server autoupdate? No one for many reasons!

 

[cobaltit]

So many people are mad at 3CX for that. I saw about 25 posts just about CFD and another 10 about auto-update.

I just wish people would understand auto-update is a feature for a lab instance, not production. Who let Windows Server autoupdate? No one for many reasons!

Well the bigger problem is the lack of granularity for auto-updates. If you have hundreds of instances you manage I doubt you want to manually update each and every one of them. But 3CX auto-updates needs to be more configurable to have control over major/minor version updates as well as a delay. In your example we have Windows Servers that auto-update but it's configured to run in a defined maintenance window and with a delay after patches are released. The current 3CX implementation is basically to auto update immediately which is like running Windows Updates on patch Tuesday; generally a bad idea. Let someone else be the guinea pig.

I think the instance manager is going to give folks with many instances more control to be able to do things like update in bulk.

 

[Evolute IT]

Well the bigger problem is the lack of granularity for auto-updates. If you have hundreds of instances you manage I doubt you want to manually update each and every one of them. But 3CX auto-updates needs to be more configurable to have control over major/minor version updates as well as a delay. In your example we have Windows Servers that auto-update but it's configured to run in a defined maintenance window and with a delay after patches are released. The current 3CX implementation is basically to auto update immediately which is like running Windows Updates on patch Tuesday; generally a bad idea. Let someone else be the guinea pig.

I think the instance manager is going to give folks with many instances more control to be able to do things like update in bulk.

I hope for exactly the same things! Maybe in SP1, looks like a lot will be in this update.

 

[JohnS_3CX]

After investigating some reported cases it appears there was a 3rd party remote management solution installed on Debian by our customers (not included by 3CX) that was configured to run a system wide upgrade command on Linux.

Please check your machines to see if you had anything similar or any scheduled jobs that would issue an upgrade command since this will automatically force upgrade your PBX too, regardless of whether you enabled updates via our management console.

 

[StefanW]

Well the bigger problem is the lack of granularity for auto-updates. If you have hundreds of instances you manage I doubt you want to manually update each and every one of them. But 3CX auto-updates needs ..

In this case we have the instance manager where you can bach upgrade remotely all your customers.
Just select X amount of them via the check box and press update, comment why and lean back!

 

[WolfgangOne]

I really don't mind auto-updates for minor version things. But I'd just like 3CX to know just how terrible they made my morning. Major version changes with known major functionality removal should absolutely not happen without human intervention. I have too many other things to do to be keeping up with 3CX's blogs and nonsense, and even if I had known about the loss of functionality, unless it was explicitly stated, I would have completely assumed that it would not auto update that. Thank the deity of your choice that ours couldn't update, being Windows. Since I just learned how to use the stupid CFD and am quite happy with the results. In the meantime, thankfully, only one of my customers broke - just too bad it was the one that's always been the biggest nuisance. And all that stress just to find that their call queue functionality was removed. Fairly easily fixed by moving to a ring group, at least for these people.

And now I've turned auto-update off on all my instances.

Oh, and? Most of my other systems like to brag about what's new in the new version with a splash screen or other such notification. Either before or after the upgrade. This draws more attention to the changelog and so forth. Rather than just logging in and finding everything looks almost exactly the same. For that matter, it could have told me as soon as I logged in that I had something routed to an invalid destination (i.e., the newly-unavailable call queue).

Rant over.