mysql upgrade logs


after adding mysql apt repo ( /etc/apt/sources.list.d/mysql.list will be created )
$ sudo apt-get update
$ sudo apt-get install mysql-server

"""...
...
Once you are satisfied with the configuration then select last option 'Apply' to
save the configuration. Advanced users can always change the configurations
later, depending on their own needs.

1. Server 2. Workbench 3. Connector-Python 4. Utilities 5. Apply

Which MySQL product do you wish to configure? 1


...
If you are not sure which version to
choose for yourself, do not change the auto-selected version. Advanced users can
always change the version later, depending on their own needs.

1. mysql-5.6 2. mysql-5.7-dmr 3. none

Which server version do you wish to receive? 1


...
Once you are satisfied with the configuration then select last option 'Apply' to
save the configuration. Advanced users can always change the configurations
later, depending on their own needs.

1. Server 2. Workbench 3. Connector-Python 4. Utilities 5. Apply

Which MySQL product do you wish to configure? 5

..."""


//=== backup old conf on another terminal
cp /etc/mysql/my.cnf my.cnf.bak


"""...
Configuration file '/etc/mysql/my.cnf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/mysql/my.cnf ...
Setting up libapparmor1:amd64 (2.8.95~2430-0ubuntu5.1) ...
Setting up libapparmor-perl (2.8.95~2430-0ubuntu5.1) ...

..."""


//===
$ nano /etc/mysql/my.cnf
$ sudo service mysql start
No directory, logging in with HOME=/
150508 06:45:50 mysqld_safe Can't log to error log and syslog at th Remove all --log-error configuration options for --syslog to take
......
* MySQL Community Server 5.6.24 did not start. Please check logs fls.

$ cat /var/log/mysql/error.log

--> $ nano /etc/mysql/my.cnf [to correct typo errors]

$ sudo service mysql start
No directory, logging in with HOME=/
150508 06:48:53 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error configuration options for --syslog to take effect.
......
* MySQL Community Server 5.6.24 is started


-->
http://serverfault.com/questions/441195/mysqld-safe-cant-log-to-error-log-and-syslog-at-the-same-time-remove-all-log
http://shinguz.blogspot.hk/2010/01/mysql-reporting-to-syslog.html
https://bugs.launchpad.net/mylvmbackup/+bug/1091950
http://dev.mysql.com/doc/refman/5.1/en/error-log.html


??? add "--skip-syslog" to the options

http://dba.stackexchange.com/questions/10117/why-is-mysql-logging-to-syslog
"""...
From 5.1.20 on, mysqld_safe has two additional error-logging options, --syslog and --skip-syslog.

In 5.1.21 and up, the default with no logging options is --skip-syslog, which is compatible with the default behavior of writing an error log file for releases prior to 5.1.20. To explicitly specify use of an error log file, specify --log-error=file_name to mysqld_safe, and mysqld_safe will arrange for mysqld to write messages to a log file. To use syslog instead, specify the --syslog option.

In 5.1.20 only, the following conditions apply: 1) The default is to use syslog, which is not compatible with releases prior to 5.1.20. 2) Logging to syslog may fail to operate correctly in some cases; if so, use --skip-syslog or --log-error.
..."""


$ cat /etc/mysql/conf.d/my.cnf
[mysqld]
bind-address=0.0.0.0

$ cat /etc/mysql/conf.d/mysqld_safe_syslog.cnf
[mysqld_safe]
syslog


-->
[mysqld_safe]
skip-syslog