Scientific Linux - mysql and apache fail to start on reboot
- by Derek Deed
Both mysqld and httpd fail to restart following a reboot of the server, although chkconfig --list shows both daemons set to on for run levels 2,3,4 & 5
All control is being exectuted via Webmin
Reboot server – MySQl and Apache not running
MySQL Database Server
MySQL version 5.1.69
MySQL is not running on your system - database list could not be retrieved.
________________________________________
Click this button to start the MySQL database server on your system with the command /etc/rc.d/init.d/mysqld start. This Webmin module cannot administer the database until it is started.
Apache Webserver
Apache version 2.2.15 Start Apache
Search Docs..
Global configuration
Existing virtual hosts
Create virtual host
Select all. | Invert selection.
Default Server
Defines the default settings for all other virtual servers, and processes any unhandled requests.
Address Any
Port Any Server Name Automatic
Document Root /var/www/drupal
Virtual Server
Processes all requests on port 443 not handled by other virtual servers.
Address Any
Port 443 Server Name Automatic
Document Root /var/www/drupal
Select all. | Invert selection.
chkconfig --list mysqld
mysqld 0:off 1:off 2:on 3:on 4:on 5:on 6:off
chkconfig --list httpd
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Manually Restart Apache
chkconfig --list httpd
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Manually Restart MySQL
chkconfig --list mysqld
mysqld 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Everything now running okay; but no difference in the chkconfig outputs above.
I tried:
chkconfig --levels 235 httpd on
/etc/init.d/httpd start
and the same for mysqld but no change in operation.
Log files show that the shutdown has been completed successfully; but there is no indication of the service restarting until it is executed manually:
131112 13:59:15 InnoDB: Starting shutdown...
131112 13:59:16 InnoDB: Shutdown completed; log sequence number 0 881747021
131112 13:59:16 [Note] /usr/libexec/mysqld: Shutdown complete
131112 13:59:16 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
131112 14:09:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
131112 14:09:52 InnoDB: Initializing buffer pool, size = 8.0M
131112 14:09:52 InnoDB: Completed initialization of buffer pool
And the Apache logs:
[Tue Nov 12 13:59:13 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Nov 12 13:59:13 2013] [notice] Digest: generating secret for digest authentication ...
[Tue Nov 12 13:59:13 2013] [notice] Digest: done
[Tue Nov 12 13:59:14 2013] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.0-fips configured -- resuming normal operations
[Tue Nov 12 13:59:14 2013] [notice] caught SIGTERM, shutting down
[Tue Nov 12 14:27:13 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Nov 12 14:27:13 2013] [notice] Digest: generating secret for digest authentication ...
[Tue Nov 12 14:27:13 2013] [notice] Digest: done
[Tue Nov 12 14:27:13 2013] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.0-fips configured -- resuming normal operations
Is anyone able to shed any light on this problem?
