hi my server block ever time when i use it for 6 month and 100 cars send data ever 10 s
the problem is in mysql server is shetdown evry time i loss my data and return to the 0 point
somme one help me plese
mysql logs look lik this :
2021-03-24T22:48:11.090049Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2021-03-24T22:48:11.090312Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2021-03-24T22:48:11.545297Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-24T22:48:11.591776Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16.04.1) starting as process 1061 ...
2021-03-24T22:48:11.676469Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-03-24T22:48:11.676577Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-24T22:48:11.676609Z 0 [Note] InnoDB: Uses event mutexes
2021-03-24T22:48:11.676749Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-24T22:48:11.676825Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-03-24T22:48:11.676853Z 0 [Note] InnoDB: Using Linux native AIO
2021-03-24T22:48:11.687431Z 0 [Note] InnoDB: Number of pools: 1
2021-03-24T22:48:11.702550Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-03-24T22:48:11.720147Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-24T22:48:11.781904Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-24T22:48:11.790288Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-24T22:48:11.848909Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-24T22:48:11.887887Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 79684856617
2021-03-24T22:48:12.518150Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79690099200
2021-03-24T22:48:12.786360Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79693046038
2021-03-24T22:48:12.792929Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-24T22:48:12.792984Z 0 [Note] InnoDB: Starting crash recovery.
2021-03-24T22:48:13.253459Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 22:48:13 UTC - mysqld got signal 11 ;
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 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...
0 1 2 stack_bottom = 0 thread_stack 0x30000
2021-03-24T22:56:14.175963Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2021-03-24T22:56:14.176330Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2021-03-24T22:56:14.534974Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-24T22:56:14.542777Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16.04.1) starting as process 1519 ...
2021-03-24T22:56:14.561729Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-03-24T22:56:14.561847Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-24T22:56:14.561876Z 0 [Note] InnoDB: Uses event mutexes
2021-03-24T22:56:14.561894Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-24T22:56:14.561909Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-03-24T22:56:14.561924Z 0 [Note] InnoDB: Using Linux native AIO
2021-03-24T22:56:14.563194Z 0 [Note] InnoDB: Number of pools: 1
2021-03-24T22:56:14.564174Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-03-24T22:56:14.572809Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-24T22:56:14.616520Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-24T22:56:14.628758Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-24T22:56:14.651923Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-24T22:56:14.657002Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 79684856617
2021-03-24T22:56:15.104425Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79690099200
2021-03-24T22:56:15.338581Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79693046038
2021-03-24T22:56:15.343192Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-24T22:56:15.343242Z 0 [Note] InnoDB: Starting crash recovery.
2021-03-24T22:56:15.475486Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 22:56:15 UTC - mysqld got signal 11 ;
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 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...
1 2
It would be nice if you format your post with proper markdown to make it readable.
what are your server stats?
hi my server block ever time when i use it for 6 month and 100 cars send data ever 10 s
the problem is in mysql server is shetdown evry time i loss my data and return to the 0 point
somme one help me plese
mysql logs look lik this :
2021-03-24T22:48:11.090049Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2021-03-24T22:48:11.090312Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2021-03-24T22:48:11.545297Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-24T22:48:11.591776Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16.04.1) starting as process 1061 ...
2021-03-24T22:48:11.676469Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-03-24T22:48:11.676577Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-24T22:48:11.676609Z 0 [Note] InnoDB: Uses event mutexes
2021-03-24T22:48:11.676749Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-24T22:48:11.676825Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-03-24T22:48:11.676853Z 0 [Note] InnoDB: Using Linux native AIO
2021-03-24T22:48:11.687431Z 0 [Note] InnoDB: Number of pools: 1
2021-03-24T22:48:11.702550Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-03-24T22:48:11.720147Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-24T22:48:11.781904Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-24T22:48:11.790288Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-24T22:48:11.848909Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-24T22:48:11.887887Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 79684856617
2021-03-24T22:48:12.518150Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79690099200
2021-03-24T22:48:12.786360Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79693046038
2021-03-24T22:48:12.792929Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-24T22:48:12.792984Z 0 [Note] InnoDB: Starting crash recovery.
2021-03-24T22:48:13.253459Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 22:48:13 UTC - mysqld got signal 11 ;
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 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...
0 1 2 stack_bottom = 0 thread_stack 0x30000
2021-03-24T22:56:14.175963Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2021-03-24T22:56:14.176330Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2021-03-24T22:56:14.534974Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2021-03-24T22:56:14.542777Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16.04.1) starting as process 1519 ...
2021-03-24T22:56:14.561729Z 0 [Note] InnoDB: PUNCH HOLE support available
2021-03-24T22:56:14.561847Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-24T22:56:14.561876Z 0 [Note] InnoDB: Uses event mutexes
2021-03-24T22:56:14.561894Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-24T22:56:14.561909Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2021-03-24T22:56:14.561924Z 0 [Note] InnoDB: Using Linux native AIO
2021-03-24T22:56:14.563194Z 0 [Note] InnoDB: Number of pools: 1
2021-03-24T22:56:14.564174Z 0 [Note] InnoDB: Using CPU crc32 instructions
2021-03-24T22:56:14.572809Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-24T22:56:14.616520Z 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-24T22:56:14.628758Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-24T22:56:14.651923Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-24T22:56:14.657002Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 79684856617
2021-03-24T22:56:15.104425Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79690099200
2021-03-24T22:56:15.338581Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 79693046038
2021-03-24T22:56:15.343192Z 0 [Note] InnoDB: Database was not shutdown normally!
2021-03-24T22:56:15.343242Z 0 [Note] InnoDB: Starting crash recovery.
2021-03-24T22:56:15.475486Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 22:56:15 UTC - mysqld got signal 11 ;
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 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...
1 2