Unreachable rest-aggregator returns NoSuchKeyset logs

[antonio-altr]

Log messages around unreachable rest-aggregator can be a bit misleading, for this particular setup:

1. One docker container for daserver
2. Another docker container for nitro
   • Sequencer, batchposter, and staker all enabled
   • rpc-aggregator and rest-aggregator are set to 0.0.0.0:<the rpc or rest port>

You'll see the logs below, which seem to say the nitro can reach the daserver fine but actually it couldn't:

WARN [11-27|00:25:46.365] Recording for validation failed, retrying.. pos=385739
INFO [11-27|00:25:47.469] rpc response                             method=eth_call            logId=97986 err="execution reverted" result="\"0x\""  attempt=0 args="[{\"from\":\"0x0000000000000000000000000000000000000000\",\"input\":\"0x258f04955504a989aa8e6dcfc4e1973d5fe14583b60bbba54678b04f577ad3aa9aaa98a0\",\"to\":\"0x58b38152dc53aab5f6c41f33aa543e224a7ff709\"}, \"latest\"]" errorData="\"0x00f20c5d5504a989aa8e6dcfc4e1973d5fe14583b60bbba54678b04f577ad3aa9aaa98a0\""
ERROR[11-27|00:25:47.469] Couldn't fetch DAS batch contents        err="execution reverted: NoSuchKeyset(0x5504a989aa8e6dcfc4e1973d5fe14583b60bbba54678b04f577ad3aa9aaa98a0)"
ERROR[11-27|00:25:47.469] Error while recording                    err="execution reverted: NoSuchKeyset(0x5504a989aa8e6dcfc4e1973d5fe14583b60bbba54678b04f577ad3aa9aaa98a0)" status=2

By changing the IP of the rest and rpc aggregator in the nitro from 0.0.0.0 to the actual external IP of the host machine, the nitro is able to reach the daserver fine and the error logs disappear.