BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] mysql problem
- Subject: [Discuss] mysql problem
- From: cra at WPI.EDU (Chuck Anderson)
- Date: Sat, 3 Feb 2018 07:40:25 -0500
- In-reply-to: <00cf01d39c61$cb001f60$61005e20$@Polcari.com>
- References: <20180202195528.GA32708@rigel.localdomain> <00cf01d39c61$cb001f60$61005e20$@Polcari.com>
You should have a tmpfiles.d/mariadb.conf file that re-creates the directory on each boot: >cat /usr/lib/tmpfiles.d/mariadb.conf # Do not edit this file. # To override this, put /etc/tmpfiles.d/mariadb.conf instead. d /run/mariadb 0755 mysql mysql - d /run/mysqld 0755 mysql mysql - Make sure systemd-tmpfiles services are enabled (static): >sudo systemctl list-unit-files|grep tmpfile systemd-tmpfiles-clean.service static systemd-tmpfiles-setup-dev.service static systemd-tmpfiles-setup.service static systemd-tmpfiles-clean.timer static On Fri, Feb 02, 2018 at 03:09:54PM -0500, Joe Polcari wrote: > It will disappear - it's part of tmpfs which is memory. > Is /run 755? > Do you have selinux enabled? > What does getenforce return? > > > -----Original Message----- > From: Discuss [mailto:discuss-bounces+joe=polcari.com at blu.org] On Behalf Of > dan moylan > Sent: Friday, February 02, 2018 2:55 PM > To: boston linux and unix (blu) > Cc: betty moylan > Subject: Re: [Discuss] mysql problem > > > joe polcari writes: > > > What's the mysqld log say? > > > -----Original Message----- > > > running fc26 on acer aspire laptop > > using mariadb > > > mysql been running fine for months. > > > suddenly: > > > # mysql > > > ERROR 2002 (HY000): Can't connect to local MySQL server > > through socket '/var/lib/mysql/mysql.sock' (111 "Connection > > refused") > > > . > > . > > . > > here's a segment of /var/log/mariadb/mariadb.log > > 2018-01-28 15:47:06 140045973009600 [Note] Plugin 'FEEDBACK' is disabled. > 2018-01-28 15:47:07 140045973009600 [Note] Server socket created on IP: > '::'. > 2018-01-28 15:47:07 140045973009600 [Note] /usr/libexec/mysqld: ready for > connections. > Version: '10.1.30-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 > MariaDB Server > 2018-02-01 13:01:35 140045972228864 [Note] /usr/libexec/mysqld: Normal > shutdown > 2018-02-01 13:01:47 140045972228864 [Note] Event Scheduler: Purging the > queue. 0 events > 2018-02-01 13:03:09 140045266708224 [Note] InnoDB: FTS optimize thread > exiting. > 2018-02-01 13:03:09 140045972228864 [Note] InnoDB: Starting shutdown... > 2018-02-01 13:03:11 140045972228864 [Note] InnoDB: Waiting for page_cleaner > to finish flushing of buffer pool > 2018-02-01 13:03:49 140045972228864 [Note] InnoDB: Shutdown completed; log > sequence number 1819735 > 2018-02-01 13:03:52 140045972228864 [Note] /usr/libexec/mysqld: Shutdown > complete > > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: > innodb_empty_free_list_algorithm has been changed to legacy because of small > buffer pool size. In order to use backoff, increase buffer pool at least up > to 20MB. > > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: Using mutexes to ref > count buffer pool pages > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: The InnoDB memory heap is > disabled > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: Mutexes and rw_locks use > GCC atomic builtins > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: GCC builtin > __atomic_thread_fence() is used for memory barrier > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: Compressed tables use > zlib 1.2.11 > 2018-02-01 14:21:28 139831392437440 [Note] InnoDB: Using Linux native AIO > 2018-02-01 14:21:29 139831392437440 [Note] InnoDB: Using generic crc32 > instructions > 2018-02-01 14:21:29 139831392437440 [Note] InnoDB: Initializing buffer pool, > size = 128.0M > 2018-02-01 14:21:29 139831392437440 [Note] InnoDB: Completed initialization > of buffer pool > 2018-02-01 14:21:29 139831392437440 [Note] InnoDB: Highest supported file > format is Barracuda. > 2018-02-01 14:21:31 139831392437440 [Note] InnoDB: 128 rollback segment(s) > are active. > 2018-02-01 14:21:31 139831392437440 [Note] InnoDB: Waiting for purge to > start > 2018-02-01 14:21:31 139831392437440 [Note] InnoDB: Percona XtraDB > (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1819735 > 2018-02-01 14:21:38 139830732252928 [Note] InnoDB: Dumping buffer pool(s) > not yet started > 2018-02-01 14:21:38 139831392437440 [Note] Plugin 'FEEDBACK' is disabled. > 2018-02-01 14:21:39 139831392437440 [Note] Server socket created on IP: > '::'. > 2018-02-01 14:21:39 139831392271104 [ERROR] mysqld: Can't create/write to > file '/run/mariadb/mariadb.pid' (Errcode: 2 "No such file or directory") > 2018-02-01 14:21:39 139831392271104 [ERROR] Can't start server: can't create > PID file: No such file or directory > 2018-02-01 15:32:38 140015635989696 [Note] InnoDB: > innodb_empty_free_list_algorithm has been changed to legacy because of small > buffer pool size. In order to use backoff, increase buffer pool at least up > to 20MB. > > don't quite know what to make of it. fwiw /run/mariadb/ > didn't exist so i created it, but after reboot it was gone. > > tnx, > ole dan > > j. daniel moylan > 84 harvard ave > brookline, ma 02446-6202 > 617-777-0207 (cel) > jdm at moylan.us > www.moylan.us > [no html pls]
- References:
- [Discuss] mysql problem
- From: jdm at moylan.us (dan moylan)
- [Discuss] mysql problem
- From: Joe at Polcari.com (Joe Polcari)
- [Discuss] mysql problem
- Prev by Date: [Discuss] mysql problem
- Next by Date: [Discuss] mysql problem
- Previous by thread: [Discuss] mysql problem
- Next by thread: [Discuss] mysql problem
- Index(es):