epgd und mariadb inkompatibel?

Maniac · 30. Juli 2014

Ich bin gerade dabei mir einen neuen VDR aufzusetzen. Als DB wollte ich mariadb anstatt mysql nutzen. Leider bekomme ich beim Start vom epgd immer einen Segfault.
Ich habe bereits versucht /srv/mysql zu löschen und es wieder über mysql_install_db neu erstellt. Ich habe versucht die Tabelle components (bei der er jedesmal auf den Fehler) läuft per Hand zu erstellen.

Hat jemand eine Idee woran dies liegen kann? Die .so für mysql von epgd wird an dieser Stelle ja auch nicht genutzt?

Code

15:43:41,972  create index idxscrseriesid on events(scrseriesid);
15:43:42,063  Statement 'select eventid, channelid, masterid, useid, source, fileref, inssp, updsp, updflg, delflg, tableid, version, title, comptitle, shorttext, compshorttext, longdescription, starttime, duration, parentalrating, vps, shortdescription, actor, audio, category, country, director, flags, genre, info, music, producer, screenplay, shortreview, tipp, topic, year, rating, fsk, movieid, moderator, other, guest, camera, extepnum, imagecount, episode, episodepart, episodelang, scrseriesid, scrseriesepisode, scrmovieid, scrsp from events where eventid = ? and channelid = ?;' with (2) in parameters and (53) out bindings prepared
15:43:42,063  Statement 'insert into events set eventid = ?, channelid = ?, useid = ?, source = ?, fileref = ?, inssp = ?, updsp = ?, updflg = ?, delflg = ?, tableid = ?, version = ?, title = ?, comptitle = ?, shorttext = ?, compshorttext = ?, longdescription = ?, starttime = ?, duration = ?, parentalrating = ?, vps = ?, shortdescription = ?, actor = ?, audio = ?, category = ?, country = ?, director = ?, flags = ?, genre = ?, info = ?, music = ?, producer = ?, screenplay = ?, shortreview = ?, tipp = ?, topic = ?, year = ?, rating = ?, fsk = ?, movieid = ?, moderator = ?, other = ?, guest = ?, camera = ?, extepnum = ?, imagecount = ?, episode = ?, episodepart = ?, episodelang = ?, scrseriesid = ?, scrseriesepisode = ?, scrmovieid = ?, scrsp = ?;' with (52) in parameters and (0) out bindings prepared
15:43:42,064  Statement 'update events set useid = ?, source = ?, fileref = ?, updsp = ?, updflg = ?, delflg = ?, tableid = ?, version = ?, title = ?, comptitle = ?, shorttext = ?, compshorttext = ?, longdescription = ?, starttime = ?, duration = ?, parentalrating = ?, vps = ?, shortdescription = ?, actor = ?, audio = ?, category = ?, country = ?, director = ?, flags = ?, genre = ?, info = ?, music = ?, producer = ?, screenplay = ?, shortreview = ?, tipp = ?, topic = ?, year = ?, rating = ?, fsk = ?, movieid = ?, moderator = ?, other = ?, guest = ?, camera = ?, extepnum = ?, imagecount = ?, episode = ?, episodepart = ?, episodelang = ?, scrseriesid = ?, scrseriesepisode = ?, scrmovieid = ?, scrsp = ? where eventid = ? and channelid = ?;' with (51) in parameters and (0) out bindings prepared
15:43:42,064  Initialy creating table 'components'
15:43:42,064  create table components(eventid INT(11) unsigned, channelid VARCHAR(50), stream INT(3), type INT(3), lang VARCHAR(8), description VARCHAR(100), inssp INT(11), updsp INT(11), PRIMARY KEY(eventid DESC, channelid DESC, stream DESC, type DESC, lang DESC, description DESC)) ENGINE InnoDB;
15:43:42,225  SQL-Error in 'create table components(eventid INT(11) unsigned, channelid VARCHAR(50), stream INT(3), type INT(3), lang VARCHAR(8), description VARCHAR(100), inssp INT(11), updsp INT(11), PRIMARY KEY(eventid DESC, channelid DESC, stream DESC, type DESC, lang DESC, description DESC)) ENGINE InnoDB;' - Lost connection to MySQL server during query (2013) 
15:43:42,225  Fatal, lost connection to mysql server, aborting pending actions
15:43:42,225  SQL-Error in 'createTable()' - Lost connection to MySQL server during query (2013) '' [create table components(eventid INT(11) unsigned, channelid VARCHAR(50), stream INT(3), type INT(3), lang VARCHAR(8), description VARCHAR(100), inssp INT(11), updsp INT(11), PRIMARY KEY(eventid DESC, channelid DESC, stream DESC, type DESC, lang DESC, description DESC)) ENGINE InnoDB;]
15:43:42,225  Fatal, lost connection to mysql server, aborting pending actions
Segmentation fault (core dumped)

