Re: Persistent MySQL Process
On Tuesday, 9 October 2012 02:00:02 UTC+1, Christofer C. Bell wrote: > On Mon, Oct 8, 2012 at 2:48 PM, Daniel Latter wrote: > > > Hi, Thanks for the reply. > > > > > > I did as you suggested and found evidence in the second command, but the > > only that stood out was the Debian start up script that I have already > > commented out and restarted MySQL, I'm going to try a server reboot, but > > I'm not 100% that will get rid of the process. > > > > > > Would you suggest anything else? > > > > Do you by any chance use KDE? > > > > -- > > Chris > > > > > Hi, I do not use KDE myself but my colleague does, but its just to browse to a web address, can I ask what you are alluding to? Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e6c4bad7-894c-4a49-a094-3a1140144...@googlegroups.com
Re: Persistent MySQL Process
Hi, It seems to be the second issue (I/O) load. Here's a snippet from top: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 22178 mysql 20 0 416m 119m 7456 S 31 3.0 137:12.52 mysqld I know there needs to be a mysqld process but this does not look right? On Monday, 8 October 2012 22:50:03 UTC+1, Sven Hartge wrote: > Daniel Latter wrote: > > > > > I did as you suggested and found evidence in the second command, but > > > the only that stood out was the Debian start up script that I have > > > already commented out and restarted MySQL, I'm going to try a server > > > reboot, but I'm not 100% that will get rid of the process. > > > > Umm, why do you have MySQL installed when you don't want to use it? > > > > If course will there be a running mysqld-process, because MySQL needs a > > running mysqld to function, there is now way to prevent this and _still_ > > be able to use a MySQL-DB. > > > > I fail to grasp your problem. If the mysqld crashes your server, then > > you need to investigate why. Foremost you need to define (and tell this > > list) what you mean by "crashes the server". > > > > Does it run out of free RAM? > > Does it create a heavy I/O load and thus slowing down everything else? > > > > Grüße, > > Sven. > > > > -- > > Sigmentation fault. Core dumped. > > > > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8650c525-1647-485d-b90b-b51158dcf...@googlegroups.com
Re: Persistent MySQL Process
Hi, Thanks for the reply. I did as you suggested and found evidence in the second command, but the only that stood out was the Debian start up script that I have already commented out and restarted MySQL, I'm going to try a server reboot, but I'm not 100% that will get rid of the process. Would you suggest anything else? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/110e7a4c-1a66-4aaf-a4ee-4f94ecea4...@googlegroups.com
Persistent MySQL Process
Hi All, System: cat /etc/issue Debian GNU/Linux 6.0 I have a long running MySQL process that runs for days and eventually crashes the server. I googled about and discovered that Debian has it's own MySQL start up script that runs a "check tables" command, so I commented this out and restarted, but the process immediately started again. I have webmin installed and when I view the process information it has a parent process of "init[2]"? Also, when I view the files and programs related to the persistent process in question, it lists ibdata files (innodb data files), one being 8GB in size! I am wondering if this has anything to do with it? Any help or pointers would be greatly appreciated. Also, regarding webmin I have turned off the db module. Thanks Daniel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e6969273-43d4-48bd-a5d1-d23610f59...@googlegroups.com
