Dave-Kay

sorry, i don't get that. is there a manual to do it, like you intend it to be done? the "openhabian-way" doesn't work the runtime update says i am already on 2.5.0 even if i tell him to update to 2.5.11 and with apt i am getting nowhere

So, how is it possible to update it to 2.5.x?

Ok, so after a while igot it back. Root password found and this one did the trick, to get connection to the DB again https://stackoverflow.com/questions/49992868/mysql-errorthe-user-specified-as-a-definer-mysql-infoschemalocalhost-doe Thx a lot for your help!

also is it in any way possible to take that appdata backup, set up a new docker with mysql and restore databases from appdata? And last question how do i set the password for root while installing a new docker? or what is standard pw? i don't remeber what was going on, when i did it the frist time.

so the was to do it would be, stop mysql docker, delete mysql appdate, restore the old data and fire it up again? else, when i try to access from docker console an put in mysql -u root it tells me ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) is it in any way possible to get root account to work (again)?

it's a pretty fuckup around here... the user i connected with is now reported to be not able to login at V8. it sais "he's a definer" and i lost root-pw and i tried mysql -p root but that gives back an error that root is not allowed to do that... so i don't need much, but there are 2 databases i would like to save. there should be an older backup of appdata, around 3 weeks ago... is it possible to just overwrite appdata in the folder mysql and everything will be restored from a few weeks ago? Kodi Alpha 18 is not connecting to the database anymore. I'm quite sure it started with upgrade to V8

going back to V8 works btw. the container starts immediately. it seems that V8 made a change, which needs to be reverted manually?

docker logs mysql 2018-06-24T14:49:35.857053Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2018-06-24T14:49:35.859380Z 0 [Note] mysqld (mysqld 5.7.22) starting as process 1 ... 2018-06-24T14:49:35.866733Z 0 [Note] InnoDB: PUNCH HOLE support available 2018-06-24T14:49:35.866771Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-06-24T14:49:35.866783Z 0 [Note] InnoDB: Uses event mutexes 2018-06-24T14:49:35.866794Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2018-06-24T14:49:35.866805Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-06-24T14:49:35.866817Z 0 [Note] InnoDB: Using Linux native AIO 2018-06-24T14:49:35.867388Z 0 [Note] InnoDB: Number of pools: 1 2018-06-24T14:49:35.868236Z 0 [Note] InnoDB: Using CPU crc32 instructions 2018-06-24T14:49:35.871443Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2018-06-24T14:49:35.893420Z 0 [Note] InnoDB: Completed initialization of buffer pool 2018-06-24T14:49:35.897308Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-06-24T14:49:35.914911Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000! 2018-06-24 16:49:35 0x1482ac8ef740 InnoDB: Assertion failure in thread 22551473354560 in file ut0ut.cc line 942 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. 14:49:35 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=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 = 68195 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 mysqld(my_print_stacktrace+0x2c)[0x55fbef4f11ec] mysqld(handle_fatal_signal+0x479)[0x55fbeee1fe59] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x1482ac4cd0c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x1482aac59fff] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x1482aac5b42a] mysqld(+0x628387)[0x55fbeedf6387] mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55fbef6bfc8d] mysqld(+0xf9ead1)[0x55fbef76cad1] mysqld(+0xf9f108)[0x55fbef76d108] mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x55fbef776230] mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55fbef72b1ee] mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55fbef6fa34a] mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55fbef69de23] mysqld(+0x6274fb)[0x55fbeedf54fb] mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55fbef66acdd] mysqld(+0xd69f63)[0x55fbef537f63] mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55fbeee6abff] mysqld(+0xb138e6)[0x55fbef2e18e6] mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55fbef2e4ad0] mysqld(+0x64a566)[0x55fbeee18566] mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55fbeee1a121] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x1482aac472e1] mysqld(_start+0x2a)[0x55fbeee1080a] 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-06-24T14:49:45.387944Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2018-06-24T14:49:45.391051Z 0 [Note] mysqld (mysqld 5.7.22) starting as process 1 ... 2018-06-24T14:49:45.398206Z 0 [Note] InnoDB: PUNCH HOLE support available 2018-06-24T14:49:45.398247Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-06-24T14:49:45.398259Z 0 [Note] InnoDB: Uses event mutexes 2018-06-24T14:49:45.398270Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2018-06-24T14:49:45.398286Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-06-24T14:49:45.398296Z 0 [Note] InnoDB: Using Linux native AIO 2018-06-24T14:49:45.398867Z 0 [Note] InnoDB: Number of pools: 1 2018-06-24T14:49:45.399062Z 0 [Note] InnoDB: Using CPU crc32 instructions 2018-06-24T14:49:45.402126Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2018-06-24T14:49:45.423700Z 0 [Note] InnoDB: Completed initialization of buffer pool 2018-06-24T14:49:45.427567Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2018-06-24T14:49:45.440538Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000! 2018-06-24 16:49:45 0x1480c3218740 InnoDB: Assertion failure in thread 22543262123840 in file ut0ut.cc line 942 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. 14:49:45 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=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 = 68195 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 mysqld(my_print_stacktrace+0x2c)[0x55760de621ec] mysqld(handle_fatal_signal+0x479)[0x55760d790e59] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x1480c2df60c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x1480c1582fff] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x1480c158442a] mysqld(+0x628387)[0x55760d767387] mysqld(_ZN2ib5fatalD1Ev+0x12d)[0x55760e030c8d] mysqld(+0xf9ead1)[0x55760e0ddad1] mysqld(+0xf9f108)[0x55760e0de108] mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x2b0)[0x55760e0e7230] mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xce)[0x55760e09c1ee] mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4aa)[0x55760e06b34a] mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x143)[0x55760e00ee23] mysqld(+0x6274fb)[0x55760d7664fb] mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2f3d)[0x55760dfdbcdd] mysqld(+0xd69f63)[0x55760dea8f63] mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x55760d7dbbff] mysqld(+0xb138e6)[0x55760dc528e6] mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x2f0)[0x55760dc55ad0] mysqld(+0x64a566)[0x55760d789566] mysqld(_Z11mysqld_mainiPPc+0xc71)[0x55760d78b121] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x1480c15702e1] mysqld(_start+0x2a)[0x55760d78180a] 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.

