List:General Discussion« Previous MessageNext Message »
From:Glyn Astill Date:December 12 2008 10:35pm
Subject:Re: Pid file issue
View as plain text  
Where does the pid file usually live?  Does it exist?

I guess you need to do some digging, but as a punt you could always try firing off the
stop part of the init script and then try to start it again

/etc/init.d/mysql top
/etc/init.d/mysql start

Assuming you're running some linux flavour, otherwise run the script from wherever they
are in your os i.e. rc.d

If that fails, and mysql.pid is nowhere to be found you could have bash at creating it and
making sure mysql has permissions.


However, looking at this part of the message:

> 081212 10:59:50  InnoDB: Started; log sequence number 5
> 2292330012
> /usr/sbin/mysqld(print_stacktrace+0x1e)[0x6cd03e]
> /usr/sbin/mysqld(handle_segfault+0x320)[0x5b8610]

It's possible a) your filesystem is shagged, or b) Some part of the mysql install is
corrupt, missing libraries or not compiled right.

--- On Fri, 12/12/08, Olaf Stein <olaf.stein@stripped> wrote:

> From: Olaf Stein <olaf.stein@stripped>
> Subject: Pid file issue
> To: "MySql" <mysql@stripped>
> Date: Friday, 12 December, 2008, 9:26 PM
> Hi all,
> 
> I just rebooted one of my servers and get the following
> error when trying to
> restart the mysql daemon:
> 
> Starting MySQL....Manager of pid-file quit without
> updating[FAILED]
> 
> The server shut down fine and that is when the pid file
> should have gone
> away. Any ideas?
> 
> This is from the error log:
> 
> 081212 10:59:47 mysqld_safe Starting mysqld daemon with
> databases from
> /var/lib/mysql
> 081212 10:59:50  InnoDB: Started; log sequence number 5
> 2292330012
> /usr/sbin/mysqld(print_stacktrace+0x1e)[0x6cd03e]
> /usr/sbin/mysqld(handle_segfault+0x320)[0x5b8610]
> /lib64/libpthread.so.0[0x319ae0de70]
> /usr/sbin/mysqld(_Z12push_warningP3THDN11MYSQL_ERROR18enum_warning_levelEjPK
> c+0x40)[0x632b30]
> /usr/sbin/mysqld(_Z19push_warning_printfP3THDN11MYSQL_ERROR18enum_warning_le
> velEjPKcz+0xd9)[0x632de9]
> /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG22purge_logs_before_dateEl+0x236)[0x64192
> 6]
> /usr/sbin/mysqld[0x5b7072]
> /usr/sbin/mysqld(main+0x6f9)[0x5b9059]
> /lib64/libc.so.6(__libc_start_main+0xf4)[0x319a21d8b4]
> /usr/sbin/mysqld[0x507ea9]
> 081212 10:59:50 - mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible
> that this binary
> or one of the libraries it was linked against is corrupt,
> improperly built,
> or misconfigured. This error can also be caused by
> malfunctioning hardware.
> We will try our best to scrape up some info that will
> hopefully help
> diagnose
> the problem, but since we have already crashed, something
> is definitely
> wrong
> and this may fail.
> 
> 
> 
> ----------------------------------------- Confidentiality
> Notice:
> The following mail message, including any attachments, is
> for the
> sole use of the intended recipient(s) and may contain
> confidential
> and privileged information. The recipient is responsible to
> maintain the confidentiality of this information and to use
> the
> information only for authorized purposes. If you are not
> the
> intended recipient (or authorized to receive information
> for the
> intended recipient), you are hereby notified that any
> review, use,
> disclosure, distribution, copying, printing, or action
> taken in
> reliance on the contents of this e-mail is strictly
> prohibited. If
> you have received this communication in error, please
> notify us
> immediately by reply e-mail and destroy all copies of the
> original
> message. Thank you.
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:   
> http://lists.mysql.com/mysql?unsub=1


      
Thread
Pid file issueOlaf Stein12 Dec
  • Re: Pid file issueGlyn Astill12 Dec