DAY 17 100days devops chalenge

The Nautilus application development team has shared that they are planning to deploy one newly developed application on Nautilus infra in Stratos DC. The application uses PostgreSQL database, so as a pre-requisite we need to set up PostgreSQL database server as per requirements shared below:

PostgreSQL database server is already installed on the Nautilus database server.

a. Create a database user kodekloud_top and set its password to Rc5C9EyvbU.

b. Create a database kodekloud_db4 and grant full permissions to user kodekloud_top on this database.

Note: Please do not try to restart PostgreSQL server service.

For the above question, when I try to SSH into the DB server, it’s not booting up. I waited for long time , even I tried a second time, but the same issue.
this is the error that is being displayed on the terminal

or@jumphost ~$ ssh peter@stdb01 The authenticity of host ‘stdb01 (172.16.239.10)’ can’t be established. ED25519 key fingerprint is SHA256:zBQmzOcI54OUgvCE+nN5dYsO+2ZjDJGk11+u1hvQnjg. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added ‘stdb01’ (ED25519) to the list of known hosts. peter@stdb01’s password: “System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8).” Connection closed by 172.16.239.10 port 22 thor@jumphost ~$ ssh peter@stdb01 peter@stdb01’s password: “System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8).” Connection closed by 172.16.239.10 port 22

Please let me know what can be done to fix this issue

Hey @saivardhanguduru,
Thanks for bringing this up. I’ve notified the team, will let you know once it’s resolved.

I’m facing the same issue

I’m also having this issue

On the Day 17 lab, or on a different lab (please say which if so). Also, which server is not working for you?

It was on day17 and it was the stdb01 that I could ssh onto

I’m also facing similar issues.

check this repo , u can find the solution here : 100-Days-Of-DevOps-KodeKloud-Challenges-Solutions

@saivardhanguduru, @dilushalakshan, @sambo696
This issue for Day 17 task has been fixed. Please check.