Solved SBC is not applying update 18.0.30

[AWS2P]

Hi ,
on a AWS cloud V18 PBX , I have a Pi 3B+ as SBC until its install more than 2 years, I never got any problem to update SBC release until this latest release.

Now SBC is 18.0.27 and 3CX console display there's a 18.0.30 update awaiting to apply. SBC was installed with 3CX guide and release available at install time, I never changed something since it runs in production, and unfortunatelly I have no SSH access enabled on this one , so I can't log in remotely.

I have done several tries to update (selecting SBC in SIP trunk, and then clicking on Update button) and nothing seems to react. SBC stays always connected and in same release.

Push config button seems to work as Sbc is disconnected and reconnected after config sent.

Anyway, is there some PBx logs that can trace what 's the problem avoiding update to apply?

Thanks for advices or way to find a reason it's not working .

 

[NickD_3CX]

There are no logs on 3CX Server that will tell you, the server simply instructs the SBC to check the repositories it has and update.
This leads me to believe that there is probably some repo issue on the SBC.

If you log into the SBC via SSH and type commands:

apt update
apt policy 3cxsbc

Do you see the version you are trying to install?

 

[AWS2P]

This leads me to believe that there is probably some repo issue on the SBC.

Never done a change on it , and all previous release have been applyied without a problem, this is only 18.0.30 which cause some problem.
If issue is like you say on repo, then this is coming from 3CX .
As SSH is not enabled on this one PI 3B+ , I will go on location next week on 14th of october.

Is it possible I prepare a new SD card based on a PI4 with same SBC config and then go on location an replace SD on PI 3B+ and restart with fresh install?

Or almost prepare a new SD card with fresh SBC install and then on location do all the settings

 

[Lee Cramman]

My recent thread might be relevant:

https://www.3cx.com/community/threads/sbc-wont-update.84326/

 

[NickD_3CX]

Never done a change on it , and all previous release have been applyied without a problem, this is only 18.0.30 which cause some problem.
If issue is like you say on repo, then this is coming from 3CX .
As SSH is not enabled on this one PI 3B+ , I will go on location next week on 14th of october.

Is it possible I prepare a new SD card based on a PI4 with same SBC config and then go on location an replace SD on PI 3B+ and restart with fresh install?

Or almost prepare a new SD card with fresh SBC install and then on location do all the settings

What @Lee Cramman said is a very likely possibility!
The only preparation you could do is have a new SD card and follow the instructions up until Step 2:
https://www.3cx.com/docs/installing-pbx-raspberry-pi/

Step 3 onward would have to be done on site.
Also, enable SSH, as you can see it is very useful, especially if you are remote and it is a headless machine (which RPIs usually are...)
If not not allow SSH from the outside, at least you could TeamViewer onto another machine on the customer premise and from there SSH.

 

[AWS2P]

Finally, I installed on a new SD card 64 Gb, a fresh SBC image and then inserted in a spare PI3B+ to follow install.
I did the 3CX SBC steps til the end with all same settings than the one in production. The "new SBC" has replaced the existing one on location in console.

Then I pushed update to 18.0.30 and It worked really smooth and quickly.
After a console check , SBC was really updated to latest and connected to PBX then I shut it down to keep the new SD card ready to send on customer location.

After SBC shutdown, old PI came back connected in console , now I've just sent a mail to customer with the new SD card inside, and giving him steps to replace SD card in his PI SBC.

SSH is now enabled so I'll be able to have a remote access in case of need.

Hope the SD card be switched on monday to let you know if this is well done

 

[AWS2P]

Today finally customer received mail with new SD card and replace it just past 10 minutes, and now it works like a charm.
SSH is now available , so this post can be stated as solved

 

[NickD_3CX]

Glad everything went smoothly!

Settings to 'Solved'.