Beiträge von Dennis Friebe

• Moin moin

Wie oben bereits erwähnt suche ich einen entpacker.
ebenso suche ich jemand der mir zeigt wie ich einen dumper erstellen kann vielen Dank schonmal im voraus

ps so das ich aus item proto dump eine txt machen kann

Zitat von Fliegex3

Check es nicht mit "Service mysql-server status" sondern über "top", die Statusabfrage von Mysql funktioniert nicht richtig, wenn bei top was mit mysql/mysqld steht dann läuft dein mysql.

ja mysql läuft

Zitat von Therulas

[/tabmenu][tabmenu]err. datei was sagt die?

und 2te frage zur Sicherheit wv GB Ram hat dein Root?

8Gb die files waren schon auf den root server habe in nur nochmal resetet

DB
[tabmenu]
SYSERR: May 17 20:11:15 :: pid_init:
Start of pid: 1609
SYSERR: May 17 20:11:15 :: Start: TABLE_POSTFIX not configured use default
SYSERR: May 17 20:11:15 :: pid_init:
Start of pid: 1621
SYSERR: May 17 20:11:15 :: Start: TABLE_POSTFIX not configured use default
[/tabmenu]

aus var/db/mysql

[tabmenu]
2017-05-17 20:12:58 2597 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:12:58 2597 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:12:58 2597 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:12:58 2597 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:12:58 2597 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:12:58 2597 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:12:58 2597 [Note] IPv6 is available.
2017-05-17 20:12:58 2597 [Note] - '::' resolves to '::';
2017-05-17 20:12:58 2597 [Note] Server socket created on IP: '::'.
18:12:58 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:12:58 mysqld_safe mysqld restarted
2017-05-17 20:12:59 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:12:59 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2615 ...
2017-05-17 20:12:59 2615 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:12:59 2615 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:12:59 2615 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:12:59 2615 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:12:59 2615 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:12:59 2615 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:12:59 2615 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:12:59 2615 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:12:59 2615 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:12:59 2615 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:12:59 2615 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:12:59 2615 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:12:59 2615 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:12:59 2615 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:12:59 2615 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:12:59 2615 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:12:59 2615 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:00 2615 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:00 2615 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:00 2615 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:00 2615 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:00 2615 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:00 2615 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:00 2615 [Note] IPv6 is available.
2017-05-17 20:13:00 2615 [Note] - '::' resolves to '::';
2017-05-17 20:13:00 2615 [Note] Server socket created on IP: '::'.
18:13:00 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:00 mysqld_safe mysqld restarted
2017-05-17 20:13:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:00 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2625 ...
2017-05-17 20:13:00 2625 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:00 2625 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:00 2625 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:00 2625 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:00 2625 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:00 2625 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:00 2625 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:00 2625 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:00 2625 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:00 2625 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:00 2625 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:00 2625 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:00 2625 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:00 2625 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:00 2625 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:00 2625 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:01 2625 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:01 2625 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:01 2625 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:01 2625 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:01 2625 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:01 2625 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:01 2625 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:01 2625 [Note] IPv6 is available.
2017-05-17 20:13:01 2625 [Note] - '::' resolves to '::';
2017-05-17 20:13:01 2625 [Note] Server socket created on IP: '::'.
18:13:01 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:01 mysqld_safe mysqld restarted
2017-05-17 20:13:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:02 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2642 ...
2017-05-17 20:13:02 2642 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:02 2642 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:02 2642 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:02 2642 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:02 2642 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:02 2642 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:02 2642 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:02 2642 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:02 2642 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:02 2642 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:02 2642 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:02 2642 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:02 2642 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:02 2642 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:02 2642 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:02 2642 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:02 2642 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:03 2642 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:03 2642 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:03 2642 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:03 2642 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:03 2642 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:03 2642 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:03 2642 [Note] IPv6 is available.
2017-05-17 20:13:03 2642 [Note] - '::' resolves to '::';
2017-05-17 20:13:03 2642 [Note] Server socket created on IP: '::'.
18:13:03 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:03 mysqld_safe mysqld restarted
2017-05-17 20:13:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:03 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2653 ...
2017-05-17 20:13:03 2653 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:03 2653 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:03 2653 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:03 2653 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:03 2653 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:03 2653 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:03 2653 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:03 2653 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:03 2653 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:03 2653 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:03 2653 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:03 2653 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:03 2653 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:03 2653 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:03 2653 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:03 2653 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:03 2653 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:04 2653 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:04 2653 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:04 2653 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:04 2653 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:04 2653 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:04 2653 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:04 2653 [Note] IPv6 is available.
2017-05-17 20:13:04 2653 [Note] - '::' resolves to '::';
2017-05-17 20:13:04 2653 [Note] Server socket created on IP: '::'.
18:13:04 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:04 mysqld_safe mysqld restarted
2017-05-17 20:13:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:05 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2669 ...
2017-05-17 20:13:05 2669 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:05 2669 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:05 2669 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:05 2669 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:05 2669 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:05 2669 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:05 2669 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:05 2669 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:05 2669 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:05 2669 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:05 2669 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:05 2669 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:05 2669 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:05 2669 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:05 2669 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:05 2669 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:05 2669 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:05 2669 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:05 2669 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:05 2669 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:05 2669 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:05 2669 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:05 2669 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:05 2669 [Note] IPv6 is available.
2017-05-17 20:13:05 2669 [Note] - '::' resolves to '::';
2017-05-17 20:13:05 2669 [Note] Server socket created on IP: '::'.
18:13:05 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:06 mysqld_safe mysqld restarted
2017-05-17 20:13:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:06 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2684 ...
2017-05-17 20:13:06 2684 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:06 2684 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:06 2684 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:06 2684 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:06 2684 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:06 2684 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:06 2684 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:06 2684 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:06 2684 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:06 2684 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:06 2684 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:06 2684 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:06 2684 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:06 2684 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:06 2684 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:06 2684 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:06 2684 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:07 2684 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:07 2684 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:07 2684 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:07 2684 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:07 2684 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:07 2684 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:07 2684 [Note] IPv6 is available.
2017-05-17 20:13:07 2684 [Note] - '::' resolves to '::';
2017-05-17 20:13:07 2684 [Note] Server socket created on IP: '::'.
18:13:07 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:07 mysqld_safe mysqld restarted
2017-05-17 20:13:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-05-17 20:13:07 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.35) starting as process 2694 ...
2017-05-17 20:13:07 2694 [Note] Plugin 'FEDERATED' is disabled.
2017-05-17 20:13:07 2694 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-05-17 20:13:07 2694 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-17 20:13:07 2694 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-17 20:13:07 2694 [Note] InnoDB: Memory barrier is not used
2017-05-17 20:13:07 2694 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-17 20:13:07 2694 [Note] InnoDB: Using CPU crc32 instructions
2017-05-17 20:13:07 2694 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-05-17 20:13:08 2694 [Note] InnoDB: Completed initialization of buffer pool
2017-05-17 20:13:08 2694 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-17 20:13:08 2694 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2017-05-17 20:13:08 2694 [Note] InnoDB: Database was not shutdown normally!
2017-05-17 20:13:08 2694 [Note] InnoDB: Starting crash recovery.
2017-05-17 20:13:08 2694 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-05-17 20:13:08 2694 [Note] InnoDB: Restoring possible half-written data pages
2017-05-17 20:13:08 2694 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2017-05-17 20:13:08 2694 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-05-17 20:13:08 2694 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-17 20:13:08 2694 [Note] InnoDB: Waiting for purge to start
2017-05-17 20:13:08 2694 [Note] InnoDB: 5.6.35 started; log sequence number 1600607
2017-05-17 20:13:08 2694 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:08 2694 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2017-05-17 20:13:08 2694 [Note] Server hostname (bind-address): '*'; port: 3306
2017-05-17 20:13:08 2694 [Note] IPv6 is available.
2017-05-17 20:13:08 2694 [Note] - '::' resolves to '::';
2017-05-17 20:13:08 2694 [Note] Server socket created on IP: '::'.
18:13:08 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.
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=8388608
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 = 68057 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x827bfc000
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 = 7fffffffdd58 thread_stack 0x40000
0x87c4b7 <my_print_stacktrace+0x27> at /usr/local/libexec/mysqld
0x63081e <handle_fatal_signal+0x27e> at /usr/local/libexec/mysqld
0x8028c4b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
0x8028c422c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
The manual page at Bitte melden Sie sich an, um diesen Link zu sehen. contains
information that should help you find out what is causing the crash.
170517 20:13:08 mysqld_safe mysqld restarted
[/tabmenu]

