Toggle sidebar Toggle sidebar

debian update policy - 3cx debian still at debian 12.9

ITSupportCyb

Customer
Joined
Mar 22, 2024
Messages
4
Reaction score
2
hello,

i see that debian bookworm in 3cx is still at 12.9 ( /etc/debian_version) while regular debian is at 12.11

some coleague made an error with adding package repo for monitoring agent and our 3cx system accidentally updated to 12.11 and is "out of support" now (running fine, though)

the question is if i just simply should wait until this fixes itself or if we should downgrade the accidentally upgraded packages.




https://en.wikipedia.org/wiki/Debian_version_history

 
hello, can nobody answer this?

perhaps anybody who is using 3cx on prem could check which debian_version is their own 3cx install ?
 
Hi,

I have a U6 Build 675 On Prem that's showing Debian 12.11, no custom debian shenanigans, just normal updates through 3CX.
 
  • Like
Reactions: Evolute IT
Support will also tell you to not install any 3rd party stuff and to leave 3CX to run alone.
 
  • Like
Reactions: Evolute IT
  • Like
Reactions: Saky and paulodagraca
FYI going forward, 3CX advises to not update at the command line. Their recommended method is to enable automatic update in 3CX (even if temporarily) which installs updates to 3CX and Debian. A manual update in the 3CX GUI updates only 3CX.
 
  • Like
Reactions: bitn2, KyriacosS_3CX and Evolute IT
SteveITS said:
FYI going forward, 3CX advises to not update at the command line. Their recommended method is to enable automatic update in 3CX (even if temporarily) which installs updates to 3CX and Debian. A manual update in the 3CX GUI updates only 3CX.
Click to expand...

How about for SBCs? I regularly log into mine and run "apt update", "apt upgrade", "apt autoremove" on the CLI.

I am interested in upgrading my Raspberry Pi SBCs to Debian 13, as I cannot safely update my switch firmware when I have two Raspberry Pi SBCs in a HA pair, as the SBC functionality runs into all sorts of troubles as I have posted about here:

Thread 'Will Debian 13 fix the SBC HA Cluster Breakage Issue?'

In reference to the SBC High Availability docs and quoting from the last bullet point of "Known Issues and Limitations"
  • If local network connectivity is temporarily disabled or broken for any of the member nodes, the clustering service may not recover when connectivity is restored. Ensure network connectivity between the member nodes, to avoid causing nodes to assume the active role concurrently and activating the cluster resources on both nodes. This issue is to be resolved in a subsequent Debian / Raspbian Linux version.
Click to expand...

I have this exact issue when doing...
 
the SBC is different actually, 3CX has posted to install updates manually.

For version upgrades they had https://www.3cx.com/blog/news/sbc-eol-upgrade/ which isn’t for D13 yet since it’s new. And for Pi it’s a reinstall anyway.
 
OK I'll continue to update my SBCs manually.

I checked here https://www.raspberrypi.com/software/operating-systems/ and see the latest is still D12. I queried AI on an expected release date for Raspberry Pi OS Lite based on Debian 13 ("Trixie") and it said beta images are expected soon. It also said an in-place upgrade should work, but not recommended for production use.

I am desperate for a fix for SBC HA failover "split brain" issues that occur when updating switch firmware, as described in that other thread.
 
You must log in or register to reply here.

Latest Posts

Members Online Now

No members online now.
Total: 195 (members: 0, guests: 195)

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom