Dump kann nicht mehr erstellt werden

Hilfe zu OTRS Problemen aller Art
Post Reply
ronnybaer
Znuny newbie
Posts: 8
Joined: 27 Feb 2013, 10:52
Znuny Version: 4.0.13
Real Name: Ronny Baer
Company: OPM IT Service GmbH

Dump kann nicht mehr erstellt werden

Post by ronnybaer »

Liebe OTRS Community,

ich habe seit ein paar Wochen das Problem bei unserem Server, dass ich kein Backup des OTRS mehr erstellen kann. Das mitgelieferte Backupscript endet immer mit der folgenden Fehlermeldung:

Code: Select all

mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `article_plain` at row: 58762
Auch wenn ich versuche "manuel" ein Dump der Datenbank zu erstellen, kommt die selbe Fehlermeldung.

Die Datei "my.cnf" habe ich auch schon entsprechend angepasst, sodass Timeout Fehler eigentlich ausgeschlossen werden können. Der Inhalt meiner my.cnf sieht wiefolgt aus:

Code: Select all

[mysqld]
max_allowed_packet   = 1G
query_cache_size     = 32M
innodb_log_file_size = 256M
net_read_timeout     = 7200
net_write_timeout    = 7200
innodb_buffer_pool_size = 100M


[mysqldump]
max_allowed_packet   = 1G
Die Fehlermeldung erscheint auch, wenn ich ein Update auf die aktuellste Version durchführen möchte.

Jetzt stehe ich natürlich vor dem Problem, dass ich a) kein Backup erstellen kann und b) nicht updaten kann.

Hat vielleicht irgendeiner von Euch eine Idee was ich da noch machen kann? <br/>

Danke im Voraus
Ronny
OTRS 5.0.22
Ubuntu 16.04.5 LTS
Apache2/MySQL
root
Administrator
Posts: 3931
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Dump kann nicht mehr erstellt werden

Post by root »

Hi,

Evtl. steht ja im MySQL log drin warum die Verbindung beendet wurde.Evtl. auch mal prüfen ob RAM oder Platte voll sind (beim Erstellen des Dumps)

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
ronnybaer
Znuny newbie
Posts: 8
Joined: 27 Feb 2013, 10:52
Znuny Version: 4.0.13
Real Name: Ronny Baer
Company: OPM IT Service GmbH

Re: Dump kann nicht mehr erstellt werden

Post by ronnybaer »

Hallo Roy,

erstmal Danke für Deine Antwort.

Ich kann allerdings keine Engpässe bei den Ressourcen (RAM/HDD) sehen.

Arbeitsspeicher (free -m)

Code: Select all

              gesamt       benutzt     frei      gemns.  Puffer/Cache verfügbar
Speicher:        3918        1267          37           5        2613        2566
Auslagerungsspeicher:        2043         124        1919
HDD (df -h)

Code: Select all

udev                                  1,9G       0  1,9G    0% /dev
tmpfs                                 392M    5,6M  387M    2% /run
/dev/sda2                             195G     15G  170G    8% /
tmpfs                                 2,0G       0  2,0G    0% /dev/shm
tmpfs                                 5,0M       0  5,0M    0% /run/lock
tmpfs                                 2,0G       0  2,0G    0% /sys/fs/cgroup
/dev/sda1                             511M    3,4M  508M    1% /boot/efi
//terranas.opmgmbh.local/Backup_OTRS  1,8T    1,8T   68G   97% /mnt/backup_otrs
tmpfs                                 392M       0  392M    0% /run/user/1000
Die beiden Befehle wurden jeweils wärend das Dump erstellt wurde ausgeführt.

Das mysql error.log spuckt wenn der Fehler auftritt das folgende aus:

Code: Select all

