SEO

Hi Everyone.

I had a perfectly good working version of MySQL and then I decided to
try something new... Now, I can start up as root with mysqld, but
when I start with mysqld_safe as I always have in the past, mysqld
quits immediately. Here's the saga:

I decided to use phpmyadmin to change all my user passwords to SHA1.
After reloading MySQL, I couldn't connect with ANY password. In order
to reset root, I tried starting with a mysql-init file. That didn't
work, so I started with mysqld and --skip-grant-tables. After
resetting the root password, I was able to check and repair the mysql
database tables, as well as fix all the other user passwords. I also
used mysqladmin to flush and refresh everything.

When I tried to start with my usual startup script, which references
mysqld_safe, MySQL started and then immediately quit. I got an error
in my log, "Failed to open log (file '/usr/local/mysql-5.0.41-osx10.4-
i686/data/me-web2-bin.000027', errno 13)". I noticed this particular
file was now owned by root, so I chown'd it to mysql and restarted
mysqld_safe, which quit immediately.

I thought if there were no binary logs and no log index, it would
stop looking for that file, so I deleted all the -bin files and the
index. I restarted mysqld_safe, and it started and quit. I removed --
log-bin from my mysqld_safe startup options, restarted, and it quit.
Here is the log entry for a typical startup now:

-------------
070717 22:44:12 mysqld started
070717 22:44:12 [Warning] Setting lower_case_table_names=2 because
file system for /usr/local/mysql/data/ is case insensitive
070717 22:44:12 [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=/usr/local/mysql/data/me-web2-bin' to avoid this problem.
070717 22:44:12 InnoDB: Started; log sequence number 0 335107
/usr/local/mysql/bin/mysqld: File '/usr/local/mysql-5.0.41-osx10.4-
i686/data/me-web2-bin.000027' not found (Errcode: 13)
070717 22:44:12 [ERROR] Failed to open log (file '/usr/local/
mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027', errno 13)
070717 22:44:12 [ERROR] Could not open log file
070717 22:44:12 [ERROR] Can't init tc log
070717 22:44:12 [ERROR] Aborting
070717 22:44:12 InnoDB: Starting shutdown...
070717 22:44:14 InnoDB: Shutdown completed; log sequence number 0
335107
070717 22:44:14 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
070717 22:44:15 mysqld ended
-------------

I'm not using replication, but I am using mirrored drives, and this
is the first time I've ever done that. Still, it didn't seem to be a
problem until I screwed up the passwords.

I'm just setting up a new server, so the tables and data are not dear
to me. Right now, I just want MySQL to work -- with logging!!

--
Chris Africa
Web Project Manager
Department of Mechanical Engineering
University of Michigan
734-764-8482
Fridays: 734-355-6577
AIM/iChat/Skype ID: baiewola

Chris Africa wrote:
-------------
> 070717 22:44:12 mysqld started
> 070717 22:44:12 [Warning] Setting lower_case_table_names=2 because file
> system for /usr/local/mysql/data/ is case insensitive
> 070717 22:44:12 [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=/usr/local/mysql/data/me-web2-bin' to avoid this problem.
> 070717 22:44:12 InnoDB: Started; log sequence number 0 335107
> /usr/local/mysql/bin/mysqld: File '/usr/local/mysql-5.0.41-osx10.4-
> i686/data/me-web2-bin.000027' not found (Errcode: 13)
> 070717 22:44:12 [ERROR] Failed to open log (file '/usr/local/
> mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027', errno 13)
> 070717 22:44:12 [ERROR] Could not open log file
> 070717 22:44:12 [ERROR] Can't init tc log
> 070717 22:44:12 [ERROR] Aborting
> 070717 22:44:12 InnoDB: Starting shutdown...
> 070717 22:44:14 InnoDB: Shutdown completed; log sequence number 0 335107
> 070717 22:44:14 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
> 070717 22:44:15 mysqld ended
> -------------
>
> I'm not using replication, but I am using mirrored drives, and this is
> the first time I've ever done that. Still, it didn't seem to be a
> problem until I screwed up the passwords.
>
> I'm just setting up a new server, so the tables and data are not dear
> to me. Right now, I just want MySQL to work -- with logging!!
>
> --
> Chris Africa
> Web Project Manager
> Department of Mechanical Engineering
> University of Michigan
> 734-764-8482
> Fridays: 734-355-6577
> AIM/iChat/Skype ID: baiewola
>
>
mysql does not have write privilege in
/usr/local/mysql-5.0.41-osx10.4-i686/data.
Is this owned by root too?

--
Gerald L. Clark
Supplier Systems Corporation

Hi Gerald.

Actually, mysql should have access, as it owns the entire directory.
drwxr-xr-x 19 mysql wheel 646 May 30 09:41 mysql-5.0.41-osx10.4-
i686

and nested inside that is
drwxr-x--- 27 mysql wheel 918 Jul 18 12:53 data

Thanks!

--
Chris Africa
Web Project Manager
Department of Mechanical Engineering
University of Michigan
734-764-8482
Fridays: 734-355-6577
AIM/iChat/Skype ID: baiewola


On Jul 18, 2007, at 1:32 PM, Gerald L. Clark wrote:
> Chris Africa wrote:
> -------------
>> 070717 22:44:12 mysqld started
>> 070717 22:44:12 [Warning] Setting lower_case_table_names=2
>> because file system for /usr/local/mysql/data/ is case insensitive
>> 070717 22:44:12 [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=/usr/local/mysql/data/me-web2-bin' to avoid
>> this problem.
>> 070717 22:44:12 InnoDB: Started; log sequence number 0 335107
>> /usr/local/mysql/bin/mysqld: File '/usr/local/mysql-5.0.41-
>> osx10.4- i686/data/me-web2-bin.000027' not found (Errcode: 13)
>> 070717 22:44:12 [ERROR] Failed to open log (file '/usr/local/
>> mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027', errno 13)
>> 070717 22:44:12 [ERROR] Could not open log file
>> 070717 22:44:12 [ERROR] Can't init tc log
>> 070717 22:44:12 [ERROR] Aborting
>> 070717 22:44:12 InnoDB: Starting shutdown...
>> 070717 22:44:14 InnoDB: Shutdown completed; log sequence number
>> 0 335107
>> 070717 22:44:14 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
>> 070717 22:44:15 mysqld ended
>> -------------
>> I'm not using replication, but I am using mirrored drives, and
>> this is the first time I've ever done that. Still, it didn't seem
>> to be a problem until I screwed up the passwords.
>> I'm just setting up a new server, so the tables and data are not
>> dear to me. Right now, I just want MySQL to work -- with logging!!
>> --
>> Chris Africa
>> Web Project Manager
>> Department of Mechanical Engineering
>> University of Michigan
>> 734-764-8482
>> Fridays: 734-355-6577
>> AIM/iChat/Skype ID: baiewola
> mysql does not have write privilege in /usr/local/mysql-5.0.41-
> osx10.4-i686/data.
> Is this owned by root too?
>
> --
> Gerald L. Clark
> Supplier Systems Corporation
>
> !DSPAM:469e4ec246291493215846!
>
>
>

You have bin log enabled and it might be looking for the last bin log before
the last shutdown
('/usr/local/mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027')

You can either:

- move the missing binlog file where mysql is looking for it
- delete the $hostname.index file that keeps track of binlogs
- disable binlog

Olaf


On 7/18/07 12:57 PM, "Chris Africa" <cafrica@umich.edu> wrote:

> Hi Everyone.
>
> I had a perfectly good working version of MySQL and then I decided to
> try something new... Now, I can start up as root with mysqld, but
> when I start with mysqld_safe as I always have in the past, mysqld
> quits immediately. Here's the saga:
>
> I decided to use phpmyadmin to change all my user passwords to SHA1.
> After reloading MySQL, I couldn't connect with ANY password. In order
> to reset root, I tried starting with a mysql-init file. That didn't
> work, so I started with mysqld and --skip-grant-tables. After
> resetting the root password, I was able to check and repair the mysql
> database tables, as well as fix all the other user passwords. I also
> used mysqladmin to flush and refresh everything.
>
> When I tried to start with my usual startup script, which references
> mysqld_safe, MySQL started and then immediately quit. I got an error
> in my log, "Failed to open log (file '/usr/local/mysql-5.0.41-osx10.4-
> i686/data/me-web2-bin.000027', errno 13)". I noticed this particular
> file was now owned by root, so I chown'd it to mysql and restarted
> mysqld_safe, which quit immediately.
>
> I thought if there were no binary logs and no log index, it would
> stop looking for that file, so I deleted all the -bin files and the
> index. I restarted mysqld_safe, and it started and quit. I removed --
> log-bin from my mysqld_safe startup options, restarted, and it quit.
> Here is the log entry for a typical startup now:
>
> -------------
> 070717 22:44:12 mysqld started
> 070717 22:44:12 [Warning] Setting lower_case_table_names=2 because
> file system for /usr/local/mysql/data/ is case insensitive
> 070717 22:44:12 [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=/usr/local/mysql/data/me-web2-bin' to avoid this problem.
> 070717 22:44:12 InnoDB: Started; log sequence number 0 335107
> /usr/local/mysql/bin/mysqld: File '/usr/local/mysql-5.0.41-osx10.4-
> i686/data/me-web2-bin.000027' not found (Errcode: 13)
> 070717 22:44:12 [ERROR] Failed to open log (file '/usr/local/
> mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027', errno 13)
> 070717 22:44:12 [ERROR] Could not open log file
> 070717 22:44:12 [ERROR] Can't init tc log
> 070717 22:44:12 [ERROR] Aborting
> 070717 22:44:12 InnoDB: Starting shutdown...
> 070717 22:44:14 InnoDB: Shutdown completed; log sequence number 0
> 335107
> 070717 22:44:14 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
> 070717 22:44:15 mysqld ended
> -------------
>
> I'm not using replication, but I am using mirrored drives, and this
> is the first time I've ever done that. Still, it didn't seem to be a
> problem until I screwed up the passwords.
>
> I'm just setting up a new server, so the tables and data are not dear
> to me. Right now, I just want MySQL to work -- with logging!!
>
> --
> Chris Africa
> Web Project Manager
> Department of Mechanical Engineering
> University of Michigan
> 734-764-8482
> Fridays: 734-355-6577
> AIM/iChat/Skype ID: baiewola
>

Chris Africa wrote:
> Hi Gerald.
>
> Actually, mysql should have access, as it owns the entire directory.
> drwxr-xr-x 19 mysql wheel 646 May 30 09:41
> mysql-5.0.41-osx10.4- i686
>
> and nested inside that is
> drwxr-x--- 27 mysql wheel 918 Jul 18 12:53 data
>
> Thanks!
>
>
Error 13 is a permissions error. Check all directories from / to the
data directory.
--
Gerald L. Clark
Supplier Systems Corporation

1. Get rid of the offending $hostname.index file that keeps track of
binlogs (Thanks, Olaf!).
2. Fix permissions (Thanks, Gerald Clark!).

Have a nice day!

Chris


On Jul 18, 2007, at 2:19 PM, Olaf Stein wrote:

> You have bin log enabled and it might be looking for the last bin
> log before
> the last shutdown
> ('/usr/local/mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027')
>
> You can either:
>
> - move the missing binlog file where mysql is looking for it
> - delete the $hostname.index file that keeps track of binlogs
> - disable binlog
>
> Olaf
>
>
> On 7/18/07 12:57 PM, "Chris Africa" <cafrica@umich.edu> wrote:
>
>> Hi Everyone.
>>
>> I had a perfectly good working version of MySQL and then I decided to
>> try something new... Now, I can start up as root with mysqld, but
>> when I start with mysqld_safe as I always have in the past, mysqld
>> quits immediately. Here's the saga:
>>
>> I decided to use phpmyadmin to change all my user passwords to SHA1.
>> After reloading MySQL, I couldn't connect with ANY password. In order
>> to reset root, I tried starting with a mysql-init file. That didn't
>> work, so I started with mysqld and --skip-grant-tables. After
>> resetting the root password, I was able to check and repair the mysql
>> database tables, as well as fix all the other user passwords. I also
>> used mysqladmin to flush and refresh everything.
>>
>> When I tried to start with my usual startup script, which references
>> mysqld_safe, MySQL started and then immediately quit. I got an error
>> in my log, "Failed to open log (file '/usr/local/mysql-5.0.41-
>> osx10.4-
>> i686/data/me-web2-bin.000027', errno 13)". I noticed this particular
>> file was now owned by root, so I chown'd it to mysql and restarted
>> mysqld_safe, which quit immediately.
>>
>> I thought if there were no binary logs and no log index, it would
>> stop looking for that file, so I deleted all the -bin files and the
>> index. I restarted mysqld_safe, and it started and quit. I removed --
>> log-bin from my mysqld_safe startup options, restarted, and it quit.
>> Here is the log entry for a typical startup now:
>>
>> -------------
>> 070717 22:44:12 mysqld started
>> 070717 22:44:12 [Warning] Setting lower_case_table_names=2 because
>> file system for /usr/local/mysql/data/ is case insensitive
>> 070717 22:44:12 [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=/usr/local/mysql/data/me-web2-bin' to avoid this
>> problem.
>> 070717 22:44:12 InnoDB: Started; log sequence number 0 335107
>> /usr/local/mysql/bin/mysqld: File '/usr/local/mysql-5.0.41-osx10.4-
>> i686/data/me-web2-bin.000027' not found (Errcode: 13)
>> 070717 22:44:12 [ERROR] Failed to open log (file '/usr/local/
>> mysql-5.0.41-osx10.4-i686/data/me-web2-bin.000027', errno 13)
>> 070717 22:44:12 [ERROR] Could not open log file
>> 070717 22:44:12 [ERROR] Can't init tc log
>> 070717 22:44:12 [ERROR] Aborting
>> 070717 22:44:12 InnoDB: Starting shutdown...
>> 070717 22:44:14 InnoDB: Shutdown completed; log sequence number 0
>> 335107
>> 070717 22:44:14 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
>> 070717 22:44:15 mysqld ended
>> -------------
>>
>> I'm not using replication, but I am using mirrored drives, and this
>> is the first time I've ever done that. Still, it didn't seem to be a
>> problem until I screwed up the passwords.
>>
>> I'm just setting up a new server, so the tables and data are not dear
>> to me. Right now, I just want MySQL to work -- with logging!!
>>
>> --
>> Chris Africa
>> Web Project Manager
>> Department of Mechanical Engineering
>> University of Michigan
>> 734-764-8482
>> Fridays: 734-355-6577
>> AIM/iChat/Skype ID: baiewola
>>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?
> unsub=cafrica@umich.edu
>
>
> !DSPAM:469e59ed258113798219729!
>
>
>