# Duplicate DB name Updating to 2021.10 from 2020.03

**URL:** <https://forum.eaasi.cloud/t/duplicate-db-name-updating-to-2021-10-from-2020-03/325>\
**Category:** Support\
**Created:** [February 3, 2022, 5:14pm UTC](https://forum.eaasi.cloud/t/duplicate-db-name-updating-to-2021-10-from-2020-03/325 "2022-02-03T17:14:38Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![oooleg](https://avatars.discourse-cdn.com/v4/letter/o/aca169/32.png) [@oooleg](https://forum.eaasi.cloud/u/oooleg)\
**Post date:** [March 4, 2022, 9:37pm UTC](https://forum.eaasi.cloud/t/duplicate-db-name-updating-to-2021-10-from-2020-03/325/13 "2022-03-04T21:37:17Z")

</div>

OK, great! Now let’s try to find out why login fails.

That specific migration of legacy users is executed outside of our backend, so we need to check the following log instead:

```nohighlight
$ sudo journalctl -u eaas | grep eaasi-web-api > eaasi-web-api.log

```

Please post the produced log file here.

---

_[View the full topic](https://forum.eaasi.cloud/t/duplicate-db-name-updating-to-2021-10-from-2020-03/325)._