Solved SBC won't update

[Lee Cramman]

18.0 (build 1880) hosted with Google.

We have 2 SBC's running bare metal that were both on 18.0.27. An update alert popped up so I tried to update them one at a time through the web management portal.

SBC1 updated and very quickly came back online with version 18.0.30.

SBC2... didn't. Tried a few times, nothing. SSH'd in, tried manual upgrade using apt-get, nothing other than "The following packages have been kept back: linux-image-amd64". Tried a reboot, and repeated previous steps, nothing. I note that even though the server has rebooted the uptime is still showing as 27 days .

Any ideas how I can force the upgrade or where I should start troubleshooting please?

 

[SteveITS]

If SBC2 is working, I would be tempted to wait until this release is out of beta and try then. (rather than forcing it)

 

[DSXVOICE]

sudo apt-get dist-upgrade will install the held-back package as well as everything else that's needed. If the machine is just an SBC you should be safe doing that. If it has other missions, a dist-upgrade may have unintended consequences. In which case, you could try sudo apt-get --with-new-pkgs upgrade if you want to be conservative.

 

[AWS2P]

I get the same "nothing happens" with a PI3B+ SBC actually in 18.0.27 other PI4 are all updated in 18.0.30 very quickly

 

[ChrisC_3CX]

This may be related to the repositories, give the following a try:

1. SSH to the sbc host.

2. navigate to:

/etc/apt/sources.list.d

3. move everything other that "3cxpbx.list" and "3cxpbx-testing.list" out of this directory.

4. run:

sudo apt update

5. Try upgrading again

 

[Lee Cramman]

If SBC2 is working, I would be tempted to wait until this release is out of beta and try then. (rather than forcing it)

That would be the sensible option, but unless this problem is known to 3CX (i.e. a bug that gets fixed) won't the problem just be present in the proper release? Unless the problem is the machine in which case, it would also still be present.

I suspect it must be the latter or else there would be loads of people on here with the same problem rather than just the odd one.

sudo apt-get dist-upgrade will install the held-back package as well as everything else that's needed. If the machine is just an SBC you should be safe doing that. If it has other missions, a dist-upgrade may have unintended consequences. In which case, you could try sudo apt-get --with-new-pkgs upgrade if you want to be conservative.

The machine is just an SBC. I did think about the --with-new-pkgs flag rather than using disty-upgrade because some light Debian forum reading suggests that using dist-upgrade may cause problems further down the road..

To be fair, blowing away the install and starting again isn't exactly a huge hardship but stuff like this gets me curious...

However, I wonder if @SteveITS has a point, I should just leave this alone until the proper release.

I get the same "nothing happens" with a PI3B+ SBC actually in 18.0.27 other PI4 are all updated in 18.0.30 very quickly

Good to know I'm not the only one, although I'm on x86 silicon rather than using a Pi.

 

[Lee Cramman]

This may be related to the repositories, give the following a try:

1. SSH to the sbc host.

2. navigate to:

/etc/apt/sources.list.d

3. move everything other that "3cxpbx.list" and "3cxpbx-testing.list" out of this directory.

4. run:

sudo apt update

5. Try upgrading again

Weird, both 3cxpbx.list and 3cxpbx-testing.list do not exist in /etc/apt/sources.list.d.

There is a single entry which relates to some remote monitoring / access software we use, I have moved this out and run apt update but can't give the upgrade another try until after closing time.

 

[ChrisC_3CX]

Lee Cramman said:
Weird, both 3cxpbx.list and 3cxpbx-testing.list do not exist in /etc/apt/sources.list.d.

In that case, you'll have to create them as follows:

File "3cxpbx.list" must contain the following line:

deb http://downloads-global.3cx.com/downloads/debian stretch main

File "3cxpbx-testing.list" must contain the following:

deb [arch=amd64] http://downloads-global.3cx.com/downloads/debian stretch-testing main

Note: If you're running Debian 10 (Buster) replace the word "stretch" with "buster".

Once you've created the files you will have to run "apt update" again.

 

[SteveITS]

but unless this problem is known to 3CX (i.e. a bug that gets fixed) won't the problem just be present in the proper release?

Oh, right, I didn't really expound on my point very well. Of course report bugs. From your post it wasn't clear you knew it was a beta...others have just seen an upgrade notice and upgraded, without paying attention to what they're upgrading to.

Did both SBCs have the same monitoring software?

 

[Lee Cramman]

Oh, right, I didn't really expound on my point very well. Of course report bugs. From your post it wasn't clear you knew it was a beta...others have just seen an upgrade notice and upgraded, without paying attention to what they're upgrading to.

Did both SBCs have the same monitoring software?

You're right in that I didn't notice the beta tag until after the failure but given the one that successfully updated before I noticed gave no issues I thought "In for a penny..."! That said, it probably isn't a bug or there would have been lots of other complaints about failed upgrades.

They don't both have the same software installed (the SBC that worked is on-site with me so doesn't need it) and that may well be the difference. I'm aware that unexpected sources did trip up our recent V18 PBX upgrade (the 3CX script terminates if it sees sources it doesn't like) so it's a real possibility that this is something similar. However, as per the support answer, I also seem to be missing some 3CX sources for apt which could also be the problem. I've no idea how that could have happened happened as this was an install from a 3CX ISO.

Hopefully all will become clear once our phones close down for the day and I can get some maintenance time.

 

[Lee Cramman]

In that case, you'll have to create them as follows:

File "3cxpbx.list" must contain the following line:

deb http://downloads-global.3cx.com/downloads/debian stretch main

File "3cxpbx-testing.list" must contain the following:

deb [arch=amd64] http://downloads-global.3cx.com/downloads/debian stretch-testing main

Note: If you're running Debian 10 (Buster) replace the word "stretch" with "buster".

Once you've created the files you will have to run "apt update" again.

It's complaining that the repository isn't signed / the public key is not available.

edit: I've manually added the key. I'll try again.

 

[Lee Cramman]

What I've done so far and in order:

1. Removed the spurious .list file for our remote management software in /etc/apt/sources.list.d so the folder is empty
2. Created the 3cxpbx.list and 3cxpbx-testing.list files in this folder as per instructions (using "buster")
3. Added the public key so apt is happy to hit the 3cx repositories
4. Run apt-get update (all sources were hit successfully)
5. Tried to upgrade through the management portal
6. When that didn't work tried to upgrade with apt-get upgrade

Apt still says "The following packages have been kept back: linux-image-amd64".

I'm reluctant to try dist-upgrade in case I kill the SBC (it's at a remote site).

I can try apt-get --with-new-pkgs upgrade as a more conservative option but thought I should check in first...

 

[Lee Cramman]

@ChrisC_3CX

Should I give that a go?

 

[NickD_3CX]

Hi!

You could give it a shot yes, --with-new-pkgs does reduce the probability of something not upgrading correctly, not completely, but lower risk.

I do have to say though, with these kind of things, you always need to be prepared for the worst.

 

[Lee Cramman]

Hi!

You could give it a shot yes, --with-new-pkgs does reduce the probability of something not upgrading correctly, not completely, but lower risk.

I do have to say though, with these kind of things, you always need to be prepared for the worst.

Good point. I'll give it a try but wait until I'm on site in case I need to re-deploy that SBC.

 

[Lee Cramman]

That (plus fixing a typo in 3cxpbx-testing.list) did it, thank you.

 

[ChrisC_3CX]

Glad to see you've managed to resolve this!

Feel free to start a new thread if you need any more info or assistance!