MySQL crashed suddenly

MySQL seems to crash suddenly but recovered in around 2minutes. I am running on Ubuntu 18.04 (16vcpu, 32GB RAM). I dont know what caused it.

Here is my.ini

[mysql] default-character-set=utf8mb4  [mysqld] lower_case_table_names = 1 pid-file        = /var/run/mysqld/mysqld.pid socket          = /var/run/mysqld/mysqld.sock datadir         = /data/mysql log-error       = /var/log/mysql/error.log # By default we only accept connections from localhost #bind-address   = 127.0.0.1 # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 max_allowed_packet=1G max_connect_errors=1000 max_connections=2500 character-set-server=utf8mb4 collation-server=utf8mb4_unicode_ci innodb_buffer_pool_size=27G server-id=2 log-bin=env1 expire_logs_days=2 sql_mode='STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' net_read_timeout=300 net_write_timeout=300 log_bin_trust_function_creators=1 

Here is my /var/log/mysql/error.log enter image description here

The crash is around 8:11am as seen on the image above

Im trying to find the root cause for this. Is there any logs in Ubuntu that I can check to find more info on what caused MySQL to crash?

Check if coroutine crashed

I can check if coroutine still running by setting boolean variable outside the coroutine and then letting the coroutine itself set the value to true when it runs and set it to false when it decide to stop .

But this method of detecting whether coroutine still active or not doesn’t work when the coroutine crashed due to error (invalid input, null reference , ect) because the boolean variable remain true while the coroutine itself has stopped due to error.

How do i check if coroutine still running or not in current frame ? i can’t spend my code checking for next frame .

Preferably C# , but answer in javascript also accepted.

MySQL version 5.6.35 RDS DB Instance crashed with error code 6

DB instance is running on MySQL version 5.6.35 Please see below for more details… Is it a bug in this version which needs an upgrade to a later version or there is something to look at the memory parameter tuning.

DB Instance Crashing consecutively for 2 days at the same time with the same error log as below:

