Day 14. of 100 days of DevOps event

KodeKloud Engineer
#1

Hello kodekloud.

The task is about apache troubleshooting (failed to start on certain port).

Why the task failed, if everything done the right way?

Why do you check if a process (that interferes with httpd process) is not exist in the memory. Why should I kill the process?

I just change the config of the process, I mentioned above and run it on the other port, but apache (httpd) process is listening on the right port and serve as needed. It returns 200 OK from all the app servers.

Systemd units enabled and running and servers available on the port needed from jump host…

Why is it failed?

In feedback dialog (in the end of the task) I’ve sent all the 200OK from servers…

It’s really upset me though =)

Thank you in advance.

#2

:slight_smile:

You might want to look at a different solution. Here’s one to try.

1 Like
#3

Thank you for reply.

I have already done this task, but it’s weird for the test itself to check in such way.

I would check the task this way:

  1. Check if service enabled and running (systemd) - all appservers
  2. Request every appservers, if response code not equal to 200 - fail (it would include such moments as, create index file, rights, ownership (enough for check if engineer knows the topic right?).

Thank you anyway for answer.

#4

check this solution 100-Days-Of-DevOps-KodeKloud-Challenges-Solutions

#5

Anyway, thank you for answer.