0 eventsġ80112 16:30:07 InnoDB: Starting shutdown.ġ80112 16:30:09 InnoDB: Shutdown completed log sequence number 234248205ġ80112 16:30:10 /usr/local/mysql/bin/mysqld: Shutdown completeġ80112 16:30:10 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid endedġ80112 16:31:31 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/dataġ80112 16:31:34 /usr/local/mysql/bin/mysqld (mysqld 5.5.58-MariaDB) starting as process 18726.
I've looked through past posts on this forum and tried suggestions, but haven't found a solution yet.ġ80112 16:30:07 /usr/local/mysql/bin/mysqld: Normal shutdownġ80112 16:30:07 Event Scheduler: Purging the queue. It's only failing during upgrades like these. Every other application including mysqld has MySQL/MariaDB working perfectly with that same socket. I don't understand what's wrong with the socket. usr/local/mysql/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/usr/local/mysql/data/mysql.sock' (2) when trying to connect Update-rc.d: error: mysqld Default-Start contains no runlevels, aborting.Įnsuring local-infile is disabled for security reasons in MySQL configuration file. Synchronizing state of rvice with SysV service script with /lib/systemd/systemd-sysv-install.Įxecuting: /lib/systemd/systemd-sysv-install enable mysqld ~# /usr/local/directadmin/custombuild/build mysql
0 kommentar(er)