mysql> show variables like 'query_cache_%' ; +------------------------------+-------+ | Variable_name                | Value | +------------------------------+-------+ | query_cache_limit            | 0     | | query_cache_min_res_unit     | 512   | | query_cache_size             | 0     | | query_cache_type             | OFF   | | query_cache_wlock_invalidate | OFF   | +------------------------------+-------+ mysql> SHOW VARIABLES LIKE "sort_buffer_size"; +------------------+--------+ | Variable_name    | Value  | +------------------+--------+ | sort_buffer_size | 262144 | +------------------+--------+ Sort_merge_passes=@SMP Sort_merge_passes rate=@SMP_RATE +------+-----------+ | @SMP | @SMP_RATE | +------+-----------+ | 1756 |     21072 | +------+-----------+  Logs:  2020-04-18 19:24:15 115590 [Warning] Event Scheduler: [rdsadmin@localhost][mysql.ev_rds_gsh_collector] Truncated incorrect DOUBLE value: 'Unknown' terminate called after throwing an instance of 'std::out_of_range'   what():  vector::_M_range_check 19:28:26 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. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed,  something is definitely wrong and this may fail.  key_buffer_size=16777216 read_buffer_size=262144 max_used_connections=416 max_threads=2000 thread_count=190 connection_count=189 It is possible that mysqld could use up to  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1065977 K  bytes of memory Hope that's ok; if not, decrease some variables in the equation.  Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /rdsdbbin/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0x8d1a7c] /rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0x481)[0x66eea1] /lib64/libpthread.so.0(+0xf100)[0x2b5e7d2ad100] /lib64/libc.so.6(gsignal+0x37)[0x2b5e7e3485f7] /lib64/libc.so.6(abort+0x148)[0x2b5e7e349ce8] /usr/lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x155)[0x2b5e7db56515] /usr/lib64/libstdc++.so.6(+0x5e6a6)[0x2b5e7db546a6] /usr/lib64/libstdc++.so.6(+0x5e6d3)[0x2b5e7db546d3] /usr/lib64/libstdc++.so.6(+0x5e8f3)[0x2b5e7db548f3] /usr/lib64/libstdc++.so.6(_ZSt20__throw_out_of_rangePKc+0x67)[0x2b5e7dba6557] /rdsdbbin/mysql/bin/mysqld[0xa95394] /rdsdbbin/mysql/bin/mysqld[0xa96cbd] /rdsdbbin/mysql/bin/mysqld[0xa97ec0] /lib64/libpthread.so.0(+0x7dc5)[0x2b5e7d2a5dc5] /lib64/libc.so.6(clone+0x6d)[0x2b5e7e409c9d] 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. 2020-04-18 19:28:49 58516 [Note] Plugin 'FEDERATED' is disabled. 2020-04-18 19:28:49 58516 [Note] InnoDB: Using atomics to ref count buffer pool pages 2020-04-18 19:28:49 58516 [Note] InnoDB: The InnoDB memory heap is disabled 2020-04-18 19:28:49 58516 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-04-18 19:28:49 58516 [Note] InnoDB: Memory barrier is not used 2020-04-18 19:28:49 58516 [Note] InnoDB: Compressed tables use zlib 1.2.3 2020-04-18 19:28:49 58516 [Note] InnoDB: Using Linux native AIO 2020-04-18 19:28:49 58516 [Note] InnoDB: Using CPU crc32 instructions 2020-04-18 19:28:49 58516 [Note] InnoDB: Initializing buffer pool, size = 117.0G 2020-04-18 19:28:56 58516 [Note] InnoDB: Completed initialization of buffer pool 2020-04-18 19:28:57 58516 [Note] InnoDB: Highest supported file format is Barracuda. 2020-04-18 19:28:57 58516 [Note] InnoDB: Log scan progressed past the checkpoint lsn 16180005449622 2020-04-18 19:28:57 58516 [Note] InnoDB: Database was not shutdown normally! 2020-04-18 19:28:57 58516 [Note] InnoDB: Starting crash recovery. 2020-04-18 19:28:57 58516 [Note] InnoDB: Reading tablespace information from the .ibd files... 2020-04-18 19:28:57 58516 [Note] InnoDB: Restoring possible half-written data pages  2020-04-18 19:28:57 58516 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 16180010692096 InnoDB: Doing recovery: scanned up to log sequence number 16180015934976 InnoDB: Doing recovery: scanned up to log sequence number 16180021177856 InnoDB: Doing recovery: scanned up to log sequence number 16180026420736 InnoDB: Doing recovery: scanned up to log sequence number 16180031663616 InnoDB: Doing recovery: scanned up to log sequence number 16180036906496 InnoDB: Doing recovery: scanned up to log sequence number 16180042149376 InnoDB: Doing recovery: scanned up to log sequence number 16180047392256 InnoDB: Doing recovery: scanned up to log sequence number 16180052635136 InnoDB: Doing recovery: scanned up to log sequence number 16180057878016 InnoDB: Doing recovery: scanned up to log sequence number 16180063120896 InnoDB: Doing recovery: scanned up to log sequence number 16180068363776 InnoDB: Doing recovery: scanned up to log sequence number 16180073606656 InnoDB: Doing recovery: scanned up to log sequence number 16180078849536 InnoDB: Doing recovery: scanned up to log sequence number 16180080849294 InnoDB: 3 transaction(s) which must be rolled back or cleaned up InnoDB: in total 27 row operations to undo InnoDB: Trx id counter is 262472787712 2020-04-18 19:29:01 58516 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99  InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 50483028, file name mysql-bin-changelog.344987 2020-04-18 19:29:08 58516 [Note] InnoDB: 128 rollback segment(s) are active. InnoDB: Starting in background the rollback of uncommitted transactions 2020-04-18 19:29:08 2bc860e82700  InnoDB: Rolling back trx with id 262472780916, 1 rows to undo 2020-04-18 19:29:08 58516 [Note] InnoDB: Waiting for purge to start 2020-04-18 19:29:08 58516 [Note] InnoDB: Rollback of trx with id 262472780916 completed 2020-04-18 19:29:08 2bc860e82700  InnoDB: Rolling back trx with id 262472779752, 2 rows to undo 2020-04-18 19:29:08 58516 [Note] InnoDB: Rollback of trx with id 262472779752 completed 2020-04-18 19:29:08 2bc860e82700  InnoDB: Rolling back trx with id 262472778249, 24 rows to undo 2020-04-18 19:29:08 58516 [Note] InnoDB: 5.6.35 started; log sequence number 16180080849294 2020-04-18 19:29:08 2bc907606700 InnoDB: Loading buffer pool(s) from /rdsdbdata/db/innodb/ib_buffer_pool 2020-04-18 19:29:08 58516 [Note] Recovering after a crash using /rdsdbdata/log/binlog/mysql-bin-changelog 2020-04-18 19:29:08 58516 [Note] InnoDB: Rollback of trx with id 262472778249 completed 2020-04-18 19:29:08 2bc860e82700  InnoDB: Rollback of non-prepared transactions completed 2020-04-18 19:29:09 58516 [Note] Starting crash recovery... 2020-04-18 19:29:09 58516 [Note] Crash recovery finished. 2020-04-18 19:29:09 58516 [Note] Server hostname (bind-address): '*'; port: 3306 2020-04-18 19:29:09 58516 [Note] IPv6 is available. 2020-04-18 19:29:09 58516 [Note]   - '::' resolves to '::'; 2020-04-18 19:29:09 58516 [Note] Server socket created on IP: '::'. 2020-04-18 19:29:09 58516 [Note] Event Scheduler: Loaded 2 events 2020-04-18 19:29:09 58516 [Note] /rdsdbbin/mysql/bin/mysqld: ready for connections. Version: '5.6.35-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL) 2020-04-18 19:29:09 58516 [Note] Event Scheduler: scheduler thread started with id 1 

