search

bitnami / vms

Bitnami VMs
https://bitnami.com
Other
206 stars 44 forks source link

Site not loading #1107

Closed crino85 closed 1 year ago

crino85 commented 1 year ago

Platform

AWS

bndiagnostic ID know more about bndiagnostic ID

cf1cae49-89bb-1646-812a-6d6c439deca2

bndiagnostic output

===== Begin of bndiagnostic tool output =====

✓ Resources: No issues found
? Connectivity: Found possible issues
? Mariadb: Found possible issues
✓ Processes: No issues found
? Wordpress: Found possible issues
? Apache: Found possible issues
✓ Php: No issues found

[Connectivity]

Server ports 22, 80 and/or 443 are not publicly accessible. Please check the following guide to open server ports for remote access:

https://docs.bitnami.com/general/faq/administration/use-firewall/

[Mariadb]

Press [Enter] to continue: Found recent error messages in the MariaDB error log:

2023-08-21 12:42:55 0 [ERROR] Aborting

Please check the following guide to troubleshoot MariaDB issues:

https://docs.bitnami.com/aws/apps/wordpress/troubleshooting/debug-errors-m ariadb/

[Wordpress]

Found recent WordPress plugin related error messages in the Apache error log.

[Mon Aug 21 11:53:22.166023 2023] [proxy_fcgi:error] [pid 772:tid
139670797227776] [client **ip_address**:38956] AH01071: Got error 'PHP message:
WordPress database error Index for table 'wp_options' is corrupt; try to repair
it for query INSERT INTO `wp_options` (`option_name`, `option_value`,
`autoload`) VALUES ('_transient_wc_attribute_taxonomies', 'a:0:{}', 'yes') ON
DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` =
VALUES(`option_value`), `autoload` = VALUES(`autol

Please check the following guide to deactivate plugins: Press [Enter] to continue:

https://developer.wordpress.org/cli/commands/plugin/deactivate/

[Apache]

Found recent error or warning messages in the Apache error log.

