[Bug]: Can't spin up multiple local L1s

[owenwahlgren]

Describe the bug
When trying to deploy multiple L1s locally, only the most recent L1 deployment's RPC is functional.

To Reproduce

1. Create chain configs

avalanche blockchain create chain1 --evm --proof-of-authority --test-defaults --evm-token="TEST" --evm-chain-id=888 

avalanche blockchain create chain2 --evm --proof-of-authority --test-defaults --evm-token="TEST" --evm-chain-id=999 

2. Deploy chain1

avalanche blockchain deploy chain1 --local

3. Note RPC URL then confirm fetching balance for chain1 is functional

cast balance 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC --rpc-url=<chain1 rpc>

999999976431274999435251

4. Deploy chain2

avalanche blockchain deploy chain2 --local

5. Note RPC URL then confirm fetching balance for chain2 is functional

cast balance 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC --rpc-url=<chain2 rpc>

999999976431274999435251

6. Try fetching balance on chain1 rpc again

cast balance 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC --rpc-url=<chain1 rpc>

Error: error sending request for url (http://127.0.0.1:43791/ext/bc/S3rjJ3oAo2vo1z4qwxDma8ii3JxAEfci17EFSaxsbtTGPKuZf/rpc)

Context:
- Error #0: error sending request for url (http://127.0.0.1:43791/ext/bc/S3rjJ3oAo2vo1z4qwxDma8ii3JxAEfci17EFSaxsbtTGPKuZf/rpc)
- Error #1: client error (Connect)
- Error #2: tcp connect error: Connection refused (os error 111)
- Error #3: Connection refused (os error 111)

Expected behavior
Both RPCs should be functional

Operating System
MacOSX / Ubuntu

[felipemadero]

Thanks! Indeed local network support for more than one l1 is needed.

[felipemadero]

Closed by #2680