- Server operating system version
- Ubuntu 18.04 x86_64
- Plesk version and microupdate number
- 18.0.49.2
Hey guys, I hope you're doing well!
root@server:~# journalctl -xe
Aug 06 18:19:12 server grafana-server[1438]: logger=alerting.evalContext t=2023-08-06T18:19:12.85+00
Aug 06 18:19:13 server mysqld[36452]: 2023-08-06 18:19:13 140085128805504 [Note] /usr/sbin/mysqld (m
Aug 06 18:19:13 server systemd[1]: nginx.service: Service hold-off time over, scheduling restart.
Aug 06 18:19:13 server systemd[1]: nginx.service: Scheduled restart job, restart counter is at 474.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Automatic restarting of the unit nginx.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 06 18:19:13 server systemd[1]: Stopped Startup script for nginx service.
-- Subject: Unit nginx.service has finished shutting down
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has finished shutting down.
Aug 06 18:19:13 server systemd[1]: Starting Startup script for nginx service...
-- Subject: Unit nginx.service has begun start-up
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has begun starting up.
Aug 06 18:19:13 server nginx[36478]: nginx: [emerg] open() "/etc/nginx/plesk.conf.d/vhosts/allhispanos.com.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/zz010_psa_nginx.conf:7
Aug 06 18:19:13 server nginx[36478]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 06 18:19:13 server systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 06 18:19:13 server systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 06 18:19:13 server systemd[1]: Failed to start Startup script for nginx service.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has failed.
--
-- The result is RESULT.
systemctl status mariadb.service
● mariadb.service - MariaDB 10.1.48 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: activating (start) since Sun 2023-08-06 18:18:10 UTC; 3s ago
Docs: man:mysqld(8)
systemd
Process: 35472 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr
Process: 35470 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exi
Process: 35469 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exit
Main PID: 35564 (mysqld)
Status: "Waiting for page cleaner"
Tasks: 15 (limit: 9484)
CGroup: /system.slice/mariadb.service
└─35564 /usr/sbin/mysqld
Aug 06 18:18:10 server systemd[1]: Starting MariaDB 10.1.48 database server...
Aug 06 18:18:10 server mysqld[35564]: 2023-08-06 18:18:10 140571712470144 [Note] /usr/sbin/mysqld (m
Aug 06 18:18:13 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILU
Aug 06 18:18:13 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
Aug 06 18:18:13 server systemd[1]: Failed to start MariaDB 10.1.48 database server.
Mysql log:
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: The InnoDB memory heap is disabled
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Using SSE crc32 instructions
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Initializing buffer pool, size = 5.9G
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Completed initialization of buffer pool
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Highest supported file format is Barracuda.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwffilemods'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwffilemods"', ignored.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwfknownfilelist'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwfknownfilelist"', ignored.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwfpendingissues'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwfpendingissues"', ignored.
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: 128 rollback segment(s) are active.
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Waiting for purge to start
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Percona XtraDB (Open Source Database Software Support & Services | Percona) 5.6.49-89.0 started; log sequence number 169462526812
2023-08-06 18:13:00 140067532142336 [Note] InnoDB: Dumping buffer pool(s) not yet started
2023-08-06 18:13:00 140074868153472 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-06 18:13:00 140074868153472 [Note] Recovering after a crash using tc.log
2023-08-06 18:13:00 140074868153472 [ERROR] Can't init tc log
2023-08-06 18:13:00 140074868153472 [ERROR] Aborting
root@server:~# journalctl -xe
Aug 06 18:19:12 server grafana-server[1438]: logger=alerting.evalContext t=2023-08-06T18:19:12.85+00
Aug 06 18:19:13 server mysqld[36452]: 2023-08-06 18:19:13 140085128805504 [Note] /usr/sbin/mysqld (m
Aug 06 18:19:13 server systemd[1]: nginx.service: Service hold-off time over, scheduling restart.
Aug 06 18:19:13 server systemd[1]: nginx.service: Scheduled restart job, restart counter is at 474.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Automatic restarting of the unit nginx.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 06 18:19:13 server systemd[1]: Stopped Startup script for nginx service.
-- Subject: Unit nginx.service has finished shutting down
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has finished shutting down.
Aug 06 18:19:13 server systemd[1]: Starting Startup script for nginx service...
-- Subject: Unit nginx.service has begun start-up
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has begun starting up.
Aug 06 18:19:13 server nginx[36478]: nginx: [emerg] open() "/etc/nginx/plesk.conf.d/vhosts/allhispanos.com.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/zz010_psa_nginx.conf:7
Aug 06 18:19:13 server nginx[36478]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 06 18:19:13 server systemd[1]: nginx.service: Control process exited, code=exited status=1
Aug 06 18:19:13 server systemd[1]: nginx.service: Failed with result 'exit-code'.
Aug 06 18:19:13 server systemd[1]: Failed to start Startup script for nginx service.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: Enterprise open source support | Ubuntu
--
-- Unit nginx.service has failed.
--
-- The result is RESULT.
systemctl status mariadb.service
● mariadb.service - MariaDB 10.1.48 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: activating (start) since Sun 2023-08-06 18:18:10 UTC; 3s ago
Docs: man:mysqld(8)
systemd
Process: 35472 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr
Process: 35470 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exi
Process: 35469 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exit
Main PID: 35564 (mysqld)
Status: "Waiting for page cleaner"
Tasks: 15 (limit: 9484)
CGroup: /system.slice/mariadb.service
└─35564 /usr/sbin/mysqld
Aug 06 18:18:10 server systemd[1]: Starting MariaDB 10.1.48 database server...
Aug 06 18:18:10 server mysqld[35564]: 2023-08-06 18:18:10 140571712470144 [Note] /usr/sbin/mysqld (m
Aug 06 18:18:13 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILU
Aug 06 18:18:13 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
Aug 06 18:18:13 server systemd[1]: Failed to start MariaDB 10.1.48 database server.
Mysql log:
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: The InnoDB memory heap is disabled
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Using SSE crc32 instructions
2023-08-06 18:12:59 140074868153472 [Note] InnoDB: Initializing buffer pool, size = 5.9G
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Completed initialization of buffer pool
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Highest supported file format is Barracuda.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwffilemods'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwffilemods"', ignored.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwfknownfilelist'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwfknownfilelist"', ignored.
2023-08-06 18:13:00 7f65b8c21c80 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Could not find a valid tablespace file for 'admin_all/wp_hostwfpendingissues'. See MySQL :: MySQL 8.0 Reference Manual :: 15.21.4 Troubleshooting InnoDB Data Dictionary Operations for how to resolve the issue.
2023-08-06 18:13:00 140074868153472 [ERROR] InnoDB: Tablespace open failed for '"admin_all"."wp_hostwfpendingissues"', ignored.
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: 128 rollback segment(s) are active.
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Waiting for purge to start
2023-08-06 18:13:00 140074868153472 [Note] InnoDB: Percona XtraDB (Open Source Database Software Support & Services | Percona) 5.6.49-89.0 started; log sequence number 169462526812
2023-08-06 18:13:00 140067532142336 [Note] InnoDB: Dumping buffer pool(s) not yet started
2023-08-06 18:13:00 140074868153472 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-06 18:13:00 140074868153472 [Note] Recovering after a crash using tc.log
2023-08-06 18:13:00 140074868153472 [ERROR] Can't init tc log
2023-08-06 18:13:00 140074868153472 [ERROR] Aborting