[Mon Aug 21 11:52:53.732074 2023] [proxy_fcgi:error] [pid 772:tid
139670797227776] [client **ip_address**:38305] AH01071: Got error 'PHP message:
WordPress database error Index for table 'wp_options' is corrupt; try to repair
it for query INSERT INTO `wp_options` (`option_name`, `option_value`,
`autoload`) VALUES ('woocommerce_custom_orders_table_data_sync_enabled', 'no',
'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`),
`option_value` = VALUES(`option_value`), `autoload` = VA [Mon Aug 21
11:52:54.182403 2023] [proxy_fcgi:error] [pid 772:tid 139670797227776] [client
**ip_address**:38305] AH01071: Got error 'o_action, WP_Hook->apply_filters,
wpsc_feed_update, update_optionPHP message: WordPress database error Index for
table 'wp_options' is corrupt; try to repair it for query DELETE FROM
`wp_options` WHERE `option_name` =
'_transient_jetpack_sync_last_checked_queue_state_sync' made by
require('wp-blog-header.php'), require_once('wp-load.php'),
require_once('wp-config.ph [Mon Aug 21 11:52:54.406944 2023] [proxy_fcgi:error]
[pid 772:tid 139670797227776] [client **ip_address**:38305] AH01071: Got error
Press [Enter] to continue:
'g\";s:5:\"width\";i:1024;s:6:\"height\";i:1024;s:9:\"mime-type\";s:9:\"image/png
\";s:8:\"filesize\";i:80210;}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\
";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\
"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s
:1:\"

Please check the following guide to troubleshoot server issues:

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro rs-apache/

===== End of bndiagnostic tool output =====

Press [Enter] to continue: The diagnostic bundle was uploaded successfully to the Bitnami servers. Please copy the following code:

cf1cae49-89bb-1646-812a-6d6c439deca2

And paste it in your Bitnami Support ticket.

bndiagnostic was not useful. Could you please tell us why?

I don't know how to proceed

Describe your issue as much as you can

Site is not loading after plugins update. I tried to rename the pludins folder but that didn't help.

crino85 commented 1 year ago 
2023-08-21 12:42:55 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-21 12:42:55 0 [Note] InnoDB: Number of pools: 1
2023-08-21 12:42:55 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-08-21 12:42:55 0 [Note] InnoDB: Using Linux native AIO
2023-08-21 12:42:55 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2023-08-21 12:42:55 0 [Note] InnoDB: Completed initialization of buffer pool
2023-08-21 12:42:55 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
2023-08-21 12:42:55 0 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-08-21 12:42:55 0 [Note] InnoDB: Retry with innodb_force_recovery=5
2023-08-21 12:42:55 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2023-08-21 12:42:55 0 [Note] InnoDB: Starting shutdown...
2023-08-21 12:42:55 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-08-21 12:42:55 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-08-21 12:42:55 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-21 12:42:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-08-21 12:42:55 0 [ERROR] Aborting
crino85 commented 1 year ago 
➜  ~ sudo /opt/bitnami/ctlscript.sh restart mariadb
Failed to restart mariadb: Failed to restart mariadb
crino85 commented 1 year ago 
➜  ~ sudo mysql -u root -p

Enter password:
ERROR 2002 (HY000): Can't connect to local server through socket '/opt/bitnami/mariadb/tmp/mysql.sock' (2)
crino85 commented 1 year ago 
➜  ~ journalctl -xe
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit bitnami.service has begun execution.
░░
░░ The job identifier is 600.
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/010_hostname...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/020_swap_file...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/030_check_if_demo_machine...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/040_change_boot_log_permissions...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/050_get_default_passwords...
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4416]: ## 2023-08-21 14:50:40+02:00 ## INFO ## Starting services...
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:40.287Z - info: Saving configuration info to disk
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:40.843Z - info: Performing service start operation for php
Aug 21 14:50:46 ip-172-26-11-190 bitnami[4497]: php 14:50:46.17 INFO  ==> php-fpm started
Aug 21 14:50:46 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:46.175Z - info: Performing service start operation for mariadb
Aug 21 14:50:53 ip-172-26-11-190 dhclient[512]: XMT: Solicit on ens5, interval 112260ms.
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4497]: mariadb 14:51:46.72 ERROR ==> mariadb did not start
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:51:46.726Z - error: Unable to perform start operation Export start for mariadb failed with exit code 1
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit bitnami.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit bitnami.service has entered the 'failed' state with result 'exit-code'.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4515 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4522 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4523 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4524 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4525 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4526 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4527 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4528 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4529 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4530 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4531 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4532 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4533 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4534 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4535 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4536 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4537 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4538 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4539 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4540 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4541 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: Failed to start LSB: bitnami init script.
░░ Subject: A start job for unit bitnami.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit bitnami.service has finished with a failure.
░░
░░ The job identifier is 600 and the job result is failed.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Consumed 2.284s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit bitnami.service completed and consumed the indicated resources.
Aug 21 14:51:46 ip-172-26-11-190 sudo[4407]: pam_unix(sudo:session): session closed for user root
Aug 21 14:51:58 ip-172-26-11-190 sshd[4642]: error: kex_exchange_identification: Connection closed by remote host
Aug 21 14:51:58 ip-172-26-11-190 sshd[4642]: Connection closed by 83.150.215.253 port 34966
Aug 21 14:52:09 ip-172-26-11-190 sudo[4653]:  bitnami : TTY=pts/0 ; PWD=/home/bitnami ; USER=root ; COMMAND=/opt/bitnami/mariadb/bin/mysql -u root -p
Aug 21 14:52:09 ip-172-26-11-190 sudo[4653]: pam_unix(sudo:session): session opened for user root(uid=0) by bitnami(uid=1000)
Aug 21 14:52:10 ip-172-26-11-190 sudo[4653]: pam_unix(sudo:session): session closed for user root
Aug 21 14:52:45 ip-172-26-11-190 dhclient[512]: XMT: Solicit on ens5, interval 125230ms.
...skipping...
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit bitnami.service has begun execution.
░░
░░ The job identifier is 600.
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/010_hostname...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/020_swap_file...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/030_check_if_demo_machine...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/040_change_boot_log_permissions...
Aug 21 14:50:39 ip-172-26-11-190 bitnami[4420]: ## 2023-08-21 14:50:39+02:00 ## INFO ## Running /opt/bitnami/var/init/pre-start/050_get_default_passwords...
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4416]: ## 2023-08-21 14:50:40+02:00 ## INFO ## Starting services...
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:40.287Z - info: Saving configuration info to disk
Aug 21 14:50:40 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:40.843Z - info: Performing service start operation for php
Aug 21 14:50:46 ip-172-26-11-190 bitnami[4497]: php 14:50:46.17 INFO  ==> php-fpm started
Aug 21 14:50:46 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:50:46.175Z - info: Performing service start operation for mariadb
Aug 21 14:50:53 ip-172-26-11-190 dhclient[512]: XMT: Solicit on ens5, interval 112260ms.
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4497]: mariadb 14:51:46.72 ERROR ==> mariadb did not start
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4497]: 2023-08-21T12:51:46.726Z - error: Unable to perform start operation Export start for mariadb failed with exit code 1
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Aug 21 14:51:46 ip-172-26-11-190 bitnami[4596]: ## 2023-08-21 14:51:46+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit bitnami.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit bitnami.service has entered the 'failed' state with result 'exit-code'.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4515 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4522 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4523 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4524 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4525 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4526 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4527 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4528 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4529 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4530 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4531 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4532 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4533 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4534 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4535 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4536 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4537 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4538 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4539 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4540 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 4541 (php-fpm) remains running after unit stopped.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: Failed to start LSB: bitnami init script.
░░ Subject: A start job for unit bitnami.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit bitnami.service has finished with a failure.
░░
░░ The job identifier is 600 and the job result is failed.
Aug 21 14:51:46 ip-172-26-11-190 systemd[1]: bitnami.service: Consumed 2.284s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit bitnami.service completed and consumed the indicated resources.
Aug 21 14:51:46 ip-172-26-11-190 sudo[4407]: pam_unix(sudo:session): session closed for user root
Aug 21 14:51:58 ip-172-26-11-190 sshd[4642]: error: kex_exchange_identification: Connection closed by remote host
Aug 21 14:51:58 ip-172-26-11-190 sshd[4642]: Connection closed by 83.150.215.253 port 34966
Aug 21 14:52:09 ip-172-26-11-190 sudo[4653]:  bitnami : TTY=pts/0 ; PWD=/home/bitnami ; USER=root ; COMMAND=/opt/bitnami/mariadb/bin/mysql -u root -p
Aug 21 14:52:09 ip-172-26-11-190 sudo[4653]: pam_unix(sudo:session): session opened for user root(uid=0) by bitnami(uid=1000)
Aug 21 14:52:10 ip-172-26-11-190 sudo[4653]: pam_unix(sudo:session): session closed for user root
Aug 21 14:52:45 ip-172-26-11-190 dhclient[512]: XMT: Solicit on ens5, interval 125230ms.
lines 1973-2052/2052 (END)
crino85 commented 1 year ago 
===== Begin of bndiagnostic tool output =====

    ✓ Resources: No issues found
    ? Connectivity: Found possible issues
    ? Mariadb: Found possible issues
    ✓ Processes: No issues found
    ✓ Wordpress: No issues found
    ✓ Apache: No issues found
    ✓ Php: No issues found

