| Summary: | =dev-db/mysql-5.1.46 : [ERROR] mysqld: unknown option '--skip-federated' | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Florian CROUZAT (SuperFlo) <gentoo> |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | OS X | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
$EPREFIX/etc/mysql/my.cnf mysqld --print-defaults mysqld --verbose --help OSX my.cnf, didn't came with the prefix. |
||
|
Description
Florian CROUZAT (SuperFlo)
2010-06-08 10:48:03 UTC
Probably need the expertise of the mysql team to triage this one. federated is a storage engine, http://dev.mysql.com/doc/refman/5.1/en/federated-storage-engine.html the option snow has inverted logic it's --federated, however you don't need it probably. grep -rls federated /etc/mysql /etc/conf.d/mysql should tell you where it's referenced Our stock config does not contain 'skip-federated' at all, so it's somewhere in your own config. Just find it and comment it out. Four things come to mind: 1/ We don't have a conf.d directory in gentoo prefix, nor a init.d script for mysql. 2/ I didn't changed my configuration and it was working before 3/ grep -Rils federated # doesn't match in etc/mysql 4/ strings $(type -p mysqld) | grep -i federated # match. Any ideas ? - You didn't give us ANY emerge --info output at all. - How are you starting the mysqld if you aren't using the init.d script? - What are the EXACT arguments you're starting it with? True, sorry. You'll find my emerge --info attached. I start mysql using this command: shell>nohup mysqld & I noticed another thing while re-reading my.cnf: shell>mysqld --verbose 100612 10:39:48 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead. The thing is under [mysqld] in my.cnf, there is skip-external-locking set. I'll paste my.cnf also. Just ask if you want any other infos, hope it helps. Created attachment 235035 [details]
emerge --info
Created attachment 235037 [details]
$EPREFIX/etc/mysql/my.cnf
Can you include the output for these: # mysqld --print-defaults # mysqld --verbose --help It's acting like you have another MySQL config file somewhere. Look around on your system maybe? Yes you are totally right, I should have thought about that before. It totally use the /etc/my.cnf from my OSX system, instead of using the PREFIXED my.cnf. I'll attach: # mysqld --print-defaults # mysqld --verbose --help # egrep -v "^(#|$)" /etc/my.cnf # the osx one, not prefixed. I guess it means either previous prefixed mysqld binary was patched to only use the prefixed my.cnf, or that it was also using my osx my.cnf, but the options were valid at this time, and I didn't noticed ... Created attachment 235057 [details]
mysqld --print-defaults
Created attachment 235059 [details]
mysqld --verbose --help
Created attachment 235061 [details]
OSX my.cnf, didn't came with the prefix.
There is your skip-federated in the OSX config yes.
The change that's biting you here is the --skip-FOO did not used to be a fatal error.
--skip-FOO where 'FOO' is not valid is now fatal. To get the old warning-only behaviour, you need --loose-skip-FOO.
In your case, I suggest you start mysqld as follows:
mysqld --defaults-file=${EPREFIX}/etc/mysql/my.cnf
That will prevent it reading the OSX system one.
However, all of the mysql commandline tools are also going to read it unless you pass the same option, so consider changing it slightly too, unless you do actually have that socket at the weird location of /tmp/mysql.sock.
if I understand this correctly, then it seems as if mysql from a prefix reads the host system config file, which means we have to fix that (possibly a patch) to make it look for the prefix config file instead Yes indeed. Looks like it. Maybe adjusting variable when configuring, such as --prefix, --eprefix, or --sysconfdir=DIR (I found these running ./configure --help) but I'm no mysql expert and both the source and the ebuild look complicated, I won't take the risk to provide a patch. ps: I remove mysql-bug@ge.org CC, looks like they aren't needed anymore. Thanks though, the --defaults-file option works fine. pps: do we need to reopen the bug so that someone provides a patch ? |