Alles anzeigen

louis · 30. Juli 2014

Wie wäre es wenn du einfach das benutzt, was der Entwickler vorgesehen hat? Alternativ solltest du das ganze so weit verstehen, dass du das Problem selbst lösen kannst.

Ciao Louis

Maniac · 30. Juli 2014

mariadb ist mehr oder weniger mysql. Einige Distris stellen da mittlerweile um, CentOS7 liefert zum Beispiel mariadb anstatt mysql.

Mein Problem scheint nach weiteren Tests nicht unbedingt etwas mit dem epgd sondern irgendwas in mariadb zu tun zu haben.

kerberos187 · 30. Juli 2014

Bei mir gehts:

Code

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 42
Server version: 10.0.12-MariaDB-1~trusty-log mariadb.org binary distribution


Copyright (c) 2000, 2014, Oracle, SkySQL Ab and others.


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.


MariaDB [(none)]> use xxx;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A


Database changed
MariaDB [xxx]> create table components(eventid INT(11) unsigned, channelid VARCHAR(50), stream INT(3), type INT(3), lang VARCHAR(8), description VARCHAR(100), inssp INT(11), updsp INT(11), PRIMARY KEY(eventid DESC, channelid DESC, stream DESC, type DESC, lang DESC, description DESC)) ENGINE InnoDB;
Query OK, 0 rows affected (0.57 sec)                                                                                                                                                                                                                                           

MariaDB [xxx]>

Alles anzeigen

Maniac · 30. Juli 2014

Da scheint es Probleme mit mariadb und inno zu geben, ich habe in den sourcen vom epgd auf myisam umgestellt, jetzt funktioniert es.

Bei den inno Tabellen konnte ich die Fehlermeldung auf frühere Tabellen vorziehen, wenn ich vorher manuell Dummy Tabellen angelegt hab

louis · 31. Juli 2014

Moin,

hm, ob das so gut ist...MyIsam unterstützt im Gegensatz zu InnoDB keine Transaktionen, die werden im epgd aber recht intensiv genutzt. Bist du sicher dass das alles so wirklich korrekt funktioniert? Vielleicht hat Horchi das in seiner DB Klasse berücksichtigt, vielleicht sagt er mal direkt was dazu.

Ciao Louis

CKone · 31. Juli 2014

Bitte man mit Alexander besprechen, der hat das meine ich mot Maria und Inno am rennen

Christian

seahawk1986 · 31. Juli 2014

Ich weiß nicht, was ich da groß dazu sagen soll - ich nutze MariaDB 10.0.12 unter Arch Linux ARM mit InnoDB auf einem Cubietruck.
Die Tabellen habe ich von Hand nach der Anleitung in der README eingerichtet, die Konfiguration sieht so aus und läuft unauffällig: http://pastebin.com/p1Gqb8gU
Hast du epgd gegen die passende libmariadbclient gebaut?

Da er laut Fehlermeldung die Verbindung zum Server verliert, würde ich mal in die Logs des Server schauen, was der zu dem Zeitpunkt gemacht hat.

Maniac · 5. August 2014

Bis jetzt funktioniert es alles mit myIsam, habe aber noch nicht wirklich viel eingerichtet.

Ja, der sql Server stirbt und startet sich neu, genauere Logmeldungen werde ich am Wochenende nochmal generieren indem ich wieder auf inno umstelle. Ich vermute den Fehler mittlerweile auch irgendwo auf MariaDB Seite.

Datenbank und User hatte ich nach Anleitung im Wiki auf vdr-developer erstellt. Die Tabellen wollte epgd dann beim ersten Start erstellen.

