httpd and mariadb are down

Manuel

• January 20, 2024 04:35

I got my disk space full today and mariadb went down. I tried deleting some files and went down to 80% of disk space but mariadb wont start. I did already tried several things including rebooting the server but non of it works. 

If I run systemctl status mariadb.service I get the following:
systemctl status mariadb.service ● mariadb.service - MariaDB 10.6.16 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: failed (Result: exit-code) since Fri 2024-01-19 22:18:39 CST; 1min 16s ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Main PID: 32525 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Jan 19 22:18:38 sonata.digitalibleserver.com systemd[1]: Starting MariaDB 10.6.16 database server... Jan 19 22:18:39 sonata.digitalibleserver.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE Jan 19 22:18:39 sonata.digitalibleserver.com systemd[1]: Failed to start MariaDB 10.6.16 database server. Jan 19 22:18:39 sonata.digitalibleserver.com systemd[1]: Unit mariadb.service entered failed state. Jan 19 22:18:39 sonata.digitalibleserver.com systemd[1]: mariadb.service failed.

And i have an extra poblem along mariadb, http isnt working as well.

 

Im desperate as i have important websites here and cant even perform a transfer to other server of this websites because of the services that are down

 

I appreciate the help

• 

  rbairwell

  • January 20, 2024 08:53

  Does "journalctl -u mariadb.service" give any indication as to why (same with "journalctl -u httpd.service").

  I take it you've tried the simple solution of just restarting the server? If you do get "Disk full" issues, it can leave Linux in a very "odd" state and rebooting is usually the easiest/quickest way of resolving (at least it's not as bad as Windows if the boot drive isn't writable..).

  0
• 

  MilesWeb

  • January 21, 2024 12:48

  Execute the following command to obtain the log-error file path for MariaDB. Review the error logs during the service startup to obtain precise details about the service failure.
  cat /etc/my.cnf
  
  The output for the file should be like this:

  [client-server]
  !includedir /etc/my.cnf.d
  
  [mysqld]
  log-error = /var/log/mysqld.log
  performance-schema = 0
  innodb_buffer_pool_size = 134217728
  max_allowed_packet = 268435456
  open_files_limit = 40000
  innodb_file_per_table = 1
  unix_socket = OFF

  tail -f /var/log/mysqld.log
  
  Likewise, examine the error logs to access Apache failure records, enabling you to pinpoint and address specific issues for both services.
  tail -f /usr/local/apache/logs/error_log

  0

Please sign in to leave a comment.