The first thing that pops into my mind is that you may not be running mysql as the mysql user. Are you using a custom startup script? Did you change the mysql_user variable in the startup script? Do you have a custom my.cnf perhaps?

-- Jacques Manukyan


Squirrel wrote:
I'm currently re-installing db41 port.  Earlier using  'innodb_force_recovery = 
6' seemed to fix that PANIC error.  But I don't understand this permission 
error.  I've tried various permissions as well 777, 766, 666, 760, etc etc.  
I've also ran mysqld_safe as root user, but with same permission error.  Also 
tried different directories without luck.

When I log in to the server shell, it won't chroot me to my home directory.  Instead it puts me in '/' 
with error message "no .bash_login.  And when I log out I get message "no .bash_logout".  
I've never had these files in any of my users' directories.  Another strange thing just discovered is IE 
or FireFox display "Forbidden - You don't have permission to access / on this server", on all 
web sites.

So it seems that I have permission problem globally not just within MySQL.  
What can possibly cause this permission problem?  Hard drive corruption?


-----Original message-----
From: "Daniel O'Connor" docon...@gsoft.com.au
Date: Thu, 19 Mar 2009 01:39:30 -0600
To: freebsd-stable@freebsd.org
Subject: Re: Crash!!!

On Thursday 19 March 2009 08:52:18 Squirrel wrote:
My webserver was working just fine on FreeBSD 6.2 Apache 2.2.11, MySQL
5.0.27.  All of sudden MySQL quit and won't start.  At the same time when
logged in using SSH, it's looking for .bash_login and .bash_logout which it
never did before, and will not chroot to user's home.

Trying to manual start mysql causes:

090318 17:09:52  mysqld started
090318 17:09:52  InnoDB: Started; log sequence number 2 2195718579
090318 17:09:52 [ERROR] bdb:  /home/mysql: Permission denied
090318 17:09:52 [ERROR] bdb:  /home/mysql/log.0000000001: Permission denied
090318 17:09:52 [ERROR] bdb:  PANIC: Permission denied
090318 17:09:52 [ERROR] bdb:  PANIC: DB_RUNRECOVERY: Fatal error, run
database recovery 090318 17:09:52 [ERROR] bdb:  fatal region error
detected; run recovery 090318 17:09:52 [ERROR] bdb:  /home/mysql:
Permission denied
090318 17:09:52 [ERROR] /usr/local/libexec/mysqld: Can't create/write to
file '/home/mysql/webserver.isot.com.pid' (Errcode: 13) 090318 17:09:52
[ERROR] Can't start server: can't create PID file: Permission denied 090318
17:09:52  mysqld ended

I tried db_recover, but it's not found.  HELP!!!
There are db_recover tools installed with BDB but they're called db41_recover or db_recover-4.2 etc.

The other error is that it doesn't appear to be able to write to /home/mysql but in your next email the perms look OK (well they are bad because 777 is insecure but they won't result in permission denied)

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C



_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to