Maniac · 8. August 2014

Ich hab es jetzt nochmal auf InnoDB umgestellt und mit einem leeren /srv/mysql gestartet was ich vorher über mysql_install_db neu erstellt hab.

Log nachdem Crash von MariaDB

Code

140808 15:19:24 [ERROR] 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.


To report this bug, see http://kb.askmonty.org/en/reporting-bugs


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.


Server version: 10.0.12-MariaDB
key_buffer_size=167772160
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 968834 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thread pointer: 0x0x8bff7008
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 = 0xb706e2fc thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x24)[0x877be44]
/usr/sbin/mysqld(handle_fatal_signal+0x39a)[0x833a44a]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb76f4a68]
:0(btr_cur_optimistic_insert(unsigned long, btr_cur_t*, unsigned long**, mem_block_info_t**, dtuple_t*, unsigned char**, big_rec_t**, unsigned long, que_thr_t*, mtr_t*))[0x860fdf4]
:0(btr_insert_on_non_leaf_level_func(unsigned long, dict_index_t*, unsigned long, dtuple_t*, char const*, unsigned long, mtr_t*))[0x86042c3]
:0(btr_page_split_and_insert(unsigned long, btr_cur_t*, unsigned long**, mem_block_info_t**, dtuple_t const*, unsigned long, mtr_t*))[0x86047ac]
:0(btr_root_raise_and_insert(unsigned long, btr_cur_t*, unsigned long**, mem_block_info_t**, dtuple_t const*, unsigned long, mtr_t*))[0x8606a57]
:0(btr_cur_pessimistic_insert(unsigned long, btr_cur_t*, unsigned long**, mem_block_info_t**, dtuple_t*, unsigned char**, big_rec_t**, unsigned long, que_thr_t*, mtr_t*))[0x8610aa1]
:0(row_ins_clust_index_entry_low(unsigned long, unsigned long, dict_index_t*, unsigned long, dtuple_t*, unsigned long, que_thr_t*))[0x859ea20]
:0(row_ins_clust_index_entry(dict_index_t*, dtuple_t*, que_thr_t*, unsigned long))[0x859ef18]
:0(row_ins_step(que_thr_t*))[0x859f478]
:0(que_run_threads(que_thr_t*))[0x8589909]
:0(que_eval_sql(pars_info_t*, char const*, unsigned long, trx_t*))[0x8589efd]
dict0stats.cc:0(dict_stats_save_index_stat(dict_index_t*, long, char const*, unsigned long long, unsigned long long*, char const*, trx_t*))[0x86633ea]
dict0stats.cc:0(dict_stats_save(dict_table_t*, unsigned long long const*))[0x8667833]
:0(dict_stats_update(dict_table_t*, dict_stats_upd_option_t))[0x8668110]
:0(ha_innobase::create(char const*, TABLE*, HA_CREATE_INFO*))[0x851e2b8]
/usr/sbin/mysqld(_ZN7handler9ha_createEPKcP5TABLEP14HA_CREATE_INFO+0x63)[0x8341dd3]
/usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P14HA_CREATE_INFOP34st_mysql_const_unsigned_lex_string+0x1f1)[0x83427b1]
/usr/sbin/mysqld(_Z16rea_create_tableP3THDP34st_mysql_const_unsigned_lex_stringPKcS4_S4_P14HA_CREATE_INFOP7handlerb+0xa5)[0x828b595]
/usr/sbin/mysqld(_Z26mysql_create_table_no_lockP3THDPKcS2_P14HA_CREATE_INFOP10Alter_infoPbi+0x1f1)[0x825d601]
/usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP14HA_CREATE_INFOP10Alter_info+0xdc)[0x825e01c]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x672e)[0x81e13ae]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x23d)[0x81e164d]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1588)[0x81e3178]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xd4)[0x81e3b44]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1f8)[0x82a2698]
/usr/sbin/mysqld(handle_one_connection+0x31)[0x82a2751]
/lib/libpthread.so.0(+0x602f)[0xb76d102f]
/lib/libc.so.6(clone+0x5e)[0xb71a39ee]


Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xb583c018): create table components(eventid INT(11) unsigned, channelid VARCHAR(50), stream INT(3), type INT(3), lang VARCHAR(8), description VARCHAR(100), inssp INT(11), updsp INT(11), PRIMARY KEY(eventid DESC, channelid DESC, stream DESC, type DESC, lang DESC, description DESC)) ENGINE InnoDB
Connection ID (thread ID): 3
Status: NOT_KILLED


Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on


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.
140808 15:19:24 mysqld_safe Number of processes running now: 0
140808 15:19:24 mysqld_safe mysqld restarted
140808 15:19:24 [Note] InnoDB: Using mutexes to ref count buffer pool pages
140808 15:19:24 [Note] InnoDB: The InnoDB memory heap is disabled
140808 15:19:24 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140808 15:19:24 [Note] InnoDB: Compressed tables use zlib 1.2.8
140808 15:19:24 [Note] InnoDB: Not using CPU crc32 instructions
140808 15:19:24 [Note] InnoDB: Initializing buffer pool, size = 160.0M
140808 15:19:24 [Note] InnoDB: Completed initialization of buffer pool
140808 15:19:24 [Note] InnoDB: Highest supported file format is Barracuda.
140808 15:19:24 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2030654
140808 15:19:24 [Note] InnoDB: Database was not shutdown normally!
140808 15:19:24 [Note] InnoDB: Starting crash recovery.
140808 15:19:24 [Note] InnoDB: Reading tablespace information from the .ibd files...
140808 15:19:24 [Note] InnoDB: Restoring possible half-written data pages
140808 15:19:24 [Note] InnoDB: from the doublewrite buffer...

