Talk:MySQL - Revision history

Ned Scott: Ned Scott moved page HOW-TO talk:Share libraries using MySQL to Talk:MySQL

2014-04-21T06:28:54Z

Ned Scott moved page HOW-TO talk:Share libraries using MySQL to Talk:MySQL

← Older revision	Revision as of 06:28, 21 April 2014
(No difference)

Iainmacleod: /* MySQL connection errors at start-up */

2014-02-08T23:30:22Z

MySQL connection errors at start-up

← Older revision		Revision as of 23:30, 8 February 2014
Line 87:		Line 87:

	== MySQL connection errors at start-up ==		== MySQL connection errors at start-up ==

			Please note: I resolved this issue by using an Openelec addon setting. Under Openelec, make sure you enable Wait for network before starting XBMC - it is specifically designed for this, and a general recommendation for Openelec when using WiFi
			[[User:Iainmacleod\|Iainmacleod]] ([[User talk:Iainmacleod\|talk]]) 18:30, 8 February 2014 (EST)

	Note: This issue is related to XBMC running on Raspberry PI using OpenElec		Note: This issue is related to XBMC running on Raspberry PI using OpenElec

Scsa20: /* Windows Firewall Rules */ new section

2014-01-05T10:16:08Z

Windows Firewall Rules: new section

← Older revision		Revision as of 10:16, 5 January 2014
Line 172:		Line 172:

	All three files go in the same location in the userdata folder. Restart XBMC and you're done! [[User:SkyLined\|SkyLined]] 09:30, 24 May 2013 (EDT)		All three files go in the same location in the userdata folder. Restart XBMC and you're done! [[User:SkyLined\|SkyLined]] 09:30, 24 May 2013 (EDT)

			== Windows Firewall Rules ==

			I've updated the Windows section about the Windows Firewall. There is no need to use UDP since MySQL only talks on TCP. Also there's no need to set up an outbound rule since you only need it for incoming traffic to get the data so why bother covering it with rules that's not needed and possibly open yourself to nasty stuff? [[User:Scsa20\|Scsa20]] ([[User talk:Scsa20\|talk]]) 05:16, 5 January 2014 (EST)

>SkyLined: /* passwords.xml */ small fix

2013-05-24T13:38:11Z

passwords.xml: small fix

← Older revision		Revision as of 13:38, 24 May 2013
Line 169:		Line 169:
	</passwords></syntaxhighlight>		</passwords></syntaxhighlight>
	''Again, you'll need to replace "smb://192.168.0.1/" with the relevant path in your setup.''		''Again, you'll need to replace "smb://192.168.0.1/" with the relevant path in your setup.''
	{{Note\|~~If you have~~ not protected ~~your share~~ with a username and password, you ~~still~~ need to ~~create this file as not all devices appear to support anonymous login to smb shares. In this case, only provide~~ a valid ~~user name~~ on the server ~~(eg~~. "smb://username@192.168.0.1")}}		{{Note\|When using an smb that is not protected with a username and password and you are getting errors when you want to playback files, you will need to supply a username:password that is valid on the server. If your user does not have a password, you can just provide the username as in "smb://username@192.168.0.1".}}

	All three files go in the same location in the userdata folder. Restart XBMC and you're done! [[User:SkyLined\|SkyLined]] 09:30, 24 May 2013 (EDT)		All three files go in the same location in the userdata folder. Restart XBMC and you're done! [[User:SkyLined\|SkyLined]] 09:30, 24 May 2013 (EDT)

>SkyLined: /* Alternative to export/import */ new section

2013-05-24T13:30:27Z

Alternative to export/import: new section