Zitat von Fliegex3

Lösch die Dateien aus /var/db/mysql raus sodass nurnoch die Ordner mit inhalt vorhanden sind, dann versuch den Mysql zu starten mit "Service mysql-server start".

leider ohne erfolg

root@root599738:~ # service mysql-server start
Starting mysql.
root@root599738:~ # service mysql-server status
mysql is not running.
root@root599738:~ #

root@root599738:/usr/game # mysql_real_connect: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

habe es mit service mysql-server restart versucht leider ohne erfolg mysql startet einfach nicht jemand eine Idee?

Zitat von Nero

Gib der Spalte "npsistem" den Default wert 1.

vielen dank

das ist die Fehlermeldung aus der DB

nope da hatte ich schon geschaut ist keine vorhanden nur die db´s
und .pid datein

Syserr ch1 leer
Client leer

und wo ist die von mysql?

Guten abend ihr lieben!

Ich bin so langsam an verzweifeln ..
Ich kann keinen neuen Char erstellen was habe ich gemacht
Ich habe bereit rebootet
Die player player indes und bannwort gelöscht und nochmals rebootet.
Leider kann ich immer noch keinen char erstellen..

Es handelt sich hier um die Serverfiles von Bestpro v1.8

vllt habt ihr eine Idee?

gerne auch via skype erreichbar [email protected]

Vielen dan schonmal im vorraus