Bug #1842 odd messages in log "Ignoring user change to 'mysql'"
Submitted: 14 Nov 2003 18:39 Modified: 17 Nov 2003 7:07
Reporter: Robin Johnson Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.15, 4.0.16 OS:Linux (Gentoo Linux)
Assigned to: Dean Ellis CPU Architecture:Any

[14 Nov 2003 18:39] Robin Johnson
Description:
This message turns up in the log after the server is restarted.
"Warning: Ignoring user change to 'mysql' because the user was set to 'mysql' earlier on the command line"

How to repeat:

Server is started as root with no parameters passed at all via:
/usr/bin/mysqld_safe
my.cnf contents:
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
[safe_mysqld]
err-log         = /var/log/mysql/mysql.err
[mysqld]
skip-innodb
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
log-error       = /var/log/mysql/mysqld.err
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-locking
set-variable    = key_buffer=16M
set-variable    = max_allowed_packet=1M
set-variable    = thread_stack=128K
bind-address    = 127.0.0.1
port            = 3306
[mysqldump]
quick
set-variable    = max_allowed_packet=1M
[mysql]
[isamchk]
set-variable    = key_buffer=16M

ps shows that mysqld is run as: 
/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock

Running mysqld using this command directly as root on the commandline produces the same error as before, but on stderr and not in the logfile. This makes absolutely no sense as it definetly isn't specified twice.

Permissions on mysqld:
cherenkov-int root # ls -l /usr/sbin/mysqld
-rwxr-xr-x    1 root     root      3830036 Oct 17 00:34 /usr/sbin/mysqld

Suggested fix:
Find why mysqld things the --user option is specified twice and fix that.
[17 Nov 2003 7:07] Dean Ellis
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem is not the result of a bug.
For a list of more appropriate places to ask for help using MySQL
products, please visit http://www.mysql.com/support/

Thank you for your interest in MySQL.

The startup script sets the user, and the option is specified (a second time, effectively) in your my.cnf file.

Thank you