How do you suggest to prevent crashed MyISAM table?

On my site was an error:
General Error SQL ERROR [ mysqli ] – Table 'phpbb_sessions' is marked as crashed and should be repaired

I could click to repair that table in mysql manager – PHPMyAdmin and that fixed it. Also the command is: REPAIR TABLE phpbb_sessions;

But the question is how to prevent it. Someone said that MyISAM tables crash like this due to something unexpected, like a server failure, out of memory/disk space or breakdown. There is nothing i can do to prevent it if i am not a…

How do you suggest to prevent crashed MyISAM table?

ERROR: gcloud crashed (UnicodeDecodeError): ‘utf8’ codec can’t decode byte 0xc8 in position 145: invalid continuation byte

I have installed SDK and try to do gcloud init but i am getting below error.

can anyone please help on this.

khumansingh@DESKTOP-97PCNCB:~$ gcloud init Welcome! This command will take you through the configuration of gcloud.

Your current configuration has been set to: [default]

You can skip diagnostics next time by using the following flag: gcloud init –skip-diagnostics

Network diagnostic detects and fixes local network connection issues. Checking network connection…done. Reachability Check passed. Network diagnostic passed (1/1 checks passed).

ERROR: gcloud crashed (UnicodeDecodeError): ‘utf8’ codec can’t decode byte 0xc8 in position 145: invalid continuation byte

If you would like to report this issue, please run the following command: gcloud feedback

To check gcloud for common problems, please run the following command: gcloud info –run-diagnostics

Windows has crashed suddenly it was includes Oracle DB

I had Oracle database XE 11G on windows 7 , but DB installation files (Old oradata , fast_recovery , product and admin) on partition (D) that is save .. I have installed fresh windows with same old name and installed new Oracle DB with same path without taking any RMAN or HOT backup , what is the steps to replace new DB files with old ?? I need to access to my old database.

Thanks..

Android’s Application automatically closed (crashed) many times

Hope you may help me. I apologize to ask this, as I am not sure whether I can ask such complex problem on Google.

I have Samsung SM-G530H or known as Grand Prime with Android 4.4.4 (KitKat). Was good so far before around 2 weeks ago. Since around two weeks ago, the application I was opening many times closed suddenly. Not many application I used and not may application I installed. I have not installed any applications in this few months. The last application I installed was Basic 8086, a small educational application.

This my phone I used for browsing (Chrome), to open FB (FB Lite), to see Youtube, to make note with ColorNote, and WhatsApp (WA). Of course there are some more applications rested in my phone, but neither I used nor I updated. But however, the application I mostly used I did update: Chrome, YouTube, WA, and especially FB Lite (most frquently). Normally I just follow the suggestion to install the update.

Before I really realize that there was problem, the keyboard was many times missing when I was typing, then shown again after sometimes. Then in this one week, the application I mostly used I mentioned above, then suddenly closed. Since yesterday, the sudden closed was more frequently. And this morning is the peak.

This morning, I tried to solve the problem by uninstall the update or uninstall the applications one by one to see if any of the applications the causing of the problem. So far, like nothing of them the suspect. Then I installed CleanMaster to clean all the junks file to see if the junk files the causing problem. But also didn’t help. Then I install Security Center antivirus. That application itself I found more problem, closed more seldom. Then the last I installed was Kampersky antivirus. With this antivirus, seems there a bit slower the sudden close (crash).

Then my question, what is the problem with my phone?