Public SourceMage Discussion List

[Paul Mahon <dufflebunk AT dufflebunk.homeip.net>]

You may want to run a check on the tables (myisam_check or some binary
like that). I frequently get errors of that sort when one of the tables
gets corrupted.

On Thu, 2005-10-02 at 22:50 -0500, vze2hn5x AT verizon.net wrote:
> Hello,
> 
> > Can you run /usr/bin/mysqld_safe on it's own and have it start?
> 
> Trying to run that command on its own generates messages:
> root@Sanctuary:/home/eric# /usr/bin/mysqld_safe
> Starting mysqld daemon with databases from /var/lib/mysql
> 
> Number of processes running now: 0
> 050210 22:42:41  mysqld restarted
> 
> Number of processes running now: 0
> 050210 22:42:41  mysqld restarted
> 
> Number of processes running now: 0
> 050210 22:42:41  mysqld restarted
> 
> Number of processes running now: 0
> 050210 22:42:42  mysqld restarted
> 
> Number of processes running now: 0
> 050210 22:42:42  mysqld restarted
> 
> Number of processes running now: 1
> kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or 
> kill -l [sigspec]
> 050210 22:42:42  mysqld restarted
> 
> Number of processes running now: 0
> 050210 22:42:42  mysqld restarted
> 
> 
> The above lines repeat over and over again for awhile, then I get:
> 
> 
> Number of processes running now: 0
> 050210 22:42:45  mysqld restarted
> 
> Number of processes running now: 1
> mysqld process hanging, pid 7820 - killed
> 050210 22:42:45  mysqld restarted
> STOPPING server from pid file /var/lib/mysql/Sanctuary.pid
> 050210 22:42:45  mysqld ended
> 
> > Did mysql get updated, or any other libraries that mysql uses?
> 
> mysql was updated, looking at the mysql depends file, it also looks 
> like perl and zlib were updated as well.
> 
> > Have you tried `cleanse --fix mysql`?
> 
> No, I didn't try that.  I did try "cast -r -c mysql" and when that 
> failed to fix the problem "dispel mysql" followed by "cast mysql".  
> Trying cleanse now...
> 
> Cleanse decided that something was wrong with procps and recast it.  
> Rebooting the computer results in the same error messages as before.  
> Re-running cleanse shows that everything is fine, even though mysql 
> still doesn't work and mysqld_safe is still giving the same messages as 
> above.  Any ideas?
> 
> Eric
> 
> 
> On Feb 10, 2005, at 8:42 PM, Eric Sandall wrote:
> 
> > Can you run /usr/bin/mysqld_safe on it's own and have it start? Did 
> > mysql get
> > updated, or any other libraries that mysql uses? Have you tried 
> > `cleanse --fix
> > mysql`?
> >
> > -sandalle
> >
> > --
> > Eric Sandall                     |  Source Mage GNU/Linux Developer
> > eric AT sandall.us PGP: 0xA8EFDD61  |  http://www.sourcemage.org/
> > http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ 
> > WSU
> > http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> > _______________________________________________
> > SM-Discuss mailing list
> > SM-Discuss AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >
> 
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>