• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Unknown variables format in my.cnf + PHPMyAdmin

Servus

Basic Pleskian
Hello!
Only two variables I edited in /etc/mysql/my.cnf under mysql daemon
[mysqld]
bind-address=127.0.0.1
sql_mode=ONLY_FULL_GROUP_BY,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
#bind-address = ::ffff:127.0.0.1
local-infile=0
innodb_flush_log_at_trx_commit=2
innodb_buffer_pool_size=1G



First was after upgrade to Ubuntu 16.04 with Plesk 17 by provider in April. It makes it very fast to playback huge backups for database. I successfully set this value since around one decade.
innodb-flush-log-at-trx-commit[=2] ...default is [=1] strongly recommend by Woltlab Communty Software

Second change was today morning, MySQL tuning, also by Woltlab.
First I ran this awesome script for checking the recommend value for innodb_buffer_pool_size in local database with the result 1G. So I also paste the second value in my.cnf. Restarted service mysql like usual. No problems.

Script for recommended_innodb_innodb_buffer_pool_size
Code:
SELECT CONCAT(ROUND(KBS/POWER(1024,
IF(PowerOf1024<0,0,IF(PowerOf1024>3,0,PowerOf1024)))+0.49999),
SUBSTR(' KMG',IF(PowerOf1024<0,0,
IF(PowerOf1024>3,0,PowerOf1024))+1,1)) recommended_innodb_buffer_pool_size
FROM (SELECT SUM(data_length+index_length) KBS FROM information_schema.tables
WHERE engine='InnoDB') A,
(SELECT 3 PowerOf1024) B;

Then I wanted to to be sure and check if everything is correctly existing after reboot and wanted also check the default value of innodb_autoextend_increment to increase it for better performance to 1-5% of RAM. In my case with 16G Ram I always used smooth 512M.
But I stopped this for now because I saw strange formats for several values. SCREENSHOT on another server (too large for uploading here)
I have to say that there was no need to look in local database PHPMyAdmin after I reinstalled the new Ubuntu 16 image. And I can't remember to see such html-like values with brackets. For me it looks like impossible or a strange issue.

<abbr title="1,073,741,824">1 GiB</abbr>

Two questions:
1. Is this kind of format correct or do I have a misconfiguration in MySQL format?
2. If this format is not correct, and I have to resolve this problem, how could I replay only a automated created mysql backup perhaps daily by Plesk.
Or, if it is the only possible way replay a full Plesk backup which is also created minimum daily.
--- I must say I made a backup of /etc/mysql/my.cnf during the today work, but I didn't made the mysql backup before using the script and changing to 1G. For some stupid reasons I made it afterwards, to have one bfore changing the 3rd value innodb_autoextend_increment to 512M.

I know the support and forum articles about replaying backups. But it would be wonderful if you could point me to the best way. Only if it's necessary at all. Perhaps the values are okay as they are. I hope it soo much.
Plesk repair all -n was without any errors, warnings infos, everything seems like usual.

Greets
 
Last edited:
Here the transfering MySQL Log /var/log/mysql/error.log

Code:
2017-08-22T05:08:56.553512Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.19-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
2017-08-22T05:08:56.553540Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2017-08-22T05:08:56.553552Z 0 [Note] Beginning of list of non-natively partitioned tables
2017-08-22T05:08:56.642347Z 0 [Note] End of list of non-natively partitioned tables
2017-08-22T05:08:57.026116Z 3 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2017-08-22T05:08:57.616789Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170822  7:08:57
2017-08-22T05:13:42.019104Z 0 [Note] Giving 0 client threads a chance to die gracefully
2017-08-22T05:13:42.019193Z 0 [Note] Shutting down slave threads
2017-08-22T05:13:42.019203Z 0 [Note] Forcefully disconnecting 0 remaining clients
2017-08-22T05:13:42.019214Z 0 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-22T05:13:42.019302Z 0 [Note] Binlog end
2017-08-22T05:13:42.022972Z 0 [Note] Shutting down plugin 'auth_socket'
............
2017-08-22T05:13:44.040247Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
...................
2017-08-22T05:15:21.877504Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-08-22T05:15:21.889860Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-08-22T05:15:22.214731Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-08-22T05:15:22.224769Z 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.
2017-08-22T05:15:22.229655Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-0ubuntu0.16.04.1) starting as process 1655 ...
2017-08-22T05:15:22.710678Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-08-22T05:15:22.710710Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-22T05:15:22.710717Z 0 [Note] InnoDB: Uses event mutexes
2017-08-22T05:15:22.710721Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-08-22T05:15:22.710726Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-08-22T05:15:22.710730Z 0 [Note] InnoDB: Using Linux native AIO
2017-08-22T05:15:22.724495Z 0 [Note] InnoDB: Number of pools: 1
2017-08-22T05:15:22.754129Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-08-22T05:15:22.813103Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2017-08-22T05:15:22.925705Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-08-22T05:15:22.938623Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-22T05:15:23.117778Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-22T05:15:25.009743Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-22T05:15:25.009833Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-22T05:15:25.198464Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-22T05:15:25.199604Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-08-22T05:15:25.199619Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-08-22T05:15:25.200574Z 0 [Note] InnoDB: 5.7.19 started; log sequence number 5134235538
2017-08-22T05:15:25.201393Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-22T05:15:25.201616Z 0 [Note] Plugin 'FEDERATED' is disabled.
2017-08-22T05:15:25.602007Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2017-08-22T05:15:25.602043Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2017-08-22T05:15:25.602060Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2017-08-22T05:15:25.602088Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2017-08-22T05:15:26.848468Z 0 [Note] Event Scheduler: Loaded 0 events
2017-08-22T05:15:26.849157Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.19-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
2017-08-22T05:15:26.849203Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2017-08-22T05:15:26.849207Z 0 [Note] Beginning of list of non-natively partitioned tables
2017-08-22T05:15:28.284927Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170822  7:15:28
2017-08-22T05:15:30.994305Z 0 [Note] End of list of non-natively partitioned tables
2017-08-22T05:15:31.013117Z 3 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2017-08-22T12:19:07.446668Z 0 [Note] Giving 1 client threads a chance to die gracefully
2017-08-22T12:19:07.446773Z 0 [Note] Shutting down slave threads
2017-08-22T12:19:09.446889Z 0 [Note] Forcefully disconnecting 1 remaining clients
2017-08-22T12:19:09.446954Z 0 [Warning] /usr/sbin/mysqld: Forcing close of thread 8  user: 'admin'