Alles anzeigen

my.cnf

Code

# Begin /etc/mysql/my.cnf
# The following options will be passed to all MySQL clients
[client]
#password       = your_password
port            = 3306
socket          = /run/mysqld/mysqld.sock
# The MySQL server
[mysqld]
port            = 3306
socket          = /run/mysqld/mysqld.sock
datadir         = /srv/mysql
skip-external-locking
key_buffer_size = 160M
max_allowed_packet = 10M
sort_buffer_size = 5120K
net_buffer_length = 160K
myisam_sort_buffer_size = 80M
# Don't listen on a TCP/IP port at all.
#skip-networking
# required unique id between 1 and 2^32 - 1
server-id       = 1
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /srv/mysql
innodb_data_file_path = ibdata1:100M:autoextend
innodb_log_group_home_dir = /srv/mysql
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 160M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 50M
innodb_log_buffer_size = 80M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 500
innodb_corrupt_table_action = assert
[mysqldump]
quick
max_allowed_packet = 16M
[code=sql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
# End /etc/mysql/my.cnf

Alles anzeigen

Edit: Gerade hab ich mir mal die aktuelle Dev 10.1.0 von mariadb gebaut, Fehler bleibt gleich.
Erstelle ich vorher die Tabelle components in einer neu angelegten epg2vdr DB kracht es schon vorher:

Code

16:15:35,171  create index idxsourceupdsp on events(source, updsp);
16:15:35,270  SQL-Error in 'create index idxsourceupdsp on events(source, updsp);' - Lost connection to MySQL server during query (2013) 
16:15:35,270  Fatal, lost connection to mysql server, aborting pending actions
16:15:35,270  SQL-Error in 'createIndices()' - Lost connection to MySQL server during query (2013) '' [create index idxsourceupdsp on events(source, updsp);]
16:15:35,270  Fatal, lost connection to mysql server, aborting pending actions
Segmentation fault (core dumped)

Maniac · 3. September 2014

Ich habe es nun auch mit innodb laufen. Eine richtige Lösung ist es zwar nicht, aber es scheint an xtradb zu liegen was mariadb für innodb nutzt.

Es ist aber möglich das xtradb plugin zu deaktivieren und wieder das ursprüngliche innodb zu nutzen, damit läuft epgd dann auch sauber.

Dazu einfach in der config folgendes einfügen:

Code

[mysqld]
ignore_builtin_innodb
plugin_load=innodb=ha_innodb.so
# The following should not be needed if you are using a mariadb package:
plugin_dir=/usr/local/mysql/lib/mysql/plugin

CKone · 4. September 2014

Prima.

wenn du ein Diff mit einer kleinen Erklärung auf das Readme machst fügen wir es gerne zu.

Christian

epgd und mariadb inkompatibel?

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema