I'm running Gentoo Linux and recently needed to install mySQL (older version). The compilation was successful, however setting up the server failed. I'm on this step: https://wiki.gentoo.org/wiki/MySQL#Preliminary_configuration The complete log follows: WaylandGnome /home/igor/dbhandler/Debug # cat /var/tmp/portage/dev-db/mysql-5.7.41/temp/build.log * Detected settings: * ================== * MySQL User: mysql * MySQL Group: mysql * MySQL DATA directory: /var/lib/mysql * MySQL TMP directory: /tmp * PID DIR: /run/mysqld * Install db log: /tmp/install_db.221119222.log * Install server log: /tmp/install_mysqld.633921321.log * Trying to get password for mysql 'root' user from 'mysql' section ... * Trying to get password for mysql 'root' user from 'client' section ... * No password for mysql 'root' user was specified via environment * variable MYSQL_ROOT_PASSWORD and no password was found in config * file like '/root/.my.cnf'. * To continue please provide a password for the mysql 'root' user * now on console: * NOTE: Please avoid ["'\_%] characters in the password! > * Retype the password > * Initializing mysql data directory: /usr/sbin/mysqld --loose-skip-host-cache --loose-skip-name-resolve --loose-skip-networking --loose-skip-slave-start --loose-skip-federated --loose-skip-ssl --loose-skip-log-bin --loose-skip-relay-log --loose-skip-slow-query-log --loose-skip-external-locking --loose-skip-log-slave-updates --initialize-insecure --init-file='/tmp/tz.222211327.sql' --basedir='/usr' --datadir='/var/lib/mysql' --tmpdir='/tmp' --log-error='/tmp/install_db.221119222.log' --user=mysql /var/tmp/portage/dev-db/mysql-5.7.41/temp/environment: line 3774: /tmp/install_db.221119222.log: Permission denied * ERROR: dev-db/mysql-5.7.41::gentoo failed (config phase): * Failed to initialize mysql data directory. Please review '/tmp/install_db.221119222.log'! * * Call stack: * ebuild.sh, line 136: Called pkg_config * environment, line 3777: Called die * The specific snippet of code: * die "Failed to initialize ${PN} data directory. Please review '${mysql_install_log}'!"; * * If you need support, post the output of emerge --info '=dev-db/mysql-5.7.41::gentoo', * the complete build log and the output of emerge -pqv '=dev-db/mysql-5.7.41::gentoo'. * The complete build log is located at '/var/tmp/portage/dev-db/mysql-5.7.41/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/mysql-5.7.41/temp/environment'. * Working directory: '/var/tmp/portage/dev-db/mysql-5.7.41/empty' * S: '/var/tmp/portage/dev-db/mysql-5.7.41/work/mysql-5.7.41' WaylandGnome /home/igor/dbhandler/Debug # How do I identify the issue? I'm trying this at home - for the development/testing purposes. The info is in the original post above. EDIT: WaylandGnome /home/igor/dbhandler/Debug # ls -la / total 202248 drwxr-xr-x 21 root root 4096 Aug 21 2021 . drwxr-xr-x 21 root root 4096 Aug 21 2021 .. drwxr-xr-x 2 root root 4096 Apr 3 2024 bin drwxr-xr-x 3 root root 4096 Jun 16 2024 boot drwxr-xr-x 16 root root 3580 Jul 16 21:07 dev drwxr-xr-x 79 root root 4096 Jul 22 19:54 etc drwxr-xr-x 3 root root 4096 Aug 16 2021 home drwxr-xr-x 12 root root 4096 Jun 24 2024 lib drwxr-xr-x 6 root root 4096 Dec 8 2024 lib64 drwx------ 2 root root 16384 Aug 9 2021 lost+found drwxr-xr-x 2 root root 4096 Aug 8 2021 media drwxr-xr-x 4 root root 4096 Aug 29 2021 mnt -rw-r--r-- 1 root root 9865 Aug 21 2021 modules_loaded drwxr-xr-x 2 root root 4096 Aug 8 2021 opt dr-xr-xr-x 278 root root 0 Jul 16 16:07 proc drwx------ 6 root root 4096 Jul 21 20:08 root drwxr-xr-x 20 root root 680 Jul 16 21:08 run drwxr-xr-x 2 root root 4096 Jun 24 2024 sbin -rw-r--r-- 1 root root 207004312 Aug 9 2021 stage3-amd64-openrc-20210808T170546Z.tar.xz dr-xr-xr-x 13 root root 0 Jul 16 21:25 sys drwxrwxrwt 10 root root 4096 Jul 23 22:47 tmp drwxr-xr-x 12 root root 4096 Aug 8 2021 usr drwxr-xr-x 10 root root 4096 Dec 8 2024 var WaylandGnome /home/igor/dbhandler/Debug # As you can see, the /tmp directory have the right rights and its owned by root (the user who tries to write the log). EDIT2: WaylandGnome /home/igor/dbhandler/Debug # ls -la /tmp/ total 1696 drwxrwxrwt 10 root root 4096 Jul 27 10:57 . drwxr-xr-x 21 root root 4096 Aug 21 2021 .. srw-rw-rw- 1 root root 0 Jul 16 21:07 dbus-LrgQbbHE srw-rw-rw- 1 root root 0 Jul 16 21:07 dbus-PLcQRTxs srwxrwxrwx 1 igor igor 0 Jul 16 21:08 dbus-SUXCQJk4lu drwx------ 2 igor igor 4096 Jul 27 10:57 dhcpcd-igor drwxrwxrwt 2 root root 4096 Jul 16 21:07 .font-unix drwxrwxrwt 2 root root 4096 Jul 16 21:08 .ICE-unix -rw-r--r-- 1 mysql root 0 Jul 16 21:10 install_db.221119222.log -rw-r--r-- 1 mysql root 0 Jul 16 21:10 install_mysqld.633921321.log drwxrwxr-x 2 portage portage 4096 Jul 16 21:07 portage drwx------ 2 igor igor 4096 Jul 16 21:08 ssh-XXXXXXjJPiXO drwx------ 2 igor igor 4096 Jul 16 21:09 Temp-204e4dce-7ae7-4061-98a7-02c745548045 -rw-r--r-- 1 igor igor 11409 Jul 17 19:57 tmpaddon -rw-r--r-- 1 igor igor 11409 Jul 20 14:41 tmpaddon-1 -rw-r--r-- 1 igor igor 11409 Jul 21 14:41 tmpaddon-2 -rw-r--r-- 1 igor igor 11409 Jul 22 20:23 tmpaddon-3 -rw-r--r-- 1 igor igor 11409 Jul 25 22:33 tmpaddon-4 -rw-r--r-- 1 igor igor 11409 Jul 26 22:33 tmpaddon-5 -rw-r--r-- 1 root root 1620537 Jul 16 21:10 tz.222211327.sql srwxr-xr-x 1 root root 0 Jul 16 21:07 wpa_ctrl_1714-1 drwxrwxrwt 2 root root 4096 Jul 16 21:08 .X11-unix drwxrwxrwt 2 root root 4096 Jul 16 21:07 .XIM-unix WaylandGnome /home/igor/dbhandler/Debug # As you can see the configure log file is there - but its size is 0. Something is definite wrong here... EDIT3: This is my mount results: WaylandGnome /home/igor/dbhandler/Debug # mount | grep tmp devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=10240k,nr_inodes=950062,mode=755) tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1520712k,nr_inodes=819200,mode=755) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=760352k,nr_inodes=190088,mode=700,uid=1000,gid=1000) WaylandGnome /home/igor/dbhandler/Debug # And this is the full mount result: WaylandGnome /home/igor/dbhandler/Debug # mount /dev/sda3 on / type ext4 (rw,noatime) devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=10240k,nr_inodes=950062,mode=755) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1520712k,nr_inodes=819200,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=760352k,nr_inodes=190088,mode=700,uid=1000,gid=1000) tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) EDIT3: I tried to run that command manually using my own home directory, but... /usr/sbin/mysqld --loose-skip-host-cache --loose-skip-name-resolve --loose-skip-networking --loose-skip-slave-start --loose-skip-federated --loose-skip-ssl --loose-skip-log-bin --loose-skip-relay-log --loose-skip-slow-query-log --loose-skip-external-locking --loose-skip-log-slave-updates --initialize-insecure --init-file='/home/igor/tz.222211327.sql' --basedir='/usr' --datadir='/var/lib/mysql' --tmpdir='/tmp' --log-error='/home/igor/install_db.221119222.log' --user=mysql 2025-08-01T19:22:05.565679Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2025-08-01T19:22:05.573910Z 0 [ERROR] Could not open file '/home/igor/install_db.221119222.log' for error logging: Permission denied 2025-08-01T19:22:05.574057Z 0 [ERROR] Aborting I presume this is some kind of compatibility issue as I also did this: WaylandGnome /home/igor/dbhandler/Debug # touch /home/igor/install_db.221119222.log WaylandGnome /home/igor/dbhandler/Debug # WaylandGnome /home/igor/dbhandler/Debug # and as you can see it finish successfully. I guess I will need to abandon the idea of using the mySQL 5 - at least for nnw... Thank you.