2017-08-22T12:19:09.447011Z 0 [Note] Event Scheduler: Purging the queue. 0 events
2017-08-22T12:19:09.447482Z 0 [Note] Binlog end
2017-08-22T12:19:09.456164Z 0 [Note] Shutting down plugin 'auth_socket'


2017-08-22T12:19:11.977896Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

2017-08-22T12:19:12.060062Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-08-22T12:19:12.060127Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-08-22T12:19:12.222808Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-08-22T12:19:12.222835Z 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.
2017-08-22T12:19:12.224519Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-0ubuntu0.16.04.1) starting as process 11635 ...
2017-08-22T12:19:12.229241Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-08-22T12:19:12.229266Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-22T12:19:12.229271Z 0 [Note] InnoDB: Uses event mutexes
2017-08-22T12:19:12.229277Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-08-22T12:19:12.229281Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-08-22T12:19:12.229285Z 0 [Note] InnoDB: Using Linux native AIO
2017-08-22T12:19:12.229539Z 0 [Note] InnoDB: Number of pools: 1
2017-08-22T12:19:12.229653Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-08-22T12:19:12.231162Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1G, instances = 8, chunk size = 128M
2017-08-22T12:19:12.310515Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-08-22T12:19:12.321960Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-22T12:19:12.334247Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-22T12:19:12.472997Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-22T12:19:12.473085Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-22T12:19:12.652135Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-22T12:19:12.655225Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-08-22T12:19:12.655266Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-08-22T12:19:12.656475Z 0 [Note] InnoDB: Waiting for purge to start
2017-08-22T12:19:12.706697Z 0 [Note] InnoDB: 5.7.19 started; log sequence number 5141068660
2017-08-22T12:19:12.708125Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-22T12:19:12.708365Z 0 [Note] Plugin 'FEDERATED' is disabled.
2017-08-22T12:19:12.712613Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2017-08-22T12:19:12.712642Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2017-08-22T12:19:12.712659Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2017-08-22T12:19:12.712708Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2017-08-22T12:19:12.723757Z 0 [Note] Event Scheduler: Loaded 0 events
2017-08-22T12:19:12.723998Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.19-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
2017-08-22T12:19:12.724018Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2017-08-22T12:19:12.724022Z 0 [Note] Beginning of list of non-natively partitioned tables
2017-08-22T12:19:12.792841Z 0 [Note] End of list of non-natively partitioned tables
2017-08-22T12:19:13.073261Z 3 [Note] Access denied for user 'root'@'localhost' (using password: NO)
2017-08-22T12:19:13.757713Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170822 14:19:13
 
...
innodb_flush_log_at_trx_commit=2
innodb_buffer_pool_size=1G

...
<abbr title="1,073,741,824">1 GiB</abbr>
...
Two questions:
1. Is this kind of format correct or do I have a misconfiguration in MySQL format?
2. If this format is not correct, and I have to resolve this problem, how could I replay only a automated created mysql backup perhaps daily by Plesk.

1) The two inndob_* lines are correct, the <abbr...>...</abbr> line is not correct, that is simply a formatted output for display on a website. It means "1G" in MySQL-config-speech.
2) ??? You want to restore a Plesk backup on a daily basis? Why?
 
Hi @Peter Debik, glad you answered me. I'm sorry for the missing Screenshot. I put it in wrong directory.
Now I fixed the screenshot and you can see the little desaster.
When you watch the screen you will see there are some other html-codes. I wonder how they came into main database? I never had a database problem like this. Thank you for answering, I thought nobody will help me in this important thing.
Please, could you tell me where to remove this html-code?
If I edit directly over PHPMyAdmin it's not persistent, changes are only for the session, that's what I know.
Before I only add changes over /etc/mysql/my.cnf under daemon (Ubuntu 16.04), like in the first box of my thread. But I don't know how and where to edit the standard values.
You know what I mean? It seems senseless to edit the daemon, which itself changes the standard value. I want to edit the wrong values exactly where they are in the system.
But what makes me more thinking about restoring database are the many values how are not be able for editing. Aren't there are a bit too many grey values?
If this part is correct, I will satisfied a lot.

best regards
 
Last edited:
Screenshot: These entries can be ignored. They seem to be formatting errors of the output display. Your configuration is done in /etc/mysql/my.cnf.
 
I must say, I haven't had any problems with mysql. Yesterday I only looked in PHPMyAdmin to check the recommended_innodb_buffer_pool_size which was in my case 1G. And so I set it in mysql.cnf. My fear was a little that the script wrote kind of bad code into ´database. For my perfectism (<--lol) there is a rest of unsureness. I think everything has its cause and nearly everything in world, especially IT, is able to be changed. As long as it the systems running...never change it...
Thank you very much @Peter Debik.

Lots of greets
 
Back
Top