Greetings, Gery .!
> When I start apache2 ('apachectl2 start'), this appears in
> /var/log/apache2/error_log:
> [Mon Oct 27 12:28:26 2014] [warn] Init: Session Cache is not configured
> [hint: SSLSessionCache]
> [Mon Oct 27 12:28:39 2014] [notice] Digest: generating secret for digest
> authentication ...
> [Mon Oct 27 12:28:39 2014] [notice] Digest: done
> [Mon Oct 27 12:28:41 2014] [notice] Apache/2.2.29 (Unix) mod_ssl/2.2.29
> OpenSSL/1.0.1j DAV/2 PHP/5.5.18 configured -- resuming normal operations
> and 'ps -a | grep httpd2' gives (a similar call displayed 6 times):
> 5644 6064 6064 5644 ? 1001 12:31:13 /usr/sbin/httpd2
> 6064 1 6064 6064 ? 1001 12:31:11 /usr/sbin/httpd2
> 3084 6064 6064 3084 ? 1001 12:31:13 /usr/sbin/httpd2
> 5204 6064 6064 5204 ? 1001 12:31:12 /usr/sbin/httpd2
> 4088 6064 6064 4088 ? 1001 12:31:12 /usr/sbin/httpd2
> 4388 6064 6064 4388 ? 1001 12:31:13 /usr/sbin/httpd2
> When I stop apache2 ('apachectl2 stop'), this appears in
> /var/log/apache2/error_log:
> [Mon Oct 27 12:29:24 2014] [notice] caught SIGTERM, shutting down
> [Mon Oct 27 12:29:25 2014] [notice] seg fault or similar nasty error detected
> in the parent process
> I have two questions:
> 1. The "seg fault or similar nasty error detected in the parent process"
> message represents a problem? if yes, how do I solve it?
Yes, it represent a problem. Either in signal handling or the application
itself.
> 2. Why ps -a displays 6 times a similar call with httpd2 and postgres? is
> that the normal behavior?
That's how Apache works in prefork mode. No idea about postgres, but likely
the case is the same.
--
WBR,
Andrey Repin ([email protected]) 27.10.2014, <16:36>
Sorry for my terrible english...
