/usr/sbin/httpd -k start

[madhuwarriors]

When i grep for the httpd processes in our linux servers, i see list of httpd process like below :

/usr/sbin/httpd -k start

/usr/sbin/httpd in few servers.

What does this -k start indicate and without that indicate?

It would be helpful if someone gives accurate info about this.

[gsjurseth · Accepted solution]

Hi,

I'm assuming that this is for an on premises setup of the developer portal. The -k option is the canonical method for sending the apache-httpd daemon a service command like start, stop, or graceful. Run this way it will start up in daemon mode, load default configuration (including the PHP module which it needs to host the developer portal) and so on. Without it it's simply running the binary itself.

I hope this helps.

/geir

[madhuwarriors]

Hi Sjurseth,

Thanks for the details.

Yes, this is for on-prem developer portal. In a developer portal server, I don't see -k start when i grep the processes. After running the httpd with -k start, process should start and it should not display -k start in the ps -acef | grep httpd output. Please correct me if i am wrong.

When I check the elapsed time of the httpd processes, i see root httpd process was up from 15 days and the child processes were up from last 21 hours.

The current issue is, users are seeing below error after submitting the credentials(all credentials are valid) :

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /user/login.

Reason: Error reading from remote server

As i said in my post, i don't see "-k start" option in the ps output for another server and the developer portal is running without issues and we are able to login.

Additional details :

For the portal with issue, we are seeing timeout error and the timeout at rev proxy server is 10 sec. For the portal without issue, the timeout is 240.

I want to know here what is reason for the error time.

[gsjurseth]

Hi,

What version of OPDK are you running? If you're running 17.09 then you should no longer be running apache. In that case it should be nginx.

Are you following these instructions when restarting the service?

https://docs.apigee.com/private-cloud/latest/starting-stopping-or-restarting-portal