Rare project developers

[Alexander Gall <>]

On Wed, 21 Dec 2022 08:53:00 +0100, mc36 <> said:

> hi,
> here we goo...
> thanks,
> cs

> core#tna-list-long-installed
> Generation Current Release Git Tag                    KernelID       Kernel 
> Release            Platform                   Install date
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>           1         1eta    release-1eta               Debian11_0     
> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-04-16 
> 22:22:46.309693289 +0200
>           2         1theta  release-1eta-16-g29bb914   Debian11_0     
> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-04-16 
> 22:22:46.313693289 +0200
>           3         1theta  release-1eta-18-g73197c4   Debian11_0     
> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-04-16 
> 22:22:46.309693289 +0200
>           4         1theta  release-1eta-33-ge6051d4   Debian11_0     
> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-04-16 
> 22:22:46.313693289 +0200
>           5         1       release-1                  Debian11_0     
> 5.10.0-8-amd64            stordis_bf2556x_1t         2022-12-20 
> 21:31:14.099817139 +0100
>           6 *       2       release-1-111-gd936209-freertr-a66e05 
> Debian11_0     5.10.0-8-amd64            stordis_bf2556x_1t         
> 2022-12-20 22:18:33.437665762 +0100


> core#
> core#show logging process bfswd
> Using bf_router profile "NOP_MCHOME"

That's only the output of the wrapper script that starts the actual
SAL. There must be more output. Maybe right after you restart the
process?  Otherwise you can start it by hand just to see what happens.

--
Alex

> core#



> On 12/21/22 08:44, Alexander Gall wrote:
>> Hi
>> 
>> On the 2556 the bfswd process is actually the SAL which waits for a
>> connection from bffwd. The actual bf_switchd is only started after
>> bffwd has connected sucessfully and asked the SAL to start bf_switchd
>> so this can't have happened yet if the connection fails.  Can you show
>> me the output of the bfswd process please?
>> 
>> Also, which version are you using (tna-list-long-installed)?
>> 
>> --
>> Alex
>> 
>> 
>> On Wed, 21 Dec 2022 08:09:27 +0100, mc36 <> said:
>> 
>>> hi,
>>> i've got my bf2556 back... i upgraded to experimental... the bfswd 
>>> process seems stable but the bffwd keeps restarting:
>> 
>>> core#attach process bffwd
>> 
>>> SalGrpcClient.TestConnection: Failed to connectd to SAL server at 
>>> 127.0.0.1:50053: <_Rendezvous of RPC that terminated with:
>>> status = StatusCode.UNAVAILABLE
>>> details = "channel is in state TRANSIENT_FAILURE"
>>> debug_error_string = 
>>> "{"created","description":"channel is in
>>> state 
>>> TRANSIENT_FAILURE","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":2917,"grpc_status":14}"
>>>> , retrying
>>> info cfgPrcss.doRound:cfgPrcss.java:509 restarting process bfswd
>>> SalGrpcClient.TestConnection: Failed to connectd to SAL server at 
>>> 127.0.0.1:50053: <_Rendezvous of RPC that terminated with:
>>> status = StatusCode.UNAVAILABLE
>>> details = "channel is in state TRANSIENT_FAILURE"
>>> debug_error_string = 
>>> "{"created","description":"channel is in
>>> state 
>>> TRANSIENT_FAILURE","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":2917,"grpc_status":14}"
>>>> , retrying
>>> info cfgPrcss.doRound:cfgPrcss.java:509 restarting process bfswd
>>> SalGrpcClient.TestConnection: Failed to connectd to SAL server at 
>>> 127.0.0.1:50053: <_Rendezvous of RPC that terminated with:
>>> status = StatusCode.UNAVAILABLE
>>> details = "channel is in state TRANSIENT_FAILURE"
>>> debug_error_string = 
>>> "{"created","description":"channel is in
>>> state 
>>> TRANSIENT_FAILURE","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":2917,"grpc_status":14}"
>>>> , retrying
>> 
>> 
>>> this is all i see... any idea on whats going on?
>>> thanks,
>>> cs