API Gateway: MySQL on the appliance contains logs regarding utf8 and log-bin formats, and more

Products

• CA API Gateway

Issue/Introduction

This article will discuss various MySQL log entries related to utf8 character sets and log-bin options.

MySQL on the appliance API Gateway may output the following warnings when MySQL starts:

2020-11-24T15:23:59.837060+09:00 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 10000 (requested 13125)

2020-11-24T15:23:59.837074+09:00 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 3682 (requested 4000)

2020-11-24T15:24:00.162082+09:00 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.

2020-11-24T15:24:00.162101+09:00 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.

2020-11-24T15:24:00.164152+09:00 0 [Warning] [MY-010161] [Server] You need to use --log-bin to make --binlog-format work.

2020-11-24T15:24:00.828074+09:00 0 [Warning] [MY-010161] [Server] You need to use --log-bin to make --binlog-expire-logs-seconds work.

Environment

This article applies to API Gateway 10.0 appliances.

Resolution

These are simply info/warning messages and are not errors. If MySQL 5.7 started successfully, then the messages can be ignored. If however MySQL is failing to start successfully, then a support case with the full MySQL logs should be created.