On Fri, Jan 14, 2005 at 05:59:06PM +0100, Christian Hammers wrote:
> Hello Marius
>
> On 2005-01-14 Marius Gedminas wrote:
> > /var/lib/mysql/`hostname`.err says
> >
> > 050114 15:20:18 mysqld started
> > /usr/sbin/mysqld: unrecognized option `--skip-external-locking'
> >
> > I have no idea where --skip-external-locking comes from:
> Check /etc/mysql/my.cnf and $HOME/.my.cnf for "external" and "locking".
> Do not grep for the "--" before it because in the config file may
> be written as "external_locking =no" or similar.
Thanks for pointing me to the right direction! I found
"skip-external-locking" in /etc/mysql/my.cnf. A number of other options
in my.cnf also prevent mysqld from starting (e.g. key_buffer=16M had to
be changed to set-variable = key_buffer=16M).
I am dismayed by these misleading mysqld error messages.
> > By the way, I see here a /var/log/mysql.log that is an empty file.
> > /var/log/mysql/mysql.err is also an empty file. There are no other
> > mysql log files in /var/log.
> /var/log/mysql.log is the old location, /var/log/mysql/* the new one.
> I found no sane way to remove the old files, I guess.
> The location of the log files is set in /etc/mysql/my.cnf, this is
> probably where you have the `hostname`.err location defined.
/etc/mysql/my.cnf only has
log = /var/log/mysql/mysql.log
but /usr/bin/safe_mysqld does
test -z "$err_log" && err_log=$DATADIR/`/bin/hostname`.err
and apparently only takes err_log from the command line.
I am not the only person who has root access on this machine (and it is
not my machine, I just help sometimes as the local Debian expert). It
is possible that someone copied over my.cnf from a different system
rather than using an example that came from Debian's mysql-server. In
fact, I am now looking at a backed up copy of my.cnf from May 2004, and
it does, in fact, use the correct syntax (set-variable, skip-locking).
Again, thank you for helping me resolve the issue. It would be nice if
mysql did not obfuscate error messages (by complaining about command
line arguments when it should complain about configuration file errors),
but nevertheless it was a pilot error.
Marius Gedminas
--
Since this protocol deals with Firewalls there are no real security
considerations.
-- RFC 3093
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
