# Interactive authentication required error and database shut down

**URL:** <https://forums.percona.com/t/interactive-authentication-required-error-and-database-shut-down/26874>\
**Category:** PostgreSQL\
**Tags:** new-release\
**Created:** [November 30, 2023, 6:53am UTC](https://forums.percona.com/t/interactive-authentication-required-error-and-database-shut-down/26874 "2023-11-30T06:53:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ponmani](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@Ponmani](https://forums.percona.com/u/Ponmani)\
**Post date:** [November 30, 2023, 6:53am UTC](https://forums.percona.com/t/interactive-authentication-required-error-and-database-shut-down/26874/1 "2023-11-30T06:53:10Z")

</div>

We have installed latest version of Postgres 16.1 in Azure VM. IT is working fine for some time. Later getting error as

 ![MicrosoftTeams-image (2)](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/9/98978586dacb38f089b6ebd35747864ff6a6ad68.png)

```auto
postgres the database system is shutting down 
interactive authentication required

```

---

<div class="post-metadata">

**Author:** ![Edith-Puclla](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/edith-puclla/32/6980_2.png) [@Edith-Puclla](https://forums.percona.com/u/Edith-Puclla)\
**Post date:** [December 4, 2023, 12:22pm UTC](https://forums.percona.com/t/interactive-authentication-required-error-and-database-shut-down/26874/2 "2023-12-04T12:22:21Z")

</div>

Hi @Ponmani  
The error messages from your PostgreSQL on Azure VM suggest there could be **permission issues** or unexpected shutdown commands. The “ **interactive authentication required** ” message happens because a non-admin user (probably postgres user) is trying to issue a systemd command or a privileged command. Postgres users by default should not do that.

You should check the PostgreSQL user permissions and confirm that the system hasn’t been compromised, as **/tmp/kinsing** is often associated with a known malware.

Let us know if this is what has happened or if you have found another signal in your logs.