[#61] Fixed bug with second `vault` instance in `run-bats-tests.sh`

[DK318]

Description

Problem

Sometimes the second vault instance doesn't start. Probably the problem is that the first vault instance starts on port 8209 and the second one starts on 8210.

Solution

Changed port of the second instance from 8210 to 8211.

Related issue(s)

• Fixes #61

  Related changes (conditional)

  • Tests

    • [ ] If I added new functionality, I added tests covering it.
    • [ ] If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.

  • Documentation

    • [x] I checked whether I should update the docs and did so if necessary:
    • README
    • Haddock

  • Public contracts

    • [x] Any modifications of public contracts comply with the Evolution of Public Contracts policy.
    • [x] I added an entry to the changelog if my changes are visible to the users and
    • [x] provided a migration guide for breaking changes if possible

  Stylistic guide (mandatory)

  • [x] My commits comply with the policy used in Serokell.
  • [x] My code complies with the style guide.

[dcastro]

Why did port 8210 not work sometimes? :thinking:

[DK318]

Maybe when we start vault on port 8209 it uses two ports actually.

If we start manually first instance on port 8201 and try to start the second one on 8202 then we would get next error

Error parsing listener configuration.
Error initializing listener of type tcp: listen tcp 127.0.0.1:8202: bind: address already in use

[DK318]

Yeah, it really listens two neighbor ports. lsof prints me this:

vault     39914 39926 vault                dk318    8u     IPv4             625209       0t0        TCP localhost:8200 (LISTEN)
vault     39914 39926 vault                dk318    9u     IPv4             625212       0t0        TCP localhost:8201 (LISTEN)

[MagicRB]

didnt know vault did that but LGTM