that won't work, since the container is unable to start it seems, the command returns "no such container" docker ps shows the other ones but not mysql oh, wait now it works

while that worked like a charm i'm now unable to start it message is

How is it possible to downgrade this docker to latest 5 Version? I'm having issues with mysql V8.

And if you still think it's too high, maybe this will help https://lime-technology.com/forum/index.php?topic=31967.msg364791#msg364791

yeah, i understood that very well and of course i didn't change just one fan, but all and it wasn't hard at all it's harder to find out, where to move the cables

Why would you feel for me? In fact, that was a simple quest and i found the thread you mentioned, too. Everything is really fine now, allthough i'm still figuring out how to place the actual hdds and the cables, just to improve it a little more. Again, Thank you

yeah! i think that solved it. Was there anything wrong with what i have done? From what i remeber it wouldn't even have been possible for me to change that in the webinterface? "Yes" was there by default. THX!

so there shouldn't be a reason that this files caused my problems?

yeah, I'm aware of that :-) But as your Post says deprecated switch to > method i used( http://lime-technology.com/forum/index.php?topic=47899.0 ) and of course there is Driver version 1.10 in your files, i assumed m,y method is the right one. I simpy don't get it atm, what's going on with your files and the plugin i used. anyway, my unraid is still in rebuild, so it will take anoter two or three hours, before i'm able to test the files in your post with Driver Version 1.10

correct file attached. i'll test your advice later on.(Array is in Rebuild atm) Can you explain, how your files are different, from the one, the plugin provides? will your files support my Technotrend-Stick? tvheadend.cfg

I'm on V6.1.9 Configfile attached (had to change name to config.txt because the board didn't let me upload without extension) i installed unRAID DVB(plugin) to get a nicer way to tvheadend and there i used 6.19 Openelec Driver Version 1.11 left side of tvheadend config: MEDIA tree: DETECTED DVB tuner: DETECTED Tvheadend login/password: ACCEPTED all green config.txt

What am i missing? This plugins causes trouble being stopped on my unraid if stopped manually it takes a few minutes and the website is going wild by showing me yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy etc. before my browser cuts it. a few minutes later it's stopped an d everythins is back to normal. if i forget to stop it and simply stop the array it has a similar effect and i need to shutdown the system with "powerdown" because rsyslogd and emhttp are going to eat the cpu to infinity while my syslog blows up simply writing "Jun 4 14:51:57 UNRAID emhttp: y" over and over and over again. i read the first post over and over, but i simply don't get it, where i am doing it wrong. Data directory is set to /mnt/cache/tvheadend

Thank you so much

Yes indeed it is, must have missed that, whilst installation as the fan, which is bothering me, is exactely this one and the server will be not easy accessable, once it's installed and up, any suggestions which fan to use instead? And, btw. many thanks for the quick answer anyway!

Sorry, but i seem to be lost in this thread i'm setting up an C2550 in a DS380 and i installed this plugin regarding my problem, that i think the rear-fan is making too much noise. But after configurig the fan-control the log tells me 2016-06-03 01:20:35 fan control config file updated, reloading settings. 2016-06-03 01:20:36 REAR_FAN1(80%):MB Temperature(41°C) while the fancontinues to be stuck at 1100RPM if there's anything in this thread considering this, if there's anything i missed, please just point me to it. i couldn't find it

Hello, how's this plan going? I'm currently switching to unraid and this plugin would be nice, because i would be able to drop my rpi2 which is running TVHeadend 4.2 Since 4.2 could possibly be breaking sonfiguration i assume, your next update will do so, too and i like to spare me the double configuration within a few days/weeks