@Diego Seems to complain from node 10.0.0.120 which is an executor. Can you restart this executor and when it is coming up, tail the server.log and make sure the plugin status is marked healthy and if not see why?
Maybe you have not added this IP in pg_hba.conf to allow access to PG?
@Diego Check the error tab and see if it is the same executor again 10.0.0.120, if not maybe all the executors where not added to pg_hba.conf? Also review the server.log on the executor it is complaining on and look at the startup section to see if the plugin reports healthy
@Diego Is this part of the server.log as the last line in the server.log just has the start fragment
023-01-12 20:43:49,136 [FABRIC-rpc-event-queue] INFO c.d.sabot.exec.FragmentExecutors - Received remote fragment start instruction for 1c3f8efb-0643-edc9-d8d2-9a29a5b54f00:0:0 with assigned weight 1 and scheduling weight 1
2023-01-12 20:43:49,140 [FABRIC-rpc-event-queue] INFO c.d.s.e.f.FragmentExecutorBuilder - Setting outStandingRPCsPerTunnel:3