← Older revision		Revision as of 13:30, 24 May 2013
Line 115:		Line 115:

	:Good point, and I guess I don't need to mount anything just make sure the network interface is up. This is probably not an issue on a standard XBMC installation, it appears to be a startup synchronization problem on OpenElec and an appliance like Raspberry PI. [[User:Jpgeek\|Jpgeek]] 16:14, 30 April 2013 (EDT)		:Good point, and I guess I don't need to mount anything just make sure the network interface is up. This is probably not an issue on a standard XBMC installation, it appears to be a startup synchronization problem on OpenElec and an appliance like Raspberry PI. [[User:Jpgeek\|Jpgeek]] 16:14, 30 April 2013 (EDT)

			== Alternative to export/import ==

			I have an alternative to exporting/importing that I find to be easier to use and explain. I developed it after I ran into a few issues with a Windows server hosting my media which I resolved by using its IP address, rather than its NetBIOS name and providing a valid user in "passwords.xml", even though I was sharing my media without username/password. I am not entirely sure what the root cause of my issues was. I was getting errors on my Android and Raspberry PI devices but not on my Windows laptop, so I assumed it had to do with the smb implementation on nix machines wasn't working as expected. The sync seemed to work fine on all my devices as I could see all the media files in my library, but when I wanted to play something on the nix based devices, I got an error saying that "the file is no longer available" and would I want to remove it from the library? I never bothered to check my log files, so I can't tell you more about it.

			Anyway, rather than export and import the media database in xbmc, you will need to create/copy two additional files (sources.xml and passwords.xml, in addition to advancedsettings.xml) in/to the userdata folder of any device you want to sync. If others agree that this is easier than exporting and importing the database we should update the HOW-TO.

			===advancedsettings.xml===
			Create advancedsettings.xml as described in the HOW-TO
			===sources.xml===
			<syntaxhighlight lang="xml"><sources>
			<programs>
			<default pathversion="1"></default>
			</programs>
			<video>
			<default pathversion="1"></default>
			<source>
			<name>Movies</name>
			<path pathversion="1">smb://192.168.0.1/Shares/Movies</path>
			</source>
			<source>
			<name>TV Shows</name>
			<path pathversion="1">smb://192.168.0.1/Shares/TV Shows</path>
			</source>
			</video>
			<music>
			<default pathversion="1"></default>
			<source>
			<name>Music</name>
			<path pathversion="1">smb://192.168.0.1/Shares/Music</path>
			</source>
			</music>
			<pictures>
			<default pathversion="1"></default>
			<source>
			<name>Pictures</name>
			<path pathversion="1">smb://192.168.0.1/Shares/Pictures</path>
			</source>
			</pictures>
			<files>
			<default pathversion="1"></default>
			</files>
			</sources></syntaxhighlight>
			''Obviously, you'll need to replace "smb://192.168.0.1/Shares/..." with the relevant path in your setup.''
			{{Note\|Use a static IP address for your media server and not "smb://MediaServer/...", as NetBIOS names may give problems on some devices.}}
			{{Note\|Remote paths should not include a username/password, even if you use one, as these are specified in passwords.xml}}</p>
			===passwords.xml===
			<syntaxhighlight lang="xml"><passwords>
			<path>
			<from pathversion="1">smb://192.168.0.1/</from>
			<to pathversion="1">smb://username:password@192.168.0.1/</to>
			</path>
			</passwords></syntaxhighlight>
			''Again, you'll need to replace "smb://192.168.0.1/" with the relevant path in your setup.''
			{{Note\|If you have not protected your share with a username and password, you still need to create this file as not all devices appear to support anonymous login to smb shares. In this case, only provide a valid user name on the server (eg. "smb://username@192.168.0.1")}}

			All three files go in the same location in the userdata folder. Restart XBMC and you're done! [[User:SkyLined\|SkyLined]] 09:30, 24 May 2013 (EDT)

>SkyLined: /* Path substitution causes duplicate entries */ possible cause

2013-05-24T12:44:23Z

Path substitution causes duplicate entries: possible cause

← Older revision		Revision as of 12:44, 24 May 2013
Line 79:		Line 79:

	:Path subs alone cannot create duplicates, as it only takes a source and points it to a different location. There would still only be one source. You only get duplicates if you have more than one source that is pointing to the same files. -- [[User:Ned Scott\|Ned Scott]] 02:58, 15 September 2012 (EDT)		:Path subs alone cannot create duplicates, as it only takes a source and points it to a different location. There would still only be one source. You only get duplicates if you have more than one source that is pointing to the same files. -- [[User:Ned Scott\|Ned Scott]] 02:58, 15 September 2012 (EDT)

			:What may have happened here is that you scanned your sources and the video files were enter into your db through the smb path. Then you added the path substitution and scanned your sources again. The substitution causes the same video files to have different paths and they get enter into your db through this new path as well. And since the old smb path is still valid, the old entries are not removed. I've had this happen when I switched from using NetBIOS name to ip address in "smb://" sources. I found the easiest way to get rid of the old ("smb://netbios-name/...") files was to change the name of the machine to something else, so these paths are no longer valid, clean up the db and then change the name of machine back. [[User:SkyLined\|SkyLined]] 08:44, 24 May 2013 (EDT)

	== MariaDB ==		== MariaDB ==

>Jpgeek: /* MySQL connection errors at start-up */

2013-05-01T00:51:14Z

MySQL connection errors at start-up

← Older revision		Revision as of 00:51, 1 May 2013
Line 94:		Line 94:
	So I decided to mess around with autostart.sh which executes before XBMC starts and pre-mount the two servers needed for these connections. That too was frustrating. Turns out when the autostart script executes the mount command the network interface has not yet been started. So to solve the problem I had to add a ifconfig up eth0 <ipaddress>. This solved the problem and XBMC now starts without issues.		So I decided to mess around with autostart.sh which executes before XBMC starts and pre-mount the two servers needed for these connections. That too was frustrating. Turns out when the autostart script executes the mount command the network interface has not yet been started. So to solve the problem I had to add a ifconfig up eth0 <ipaddress>. This solved the problem and XBMC now starts without issues.

	I ~~will add~~ the ~~script here once~~ I ~~get home and turn on~~ the ~~server.~~		So after thinking about Ned's point below I decided that the only think I need to do during autostart.sh execution is to start the network interface

			: #!/bin/sh
			: #set -x
			:echo "===== Start $0 ====="
			:ifconfig
			:ifconfig eth0 up <your IP address>
			:ifconfig
			:route
			:echo "===== End $0 ====="
			:sleep 5
			:exit

	[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)		[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)

