If you are trying to install Cyberpanel 2.1.2 on CentOS 7, you are probably seeing your installation fails with the following in the screen:<\/p>\n\n\n\n
[ERROR] We are not able to run systemctl start mysql return code: 5. Fatal error, see \/var\/log\/installLogs.txt for full details.<\/pre>\n\n\n\nThis is appearing because Cyberpanel installation script located here:<\/p>\n\n\n\n
\/usr\/local\/cyberpanel\/install\/installCyberPanel.py<\/pre>\n\n\n\nwants to restart MariaDB 10.4 with the following:<\/p>\n\n\n\n
systemctl start mysql<\/pre>\n\n\n\nUnfortunately, this was only possible until 10.3 or below. Since 10.4, Mariadb uses the following command:<\/p>\n\n\n\n
systemctl start mariadb<\/pre>\n\n\n\nCyberpanel uses that command if you are using CentOS 8 or Ubuntu. But it looks like CentOS 7 now installs MariaDB 10.4 as default unlike 10.3 as default previously.
Even if you edit this command, Cyberpanel will reclone the script, hence it is not possible to change this from here. The nasty trick would be to load a mysql.service file before starting the cyberpanel installation. Here is what you would need to do to do this.<\/p>\n\n\n\n
- First reload your VPS with CentOS 7<\/li>
- Run yum update and install nano
<\/li><\/ol>\n\n\n\nyum update -y\nyum install nano -y<\/pre>\n\n\n\n3. Now, load the following file with the text given below:<\/p>\n\n\n\n
nano \/usr\/lib\/systemd\/system\/mysql.service<\/pre>\n\n\n\nLoad the file with the following text<\/p>\n\n\n\n
# It's not recommended to modify this file in-place, because it will be\n# overwritten during package upgrades. If you want to customize, the\n# best way is to create a file \"\/etc\/systemd\/system\/mariadb.service\",\n# containing\n# .include \/usr\/lib\/systemd\/system\/mariadb.service\n# ...make your changes here...\n# or create a file \"\/etc\/systemd\/system\/mariadb.service.d\/foo.conf\",\n# which doesn't need to include \".include\" call and which will be parsed\n# after the file mariadb.service itself is parsed.\n#\n# For more info about custom unit files, see systemd.unit(5) or\n# https:\/\/mariadb.com\/kb\/en\/mariadb\/systemd\/\n#\n# Copyright notice:\n#\n# This file is free software; you can redistribute it and\/or modify it\n# under the terms of the GNU Lesser General Public License as published by\n# the Free Software Foundation; either version 2.1 of the License, or\n# (at your option) any later version.\n\n[Unit]\nDescription=MariaDB 10.4.21 database server\nDocumentation=man:mysqld(8)\nDocumentation=https:\/\/mariadb.com\/kb\/en\/library\/systemd\/\nAfter=network.target\n\n[Install]\nWantedBy=multi-user.target\nAlias=mysql.service\nAlias=mysqld.service\n\n\n[Service]\n\n##############################################################################\n## Core requirements\n##\n\nType=notify\n\n# Setting this to true can break replication and the Type=notify settings\n# See also bind-address mysqld option.\nPrivateNetwork=false\n\n##############################################################################\n## Package maintainers\n##\n\nUser=mysql\nGroup=mysql\n\n# CAP_IPC_LOCK To allow memlock to be used as non-root user\n# CAP_DAC_OVERRIDE To allow auth_pam_tool (which is SUID root) to read \/etc\/shadow when it's chmod 0\n# does nothing for non-root, not needed if \/etc\/shadow is u+r\n# CAP_AUDIT_WRITE auth_pam_tool needs it on Debian for whatever reason\nCapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE\n\n# PrivateDevices=true implies NoNewPrivileges=true and\n# SUID auth_pam_tool suddenly doesn't do setuid anymore\nPrivateDevices=false\n\n# Prevent writes to \/usr, \/boot, and \/etc\nProtectSystem=full\n\n# Doesn't yet work properly with SELinux enabled\n# NoNewPrivileges=true\n\n# Prevent accessing \/home, \/root and \/run\/user\nProtectHome=true\n\n# Execute pre and post scripts as root, otherwise it does it as User=\nPermissionsStartOnly=true\n\n\n\n# Perform automatic wsrep recovery. When server is started without wsrep,\n# galera_recovery simply returns an empty string. In any case, however,\n# the script is not expected to return with a non-zero status.\n# It is always safe to unset _WSREP_START_POSITION environment variable.\n# Do not panic if galera_recovery script is not available. (MDEV-10538)\nExecStartPre=\/bin\/sh -c \"systemctl unset-environment _WSREP_START_POSITION\"\nExecStartPre=\/bin\/sh -c \"[ ! -e \/usr\/bin\/galera_recovery ] && VAR= || \\\n VAR=`cd \/usr\/bin\/..; \/usr\/bin\/galera_recovery`; [ $? -eq 0 ] \\\n && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1\"\n\n# Needed to create system tables etc.\n# ExecStartPre=\/usr\/bin\/mysql_install_db -u mysql\n\n# Start main service\n# MYSQLD_OPTS here is for users to set in \/etc\/systemd\/system\/mariadb.service.d\/MY_SPECIAL.conf\n# Use the [Service] section and Environment=\"MYSQLD_OPTS=...\".\n# This isn't a replacement for my.cnf.\n# _WSREP_NEW_CLUSTER is for the exclusive use of the script galera_new_cluster\nExecStart=\/usr\/sbin\/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION\n\n# Unset _WSREP_START_POSITION environment variable.\nExecStartPost=\/bin\/sh -c \"systemctl unset-environment _WSREP_START_POSITION\"\n\n\n\nKillSignal=SIGTERM\n\n# Don't want to see an automated SIGKILL ever\nSendSIGKILL=no\n\n# Restart crashed server only, on-failure would also restart, for example, when\n# my.cnf contains unknown option\nRestart=on-abort\nRestartSec=5s\n\nUMask=007\n\n##############################################################################\n## USERs can override\n##\n##\n## by creating a file in \/etc\/systemd\/system\/mariadb.service.d\/MY_SPECIAL.conf\n## and adding\/setting the following under [Service] will override this file's\n## settings.\n\n# Useful options not previously available in [mysqld_safe]\n\n# Kernels like killing mysqld when out of memory because its big.\n# Lets temper that preference a little.\n# OOMScoreAdjust=-600\n\n# Explicitly start with high IO priority\n# BlockIOWeight=1000\n\n# If you don't use the \/tmp directory for SELECT ... OUTFILE and\n# LOAD DATA INFILE you can enable PrivateTmp=true for a little more security.\nPrivateTmp=false\n\n# Set an explicit Start and Stop timeout of 900 seconds (15 minutes!)\n# this is the same value as used in SysV init scripts in the past\n# Galera might need a longer timeout, check the KB if you want to change this:\n# https:\/\/mariadb.com\/kb\/en\/library\/systemd\/#configuring-the-systemd-service-timeout\nTimeoutStartSec=900\nTimeoutStopSec=900\n\n##\n## Options previously available to be set via [mysqld_safe]\n## that now needs to be set by systemd config files as mysqld_safe\n## isn't executed.\n##\n\n# Number of files limit. previously [mysqld_safe] open-files-limit\nLimitNOFILE=32768\n\n# Maximium core size. previously [mysqld_safe] core-file-size\n# LimitCore=\n\n# Nice priority. previously [mysqld_safe] nice\n# Nice=-5\n\n# Timezone. previously [mysqld_safe] timezone\n# Environment=\"TZ=UTC\"\n\n# Library substitutions. previously [mysqld_safe] malloc-lib with explicit paths\n# (in LD_LIBRARY_PATH) and library name (in LD_PRELOAD).\n# Environment=\"LD_LIBRARY_PATH=\/path1 \/path2\" \"LD_PRELOAD=\n\n# Flush caches. previously [mysqld_safe] flush-caches=1\n# ExecStartPre=sync\n# ExecStartPre=sysctl -q -w vm.drop_caches=3\n\n# numa-interleave=1 equalivant\n# Change ExecStart=numactl --interleave=all \/usr\/sbin\/mysqld......\n\n# crash-script equalivent\n# FailureAction=<\/pre>\n\n\n\nNow, save the file, and start your cyberpanel installation as it is with the following:<\/p>\n\n\n\n
sh <(curl https:\/\/cyberpanel.net\/install.sh || wget -O - https:\/\/cyberpanel.net\/install.sh)<\/pre>\n\n\n\nHope it solves the problem. I am hoping, soon enough Cyberpanel would be able to address the issue the way they solved this for CentOS 8 and Ubuntu. <\/p>\n","protected":false},"excerpt":{"rendered":"
If you are trying to install Cyberpanel 2.1.2 on CentOS 7, you are probably seeing your installation fails with the following in the screen: This is appearing because Cyberpanel installation script located here: wants to restart MariaDB 10.4 with the following: Unfortunately, this was only possible until 10.3 or below. Since 10.4, Mariadb uses the … Continue reading “[ERROR] We are not able to run systemctl start mysql return code: 5. Fatal error, see \/var\/log\/installLogs.txt for full details – Cyberpanel”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[406,412],"tags":[407,451,599,87,600],"_links":{"self":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/803"}],"collection":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/comments?post=803"}],"version-history":[{"count":1,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/803\/revisions"}],"predecessor-version":[{"id":804,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/803\/revisions\/804"}],"wp:attachment":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/media?parent=803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/categories?post=803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/tags?post=803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}