[Connectivity]

Server ports 22, 80 and/or 443 are not publicly accessible. Please check the
following guide to open server ports for remote access:

https://docs.bitnami.com/general/faq/administration/use-firewall/

[Mariadb]

Press [Enter] to continue:
Found recent error messages in the MariaDB error log:

2023-08-21 14:59:16 0 [ERROR] Aborting

Please check the following guide to troubleshoot MariaDB issues:

https://docs.bitnami.com/aws/apps/wordpress/troubleshooting/debug-errors-m
ariadb/

===== End of bndiagnostic tool output =====

Press [Enter] to continue:
The diagnostic bundle was uploaded successfully to the Bitnami servers. Please copy the following code:

390a848a-42bd-2ff8-f7a2-54fd7ecafc4d

And paste it in your Bitnami Support ticket.
crino85 commented 1 year ago 
➜  wordpress sudo systemctl start bitnami.service

Job for bitnami.service failed because the control process exited with error code.
See "systemctl status bitnami.service" and "journalctl -xe" for details.
➜  wordpress sudo systemctl status bitnami.service

● bitnami.service - LSB: bitnami init script
     Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-08-22 11:51:19 CEST; 4s ago
    Process: 1794 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
      Tasks: 21 (limit: 2311)
     Memory: 136.6M
        CPU: 2.296s
     CGroup: /system.slice/bitnami.service
             ├─684 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
             ├─688 php-fpm: pool www
             ├─689 php-fpm: pool www
             ├─690 php-fpm: pool www
             ├─691 php-fpm: pool www
             ├─692 php-fpm: pool www
             ├─693 php-fpm: pool www
             ├─694 php-fpm: pool www
             ├─695 php-fpm: pool www
             ├─696 php-fpm: pool www
             ├─697 php-fpm: pool www
             ├─698 php-fpm: pool www
             ├─699 php-fpm: pool www
             ├─700 php-fpm: pool www
             ├─701 php-fpm: pool www
             ├─702 php-fpm: pool www
             ├─703 php-fpm: pool www
             ├─704 php-fpm: pool www
             ├─705 php-fpm: pool www
             ├─706 php-fpm: pool www
             └─707 php-fpm: pool www

Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 700 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 701 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 702 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 703 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 704 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 705 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 706 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Unit process 707 (php-fpm) remains running after unit stopped.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: Failed to start LSB: bitnami init script.
Aug 22 11:51:19 ip-172-26-11-190 systemd[1]: bitnami.service: Consumed 2.296s CPU time.
crino85 commented 1 year ago

I think this is the problem:

2023-08-22 12:50:40 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
2023-08-22 12:50:40 0 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-08-22 12:50:40 0 [Note] InnoDB: Retry with innodb_force_recovery=5
2023-08-22 12:50:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
crino85 commented 1 year ago

After adding "innodb_force_recovery=5" to my.cnf file, MariaDB restarted.

sudo /opt/bitnami/ctlscript.sh restart mariadb
Restarted mariadb

Also I was able to reload bitnami services by: sudo systemctl start bitnami.service

● bitnami.service - LSB: bitnami init script
     Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-08-22 13:01:12 CEST; 1min 48s ago
    Process: 3588 ExecStart=/etc/init.d/bitnami start (code=exited, status=0/SUCCESS)
      Tasks: 551 (limit: 2311)
     Memory: 408.8M
        CPU: 1min 7.332s
     CGroup: /system.slice/bitnami.service
             ├─ 684 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
             ├─ 689 php-fpm: pool www
             ├─ 690 php-fpm: pool www
             ├─ 691 php-fpm: pool www
             ├─ 692 php-fpm: pool www
             ├─ 693 php-fpm: pool www
             ├─ 694 php-fpm: pool www
             ├─ 695 php-fpm: pool www
             ├─ 696 php-fpm: pool www
             ├─ 697 php-fpm: pool www
             ├─ 698 php-fpm: pool www
             ├─ 699 php-fpm: pool www
             ├─ 700 php-fpm: pool www
             ├─ 701 php-fpm: pool www
             ├─ 702 php-fpm: pool www
             ├─ 703 php-fpm: pool www
             ├─ 704 php-fpm: pool www
             ├─ 705 php-fpm: pool www
             ├─ 706 php-fpm: pool www
             ├─ 707 php-fpm: pool www
             ├─3705 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
             ├─3708 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
             ├─3709 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
             ├─3714 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
             ├─4102 /opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf
             ├─4233 php-fpm: pool www
             ├─4249 /opt/bitnami/gonit/bin/gonit
             ├─4310 php-fpm: pool www
             └─4312 php-fpm: pool www

Aug 22 13:01:10 ip-172-26-11-190 bitnami[3669]: apache 13:01:10.27 INFO  ==> apache started
Aug 22 13:01:10 ip-172-26-11-190 bitnami[3669]: 2023-08-22T11:01:10.273Z - info: Skipping service start operation for varnish
Aug 22 13:01:10 ip-172-26-11-190 bitnami[3669]: 2023-08-22T11:01:10.480Z - info: Starting gonit monitoring service
Aug 22 13:01:12 ip-172-26-11-190 bitnami[3669]: 2023-08-22T11:01:12.497Z - info: Start monitoring all services from gonit
Aug 22 13:01:12 ip-172-26-11-190 bitnami[4265]: ## 2023-08-22 13:01:12+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Aug 22 13:01:12 ip-172-26-11-190 bitnami[4265]: ## 2023-08-22 13:01:12+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Aug 22 13:01:12 ip-172-26-11-190 bitnami[4265]: ## 2023-08-22 13:01:12+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Aug 22 13:01:12 ip-172-26-11-190 bitnami[4265]: ## 2023-08-22 13:01:12+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Aug 22 13:01:12 ip-172-26-11-190 bitnami[4265]: ## 2023-08-22 13:01:12+02:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Aug 22 13:01:12 ip-172-26-11-190 systemd[1]: Started LSB: bitnami init script.
crino85 commented 1 year ago

now, after renaming plugins folder I was able to access wp backend.

crino85 commented 1 year ago

but when I restart, again the issue:

2023-08-22 14:53:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-22 14:53:51 0 [Note] InnoDB: Number of pools: 1
2023-08-22 14:53:51 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-08-22 14:53:51 0 [Note] InnoDB: Using Linux native AIO
2023-08-22 14:53:51 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2023-08-22 14:53:51 0 [Note] InnoDB: Completed initialization of buffer pool
2023-08-22 14:53:51 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
2023-08-22 14:53:51 0 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-08-22 14:53:51 0 [Note] InnoDB: Retry with innodb_force_recovery=5
2023-08-22 14:53:51 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2023-08-22 14:53:51 0 [Note] InnoDB: Starting shutdown...
2023-08-22 14:53:51 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-08-22 14:53:51 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-08-22 14:53:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-22 14:53:51 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-08-22 14:53:51 0 [ERROR] Aborting
crino85 commented 1 year ago

it seems "wp_options" table is corrupt:

MariaDB [bitnami_wordpress]> check table wp_options;
+------------------------------+-------+----------+---------------------------------------------------------------------------------+
| Table                        | Op    | Msg_type | Msg_text                                                                        |
+------------------------------+-------+----------+---------------------------------------------------------------------------------+
| bitnami_wordpress.wp_options | check | Warning  | InnoDB: The B-tree of index PRIMARY is corrupted.                               |
| bitnami_wordpress.wp_options | check | Warning  | InnoDB: The B-tree of index option_name is corrupted.                           |
| bitnami_wordpress.wp_options | check | Warning  | InnoDB: Index 'option_name' contains 0 entries, should be 18446744073709551615. |
| bitnami_wordpress.wp_options | check | Warning  | InnoDB: Index 'autoload' contains 0 entries, should be 18446744073709551615.    |
| bitnami_wordpress.wp_options | check | error    | Corrupt                                                                         |
+------------------------------+-------+----------+---------------------------------------------------------------------------------+
5 rows in set (0.015 sec)

any help?

crino85 commented 1 year ago

when I try to repair tables:

