Solved mysql57-server doesn't start

[ProServ]

The fix to the issue of mysql57-server not starting was fixed by adding the following to /usr/local/etc/mysql/my.cnf in the [mysqld] section:

innodb_data_file_path = ibdata1:10M:autoextend

But it did NOT fix the fact cannot load the cacti web page. I will create a new thread for cacti.
===============================================================

Hi, after running pkg update, mysql-server seems to have been removed. There was no /usr/local/etc/mysql-server for one. However mysql was still running. The client was mysql57-client.

After installing mysql57-server and trying to start it, .err log shows:

2019-07-12T20:34:47.345356Z 0 [Warning] Could not increase number of max_open_files to more than 32768 (request: 32929)
2019-07-12T20:34:47.373596Z 0 [Warning] Changed limits: table_open_cache: 16303 (requested 16384)
2019-07-12T20:34:47.629656Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-07-12T20:34:47.629691Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-07-12T20:34:47.633395Z 0 [Note] /usr/local/libexec/mysqld (mysqld 5.7.26-log) starting as process 2322 ...
2019-07-12T20:34:47.695050Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-07-12T20:34:47.695141Z 0 [Note] InnoDB: Uses event mutexes
2019-07-12T20:34:47.695173Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-07-12T20:34:47.695196Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-07-12T20:34:47.695814Z 0 [Note] InnoDB: Number of pools: 1
2019-07-12T20:34:47.696022Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2019-07-12T20:34:47.699429Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2019-07-12T20:34:47.946992Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-07-12T20:34:47.978567Z 0 [ERROR] InnoDB: The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of a different size 4864 pages (rounded down to MB) than specified in the .cnf file: initial 8192 pages, max 0 (relevant if non-zero) pages!
2019-07-12T20:34:47.978630Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-07-12T20:34:48.192377Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-07-12T20:34:48.192412Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-07-12T20:34:48.192435Z 0 [ERROR] Failed to initialize builtin plugins.
2019-07-12T20:34:48.192451Z 0 [ERROR] Aborting

2019-07-12T20:34:48.192487Z 0 [Note] Binlog end
2019-07-12T20:34:48.192582Z 0 [Note] Shutting down plugin 'CSV'
2019-07-12T20:34:48.195878Z 0 [Note] /usr/local/libexec/mysqld: Shutdown complete

Do not recall installing any plugin.

Question is how to get mysql running again. It is used for cacti.

Thanks.