Databases
StackOverflow2013
Postsdbo
POMonit on CentOS causes httpd.pid not to be created
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMonit on CentOS causes httpd.pid not to be created
    primarykey
    data
    text
    <p>The solution was to replace this line:</p> <pre><code>check process apache with pidfile /var/run/httpd.pid </code></pre> <p>With this line:</p> <pre><code>check process httpd with pidfile /var/run/httpd/httpd.pid </code></pre> <p>And I also removed the 'group apache'.</p> <p>Original post:</p> <p>After installing <a href="http://mmonit.com/monit/" rel="nofollow">Monit</a> on CentOS, and setting an alert for the Apache (httpd) service, the service no longer creates the /var/run/httpd.pid file.</p> <p>The httpd service <strong>IS</strong> running properly.</p> <p>On top of it, as if that's not enough, Monit reports the status of the service as: Execution failed</p> <p>Naturally, the only way to restart such a service is by killing it, since the 'restart' script doesn't see any running process.</p> <p>These are the contents of the /etc/monit.d/monitrc file:</p> <pre><code>set daemon 10 set logfile syslog facility log_daemon set mailserver localhost set mail-format { from: me@server.com } set alert bugs@server.com set httpd port 2812 and # SSL ENABLE # PEMFILE /var/certs/monit.pem allow user:password check process apache with pidfile /var/run/httpd.pid group apache start program = "/etc/init.d/httpd start" stop program = "/etc/init.d/httpd stop" if cpu is greater than 180% for 1 cycles then alert if totalmem &gt; 1200 MB for 2 cycles then restart if children &gt; 250 then restart check process sshd with pidfile /var/run/sshd.pid start program "/etc/init.d/sshd start" stop program "/etc/init.d/sshd stop" if failed port 22 protocol ssh for 5 cycles then restart if 5 restarts within 25 cycles then timeout </code></pre> <p>Output of "service httpd restart":</p> <pre><code>Stopping httpd: [FAILED] Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs [FAILED] </code></pre> <p>Any help will be greatly appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbizna
    1. USbizna
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. USNic Cottrell
      1. VTFavorite
    2. VO
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. USSuedehead
      1. VTFavorite
    1. CODon't you mean "monit restart httpd"? What about "monit stop httpd" and "monit start httpd"? Does monit stop/start/restart sshd OK?
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. USDavid Resnick
    2. COThanks abunetta. When doing a restart, stop, start with Monit to httpd, there is no message. But the service isn't being stopped as well. I can't try to stop sshd, since it will leave me out of my machine :-)
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. USbizna
    3. COTry using the advice found here: http://stackoverflow.com/questions/3356476/debugging-monit/4439403#4439403 to better see what's happening when monit calls stop. I assume that stop command in monitrc works when you call it from the command line. About "monit restart sshd"; I'd still recommend trying it as a sanity check. You'll manage to get back into the machine somehow, if it doesn't work :-)
      singulars
      1. POMonit on CentOS causes httpd.pid not to be created
      1. USDavid Resnick
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload