Browse through the questions and answers listed below or filter and sort to narrow down your results.
ERROR 2002 (HY000): Can't connect to local server through socket '/opt/bitnami/mariadb/tmp/mysql.sock' (111)
My website has a problem, Error establishing a database connection I fail to access to > /wp-admin/maint/repair.php So tried to Recover A MariaDB Database. But there are Error message like this. > ERROR 2002 (HY000): Can't connect to local server through socket '/opt/bitnami/mariadb/tmp/mysql.sock' (111) I appreciat you guyts if give some advice to solve the database problems [sql log] ``` 2022-09-15 11:51:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-09-15 11:51:53 0 [Note] InnoDB: Number of pools: 1 2022-09-15 11:51:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-09-15 11:51:53 0 [Note] InnoDB: Using Linux native AIO 2022-09-15 11:51:53 0 [Note] InnoDB: Initializing buffer pool, total size = 2147483648, ch unk size = 134217728 2022-09-15 11:51:53 0 [Note] InnoDB: Completed initialization of buffer pool 2022-09-15 11:51:53 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=374566523 4,3747530277 2022-09-15 11:51:53 0 [ERROR] InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY befo re FILE_CHECKPOINT for tablespace 541 2022-09-15 11:51:53 0 [ERROR] InnoDB: Plugin initialization aborted with error Data struct ure corruption 2022-09-15 11:51:53 0 [Note] InnoDB: Starting shutdown... 2022-09-15 11:51:53 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-09-15 11:51:53 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-09-15 11:51:53 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-09-15 11:51:53 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2022-09-15 11:51:53 0 [ERROR] Aborting ```
Errors Launching MariaDB on Lightsale
Hello, I recently launched a new Lightsale instance and the first thing I wanted to do is launch MariaDB. I ran the below command, which I found in AWS help docs: sudo /opt/bitnami/mariadb/bin/mysqld_safe --defaults-file=/opt/bitnami/mariadb/conf/my.cnf --init-file=/tmp/mysql-init 2> /dev/null & But the process dies almost immediately. Here is the associated errors from mysqld.log: 220914 16:02:15 mysqld_safe Starting mariadbd daemon with databases from /opt/bitnami/mariadb/data 2022-09-14 16:02:15 0 [Note] /opt/bitnami/mariadb/sbin/mariadbd (server 10.6.7-MariaDB) starting as process 17091 ... 2022-09-14 16:02:15 0 [ERROR] mariadbd: Can't lock aria control file '/opt/bitna mi/mariadb/data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds 2022-09-14 16:02:45 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/opt/bitnami/mariadb/data/aria_log_control' 2022-09-14 16:02:45 0 [ERROR] Plugin 'Aria' init function returned error. 2022-09-14 16:02:45 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2022-09-14 16:02:45 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-09-14 16:02:45 0 [Note] InnoDB: Number of pools: 1 2022-09-14 16:02:45 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-09-14 16:02:45 0 [Note] InnoDB: Using Linux native AIO 2022-09-14 16:02:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16777216, chunk size = 16777216 2022-09-14 16:02:45 0 [Note] InnoDB: Completed initialization of buffer pool 2022-09-14 16:02:45 0 [Note] InnoDB: 128 rollback segments are active. 2022-09-14 16:02:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-09-14 16:02:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-09-14 16:02:45 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-09-14 16:02:45 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-09-14 16:02:45 0 [Note] InnoDB: 10.6.7 started; log sequence number 42437; transaction id 14 2022-09-14 16:02:45 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-09-14 16:02:45 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded 2022-09-14 16:02:45 0 [ERROR] Failed to initialize plugins. 2022-09-14 16:02:45 0 [ERROR] Aborting 220914 16:02:45 mysqld_safe mysqld from pid file /opt/bitnami/mariadb/tmp/mysqld.pid ended The my.cnf is pretty basic: [mysqladmin] user= [mysqld] skip_name_resolve explicit_defaults_for_timestamp basedir=/opt/bitnami/mariadb port=3306 tmpdir=/opt/bitnami/mariadb/tmp socket=/opt/bitnami/mariadb/tmp/mysql.sock pid_file=/opt/bitnami/mariadb/tmp/mysqld.pid max_allowed_packet=16M bind_address=127.0.0.1 log_error=/opt/bitnami/mariadb/logs/mysqld.log slow_query_log=0 slow_query_log_file=/opt/bitnami/mariadb/logs/mysqld.log long_query_time=10.0 character_set_server=utf8 collation_server=utf8_general_ci plugin_dir=/opt/bitnami/mariadb/lib/plugin [client] port=3306 socket=/opt/bitnami/mariadb/tmp/mysql.sock pid_file=/opt/bitnami/mariadb/tmp/mysqld.pid !include /opt/bitnami/mariadb/conf/bitnami/my_custom.cnf !include /opt/bitnami/mariadb/conf/bitnami/memory.conf I have made no changes to anything, other than creating /tmp/mysql.init as described on another AWS kb article, but all that does is change the root password for MariaDB. Can anyone help me figure this out?
How to get a fixed IP (pingable) for Streamlit app hosted on AWS Lightsail?
Hi, I have my streamlit app hosted and running on AWS Lightsail. My app displays information by accessing data from internal organization database (MariaDB). The IT team has requested for a fixed IP address for it which needs to be ping-able. I have attached a static IP address to my instance, but it is not that. Can anyone please help?
RDS infinite reboot loop after parameter group changes
I recently changed about 5 parameter group variables on my MariaDB RDS instance and changed the parameter group to my new custom one. This apparently required a reboot, which I did. It has now been an hour and the database is stuck in the "Rebooting" status. About every 3-4 minutes a new "DB instance shutdown" event is created. The logs don't show anything except the first reboot after applying the new parameter group about 45 minutes ago. So the question is, did I brick this database from a bad custom param? Is there any way to stop the reboot process so I can revert the param group change back to default? I've started to create a new DB based on the most recent snapshot but I'd rather not lose ~8 hours of DB changes if I don't have to. Thanks!
Slow WordPress on EC2
Hey! I'm using AWS C7g.xlarge instance to host my WordPress website. The server is running Amazon Linux 2 AMI with LEMP stack that is Nginx as a reverse proxy to Apache, Mariadb, and PHP. I'm facing a very weird issue. The WordPress Admin panel is working very fast. But when a customers login to the website. The website becomes really slow. It initially take around 5-6 seconds for the customer to be redirected to the customer dashboard and then each page he visits takes up to 10 seconds to load. The same website with absolutely same code is deployed on Cloudways Vultr server as well. There without any changes, the website works very fast for both administrators and customers. After days of troubleshooting, I found that on AWS server, Nginx is forwarding the requests to the Apache very fast but it's Apache that takes too long to respond. Hence, the website becomes really slow for logged in users. Unfortunately, I can't access the server configurations on Cloudways due to their privacy. But the only difference between my AWS and cloudways server is literally just the Nginx and Apache configuration. So, I'm looking for someone who can guide me about how can I maximize the Apache performance on my EC2 instance. I already tried increasing the php.ini values but no luck. Thanks for any help in advance.
RDS MariaDB free tier
Hi there, I am new to AWS and I am evaluating it for publishing a web application that is still under development. I have set up a MariaDB database and in 83 hours of instance running with actual usage below 24h and from a single user, I've received a bill over $100. Clearly, I will not be able to afford the cost of this database whenever I will be ready to publish my website. I wanted to understand if anyone can help me with how to set up a cost-effective database. I thought I could take advantage of Free Tier during this trial period, I understand Free tier covers instance running time and storage space, but at this stage, I am unsure if it also provides transactions allowance. Any support will be greatly appreciated.
I have lots of tables that are stuck in the "Pending Records" Validation state and I can't get them to progress
I have a migration from MySQL ---> MariaDB that is pretty straightforward and is generally working well. However, I have several tables that have a Validation State of "Pending records". This task has been running for several days and the validation state never changes. The problem doesn't seem to be caused by the number of records in the table. Some of the tables have a small total number of records (~900) and a small number of records in the "pending" state (<10). Some of the tables have a large total number of records (~1.5MM) and several thousand in the "pending" state. And other tables have 0 validated records and various numbers of total records. I've have noticed that if I "Reload table data" for some of the tables it works and they become 100% validated. However, it doesn't work every time and reloading data seems like a bad way to resolve the problem. I've read through the support documents and have an open case with AWS support for this issue, but I thought I would reach out to see if anyone has had this problem and how they solved it. Tips: * You're going to need a *much* larger migration instance than you think; these migration tasks are **very** RAM intensive! * Increase the `ThreadCount` property of the Validation portion of the migration task; it *seems* to help somewhat
Where do I set innodb_force_recovery in RDS Mariadb
Our RDS Mariadb instance hit a crash recently. The instance is now stuck at 'Rebooting' state. While the instance is in 'rebooting' state, the only operation available is 'delete'. But I don't want to delete the instance. I've posted the crash log to https://jira.mariadb.org/browse/MDEV-28975 and they have suggested to set `innodb_force_recovery = 3`. But I can't find this parameter in RDS parameter groups and it's not listed as an unsupported parameters either. My other question is how do I force stop my RDS instance. I've contacted AWS Support but their response is that they don't have permission to stop customers' instances. I've just same crash again after restoring from backup. I just can't accept the fact that you can only restore from backup when you hit a crash. Anyone else had similar experience? Thanks
When upgrading RDS(mariaDB) version, will endpoint and ARN information change?
I am trying to upgrade Maria DB version. (It's because aws has stopped supporting that version.) The thing to worry about is that the DB endpoint and address such as ARN seem to have changed. Does the version upgrade change values such as endpoints or ARNs?
RDS MariaDB size actual more than usage.
Hi Everyone, I have used RDS MariaDB with the option Autoscaling enable. I receive alarm feeble storage of more than 120GB. But actually, I did check size storage in Databases is 54GB with the command below: ``` SELECT table_schema "DB Name", ROUND(SUM(data_length + index_length) / 1024 / 1024 / 1024, 1) "DB Size in GB" FROM information_schema.tables GROUP BY table_schema; ``` Please explain and help me resolve issues. Best regard.
Can't connect to Lightsail instance
I wanted to connect to my database remotely and did some modifications to allow this. Followed the instructions in the [Connect To MariaDB From A Different Machine](https://docs.bitnami.com/virtual-machine/infrastructure/lamp/administration/connect-remotely-mariadb/) page. Hit a bump in the first step; the `ufw` command was not recognized. So I tried to find a way to install it and followed the instructions in the [-bash: ufw: command not found (ubuntu 18.04)](https://dev.to/delightfullynerdy/bash-ufw-command-not-found-ubuntu-18-04-1agh) page. I did all that and now I can't connect to my instance. The site in the instance is inaccessible. Can't connect using SSH or FTP. Can't ping the IP. Restarting the services and/or the instance did not work. If I click on the "Connect using SSH" button in the instance page (in the Lightsail console) and wait long enough, I get the following error: > An error occurred and we were unable to connect or stay connected to your instance. If this instance has just started up, try again in a minute or two. > > UPSTREAM_NOT_FOUND  How can I regain access to my instance back? If the instance is not salvagable, is there a way to, well, salvage the database (and maybe the project files)?