wp_users: The storage engine for the table doesn't support repair
wp_usermeta: The storage engine for the table doesn't support repair
wp_posts: The storage engine for the table doesn't support repair
wp_comments: The storage engine for the table doesn't support repair
wp_options: The storage engine for the table doesn't support repair
wp_postmeta: The storage engine for the table doesn't support repair
wp_terms: The storage engine for the table doesn't support repair
wp_term_taxonomy: The storage engine for the table doesn't support repair
wp_term_relationships: The storage engine for the table doesn't support repair
wp_termmeta: The storage engine for the table doesn't support repair
crino85 commented 1 year ago

I'm totally blocked:

➜  ~ sudo mysqlcheck -c -uroot -pCkdP1K3hKkvw bitnami_wordpress;
bitnami_wordpress.wp_actionscheduler_actions
Warning  : InnoDB: Index hook is marked as corrupted
Warning  : InnoDB: Index status is marked as corrupted
Warning  : InnoDB: Index scheduled_date_gmt is marked as corrupted
Warning  : InnoDB: Index args is marked as corrupted
Warning  : InnoDB: Index group_id is marked as corrupted
Warning  : InnoDB: Index last_attempt_gmt is marked as corrupted
Warning  : InnoDB: Index claim_id_status_scheduled_date_gmt is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_actionscheduler_claims
Warning  : InnoDB: Index date_created_gmt is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_actionscheduler_groups
Warning  : InnoDB: Index slug is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_actionscheduler_logs
Warning  : InnoDB: Index action_id is marked as corrupted
Warning  : InnoDB: Index log_date_gmt is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_commentmeta                   OK
bitnami_wordpress.wp_comments
Warning  : InnoDB: Index comment_post_ID is marked as corrupted
Warning  : InnoDB: Index comment_approved_date_gmt is marked as corrupted
Warning  : InnoDB: Index comment_date_gmt is marked as corrupted
Warning  : InnoDB: Index comment_parent is marked as corrupted
Warning  : InnoDB: Index comment_author_email is marked as corrupted
Warning  : InnoDB: Index woo_idx_comment_type is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_e_events                      OK
bitnami_wordpress.wp_links                         OK
bitnami_wordpress.wp_mclean_refs                   OK
bitnami_wordpress.wp_mclean_scan                   OK
bitnami_wordpress.wp_options
Warning  : InnoDB: The B-tree of index PRIMARY is corrupted.
Warning  : InnoDB: Index option_name is marked as corrupted
Warning  : InnoDB: Index autoload is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_postmeta
Warning  : InnoDB: Index post_id is marked as corrupted
Warning  : InnoDB: Index meta_key is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_posts
Warning  : InnoDB: Index post_name is marked as corrupted
Warning  : InnoDB: Index type_status_date is marked as corrupted
Warning  : InnoDB: Index post_parent is marked as corrupted
Warning  : InnoDB: Index post_author is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_term_relationships
Warning  : InnoDB: Index term_taxonomy_id is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_term_taxonomy
Warning  : InnoDB: Index term_id_taxonomy is marked as corrupted
Warning  : InnoDB: Index taxonomy is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_termmeta
Warning  : InnoDB: Index term_id is marked as corrupted
Warning  : InnoDB: Index meta_key is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_terms
Warning  : InnoDB: Index slug is marked as corrupted
Warning  : InnoDB: Index name is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_tm_taskmeta                   OK
bitnami_wordpress.wp_tm_tasks                      OK
bitnami_wordpress.wp_usermeta
Warning  : InnoDB: Index user_id is marked as corrupted
Warning  : InnoDB: Index meta_key is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_users
Warning  : InnoDB: Index user_login_key is marked as corrupted
Warning  : InnoDB: Index user_nicename is marked as corrupted
Warning  : InnoDB: Index user_email is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_admin_note_actions
Warning  : InnoDB: The B-tree of index PRIMARY is corrupted.
Warning  : InnoDB: Index note_id is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_admin_notes                OK
bitnami_wordpress.wp_wc_category_lookup            OK
bitnami_wordpress.wp_wc_customer_lookup
Warning  : InnoDB: Index user_id is marked as corrupted
Warning  : InnoDB: Index email is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_download_log               OK
bitnami_wordpress.wp_wc_order_coupon_lookup        OK
bitnami_wordpress.wp_wc_order_product_lookup
Warning  : InnoDB: Index order_id is marked as corrupted
Warning  : InnoDB: Index product_id is marked as corrupted
Warning  : InnoDB: Index customer_id is marked as corrupted
Warning  : InnoDB: Index date_created is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_order_stats
Warning  : InnoDB: Index date_created is marked as corrupted
Warning  : InnoDB: Index customer_id is marked as corrupted
Warning  : InnoDB: Index status is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_order_tax_lookup           OK
bitnami_wordpress.wp_wc_product_attributes_lookup  OK
bitnami_wordpress.wp_wc_product_download_directories
Warning  : InnoDB: Index url is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_product_meta_lookup
Warning  : InnoDB: Index virtual is marked as corrupted
Warning  : InnoDB: Index downloadable is marked as corrupted
Warning  : InnoDB: Index stock_status is marked as corrupted
Warning  : InnoDB: Index stock_quantity is marked as corrupted
Warning  : InnoDB: Index onsale is marked as corrupted
Warning  : InnoDB: Index min_max_price is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_rate_limits                OK
bitnami_wordpress.wp_wc_reserved_stock             OK
bitnami_wordpress.wp_wc_tax_rate_classes
Warning  : InnoDB: Index slug is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wc_webhooks                   OK
bitnami_wordpress.wp_wfblockediplog                OK
bitnami_wordpress.wp_wfblocks7                     OK
bitnami_wordpress.wp_wfconfig                      OK
bitnami_wordpress.wp_wfcrawlers                    OK
bitnami_wordpress.wp_wffilechanges                 OK
bitnami_wordpress.wp_wffilemods                    OK
bitnami_wordpress.wp_wfhits
Warning  : InnoDB: Index k1 is marked as corrupted
Warning  : InnoDB: Index k2 is marked as corrupted
Warning  : InnoDB: Index attackLogTime is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wfhoover                      OK
bitnami_wordpress.wp_wfissues                      OK
bitnami_wordpress.wp_wfknownfilelist               OK
bitnami_wordpress.wp_wflivetraffichuman            OK
bitnami_wordpress.wp_wflocs                        OK
bitnami_wordpress.wp_wflogins
Warning  : InnoDB: Index k1 is marked as corrupted
Warning  : InnoDB: Index hitID is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wfls_2fa_secrets
Warning  : InnoDB: Index user_id is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wfls_role_counts
note     : The storage engine for the table doesn't support check
bitnami_wordpress.wp_wfls_settings                 OK
bitnami_wordpress.wp_wfnotifications               OK
bitnami_wordpress.wp_wfpendingissues               OK
bitnami_wordpress.wp_wfreversecache                OK
bitnami_wordpress.wp_wfsecurityevents              OK
bitnami_wordpress.wp_wfsnipcache                   OK
bitnami_wordpress.wp_wfstatus
Warning  : InnoDB: Index k1 is marked as corrupted
Warning  : InnoDB: Index k2 is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_wftrafficrates                OK
bitnami_wordpress.wp_wfwaffailures                 OK
bitnami_wordpress.wp_woocommerce_api_keys          OK
bitnami_wordpress.wp_woocommerce_attribute_taxonomies OK
bitnami_wordpress.wp_woocommerce_downloadable_product_permissions OK
bitnami_wordpress.wp_woocommerce_log               OK
bitnami_wordpress.wp_woocommerce_order_itemmeta
Warning  : InnoDB: Index order_item_id is marked as corrupted
Warning  : InnoDB: Index meta_key is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_woocommerce_order_items
Warning  : InnoDB: Index order_id is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_woocommerce_payment_tokenmeta OK
bitnami_wordpress.wp_woocommerce_payment_tokens    OK
bitnami_wordpress.wp_woocommerce_sessions
Warning  : InnoDB: Index session_key is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_woocommerce_shipping_zone_locations
Warning  : InnoDB: Index location_id is marked as corrupted
Warning  : InnoDB: Index location_type_code is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_woocommerce_shipping_zone_methods OK
bitnami_wordpress.wp_woocommerce_shipping_zones    OK
bitnami_wordpress.wp_woocommerce_tax_rate_locations OK
bitnami_wordpress.wp_woocommerce_tax_rates         OK
bitnami_wordpress.wp_wpmailsmtp_debug_events       OK
bitnami_wordpress.wp_wpmailsmtp_tasks_meta         OK
bitnami_wordpress.wp_yoast_indexable
Warning  : InnoDB: Index object_type_and_sub_type is marked as corrupted
Warning  : InnoDB: Index object_id_and_type is marked as corrupted
Warning  : InnoDB: Index permalink_hash_and_object_type is marked as corrupted
Warning  : InnoDB: Index subpages is marked as corrupted
Warning  : InnoDB: Index prominent_words is marked as corrupted
Warning  : InnoDB: Index published_sitemap_index is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_yoast_indexable_hierarchy
Warning  : InnoDB: Index indexable_id is marked as corrupted
Warning  : InnoDB: Index ancestor_id is marked as corrupted
Warning  : InnoDB: Index depth is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_yoast_migrations
Warning  : InnoDB: Index wp_yoast_migrations_version is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_yoast_primary_term
Warning  : InnoDB: Index post_taxonomy is marked as corrupted
Warning  : InnoDB: Index post_term is marked as corrupted
error    : Corrupt
bitnami_wordpress.wp_yoast_seo_links               OK
crino85 commented 1 year ago

