docker container crashes every 2-4 hours

[SrxDev]

Using docker container from quay and on version 4.27. I have noticed that every few hours the docker container crashes then restarts. In the error logs i see the following:

2022-05-02 04:02:55.051 [error] <0.1648.0>@natupnp_v2:discover1:65 Supervisor libp2p_swarm_auxiliary_sup_blockchain_swarm had child nat started with libp2p_nat_server:start_link(blockchain_swarm) at <0.1654.0> exit with reason no match of right hand value {error,eagain} in natupnp_v2:discover1/3 line 65 in context child_terminated

This was not happening with previous versions.

[meowshka]

@SrxDev Is this still happening on the latest version 05.12? Btw, we're moving the Discussions board, so your original issue will be closed.

[SrxDev]

Yes it is.

Error:
2022-05-16 12:43:18.392 [error] emulator Error in process <0.1786.0> on node '[email protected]' with exit value:
{{badmatch,{error,eagain}},[{natupnp_v2,discover1,3,[{file,"natupnp_v2.erl"},{line,65}]},{natupnp_v2,discover,0,[{file,"natupnp_v2.erl"},{line,55}]},{nat,discover_worker,3,[{file,"nat.erl"},{line,145}]}]}
2022-05-16 12:43:18.393 [error] <0.1647.0>@natupnp_v2:discover1:65 Supervisor libp2p_swarm_auxiliary_sup_blockchain_swarm had child nat started with libp2p_nat_server:start_link(blockchain_swarm) at <0.1653.0> exit with reason no match of right hand value {error,eagain} in natupnp_v2:discover1/3 line 65 in context child_terminated

[SrxDev]

This is from the crash.log file(s)

2022-05-16 12:13:17 =SUPERVISOR REPORT====
Supervisor: {<0.20180.0>,libp2p_simple_sup}
Context: shutdown_error
Reason: noproc
Offender: [{pid,<0.20184.0>},{id,1},{mfargs,{libp2p_yamux_stream,receive_stream,undefined}},{restart_type,temporary},{significant,false},{shutdown,1000},{child_type,worker}]

2022-05-16 12:43:18 =ERROR REPORT====
Error in process <0.1786.0> on node '[email protected]' with exit value:
{{badmatch,{error,eagain}},[{natupnp_v2,discover1,3,[{file,"natupnp_v2.erl"},{line,65}]},{natupnp_v2,discover,0,[{file,"natupnp_v2.erl"},{line,55}]},{nat,discover_worker,3,[{file,"nat.erl"},{line,145}]}]}
2022-05-16 12:43:18 =SUPERVISOR REPORT====
Supervisor: {local,libp2p_swarm_auxiliary_sup_blockchain_swarm}
Context: child_terminated
Reason: {{badmatch,{error,eagain}},[{natupnp_v2,discover1,3,[{file,"natupnp_v2.erl"},{line,65}]},{natupnp_v2,discover,0,[{file,"natupnp_v2.erl"},{line,55}]},{nat,discover_worker,3,[{file,"nat.erl"},{line,145}]}]}
Offender: [{pid,<0.1653.0>},{id,nat},{mfargs,{libp2p_nat_server,start_link,[blockchain_swarm]}},{restart_type,permanent},{significant,false},{shutdown,1000},{child_type,worker}]

[cokes518]

There is a new docker image 05.13. unclear why you're seeing p2p errors, at this point, miners have their erlang clients turned off (but not removed).

is this a fatal error?

[SrxDev]

It is but it appears to be a port issue?? I know we are using light hotspots but if I keep port 44158 open it crashes every x hours still. If port 44158 is closed then no problems. I’ll update this in a few days but maybe the issue resolved itself ?