>Jpgeek: /* MySQL connection errors at start-up */

2013-04-30T20:14:59Z

MySQL connection errors at start-up

← Older revision		Revision as of 20:14, 30 April 2013
Line 100:		Line 100:

	:Thanks for the heads up, but I think most users would not be mounting their shares on the OS level, but instead having XBMC take care of connecting to the shares? -- [[User:Ned Scott\|Ned Scott]] 14:02, 30 April 2013 (EDT)		:Thanks for the heads up, but I think most users would not be mounting their shares on the OS level, but instead having XBMC take care of connecting to the shares? -- [[User:Ned Scott\|Ned Scott]] 14:02, 30 April 2013 (EDT)

			:Good point, and I guess I don't need to mount anything just make sure the network interface is up. This is probably not an issue on a standard XBMC installation, it appears to be a startup synchronization problem on OpenElec and an appliance like Raspberry PI. [[User:Jpgeek\|Jpgeek]] 16:14, 30 April 2013 (EDT)

Ned Scott: /* MySQL connection errors at start-up */

2013-04-30T18:02:05Z

MySQL connection errors at start-up

← Older revision		Revision as of 18:02, 30 April 2013
Line 97:		Line 97:

	[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)		[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)


			:Thanks for the heads up, but I think most users would not be mounting their shares on the OS level, but instead having XBMC take care of connecting to the shares? -- [[User:Ned Scott\|Ned Scott]] 14:02, 30 April 2013 (EDT)

Ned Scott: Newer messages go on the bottom of the page.

2013-04-30T18:00:48Z

Newer messages go on the bottom of the page.

← Older revision		Revision as of 18:00, 30 April 2013
Line 1:		Line 1:
	~~== MySQL connection errors at start-up ==~~

	~~Note: This issue is related to XBMC running on Raspberry PI using OpenElec~~

	I just spent several hours debugging strange behavior in XBMC after migrating to MySQL. The strange behavior revolved around certain featured disappearing after reboot, such as the Movie tab on the home screen and under Videos. Also if you right clicked a movie you no longer had all the selection like "Movie Information".

	So after reviewing the logs under <HOME>/.xbmc/temp I noticed errors connecting to the DB and the art share. It appears there is a problem in the timing between the network interface and when XBMC looks for the shares or tries to connect to the DB.

	So I decided to mess around with autostart.sh which executes before XBMC starts and pre-mount the two servers needed for these connections. That too was frustrating. Turns out when the autostart script executes the mount command the network interface has not yet been started. So to solve the problem I had to add a ifconfig up eth0 <ipaddress>. This solved the problem and XBMC now starts without issues.

	~~I will add the script here once I get home and turn on the server.~~

	~~[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)~~

	== NAS how-to link dump ==		== NAS how-to link dump ==

Line 97:		Line 83:

	MariaDB works as a drop in replacement to MySQL and it's a bit faster. Should it be added to this page or be placed on its own separate page? (The instructions require a PPA be used in Ubuntu so they are a bit more complicated. Also, upgrading from MySQL has to be covered as well. [[User:Ivanmmj\|Ivanmmj]] 12:46, 24 January 2013 (EST)		MariaDB works as a drop in replacement to MySQL and it's a bit faster. Should it be added to this page or be placed on its own separate page? (The instructions require a PPA be used in Ubuntu so they are a bit more complicated. Also, upgrading from MySQL has to be covered as well. [[User:Ivanmmj\|Ivanmmj]] 12:46, 24 January 2013 (EST)

			== MySQL connection errors at start-up ==

			Note: This issue is related to XBMC running on Raspberry PI using OpenElec

			I just spent several hours debugging strange behavior in XBMC after migrating to MySQL. The strange behavior revolved around certain featured disappearing after reboot, such as the Movie tab on the home screen and under Videos. Also if you right clicked a movie you no longer had all the selection like "Movie Information".

			So after reviewing the logs under <HOME>/.xbmc/temp I noticed errors connecting to the DB and the art share. It appears there is a problem in the timing between the network interface and when XBMC looks for the shares or tries to connect to the DB.

			So I decided to mess around with autostart.sh which executes before XBMC starts and pre-mount the two servers needed for these connections. That too was frustrating. Turns out when the autostart script executes the mount command the network interface has not yet been started. So to solve the problem I had to add a ifconfig up eth0 <ipaddress>. This solved the problem and XBMC now starts without issues.

			I will add the script here once I get home and turn on the server.

			[[User:Jpgeek\|Jpgeek]] 13:57, 30 April 2013 (EDT)