I'm only able to run MariaDB when setting innodb_force_recovery=5.

But this parameter puts the tables in read only. So I can do nothing.

mdhont commented 1 year ago

The following guide could be of help:

https://docs.bitnami.com/general/apps/wordpress/administration/recover-database-mysql/

crino85 commented 1 year ago

hi, if you read all my messages I already tried that.

crino85 commented 1 year ago

can't repair tables as the engine is InnoDB.

crino85 commented 1 year ago

this is the error:

2023-08-23 15:03:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-23 15:03:33 0 [Note] InnoDB: Number of pools: 1
2023-08-23 15:03:33 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-08-23 15:03:33 0 [Note] InnoDB: Using Linux native AIO
2023-08-23 15:03:33 0 [Note] InnoDB: Initializing buffer pool, total size = 268435456, chunk size = 134217728
2023-08-23 15:03:33 0 [Note] InnoDB: Completed initialization of buffer pool
2023-08-23 15:03:33 0 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
2023-08-23 15:03:33 0 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-08-23 15:03:33 0 [Note] InnoDB: Retry with innodb_force_recovery=5
2023-08-23 15:03:33 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2023-08-23 15:03:33 0 [Note] InnoDB: Starting shutdown...
2023-08-23 15:03:34 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-08-23 15:03:34 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-08-23 15:03:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-08-23 15:03:34 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-08-23 15:03:34 0 [ERROR] Aborting
crino85 commented 1 year ago

