Home>

If i am a beginner, please point out if there is a lack of explanation because it is the second deployment on AWS.
Please let me know if you have any information to add.

The server does not start in the production environment

The deployment was completed yesterday and was working fine at that point.
Today, I implemented additional implementation etc., so I tried to pull git again and start it up
Master failed to start, check stderr log for details is output to the terminal

have become.
I checked the log


It seems that the file called mysql.sock is gone, so I created mysql.sock while looking at the article on qiita.
Then the error changed to Can't connect to local MySQL server through socket'/var/lib/mysql/mysql.sock' (111).

When I try to restart the mysql server or check the status, I get angry when the command is not found.

I've been fighting for about 5 hours now, but I can't stand my teeth at all ...

Could you please tell me the cause?
I think this is a rudimentary question, but please kindly ask.

  • Answer # 1

    It seems that the file mysql.sock is gone

    mysql.sock is created by the mysql server at startup. I think mysql isn't running.

    The result of systemctl status mariadb

    mariadb.service --MariaDB database server
    Loaded: loaded (/usr/lib/systemd/system/mariadb.service;disabled;vendor preset: disabled)
    Active: inactive (dead)


    Looking at, it seems that mariadb is not running. This may happen if you restart without autostart set.

    systemctl enable mariadb
    systemctl start mariadb


    You can start the mysql DB server by executing, so please try it once.
    The enable on the first line is the setting for automatic startup. By setting this setting, the mysql server will start automatically even if you restart the server.