Keywords: MySQL - AWS - Technical issue - Other
bnsupport ID: e53a61b3-187c-ae47-6144-0449a93d5708
Hello, It almost suddenly happened that the website started saying "Error Establishing database connection". I did a few things to understand the issue.
- Checked the status of services. Everything was running except Mysql.
- I checked the log file of Mysql and it indicated that there was a problem with the log file.
This is where I got stuck because this is a unique one. Never seen anything like this, neither could find a forum that could have solved it.
Here is what the log file said : "2019-04-24T11:54:33.549383Z 85170 [ERROR] [MY-010905] [Server] Can't generate a unique log-filename binlog.(1-999).
2019-04-24T11:54:33.569695Z 85170 [ERROR] [MY-011072] [Server] Binary logging not possible. Message: Can't generate a unique log-filename binlog.(1-999), while rotating the binlog. Aborting the server.
11:54:33 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 67853 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f4980009d80
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 7f49a01c9d80 thread_stack 0x46000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x1c6d98e]
/opt/bitnami/mysql/bin/mysqld.bin(MYSQL_BIN_LOG::new_file_impl(bool, Format_description_log_event*)+0x990) [0x192d110]
/opt/bitnami/mysql/bin/mysqld.bin(MYSQL_BIN_LOG::rotate(bool, bool*)+0x35) [0x192d185]
/opt/bitnami/mysql/bin/mysqld.bin(MYSQL_BIN_LOG::ordered_commit(THD*, bool, bool)+0x4d7) [0x1932077]
/opt/bitnami/mysql/bin/mysqld.bin(MYSQL_BIN_LOG::commit(THD*, bool)+0x801) [0x19334d1]
/opt/bitnami/mysql/bin/mysqld.bin(ha_commit_trans(THD*, bool, bool)+0x3a7) [0xf16497]
/opt/bitnami/mysql/bin/mysqld.bin(trans_commit_stmt(THD*, bool)+0x2d) [0xdf360d]
/opt/bitnami/mysql/bin/mysqld.bin(mysql_execute_command(THD*, bool)+0x2cd2) [0xd14af2]
/opt/bitnami/mysql/bin/mysqld.bin(mysql_parse(THD*, Parser_state*, bool)+0x33f) [0xd1657f]
/opt/bitnami/mysql/bin/mysqld.bin(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x2e1b) [0xd1980b]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f4980334418): is an invalid pointer
Connection ID (thread ID): 85170
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Quiet stuck here.