these are the corrupted tables:

wp_users: The storage engine for the table doesn't support repair
wp_usermeta: The storage engine for the table doesn't support repair
wp_posts: The storage engine for the table doesn't support repair
wp_comments: The storage engine for the table doesn't support repair
wp_options: The storage engine for the table doesn't support repair
wp_postmeta: The storage engine for the table doesn't support repair
wp_terms: The storage engine for the table doesn't support repair
wp_term_taxonomy: The storage engine for the table doesn't support repair
wp_term_relationships: The storage engine for the table doesn't support repair
wp_termmeta: The storage engine for the table doesn't support repair
mdhont commented 1 year ago

Can you search for a file named like ib_logfile1?

sudo find /opt/bitnami type f -name ib_logfile

And delete them?

https://serverfault.com/questions/379714/unknown-unsupported-storage-engine-innodb-mysql-ubuntu

crino85 commented 1 year ago

I already did that, but the file is being recreated. This is what I have:

➜  data ll
total 186M
-rw-rw---- 1 mysql mysql 1.4M Aug 24 09:29 aria_log.00000001
-rw-rw---- 1 mysql mysql   52 Aug 24 09:29 aria_log_control
drwx------ 2 mysql mysql  12K Aug 23 16:34 bitnami_wordpress
-rw-rw---- 1 mysql mysql    9 Aug 23 17:14 ddl_recovery-backup.log
-rw-rw---- 1 mysql mysql    9 Aug 23 17:14 ddl_recovery.log
-rw-rw---- 1 mysql mysql  17K Aug 23 16:39 ib_buffer_pool
-rw-rw---- 1 mysql mysql  76M Aug 23 16:39 ibdata1
-rw-rw---- 1 mysql mysql  96M Aug 23 17:14 ib_logfile0
-rw-rw---- 1 mysql mysql  12M Aug 23 17:14 ibtmp1
-rw-rw---- 1 mysql mysql    0 Feb 13  2023 multi-master.info
drwx------ 2 mysql mysql 4.0K Feb 13  2023 mysql
-rw-r--r-- 1 root  root    16 Feb 13  2023 mysql_upgrade_info
drwx------ 2 mysql mysql 4.0K Aug 23 16:35 pepe
drwx------ 2 mysql mysql 4.0K Feb 13  2023 performance_schema
drwx------ 2 mysql mysql  12K Feb 13  2023 sys
crino85 commented 1 year ago

in the DB process list I see these smal queries all the time:

MariaDB [bitnami_wordpress]> show processlist;
+-----+--------------+-----------------+-------------------+---------+------+----------------+-------------------------------------------------------------------------+----------+
| Id  | User         | Host            | db                | Command | Time | State          | Info                                                                    | Progress |
+-----+--------------+-----------------+-------------------+---------+------+----------------+-------------------------------------------------------------------------+----------+
| 197 | root         | localhost       | bitnami_wordpress | Query   |    0 | starting       | show processlist                                                        |    0.000 |
| 290 | bn_wordpress | 127.0.0.1:59202 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 293 | bn_wordpress | 127.0.0.1:35326 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 294 | bn_wordpress | 127.0.0.1:35336 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 296 | bn_wordpress | 127.0.0.1:39276 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                    |    0.000 |
| 299 | bn_wordpress | 127.0.0.1:55390 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 300 | bn_wordpress | 127.0.0.1:55406 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 301 | bn_wordpress | 127.0.0.1:55420 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 302 | bn_wordpress | 127.0.0.1:33054 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                    |    0.000 |
| 303 | bn_wordpress | 127.0.0.1:57232 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 304 | bn_wordpress | 127.0.0.1:58692 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 305 | bn_wordpress | 127.0.0.1:54272 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 306 | bn_wordpress | 127.0.0.1:40146 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                    |    0.000 |
| 307 | bn_wordpress | 127.0.0.1:58460 | bitnami_wordpress | Query   |    1 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 308 | bn_wordpress | 127.0.0.1:33524 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                    |    0.000 |
| 309 | bn_wordpress | 127.0.0.1:33406 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 310 | bn_wordpress | 127.0.0.1:39446 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 311 | bn_wordpress | 127.0.0.1:38078 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 312 | bn_wordpress | 127.0.0.1:38084 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 313 | bn_wordpress | 127.0.0.1:38094 | bitnami_wordpress | Query   |    0 | Statistics     | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 314 | bn_wordpress | 127.0.0.1:51956 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 315 | bn_wordpress | 127.0.0.1:51960 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 316 | bn_wordpress | 127.0.0.1:40736 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 317 | bn_wordpress | 127.0.0.1:48502 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 318 | bn_wordpress | 127.0.0.1:48514 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                    |    0.000 |
| 319 | bn_wordpress | 127.0.0.1:52834 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 320 | bn_wordpress | 127.0.0.1:52848 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 321 | bn_wordpress | 127.0.0.1:58648 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 322 | bn_wordpress | 127.0.0.1:33808 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
| 323 | bn_wordpress | 127.0.0.1:54566 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                        |    0.000 |
| 324 | bn_wordpress | 127.0.0.1:54574 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes' |    0.000 |
+-----+--------------+-----------------+-------------------+---------+------+----------------+-------------------------------------------------------------------------+----------+
31 rows in set (0.000 sec)

