2014-12-11, 22:03
Not sure I follow? As far I know, yes. What should I check?
2014-12-11, 23:21
So which machine has the files stored on it?
How are you sharing the files? I guess smb?
When you added sources on the original machine did you add them via smb shares or as local files?
How are you sharing the files? I guess smb?
When you added sources on the original machine did you add them via smb shares or as local files?
2014-12-12, 06:55
Ah, got it.
- All files are stored locally on the same HTPC running my MySQL. When I set up MySQL I already had an extensive library going, so I just imported my library after installing MySQL.
- Checking the DB, I see the paths are all saved as local paths (e.g. E:\Movies\Boxsets\Indiana Jones - Trilogy\01 - Indiana Jones - Raiders of the lost Ark.avi)
- All files are stored locally on the same HTPC running my MySQL. When I set up MySQL I already had an extensive library going, so I just imported my library after installing MySQL.
- Checking the DB, I see the paths are all saved as local paths (e.g. E:\Movies\Boxsets\Indiana Jones - Trilogy\01 - Indiana Jones - Raiders of the lost Ark.avi)
2014-12-12, 07:07
Thats the problem then. The clients can't follow that path.
I think the solution is to end up with all computers accessing via smb, even the local computer (it should be able to access it's own shares even though that seems counter-intuitive).
I think that will mean deleting all your sources and deleting the database, then adding them as smb shares. Then rescrape. If you export your database to indivdual files first it will ease the process at the expense of cluttering up your media directories with .nfo files.
I think the solution is to end up with all computers accessing via smb, even the local computer (it should be able to access it's own shares even though that seems counter-intuitive).
I think that will mean deleting all your sources and deleting the database, then adding them as smb shares. Then rescrape. If you export your database to indivdual files first it will ease the process at the expense of cluttering up your media directories with .nfo files.
2014-12-12, 07:43
You could also export the database to a single file and do a global search/replace of the local path(s) to the SMB paths.
I've done this with notepad+ a few times for friends.
I've done this with notepad+ a few times for friends.
2014-12-12, 08:28
Or indeed you could do that kind of change directly on the mysql database if you knew a bit of SQL.
2014-12-12, 08:51
Awesome thanks.
- Plan A would be to backup DB, then write script and update DB
- Plan B would be to restore DB, notepad++ it
- Plan C is to wipe and start from scratch
- Plan A would be to backup DB, then write script and update DB
- Plan B would be to restore DB, notepad++ it
- Plan C is to wipe and start from scratch
2014-12-25, 08:14
I don't want to post in two sections, but i found some speed differences with mysql between Gotham and Kodi. I thought it was OSX related, but i am doubting that now.
Please check it out here : http://forum.kodi.tv/showthread.php?tid=...pid1870606
Please check it out here : http://forum.kodi.tv/showthread.php?tid=...pid1870606
2014-12-29, 21:32
Has anyone got this setup using OS X Yosemite (10.10.1) as the server for MySQL?
I installed mysql-5.6.22-osx10.9-x86_64.dmg and tried to follow the guide but when trying to copy the file using "sudo cp my-huge.cnf /etc/my.cnf" it failed as there is no such file to copy.
It seems Yosemite has a problem launching MySQL on startup, can anyone confirm a fix for this?
I installed mysql-5.6.22-osx10.9-x86_64.dmg and tried to follow the guide but when trying to copy the file using "sudo cp my-huge.cnf /etc/my.cnf" it failed as there is no such file to copy.
It seems Yosemite has a problem launching MySQL on startup, can anyone confirm a fix for this?
2015-01-01, 09:42
Can anyone explain why when there's a DB change, I get a new DB with the new DB version number, but no data gets written to it (and the new version then crashes every time it gets started after that)?
I thought it might be the RaspBMC build of Kodi not working right, but the official Windows version does exactly the same thing. Drop the empty table, run the new version, and it creates a blank DB with the new name. No tables are created, and certainly no data is copied.
I have checked the permissions as best I can - the user I'm using now has full global privileges, and it still just creates a blank DB.
What can I do to further debug this rather painful problem?
I thought it might be the RaspBMC build of Kodi not working right, but the official Windows version does exactly the same thing. Drop the empty table, run the new version, and it creates a blank DB with the new name. No tables are created, and certainly no data is copied.
I have checked the permissions as best I can - the user I'm using now has full global privileges, and it still just creates a blank DB.
What can I do to further debug this rather painful problem?
2015-01-01, 11:00
Check out this thread: http://forum.kodi.tv/showthread.php?tid=212218
Looks very much like that problem
Looks very much like that problem
2015-01-06, 19:16
I'm preparing to set up MySQL for 3 Kodi 14.0 installations in my home. I've seen warnings earlier to not use a MySQL version later than 5.5, but I don't know how old those warnings are, or if they still apply to Kodi. Is that still the recommended version, or is it safe to go with the newest, 5.6.x?
2015-01-07, 03:41
(2015-01-06, 19:16)pagali Wrote: I'm preparing to set up MySQL for 3 Kodi 14.0 installations in my home. I've seen warnings earlier to not use a MySQL version later than 5.5, but I don't know how old those warnings are, or if they still apply to Kodi. Is that still the recommended version, or is it safe to go with the newest, 5.6.x?
I'm still running MYSQL version 5.5 on my ubuntu server.
I believe the same issues persists though I've not installed 5.6 in a while to check up on it since I had issues way back when.