My error_log is filling up with tons of entries like: www.mine.com [Sun Dec 29 09:29:59 2024] [warn] [pid 903933] ssl_engine_mutex.c(105): (22)Invalid argument: [client AH02027: Failed to release SSL session cache lock www.mine.com [Sun Dec 29 09:30:00 2024] [warn] [pid 1177911] ssl_engine_mutex.c(92): (22)Invalid argument: [client AH02026: Failed to acquire SSL session cache lock www.mine.com [Sun Dec 29 09:30:00 2024] [warn] [pid 1177911] ssl_engine_mutex.c(105): (22)Invalid argument: [client AH02027: Failed to release SSL session cache lock www.mine.com [Sun Dec 29 09:30:00 2024] [warn] [pid 1177911] ssl_engine_mutex.c(92): (22)Invalid argument: [client AH02026: Failed to acquire SSL session cache lock www.mine.com [Sun Dec 29 09:30:00 2024] [warn] [pid 1177911] ssl_engine_mutex.c(105): (22)Invalid argument: [client AH02027: Failed to release SSL session cache lock The host solved it at first with: > I've set the following option in your MySQL configuration file: > > log_warnings = 0 > > This will prevent the logging of warnings, but won't interfere with > normal error logging. But after another MySQL upgrade they now say: > This should be resolved now. The problem was the old setting used to > suppress these of "log_warnings" was deprecated in 5.7 and removed in > mySQL 8.0. I have updated the configuration file with the new mySQL > directive below. > > log_error_verbosity = 1 > > This will result in the same behavior of warnings being suppressed and > only actual errors will be logged going forward. It didn't work so they replied back: > Our lead sysadmin has looked into this and unfortunately could not > find a way to suppress those warnings, so I'm afraid those are > "normal" for all intents and purposes. They provided some additional information: > The only mutex value set in any of the active Apache configuration > files is the following: > > Mutex default:/usr/nobody > > 'DUMP_RUN_CFG' returns these mutex values: > > Mutex default: dir="/usr/nobody" mechanism=default Mutex > ssl-cache: using_defaults Mutex mpm-accept: using_defaults Mutex > authdigest-opaque: using_defaults Mutex rewrite-map: using_defaults > Mutex ssl-stapling-refresh: using_defaults Mutex authdigest-client: > using_defaults Mutex ssl-stapling: using_defaults Mutex proxy: > using_defaults > > There had been a reported bug that caused this error in much earlier > versions of Ubuntu + Apache, such as: > > https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1565744 > > but in those cases the mutex mechanism returned by 'DUMP_RUN_CFG' was: > > mechanism=fcntl > > and we haven't been able to find anything relevant to the version of > Apache running on your server (2.4.62). Does anyone know how to stop all this logging, it makes it hard to find actual things in error_log that need to be looked at. TIA!!

I have yum install mysql in **CentOS 6.4**. Now, when I use mysql command, it throws the following error: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' When I check the directory there is no mysql folder. How should I solve this problem? It's worth mentioning when I do service mysql start (or with mysqld) it errors **unrecognized service**. I should mention that I have changed the path in my.cnf but nothing happens. The problem is that no *.sock file exists at all. **Update**: Results of checking mysql process with mysqladmin -u root -p status returns: mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! Also when I directly want to run /etc/init.d/mysqld it errors that it cannot resolve the ip (localhost.localdomain). **Second Update:** I have run the command [root@localhost /]# rpm -qa | grep mysql and it returns: mysql-libs-5.1.73-3.el6_5.x86_64 mysql-libs-5.1.73-3.el6_5.i686 mysql-5.1.73-3.el6_5.x86_64 mysql-server-5.1.73-3.el6_5.i686

I've created a user ... but forgotten the password

mysql> create user 'blayo'@'%' identified by 'right';

Which Linux command line tool can **encrypt the password the same way mysql 5.5 does ?**

mysql> select Password,User from mysql.user
------------------------------------------+-------+
*920018161824B14A1067A69626595E68CB8284CB | blayo |

...to be sure I use the right one

$ tool right
*920018161824B14A1067A69626595E68CB8284CB

I have installed Linux Mint 18.1 Serena and I have XAMPP 5.6.28-1 on my computer. After I turn on my computer, I must run the XAMPP control panel and I must start Apache and MySQL manually. Does anyone know how this can be done automatically? I don't want to turn on Apache and MySql every time when I start / restart my computer.

When I try to start postfix I get these errors: /usr/sbin/postconf: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No such...r directory /usr/bin/newaliases: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No suc...r directory /usr/sbin/postfix: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No suc...r directory Postfix use to work fine until I installed mysql. I'm not sure why mysql is even related to the Postfix errors. When I run the find . -name 'libmysqlclient*' command I get this: ./usr/lib64/mysql/libmysqlclient.so.21 ./usr/lib64/mysql/libmysqlclient.so.21.2.30 # ls -al /usr/lib64/mysql total 7520 drwxr-xr-x. 5 root root 109 Sep 29 13:47 . dr-xr-xr-x. 49 root root 28672 Sep 29 13:49 .. lrwxrwxrwx. 1 root root 25 Sep 28 21:53 libmysqlclient.so.21 -> libmysqlclient.so.21.2.30 -rwxr-xr-x. 1 root root 7651120 Jul 6 17:53 libmysqlclient.so.21.2.30 drwxr-xr-x. 4 root root 28 Sep 28 21:53 mecab drwxr-xr-x. 2 root root 4096 Sep 28 21:53 plugin drwxr-xr-x. 3 root root 131 Sep 28 21:53 private There is no 18 version installed and I'm confused as to why it is looking for 18 instead of 21. Further info which my be helpful: mysql-community-server-8.0.30-1.el7.x86_64 #which mysql: /bin/mysql/mysql #mysql -V: Ver 8.0.30 for Linux on x86_64 (MySQL Community Server - GPL) #mysqld -V: /usr/sbin/mysqld Ver 8.0.30 for Linux on x86_64 (MySQL Community Server - GPL) #php -v PHP 8.0.20 (cli) #systemctl status mysqld: Active: active (running) since Fri 2022-09-30 23:27:02 CDT; 3 days ago # rpm -qa postfix: postfix-2.10.1-6.amzn2.0.3.x86_64 AWS Linux 2 Server ***Can anyone help me with this? I checked other posts on here which are similar to my issue, however, I wasn't able to find a solution that was close enough to my situation that I could try.*** Finally, I also ran this command which outputs a ton of info which is why I saved this for the end of this post: # repoquery --whatprovides *libmysqlclient* mysql-community-libs-0:8.0.18-1.el7.i686 mysql-community-libs-0:8.0.11-1.el7.i686 mysql-community-devel-0:8.0.11-1.el7.i686 mysql-community-libs-0:8.0.27-1.el7.i686 mysql-community-libs-compat-0:8.0.15-1.el7.i686 mysql-community-libs-0:8.0.27-1.el7.x86_64 mysql-community-devel-0:8.0.17-1.el7.i686 mysql-workbench-community-0:6.3.5-1.el7.x86_64 mysql-community-libs-0:8.0.30-1.el7.i686 mysql-community-devel-0:8.0.15-1.el7.x86_64 mysql-community-libs-compat-0:8.0.24-1.el7.i686 mysql-community-libs-compat-0:8.0.26-1.el7.i686 mysql-workbench-community-0:8.0.16-1.el7.x86_64 mysql-community-libs-0:8.0.26-1.el7.i686 mysql-community-libs-0:8.0.17-1.el7.i686 mysql-workbench-community-0:8.0.12-1.el7.x86_64 mysql-community-devel-0:8.0.21-1.el7.i686 mysql-community-libs-compat-0:8.0.13-1.el7.i686 mysql-community-libs-compat-0:8.0.16-2.el7.i686 mariadb-devel-1:5.5.60-1.amzn2.x86_64 mysql-community-devel-0:8.0.16-2.el7.i686 mysql-community-devel-0:8.0.19-1.el7.x86_64 mysql-community-devel-0:8.0.18-1.el7.x86_64 mysql-community-libs-0:8.0.16-2.el7.i686 mysql-community-libs-compat-0:8.0.22-1.el7.i686 mariadb-devel-1:5.5.56-2.amzn2.0.2.x86_64 mysql-community-libs-0:8.0.16-2.el7.x86_64 mysql-community-devel-0:8.0.26-1.el7.i686 mysql-community-libs-0:8.0.22-1.el7.x86_64 mysql-community-libs-0:8.0.28-1.el7.x86_64 mysql-community-libs-0:8.0.23-1.el7.x86_64 mysql-community-devel-0:8.0.30-1.el7.i686 mysql-community-devel-0:8.0.26-1.el7.x86_64 mysql-community-libs-compat-0:8.0.19-1.el7.i686 mysql-community-devel-0:8.0.11-1.el7.x86_64 mysql-community-libs-0:8.0.13-1.el7.i686 mysql-community-libs-compat-0:8.0.12-1.el7.i686 mariadb-devel-1:5.5.62-1.amzn2.0.1.x86_64 mysql-workbench-community-0:8.0.22-1.el7.x86_64 mysql-community-devel-0:8.0.15-1.el7.i686 mysql-community-devel-0:8.0.12-1.el7.x86_64 mysql-community-devel-0:8.0.12-1.el7.i686 mysql-workbench-community-0:6.2.4-1.el7.x86_64 mysql-community-devel-0:8.0.23-1.el7.i686 mariadb-libs-1:5.5.62-1.amzn2.0.1.i686 mysql-community-devel-0:8.0.16-1.el7.i686 mysql-community-libs-compat-0:8.0.25-1.el7.x86_64 mysql-community-libs-compat-0:8.0.21-1.el7.i686 mysql-community-libs-0:8.0.21-1.el7.x86_64 mysql-workbench-community-0:8.0.13-1.el7.x86_64 mysql-community-libs-compat-0:8.0.14-1.el7.x86_64 mysql-community-libs-compat-0:8.0.27-1.el7.x86_64 mysql-community-libs-compat-0:8.0.30-1.el7.i686 mysql-community-libs-compat-0:8.0.23-1.el7.i686 mysql-community-devel-0:8.0.14-1.el7.x86_64 mariadb-devel-1:5.5.56-2.amzn2.x86_64 mysql-community-libs-0:8.0.17-1.el7.x86_64 mysql-community-devel-0:8.0.22-1.el7.i686 mysql-community-libs-0:8.0.20-1.el7.i686 mariadb-libs-1:5.5.68-1.amzn2.i686 mysql-community-libs-0:8.0.25-1.el7.i686 mariadb-libs-1:5.5.56-2.amzn2.x86_64 mysql-community-libs-0:8.0.16-1.el7.i686 mysql-community-libs-compat-0:8.0.14-1.el7.i686 mariadb-libs-1:5.5.68-1.amzn2.x86_64 mysql-community-libs-compat-0:8.0.19-1.el7.x86_64 mysql-community-libs-0:8.0.12-1.el7.i686 mysql-workbench-community-0:6.3.6-1.el7.x86_64 mysql-workbench-community-0:6.3.7-1.el7.x86_64 mysql-community-libs-0:8.0.11-1.el7.x86_64 mysql-community-libs-compat-0:8.0.25-1.el7.i686 mysql-community-libs-0:8.0.20-1.el7.x86_64 mariadb-libs-1:5.5.60-1.amzn2.i686 mysql-community-libs-compat-0:8.0.30-1.el7.x86_64 mysql-community-libs-compat-0:8.0.11-1.el7.i686 mysql-community-libs-0:8.0.25-1.el7.x86_64 mariadb-devel-1:5.5.68-1.amzn2.x86_64 mysql-community-devel-0:8.0.22-1.el7.x86_64 mariadb-libs-1:5.5.56-2.amzn2.0.2.i686 mysql-community-libs-compat-0:8.0.21-1.el7.x86_64 mysql-community-libs-compat-0:8.0.18-1.el7.x86_64 mysql-community-devel-0:8.0.28-1.el7.i686 mariadb-libs-1:5.5.62-1.amzn2.0.1.x86_64 mysql-community-libs-compat-0:8.0.24-1.el7.x86_64 mysql-community-devel-0:8.0.28-1.el7.x86_64 mysql-community-libs-compat-0:8.0.18-1.el7.i686 mysql-community-libs-0:8.0.19-1.el7.i686 mysql-community-libs-0:8.0.15-1.el7.x86_64 mysql-community-devel-0:8.0.19-1.el7.i686 mysql-community-libs-0:8.0.28-1.el7.i686 mariadb-libs-1:5.5.64-1.amzn2.x86_64 mysql-workbench-community-0:6.2.5-1.el7.x86_64 mysql-community-libs-compat-0:8.0.16-1.el7.x86_64 mysql-community-libs-compat-0:8.0.28-1.el7.x86_64 mariadb-libs-1:5.5.60-1.amzn2.x86_64 mysql-workbench-community-0:8.0.14-1.el7.x86_64 mysql-workbench-community-0:8.0.15-1.el7.x86_64 mysql-community-libs-0:8.0.21-1.el7.i686 mysql-community-devel-0:8.0.23-1.el7.x86_64 mysql-community-libs-compat-0:8.0.11-1.el7.x86_64 mysql-workbench-community-0:6.3.4-1.el7.x86_64 mysql-workbench-community-0:6.2.3-1.el7.x86_64 mariadb-devel-1:5.5.64-1.amzn2.x86_64 mysql-community-devel-0:8.0.24-1.el7.x86_64 mysql-community-libs-0:8.0.23-1.el7.i686 mysql-workbench-community-0:6.3.3-1.el7.x86_64 mysql-community-devel-0:8.0.25-1.el7.i686 mysql-workbench-community-0:8.0.18-1.el7.x86_64 mysql-community-devel-0:8.0.20-1.el7.i686 mariadb-libs-1:5.5.64-1.amzn2.i686 mysql-community-libs-compat-0:8.0.23-1.el7.x86_64 mysql-community-devel-0:8.0.16-2.el7.x86_64 mysql-community-libs-0:8.0.14-1.el7.i686 mysql-community-libs-0:8.0.19-1.el7.x86_64 mysql-community-libs-compat-0:8.0.12-1.el7.x86_64 mysql-community-libs-compat-0:8.0.13-1.el7.x86_64 mysql-community-devel-0:8.0.17-1.el7.x86_64 mysql-community-devel-0:8.0.27-1.el7.x86_64 mysql-workbench-community-0:8.0.21-1.el7.x86_64 mysql-community-libs-0:8.0.22-1.el7.i686 mysql-community-devel-0:8.0.13-1.el7.x86_64 mysql-community-libs-compat-0:8.0.26-1.el7.x86_64 mysql-workbench-community-0:6.3.6-2.el7.x86_64 mysql-workbench-community-0:6.3.8-1.el7.x86_64 mysql-community-libs-0:8.0.24-1.el7.x86_64 mysql-community-libs-compat-0:8.0.16-1.el7.i686 mysql-community-libs-compat-0:8.0.17-1.el7.i686 mysql-community-libs-compat-0:8.0.22-1.el7.x86_64 mysql-community-libs-0:8.0.30-1.el7.x86_64 mysql-community-libs-compat-0:8.0.28-1.el7.i686 mysql-community-devel-0:8.0.27-1.el7.i686 mysql-community-libs-compat-0:8.0.15-1.el7.x86_64 mysql-community-devel-0:8.0.25-1.el7.x86_64 mysql-community-devel-0:8.0.18-1.el7.i686 mysql-community-libs-0:8.0.18-1.el7.x86_64 mysql-community-devel-0:8.0.16-1.el7.x86_64 mysql-community-libs-0:8.0.26-1.el7.x86_64 mysql-workbench-community-0:8.0.20-1.el7.x86_64 mysql-community-libs-0:8.0.12-1.el7.x86_64 mysql-community-libs-0:8.0.15-1.el7.i686 mysql-workbench-community-0:8.0.19-1.el7.x86_64 mysql-community-devel-0:8.0.30-1.el7.x86_64 mysql-community-libs-compat-0:8.0.17-1.el7.x86_64 mysql-community-libs-compat-0:8.0.20-1.el7.i686 mysql-community-libs-0:8.0.14-1.el7.x86_64 mysql-community-libs-compat-0:8.0.20-1.el7.x86_64 mysql-community-libs-0:8.0.24-1.el7.i686 mysql-community-devel-0:8.0.14-1.el7.i686 mysql-community-devel-0:8.0.13-1.el7.i686 mysql-community-libs-compat-0:8.0.16-2.el7.x86_64 mysql-community-devel-0:8.0.24-1.el7.i686 mysql-community-libs-compat-0:8.0.27-1.el7.i686 mysql-community-libs-0:8.0.13-1.el7.x86_64 mariadb-libs-1:5.5.56-2.amzn2.0.2.x86_64 mysql-workbench-community-0:8.0.17-1.el7.x86_64 mysql-community-devel-0:8.0.20-1.el7.x86_64 mysql-community-devel-0:8.0.21-1.el7.x86_64 mysql-community-libs-0:8.0.16-1.el7.x86_64

Is there any way to install MySQL 5.1 and PHP 5.3 on Centos 7. I researched a lot but could not find any link which gives step by step procedure. Can someone please give me steps to be followed to install these .

My server has 800+ days uptime, but ever since a couple weeks the **MySQL server** keeps hitting **100% CPU** and I have to restart the mysqld service. Where do I start to find out where this issue is coming from? As all the sites on my server keep freezing until I restart. I don't want to keep restarting the service every time. Sometimes it is after a couple minutes, sometimes a couple hours, sometimes a couple days. Nothing changed really. I only once updated the my.cnf file for the default character set and restarted recently, but I don't believe this is linked in any way. **--- Server details ---**
Debian 10 Buster
MySQL Version: 14.14
Average users: 150 - 200 per day
vCPU's: 4
RAM: 4GB
**my.cnf** No slow queries shown so far. [mysqld] collation_server = utf8mb4_unicode_ci character_set_server = utf8mb4 sql-mode="NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" slow_query_log = 1 slow_query_log_file = /var/log/mysql/slow_queries.log log_queries_not_using_indexes = 'OFF' long_query_time = 5

In my CentOS Stream Linux 9 when I run the command: yum install perl-DBD-MySQL It gives me an error: Transaction Summary ================================================================================================================================================================================================================ Install 3 Packages Total size: 1.4 M Installed size: 7.3 M Is this ok [y/N]: y Downloading Packages: [SKIPPED] mysql-common-8.0.41-2.el9.x86_64.rpm: Already downloaded [SKIPPED] mysql-libs-8.0.41-2.el9.x86_64.rpm: Already downloaded [SKIPPED] perl-DBD-MySQL-4.053-1.el9.x86_64.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'yum clean packages'. Error: Transaction test error: file /usr/share/mysql/charsets/Index.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/armscii8.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/ascii.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp1250.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp1251.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp1256.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp1257.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp850.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp852.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/cp866.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/dec8.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/geostd8.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/greek.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/hebrew.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/hp8.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/keybcs2.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/koi8r.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/koi8u.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/latin1.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/latin2.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/latin5.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/latin7.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/macce.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/macroman.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 file /usr/share/mysql/charsets/swe7.xml from install of mysql-common-8.0.41-2.el9.x86_64 conflicts with file from package MariaDB-common-10.6.22-1.el9.x86_64 I have done yum install perl-DBD-MySQL --enablerepo=* But got no luck! What else can I do? Thanks in advance!

I tried installing the package "default-mysql-server" via apt. Like this sudo apt install default-mysql-server. While the install was running i got this error:

Preparing to unpack .../mariadb-server_1%3a10.11.11-0+deb12u1_arm64.deb ...
dpkg: error processing archive /var/cache/apt/archives/mariadb-server_1%3a10.11.11-0+deb12u1_arm64.deb (--unpack):
 new mariadb-server package pre-installation script subprocess returned error exit status 1
Selecting previously unselected package default-mysql-server.
Preparing to unpack .../default-mysql-server_1.1.0_all.deb ...
Unpacking default-mysql-server (1.1.0) ...
Errors were encountered while processing:
 /var/cache/apt/archives/mariadb-server_1%3a10.11.11-0+deb12u1_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

For me this error said nothing that would help me, so i tried to finde some solutions online and came across, that maybe the created mysql user password had an error, so i checked it:

sudo chage -l mysql
Last password change					: May 12, 2025
Password expires					: never
Password inactive					: never
Account expires						: never
Minimum number of days between password change		: -1
Maximum number of days between password change		: -1
Number of days of warning before password expires	: -1

I could not find any documentation what -1 represents, but for me it looks off, i now that most of the time its 0 99999 7. Im running Debian 12 Version: 6.1.0-34-arm64. On older machines i did not get this error, but now i got three machines with the same version, having the same problem. I checked also my root and sudo user but they looked fine like always no -1 or something else, so my guess is that something is off with apt but not sure. I also tried to install it as the root user without sudo but still got the same error. Also i rebooted and reinstalled debian on that system, but nothing seems to effect this. If someone knows this issued and can help, that would be awesome. If more informations are need feel free to ask, i really would like to now whats the matter with this.

I am building a set of bash scripts which basically prepare apache virtual hosts, git repositories and other stuff on a cloud server. So far so good, everything is working, but a big problem occurred: **MySQL database and users creation**. The current scripts use ssh with keys to authenticate to the cloud server and everyone from my team can execute commands. I want to keep it this way and somehow let them create new MySQL database and user without needing to login to mysql as root or any other user with high privileges, but I don't have any solution for this. **Idea #1** is to create a new mysql user without password and give it full rights (like root) but make it usable only @'localhost'. **Idea #2** is to store the password for this MySQL control user in a file and make it accessible only to the current ssh user which the other scripts use. Then the mysql login will use this stored password to login and create the database and user. I don't know which option is better and I know they are dangerous. I ask for opinion and any better ideas.

I get php warning: > mysql_connect(): Headers and client library minor version mismatch. Headers:50547 Library:50624 Also I read that I need to install mysqlnd to my server. I tried do it using: > yum install php-mysqlnd but get error: Transaction check error: file /etc/php.ini from install of php-common-5.5.34-1.el6.remi.x86_64 conflicts with file from package php56w-common-5.6.20-1.w7.x86_64 file /usr/lib64/....

I want to run a website from my computer. I use XAMPP on a Kali Linux. I installed MySQL server with the command: apt-get install mysql-server After it was successfully installed, I entered the command mysql_secure_installation It prompted me to login to MySQL, but it repeatedly gave the error ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) I tried my password several times, with no changes just to check if I have typed it wrong the first time. Can anyone tell me how to fix this? I am following a tutorial from this site .

In Debian **Desktop** 12 if I want to do a remote connection as client to a MySQL Server in other machine in the LAN I need use the mysql command, when it is executed happens the following:

manueljordan@vm163:~$ mysql 
bash: mysql: command not found

If is executed the apt search mysql-client command happens the following:

manueljordan@vm163:~$ apt search mysql-client
Sorting... Done
Full Text Search... Done
default-mysql-client/stable 1.1.0 all
  MySQL database client binaries (metapackage)

default-mysql-client-core/stable 1.1.0 all
  MySQL database core client binaries (metapackage)

Therefore: * What is the correct package to install? **default-mysql-client** or **default-mysql-client-core**? and Why? And just being curious: * What exists two packages? * What is the difference between them? Thanks in advance

I'm on Ubuntu 18.04, I'm installing Mysql, i typed: sudo apt-get install mysql-server i received this with an error at the end: Reading package lists... Done Building dependency tree Reading state information... Done mysql-server is already the newest version (5.7.28-0ubuntu0.18.04.4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up mysql-server-5.7 (5.7.28-0ubuntu0.18.04.4) ... /var/lib/dpkg/info/mysql-server-5.7.postinst: line 191: /usr/share/mysql-common/configure-symlinks: No such file or directory dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.7; however: Package mysql-server-5.7 is not configured yet. dpkg: error processing package mysql-server (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: mysql-server-5.7 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1) Additional Information: When i typed: apt-cache policy mysql-common I got this response: mysql-common: Installed: 1:10.4.11+maria~bionic Candidate: 1:10.4.11+maria~bionic Version table: *** 1:10.4.11+maria~bionic 100 100 /var/lib/dpkg/status 1:10.3.21+maria~bionic 500 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main ppc64el Packages 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main arm64 Packages 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main amd64 Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main ppc64el Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main arm64 Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main amd64 Packages 1:10.3.20+maria~bionic 500 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main ppc64el Packages 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main arm64 Packages 500 http://ftp.utexas.edu/mariadb/repo/10.3/ubuntu bionic/main amd64 Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main ppc64el Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main arm64 Packages 500 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic/main amd64 Packages 1:10.3.14+maria~bionic 500 500 http://archive.mariadb.org/mariadb-10.3.14/repo/ubuntu bionic/main ppc64el Packages 500 http://archive.mariadb.org/mariadb-10.3.14/repo/ubuntu bionic/main amd64 Packages 500 http://archive.mariadb.org/mariadb-10.3.14/repo/ubuntu bionic/main arm64 Packages 5.8+1.0.4 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages I have tried SO MANY solutions, from desintalling mysql, installing mariadb, seeing different solutions on stackOverflow.. and didnt get to put my finger on the error exactly. Really appreciate the help i have been stuck with this for a while...

There are many servers in the network that I manage, and throughout that network, mysql is the standard and only "mysql-like" database used. (There's some postgre but that is another matter). Today, I wanted to install mysql on a new server (rPi running bookworm) and was surprised that "mysql-client" and "mysql-server" are no longer candidates for the platform. Instead, it seems we're supposed to use apt install default-mysql-client default-mysql-server So I did that, and mariadb was installed. (I quickly removed it and the other products installed with it.) I've tried to search how to force this to mysql rather than mariadb, to no avail. I checked /etc/alternatives and that does not seem to be the thing in my way. My research has led me only to comments like "Just use mariadb - it'll work." But there's apparently no refund when that proves incorrect. :| I know, mariadb is **meant to be** "almost completely" compatible with mysql. I don't need "almost" in this network. I need reliability and consistency. I'm sure the key word here is "**default**"-mysql (the key word should be mysql - call it what it is) but I could find no way to set my preferred **default**. How can I install mysql and not mariadb on Bookworm and any other variants that try to force us away from mysql? I get that there is SQL-level compatibility between Maria and MySql. But I'm more concerned about administration and what the NEXT change one or the other might make. Anyone with administrative experience will agree that maintaining two slightly dissimilar products is more than twice the effort from the standpoint that not only do you have to "know" both platforms, you also have to know the differences.

In a server that I do not have admin access I managed to make an ssh tunnel as:

ssh -N -L 33308:127.0.0.1:3306 user@example.com

Then I attempt to connect into mysql via the tunnel:

mysql -u testusr -p -h 127.0.0.1 -P 33308 testdb

By I ended getting the error:

ERROR 1045 (28000): Access denied for user 'testusr'@'127.0.0.1' (using password: YES)

But once I have a shell session upon DB I manage to connect into mysql like this:

mysql -u testusr -p -h localhost testdb
mysql>

But I am unable to connect like this:

mysql -u testusr -p -h 127.0.0.1 testdb
ERROR 1045 (28000): Access denied for user 'testusr'@'127.0.0.1' (using password: YES)

Meaning that testusr is able to be connected via providing localhost as domain upon connection. So how I can setup the tunnel in order to be able to connect as?

mysql -u testusr -p -h localhost -P 33308 testdb

Upon my local machine?

I'm in the process of setting up a singe-node Slurm workstation machine and I believe I followed the process closely and everything is working just fine. *See* below: **sudo systemctl restart slurmdbd && sudo systemctl status slurmdbd**

● slurmdbd.service - Slurm DBD accounting daemon
     Loaded: loaded (/usr/lib/systemd/system/slurmdbd.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-03-09 17:15:43 CET; 10ms ago
       Docs: man:slurmdbd(8)
   Main PID: 2597522 (slurmdbd)
      Tasks: 1
     Memory: 1.6M (peak: 1.8M)
        CPU: 5ms
     CGroup: /system.slice/slurmdbd.service
             └─2597522 /usr/sbin/slurmdbd -D -s

Mar 09 17:15:43 NeoPC-mat systemd: Started slurmdbd.service - Slurm DBD accounting daemon.
Mar 09 17:15:43 NeoPC-mat (slurmdbd): slurmdbd.service: Referenced but unset environment variable evaluates to an empty string: SLURMDBD_OPTIONS
Mar 09 17:15:43 NeoPC-mat slurmdbd: slurmdbd: Not running as root. Can't drop supplementary groups
Mar 09 17:15:43 NeoPC-mat slurmdbd: slurmdbd: accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL server version is: 5.5.5-10.11.8-MariaDB-0ubuntu0.24.04.1

**sudo systemctl restart slurmctld && sudo systemctl status slurmctld**

● slurmctld.service - Slurm controller daemon
     Loaded: loaded (/usr/lib/systemd/system/slurmctld.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-03-09 17:15:52 CET; 11ms ago
       Docs: man:slurmctld(8)
   Main PID: 2597573 (slurmctld)
      Tasks: 7
     Memory: 1.8M (peak: 2.8M)
        CPU: 4ms
     CGroup: /system.slice/slurmctld.service
             ├─2597573 /usr/sbin/slurmctld --systemd
             └─2597574 "slurmctld: slurmscriptd"

Mar 09 17:15:52 NeoPC-mat systemd: Starting slurmctld.service - Slurm controller daemon...
Mar 09 17:15:52 NeoPC-mat (lurmctld): slurmctld.service: Referenced but unset environment variable evaluates to an empty string: SLURMCTLD_OPTIONS
Mar 09 17:15:52 NeoPC-mat slurmctld: slurmctld: slurmctld version 23.11.4 started on cluster mat_workstation
Mar 09 17:15:52 NeoPC-mat systemd: Started slurmctld.service - Slurm controller daemon.
Mar 09 17:15:52 NeoPC-mat slurmctld: slurmctld: accounting_storage/slurmdbd: clusteracct_storage_p_register_ctld: Registering slurmctld at port 6817 with slurmdbd

**sudo systemctl restart slurmd && sudo systemctl status**

● slurmd.service - Slurm node daemon
     Loaded: loaded (/usr/lib/systemd/system/slurmd.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-03-09 17:16:02 CET; 9ms ago
       Docs: man:slurmd(8)
   Main PID: 2597629 (slurmd)
      Tasks: 1
     Memory: 1.5M (peak: 1.9M)
        CPU: 13ms
     CGroup: /system.slice/slurmd.service
             └─2597629 /usr/sbin/slurmd --systemd

Mar 09 17:16:02 NeoPC-mat systemd: Starting slurmd.service - Slurm node daemon...
Mar 09 17:16:02 NeoPC-mat (slurmd): slurmd.service: Referenced but unset environment variable evaluates to an empty string: SLURMD_OPTIONS
Mar 09 17:16:02 NeoPC-mat slurmd: slurmd: slurmd version 23.11.4 started
Mar 09 17:16:02 NeoPC-mat slurmd: slurmd: slurmd started on Sun, 09 Mar 2025 17:16:02 +0100
Mar 09 17:16:02 NeoPC-mat slurmd: slurmd: CPUs=16 Boards=1 Sockets=1 Cores=8 Threads=2 Memory=128445 TmpDisk=575645 Uptime=2069190 CPUSpecList=(null) FeaturesAvail=(null) FeaturesActive=(null)
Mar 09 17:16:02 NeoPC-mat systemd: Started slurmd.service - Slurm node daemon.

If needed, I can attach the results for the corresponding journalctl, but no error is shown other than these two messages slurmd.service: Referenced but unset environment variable evaluates to an empty string: SLURMD_OPTIONS and slurmdbd: Not running as root. Can't drop supplementary groups in the journalctl -fu slurmd and in the journalctl -fu slurmdbd, respectively. For some reason, however, I'm unable to run sinfo in a new tab even after setting the link the *slurm.conf* in my *.bashrc*... this is what I'm prompted with > sinfo: error: Couldn't find the specified plugin name for auth/munge > looking at all files sinfo: error: cannot find auth plugin for > auth/munge sinfo: error: cannot create auth context for auth/munge > sinfo: fatal: failed to initialize auth plugin which seems to depend on munge but I'm cannot really understand to what specifically — it is my first time installing Slurm. Any help is much appreciated, thanks in advance!

I have Ubuntu 24.04 on a Raspberry Pi 4 and after months of working fine, today it has jumped to a load 41 for no apparent reason. Can't connect to remote MySQL instance from the server. And gitlab keeps telling me my login is invalid. Not sure where to start researching what's causing the problem The only thing running all this time was gitlab 16.9.2 community edition, and I was doing some react Front and and node.js API development. I'd appreciate some tips on deciphering this crazy load?

Hi I was working on installing Slurm and got most things sorted out but upon launching

journalctl -fu slurmdbd

I get the following: > Jan 25 12:49:49 ... systemd: Stopped slurmdbd.service - Slurm DBD > accounting daemon. Jan 25 12:49:49 ... systemd: Started > slurmdbd.service - Slurm DBD accounting daemon. Jan 25 12:49:49 ... > (slurmdbd): slurmdbd.service: Referenced but unset > environment variable evaluates to an empty string: SLURMDBD_OPTIONS > Jan 25 12:49:49 ... slurmdbd: slurmdbd: error: Unable to open > pidfile `/run/slurmdbd.pid': Permission denied Jan 25 12:49:49 ... > slurmdbd: slurmdbd: Not running as root. Can't drop > supplementary groups Jan 25 12:49:49 ... slurmdbd: slurmdbd: > accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL server > version is: 8.0.40-0ubuntu0.24.04.1 Jan 25 12:49:49 ... > slurmdbd: slurmdbd: error: mysql_query failed: 1193 Unknown > system variable 'wsrep_on' Jan 25 12:49:49 ... slurmdbd: > select @@wsrep_on; Jan 25 12:49:49 ... slurmdbd: slurmdbd: > error: mysql_db_get_var_str: null result from query `select > @@wsrep_on;` Jan 25 12:49:49 ... slurmdbd: slurmdbd: slurmdbd > version 23.11.4 started which I assume being the cause for sinfo not displaying correctly with the following message: > sinfo: error: Couldn't find the specified plugin name for auth/munge > looking at all files sinfo: error: cannot find auth plugin for > auth/munge sinfo: error: cannot create auth context for auth/munge > sinfo: fatal: failed to initialize auth plugin To be noted that munge seems to be working correctly, see below, and therefore I cannot pinpoint the cause of Slum not showing sinfo option other than the issue I presented before. I also attach my **slurm.conf** and **slurmdbd.conf** for clarity in case helpful; this should be the recommended installation for a single node machine. Thanks in advance! **slurm.conf**

# slurm.conf file generated by configurator.html.
# Put this file on all nodes of your cluster.
# See the slurm.conf man page for more information.
#
ClusterName=
SlurmctldHost=
MpiDefault=none
ProctrackType=proctrack/cgroup
ReturnToService=2
SlurmctldPidFile=/run/slurmctld.pid
#SlurmctldPort=6817
SlurmdPidFile=/run/slurmd.pid
#SlurmdPort=6818
SlurmdSpoolDir=/var/lib/slurm/slurmd
SlurmUser=slurm
StateSaveLocation=/var/lib/slurm/slurmctld
SwitchType=switch/none
TaskPlugin=task/cgroup
#
# TIMERS
InactiveLimit=0
KillWait=30
MinJobAge=300
SlurmctldTimeout=120
SlurmdTimeout=300
Waittime=0
# SCHEDULING
SchedulerType=sched/backfill
SelectType=select/cons_tres
SelectTypeParameters=CR_CPU_Memory
#
#ACCOUNTING STORAGE PORT
AccountingStorageType=accounting_storage/slurmdbd
AccountingStorageHost=
AccountingStoreFlags=job_comment
JobCompType=jobcomp/none
JobAcctGatherType=jobacct_gather/cgroup
JobAcctGatherFrequency=30
SlurmctldDebug=info
SlurmctldLogFile=/var/log/slurm/slurmctld.log
SlurmdDebug=info
SlurmdLogFile=/var/log/slurm/slurmd.log
#
# COMPUTE NODES
NodeName= CoresPerSocket=8 ThreadsPerCore=2 RealMemory=126397 Sockets=1
PartitionName=local Nodes=ALL Default=YES MaxTime=INFINITE State=UP

**slurmdbd.conf**

=auth/munge
DbdHost=localhost
DebugLevel=info
StorageHost=localhost
StorageLoc=slurm_acct_db
StoragePass=slurmdbpass
StorageType=accounting_storage/mysql
StorageUser=slurm
LogFile=/var/log/slurm/slurmdbd.log
PidFile=/run/slurmdbd.pid
SlurmUser=slurm

P.S. output of munge -n | unmunge

STATUS:          Success (0)
ENCODE_HOST:      (127.0.1.1)
ENCODE_TIME:     2025-02-11 09:27:00 +0100 (1739262420)
DECODE_TIME:     2025-02-11 09:27:00 +0100 (1739262420)
TTL:             300
CIPHER:          aes128 (4)
MAC:             sha256 (5)
ZIP:             none (0)
UID:              (1000)
GID:              (1000)
LENGTH:          0