MariaDB [bitnami_wordpress]> show processlist;
+-----+--------------+-----------------+-------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+
| Id  | User         | Host            | db                | Command | Time | State          | Info                                                                                                 | Progress |
+-----+--------------+-----------------+-------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+
| 197 | root         | localhost       | bitnami_wordpress | Query   |    0 | starting       | show processlist                                                                                     |    0.000 |
| 290 | bn_wordpress | 127.0.0.1:59202 | bitnami_wordpress | Query   |    1 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 293 | bn_wordpress | 127.0.0.1:35326 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 294 | bn_wordpress | 127.0.0.1:35336 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 296 | bn_wordpress | 127.0.0.1:39276 | bitnami_wordpress | Query   |    0 | Opening tables | INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_astra-theme |    0.000 |
| 299 | bn_wordpress | 127.0.0.1:55390 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 300 | bn_wordpress | 127.0.0.1:55406 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 301 | bn_wordpress | 127.0.0.1:55420 | bitnami_wordpress | Query   |    1 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 302 | bn_wordpress | 127.0.0.1:33054 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 303 | bn_wordpress | 127.0.0.1:57232 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 304 | bn_wordpress | 127.0.0.1:58692 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 305 | bn_wordpress | 127.0.0.1:54272 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 306 | bn_wordpress | 127.0.0.1:40146 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 307 | bn_wordpress | 127.0.0.1:58460 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 308 | bn_wordpress | 127.0.0.1:33524 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 309 | bn_wordpress | 127.0.0.1:33406 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 310 | bn_wordpress | 127.0.0.1:39446 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 311 | bn_wordpress | 127.0.0.1:38078 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 312 | bn_wordpress | 127.0.0.1:38084 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 313 | bn_wordpress | 127.0.0.1:38094 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 314 | bn_wordpress | 127.0.0.1:51956 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 315 | bn_wordpress | 127.0.0.1:51960 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 316 | bn_wordpress | 127.0.0.1:40736 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 317 | bn_wordpress | 127.0.0.1:48502 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 318 | bn_wordpress | 127.0.0.1:48514 | bitnami_wordpress | Query   |    0 | starting       | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 319 | bn_wordpress | 127.0.0.1:52834 | bitnami_wordpress | Query   |    1 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
| 320 | bn_wordpress | 127.0.0.1:52848 | bitnami_wordpress | Query   |    0 | Writing to net | SELECT option_name, option_value FROM wp_options                                                     |    0.000 |
| 321 | bn_wordpress | 127.0.0.1:58648 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 322 | bn_wordpress | 127.0.0.1:33808 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 323 | bn_wordpress | 127.0.0.1:54566 | bitnami_wordpress | Sleep   |    0 |                | NULL                                                                                                 |    0.000 |
| 324 | bn_wordpress | 127.0.0.1:54574 | bitnami_wordpress | Query   |    0 | Sending data   | SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'                              |    0.000 |
+-----+--------------+-----------------+-------------------+---------+------+----------------+------------------------------------------------------------------------------------------------------+----------+
31 rows in set (0.000 sec)
crino85 commented 1 year ago

I finally had to recover from an old snapshot...

please, take care of this kind of degradation and instability on AWS.

Yasin-Ali-Cpuflat commented 1 year ago

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro rs-apache/

how did you fix apache

jotamartos commented 1 year ago

Hi @Yasin-Ali-Cpuflat,

He basically had an issue with the database and that's why WordPress couldn't work properly and returned errors in the Apache's log. If you are running into issues with Apache, please create a separate ticket and provide as much information as you can so the team can review it and provide feedback.

Thanks