August 22, 201411 yr I currently have several windows htpcs with xbmc, my "main" htpc has mysql. If I install MariaDB on my unraid box and move the mysql DB to it, and update my advancedsettings.xml to reflect the new location will it work the same as it does now? Do I need xbmc running on the unraid server, or just the MariaDB? I would like to be able to power off the old main xbmc htpc when not in use, and still be able to use the others with it off.
August 22, 201411 yr The move should work. Obviously take backups and try pointing to the unRAID MariaDB in advancedsettimgs without disabling your local MySQL just yet. You just need MariaDB for a central Db for all your devices. If you want a headless instance of xbmc to accept the sickbeard / sabnzbd notifications and update the library off all the devices, then install the xbmc headless docker as well.
August 22, 201411 yr Author OK, I'm not sure what I'm doing wrong. I installed the MariaDB docker container using the docker extension stopped the docker container and mysql service on pc copied mysql and preformance_schema folders from C:\Program Files\MySQL\MySQL Server 5.5\data to the maridb appdata folder edited advancedsettings.xml to the new ip now xbmc starts and acts like there is no video sources. I know the mysql database had a username and password, does all of that carry over with the database move? does MaridaDB require any configuration besides installing and copying the mysql database?
August 22, 201411 yr Author alright, I can connect to a fresh install or mariadb with mysql workbench and add users. after I copy my mysql data from my windows pc into the appdata folder I cannot connect and get not allowed to connect errors. I tried changing the host for the root and xbmc users to % before copying the data, but that didn't make any difference. I'm sure this is a simple security setting somewhere but I have no idea what else to try. any advice would be greatly appreciated.
August 22, 201411 yr When i dont this I just dumped the dbase to sql files and reimported them the old fashioned way. Didnt trust trying to move binary files.
August 22, 201411 yr Author Thanks NAS, I tired the .sql import with the same result, I had this in my log: [Warning] IP address '192.168.1.3' could not be resolved: Name or service not known I also found this link http://serverfault.com/questions/393862/mysql-warning-ip-address-could-not-be-resolved according to that I should just need to edit the my.cnf file. Anyone know how to edit this on docker?
August 22, 201411 yr Thats a classic XBMC + mysql refinement. I dont thnk the stock docker exports that config file. Ideally you would request an enhancement to allow it. It is not a hard upgrade. In the interim you will need to copy out the config then modify the volume mounts to share you edited config
August 22, 201411 yr Author I think I know how to do the volume mounts, but would I have to point it to where it resides on a linux install? I'm running all windows...
August 22, 201411 yr So basically you are doing 2 simple tings: 1. get a hold of a copy of the config file and fix it (ideally from within the container itself) 2. tell docker to load that volume (in this case just the config file) from your host and place it inside the contaniner if you are in no rush I would just make the feature request in the needo thread. He could do this enhancement on 10 mins since it is just more the of the same.
August 22, 201411 yr Install the MariaDB docker and just see if you can attach to it via HeidiSQL or something. Once you know the db is up and running then look at how to import. Note, the data/config/db directory should be on the unRAID server cache drive in a non-caching directory.
August 22, 201411 yr Author Install the MariaDB docker and just see if you can attach to it via HeidiSQL or something. Once you know the db is up and running then look at how to import. Note, the data/config/db directory should be on the unRAID server cache drive in a non-caching directory. See my post above, the problem is not creating or importing the mysql database, I need to change an option in a config file that is not accessible in the current docker container. Without making the change no other pc on my network will be able to connect to the database.
August 22, 201411 yr Plenty of people here using MariaDB as a central DB for XBMC clients, multiple ones. I'm not sure that fix is what you need. Unless of course these xbmc clients are not in your LAN but trying to access your db over the internet. If that the case then I can't help you as I've never tried that. Fwiw I have 4 xbmc clients using my central dockered MariaDB XBMC DB
August 22, 201411 yr What is the exact problem with the IP error you're getting? I don't think people understand what needs to be changed in the conf file. You can use heidisql to export the data to SQL files. The SQL files can be text edited to search and replace text that needs to be changed
August 22, 201411 yr Author Plenty of people here using MariaDB as a central DB for XBMC clients, multiple ones. I'm not sure that fix is what you need. Unless of course these xbmc clients are not in your LAN but trying to access your db over the internet. If that the case then I can't help you as I've never tried that. Fwiw I have 4 xbmc clients using my central dockered MariaDB XBMC DB Do you have anything running DNS on your LAN? I know I don't and the link above has the exact same error I'm getting, with the same cause, so I'm not sure why that wouldn't be the cause of my problem, I can install MariaDB, import my .sql export from mysql on my htpc, I can even connect to it with mysql workbench, but whenever I start xbmc and I get the following in the log: Version: '5.5.37-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 140822 14:25:57 [Warning] IP address '192.168.1.3' could not be resolved: Name or service not known 140822 14:30:03 [Note] /usr/sbin/mysqld: Normal shutdown after hours of reinstalling and troubleshooting today that's the best I can come up with. If you have anything else to try I'm up for anything!!
August 22, 201411 yr Author What is the exact problem with the IP error you're getting? I don't think people understand what needs to be changed in the conf file. You can use heidisql to export the data to SQL files. The SQL files can be text edited to search and replace text that needs to be changed In my replies above I have the IP error that was in my log: Version: '5.5.37-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 140822 14:25:57 [Warning] IP address '192.168.1.3' could not be resolved: Name or service not known 140822 14:30:03 [Note] /usr/sbin/mysqld: Normal shutdown
August 23, 201411 yr No, I don't have a local DNS. Is 192.168.1.3 your old windows PC or your unRAID server ?
August 23, 201411 yr Author 192.168.1.3 is my windows pc that currently has mysql, 192.168.1.2 is my unraid server, whenever I export the .sql from the old box to unraid using mysql workbench and change my advancedsettings.xml to point at the unraid MariaDB I get that in the MariaDB log and xbmc acts like it has no sources, it shows no movies or tvshows.
August 23, 201411 yr Ok, them what's the problem here ? Is it just the export/import of the old DB ? Has everything else checked out ok ? You can access the new MariaDB with HeidiSQL ? Your xbmc install can see the new DB ?
August 23, 201411 yr Author Ok, I just downloaded HeidiSQL and it's able to connect, the problem seems to be xbmc is not able to. My MySQL install is version 5.5, I don't know if that helps or not Here's more log, I just tried on a different pc on my LAN with xbmc: 140822 20:20:03 mysqld_safe Starting mysqld daemon with databases from /db 140822 20:20:03 InnoDB: The InnoDB memory heap is disabled 140822 20:20:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140822 20:20:03 InnoDB: Compressed tables use zlib 1.2.8 140822 20:20:03 InnoDB: Using Linux native AIO 140822 20:20:03 InnoDB: Initializing buffer pool, size = 128.0M 140822 20:20:03 InnoDB: Completed initialization of buffer pool 140822 20:20:03 InnoDB: highest supported file format is Barracuda. 140822 20:20:04 InnoDB: Waiting for the background threads to start 140822 20:20:05 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 46038542 140822 20:20:05 [Note] Plugin 'FEEDBACK' is disabled. 140822 20:20:06 [Note] Server socket created on IP: '0.0.0.0'. 140822 20:20:06 [Note] Event Scheduler: Loaded 0 events 140822 20:20:06 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.37-MariaDB-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 140822 20:21:12 [Warning] IP address '192.168.1.31' could not be resolved: Name or service not known
August 23, 201411 yr What's device 192.168.1.31 ? Just try a step at a tone. HeidiSQL connected, great. Is there an xbmc db there ? Video table ? Is there a user called xbmc or whatever you gave specified in the advancedsettimgs.xml of your xbmc build ? Start slowly, from the beginning, one step at a time.
August 23, 201411 yr Author What's device 192.168.1.31 ? Just try a step at a tone. HeidiSQL connected, great. Is there an xbmc db there ? Video table ? Is there a user called xbmc or whatever you gave specified in the advancedsettimgs.xml of your xbmc build ? Start slowly, from the beginning, one step at a time. 192.168.1.31 is just another pc on the network, at a desk so it's a little easier to troubleshoot. I am seeing the tables there after doing the import, and I am seeing the user xbmc as well.
August 23, 201411 yr Author Ok, I got it working, I decided to throw in the towel and just did a fresh install of MariaDB and started a new XBMC database instead of trying to import the old one. Not a major loss, and I'm hoping to run with this setup for a long time! Thanks for all the advice everyone!
September 9, 201411 yr I would be very much interested how to migrate a XBMC database from a VM e.g. under Arch to Docker. What I did: installed MariaDB Docker copied all files from the ArchVM: /var/lib/mysql to the Docker directory: /mnt/user/appdata/mariadb updated advancedsettings.xml to reflect the new location (IP of TOWER) started XBMC XBMC log is showing: 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic46 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic45 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic44 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic43 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic42 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic41 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic40 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic39 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic38 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic37 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic36 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic35 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic34 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic33 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic32 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic31 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic30 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic29 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic28 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic27 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic26 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic25 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic24 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic23 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic22 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic21 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic20 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic19 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic18 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyMusic46 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to create new database 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos78 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos77 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos76 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos75 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos74 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos73 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos72 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos71 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos70 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos69 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos68 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos67 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos66 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos65 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos64 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos63 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos62 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos61 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos60 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to open database: MyVideos78 [2003](Can't connect to MySQL server on '192.168.178.28' (61)) 10:26:32 T:140735099728656 ERROR: Unable to create new database As I'm not getting any connection via Sequel Pro (the Mac app instead of HeidiSQL on Windows) I was trying to check the basics (similar tho the XBMC guide for Arch: Create a password: $ /usr/bin/mysql_secure_installation. Get into the MariaDB command line utility: $ mysql -u root -p Enter the following commands: Type in: CREATE USER 'xbmc' IDENTIFIED BY 'xbmc'; and press return Type in: GRANT ALL ON *.* TO 'xbmc'; and press return Close out the command line tool with \q What step have I missed or what error have I made? Appreciate any guidance. Thanks a lot.
September 9, 201411 yr I am also unable to utilise my existing XBMC database when using needo's MariaDB docker. The problem seems to be that there are values specified in the my.cnf file which conflict with the existing database. The MariaDB docker will start up and run fine with the database/configuration as delivered, however, as soon as I point it at my existing database, the docker fails with an error that the size of the ib_logfile0 size conflicts with the size specified in my.cnf. For the time being, I have reverted to MariaDB running in an ArchVM.
September 9, 201411 yr I am also unable to utilise my existing XBMC database when using needo's MariaDB docker. The problem seems to be that there are values specified in the my.cnf file which conflict with the existing database. The MariaDB docker will start up and run fine with the database/configuration as delivered, however, as soon as I point it at my existing database, the docker fails with an error that the size of the ib_logfile0 size conflicts with the size specified in my.cnf. For the time being, I have reverted to MariaDB running in an ArchVM. I think you can delete that logfile and mariadb will create it when it starts.
Archived
This topic is now archived and is closed to further replies.