Solved SBC stopped working after update to SP4 (SSL error)

Status
Not open for further replies.

mamo

Forum User
Joined
Aug 22, 2016
Messages
39
Reaction score
2
I have two raspberry pis running as SBCs at two remote locations.
For the last two months, both SBCs worked flawless without any issue. Yesterday, I updated our main server from v15 SP3 to SP4 (did not change anything else). After that, both SBCs stopped working.

Here is the part from the log file of one of the SBCs, that I guess is relevant for the error:
Code:
 NOTICE | 20161222-004704.821 | 3CXTunnel | TUNL | 2180 | 1995960848 | security.cpp:1229 | Secure tunnel: got SSA with mode = 1
 DEBUG | 20161222-004705.302 | 3CXTunnel | TUNL | 2180 | 1995960848 | security.cpp:689 | SSL error (5): error:00000005:lib(0):func(0):DH lib#012  Unknown system error
 DEBUG | 20161222-004705.302 | 3CXTunnel | TUNL | 2180 | 1995960848 | security.cpp:607 | Handshake: SSL error (5): error:00000005:lib(0):func(0):DH lib#012  Unknown system error
 NOTICE | 20161222-004705.302 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:436 | Secure tunnel is failed. Error 3: TLS handshake failed: error:00000005:lib(0):func(0):DH lib#012  Unknown system error
 ERR | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:258 | Bridge [3CXt] failure 'TLS handshake failed: error:00000005:lib(0):func(0):DH lib#012  Unknown system error' on TCP connection: secure negotiation
 NOTICE | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:388 | === Statistics:#012  Keep-alives: recv 1, sent 1#012  Transfers:   recv last 482 ms ago,#011total 41 bytes#012               sent last 555 ms ago,#011total 101 bytes#012===
 WARNING | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | Bridge.cpp:225 | Tunnel disconnected. Terminating all active calls.
 ERR | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:425 | Socket error (9): while begin to read a packet from tunnel at while begin to read a packet from tunnel (TunnelTcp::process)
 ERR | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:258 | Bridge [3CXt] failure 'Bad file descriptor' on TCP connection: while begin to read a packet from tunnel
 NOTICE | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:388 | === Statistics:#012  Keep-alives: recv 0, sent 1#012  Transfers:   recv last 482 ms ago,#011total 0 bytes#012               sent last 555 ms ago,#011total 0 bytes#012===
 WARNING | 20161222-004705.303 | 3CXTunnel | TUNL | 2180 | 1995960848 | Bridge.cpp:225 | Tunnel disconnected. Terminating all active calls.
 NOTICE | 20161222-004709.308 | 3CXTunnel | TUNL | 2180 | 1995960848 | TunnelTcp.cpp:388 | === Statistics:#012  Keep-alives: recv 0, sent 1#012  Transfers:   recv last 4487 ms ago,#011total 0 bytes#012               sent last 4560 ms ago,#011total 0 bytes#012===
 INFO | 20161222-004726.326 | 3CXTunnel | RESIP:TRANSACTION | 2180 | 1995960848 | TuSelector.cxx:84 | Stats message
 WARNING | 20161222-004726.327 | 3CXTunnel | RESIP:STATS | 2180 | 1995960848 | StatisticsMessage.cxx:98 | RESIP:TRANSACTION#012TU summary: 0 TRANSPORT 0 TRANSACTION 0 CLIENTTX 0 SERVERTX 0 TIMERS 0#012Transaction summary: reqi 3 reqo 0 rspi 0 rspo 1#012Details: INVi 0/S0/F0 INVo 0/S0/F0 ACKi 0 ACKo 0 BYEi 0/S0/F0 BYEo 0/S0/F0 CANi 0/S0/F0 CANo 0/S0/F0 MSGi 0/S0/F0 MSGo 0/S0/F0 OPTi 0/S0/F0 OPTo 0/S0/F0 REGi 3/S0/F1 REGo 0/S0/F0 PUBi 0/S0/F0 PUBo 0/S0/F0 SUBi 0/S0/F0 SUBo 0/S0/F0 NOTi 0/S0/F0 NOTo 0/S0/F0 REFi 0/S0/F0 REFo 0/S0/F0 INFi 0/S0/F0 INFo 0/S0/F0 PRAi 0/S0/F0 PRAo 0/S0/F0 SERi 0/S0/F0 SERo 0/S0/F0 UPDi 0/S0/F0 UPDo 0/S0/F0#012Retransmissions: INVx 0 finx 0 nonx 0 BYEx 0 CANx 0 MSGx 0 OPTx 0 REGx 0 PUBx 0 SUBx 0 NOTx 0 REFx 0 INFx 0 PRAx 0 SERx 0 UPDx 0


Tonight, I will probably roll back the VM, using a backup from yesterday. So, hopefully, tomorrow everything will be working again with SP3 until this issue is resolved. But obviously this is only a temporary solution, as I do not want to be stuck with SP3 forever. So, any help or a fix in the next SP would be greatly appreciated.
 
Hello mamo,

Are you running the latest version of the raspberry SBC?
 
Ok, I am stupid. Should have tried updating before.
Now it is working again. :-)

Reason why I did not update was because I was searching for updates (on the 3CX website and via google) and the most recent thing, I found, was a news post from February. Therefore, I was under the false assumption that there would be no update available.

Is there a changelog for the SBC available somewhere?
 
Status
Not open for further replies.