2018-10-18 13:58:24 0x7f710c121700  InnoDB: Assertion failure in thread 140123510544128 in file btr0cur.cc line 7218
InnoDB: Failing assertion: space_id == page_get_space_id(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:58:24 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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=11
max_threads=151
thread_count=11
connection_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x42c5630
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 = 7f710c120e70 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe93d5b]
/usr/sbin/mysqld(handle_fatal_signal+0x489)[0x78ab29]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f712823a390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f71275f3428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f71275f502a]
/usr/sbin/mysqld[0x7603f0]
/usr/sbin/mysqld[0x1136c50]
/usr/sbin/mysqld[0x1145133]
/usr/sbin/mysqld(_Z32btr_copy_externally_stored_fieldPmPKhRK11page_size_tmP16mem_block_info_t+0xd0)[0x1145490]
/usr/sbin/mysqld[0x108a93e]
/usr/sbin/mysqld[0x10900df]
/usr/sbin/mysqld(_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm+0x26d4)[0x10938d4]
/usr/sbin/mysqld(_ZN11ha_innobase13general_fetchEPhjj+0x6a)[0xf7fb5a]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0xfc)[0x7da6ac]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x35)[0xbb4615]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x13e)[0xc251fe]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x3c8)[0xc1df18]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x233)[0xc8fa53]
/usr/sbin/mysqld[0x753f3b]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x465b)[0xc5170b]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3ad)[0xc53dbd]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x102a)[0xc54efa]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1c7)[0xc563b7]
/usr/sbin/mysqld(handle_connection+0x288)[0xd18718]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeb3504]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f71282306ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f71276c541d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (42dd5e0): SELECT /*!40001 SQL_NO_CACHE */ * FROM `article_plain`
Connection ID (thread ID): 22
Status: NOT_KILLED

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.
2018-10-18T11:58:24.878676Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2018-10-18T11:58:24.879293Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2018-10-18T11:58:25.043781Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-10-18T11:58:25.048464Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23-0ubuntu0.16.04.1) starting as process 2065 ...
2018-10-18T11:58:25.060828Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-10-18T11:58:25.060902Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-18T11:58:25.060939Z 0 [Note] InnoDB: Uses event mutexes
2018-10-18T11:58:25.060981Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-10-18T11:58:25.061008Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-10-18T11:58:25.061050Z 0 [Note] InnoDB: Using Linux native AIO
2018-10-18T11:58:25.061425Z 0 [Note] InnoDB: Number of pools: 1
2018-10-18T11:58:25.061839Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-10-18T11:58:25.064756Z 0 [Note] InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
2018-10-18T11:58:25.073007Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-10-18T11:58:25.075181Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-10-18T11:58:25.091047Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-18T11:58:25.094650Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7676823644
2018-10-18T11:58:25.094732Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7676823653
2018-10-18T11:58:25.094779Z 0 [Note] InnoDB: Database was not shutdown normally!
2018-10-18T11:58:25.094850Z 0 [Note] InnoDB: Starting crash recovery.
2018-10-18T11:58:25.324747Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-10-18T11:58:25.324850Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-10-18T11:58:25.324939Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-10-18T11:58:25.344224Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-10-18T11:58:25.345278Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-10-18T11:58:25.345336Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-10-18T11:58:25.346560Z 0 [Note] InnoDB: 5.7.23 started; log sequence number 7676823653
2018-10-18T11:58:25.347373Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-10-18T11:58:25.353839Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-10-18T11:58:25.369140Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2018-10-18T11:58:25.369331Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2018-10-18T11:58:25.369406Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2018-10-18T11:58:25.369553Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2018-10-18T11:58:25.399087Z 0 [Note] InnoDB: Buffer pool(s) load completed at 181018 13:58:25
2018-10-18T11:58:25.426772Z 0 [Note] Event Scheduler: Loaded 0 events
2018-10-18T11:58:25.427148Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.23-0ubuntu0.16.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
Kann damit ggf. jemand was anfangen? Ich bin über jede Hilfestellung dankbar.


Grüße
Ronny
OTRS 5.0.22
Ubuntu 16.04.5 LTS
Apache2/MySQL
Post Reply