Date: Thu, 23 Apr 2015 20:45:06 -0400 From: David Banning <david+dated+1430268309.f45134@skytracker.ca> To: questions@freebsd.org Cc: Neil Houston <neil.a.houston@gmail.com> Subject: Re: mysql keeping running but stops serving Message-ID: <20150424004504.GA49805@skytracker.ca> In-Reply-To: <1B3CE492-E5A5-4178-8B0B-CB96D28E81A5@gmail.com> References: <20150423222819.GA17139@skytracker.ca> <1B3CE492-E5A5-4178-8B0B-CB96D28E81A5@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 24, 2015 at 01:12:32AM +0100, Neil Houston wrote: > Hi David, > > When it next happens take a look at the process with truss: > > # truss -f -p <pid> > > You will probably find you???ve got a misbehaving client that isn???t closing connections and eating all your fds or something similar. > > If you need any help deciphering the output pastebin it somewhere and I???m sure we can help! I may have found a clue. I just noticed a mysql file in /var/tmp which looks like this; -rw-rw---- 1 mysql wheel 1135702016 Apr 23 20:28 #sql_4286_0.MYD It just keeps growing larger and larger. I briefly looked at the file at it seems to have very long lines of nonsense - looks like text from a novel. The lines repeat over and over and also includes machine code interwoven. > > -N > > > > On 23 Apr 2015, at 23:28, David Banning <david+dated+1430260101.161ef0@skytracker.ca> wrote: > > > > After years of great service mysql stops working every 24 hours or so. > > Consulting the error log 3s1.com.err (my domain is 3s1.com) > > > > The log shows the server starting, then without logging anything, it stops > > working after maybe 18 hours - it keeps running, but stops serving. > > > > The shutdown is my command, but you can see mysql does not want to shutdown. > > The "Forcing close of thead.." continues indefinitely. > > > > Any pointers toward resolution would be helpful. Can I get more elaborate > > logging? > > > > > > > > 150422 22:59:17 mysqld started > > 150422 22:59:17 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=3s1-bin' to avoid this problem. > > 150422 22:59:17 InnoDB: Started; log sequence number 0 4071213443 > > 150422 22:59:17 [Note] /usr/local/libexec/mysqld: ready for connections. > > Version: '5.0.92-log' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: mysql-server-5.0.92 > > 150423 18:15:54 [Note] /usr/local/libexec/mysqld: Normal shutdown > > > > 150423 18:15:55 [ERROR] /usr/local/libexec/mysqld: Sort aborted > > 150423 18:15:55 [ERROR] /usr/local/libexec/mysqld: Sort aborted > > 150423 18:15:59 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 13077 user: 'xxxxx' > > > > 150423 18:15:59 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 13076 user: 'xxxxx' > > > > 150423 18:15:59 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 13075 user: 'xxxxx' > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150424004504.GA49805>