• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved MySQL not starting - page_cleaner - Something happens ove night

Oliver_Strixner

New Pleskian
Hi,
this morning i get the information that mymysql on the plesk server (ubu 16.04) ist not working.
Plesk repair not working - missing connect to db
no mysql.sock in run dir

thats the first problem i found mysql error log

Code:
2020-04-14T21:42:40.496340Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 7347ms. The settings might not be optimal. (flushed=5 and evicted=0, during the time.)
2020-04-14T22:08:13.068194Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-04-14T22:08:13.127844Z 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.
2020-04-14T22:08:13.211517Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.29-0ubuntu0.16.04.1) starting as process 476 ...
2020-04-14T22:08:15.558251Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-04-14T22:08:15.641616Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-04-14T22:08:15.708571Z 0 [Note] InnoDB: Uses event mutexes
2020-04-14T22:08:15.751629Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-04-14T22:08:15.817900Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2020-04-14T22:08:15.871610Z 0 [Note] InnoDB: Using Linux native AIO
2020-04-14T22:08:16.035592Z 0 [Note] InnoDB: Number of pools: 1
2020-04-14T22:08:16.239727Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-04-14T22:08:17.100878Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-04-14T22:08:17.241018Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-04-14T22:08:17.365881Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-04-14T22:08:24.763717Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-04-14T22:08:25.012333Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 90437287275
2020-04-14T22:08:25.025595Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 90437287284
2020-04-14T22:08:25.034586Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-04-14T22:08:25.046888Z 0 [Note] InnoDB: Starting crash recovery.
2020-04-14T22:08:26.842665Z 0 [ERROR] InnoDB: Trying to access page number 1953788019 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2020-04-14T22:08:26.842686Z 0 [ERROR] InnoDB: Server exits.

just repeating the whole thing

systemctl status mysql

Code:
mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Mi 2020-04-15 12:17:58 CEST; 10s ago
  Process: 6972 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
  Process: 6964 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 6972 (code=exited, status=1/FAILURE);         : 6973 (mysql-systemd-s)
   CGroup: /system.slice/mysql.service
           └─control
             ├─6973 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─7063 sleep 1

it seems that there is no .sock file

Can anybody help?
 
Hi Igor,
thanks for replying. I didn't checked this out, becaus it was time to bring the system online, so i started a system recovery and my learning field is gone :)

But it seems, that the Provider made maintanance without shuting down the mashines, so some files are get broken.
 
Back
Top