Bug 5707 – SqueezeCenter keeps a lock on Cache\MySQL folder

Bug 5707 - SqueezeCenter keeps a lock on Cache\MySQL folder

Summary:

SqueezeCenter keeps a lock on Cache\MySQL folder

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Database
Version:	7.0
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-07 14:13 UTC by Philip Meyer
Modified:	2007-11-17 04:43 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philip Meyer 2007-10-07 14:13:25 UTC

I run SqueezeCenter using activePerl, and have configured the preferences to use my own MySQL instance, which is on another disc to where the SqueezeCenter source code is installed in.

Whilst investigating another bug, I tried to clear the .\server\Cache folder.  I stopped SqueezeCenter, using Ctrl-C in the CMD window it was running in.  I then tried to delete the Cache folder, but WinXP reported that there were files in use.  The files that were locked were MySQL files.

I tried to stop the MySQL service as well, but I still couldn't remove the Cache folder.  I have now managed to delete it, following a reboot, before running SqueezeCenter.

So, it seems that some resource is not being unlocked when Ctrl-C is used to exit the server.

Comment 1 KDF 2007-10-07 17:07:50 UTC

see bug 5620

Comment 2 Chris Owens 2007-11-05 09:57:01 UTC

How are you sure that it's SqueezeCenter keeping the file open?  Although we talk to MySQL I don't think we access the files directly.

Comment 3 Philip Meyer 2007-11-05 15:34:02 UTC

What else would be accessing files within the SqueezeCenter .\server\Cache, other than SqueezeCenter?

Comment 4 Michael Herger 2007-11-17 00:36:51 UTC

If you're running your own MySQL instance, then it's probably out of SqueezeCenter's control?

Comment 5 Philip Meyer 2007-11-17 02:48:16 UTC

Maybe my bug report was confusing?  I meant that the SqueezeCenter cache folder couldn't be deleted.  Surely only SqueezeCenter writes to that cache folder?  I thought that by stopping SqueezeCenter, any file locks on the cache folder should be closed.  MySQL files should be located elsewhere, if they are not part of SqueezeCenter?

Anyway, I haven't noticed any issues since the cache folder was moved, and I've been running as a service again.  Maybe Ctrl-C in a console window was not tidying up properly?

Comment 6 Chris Owens 2007-11-17 04:43:20 UTC

Ah, sorry, we must have misread your bug.  

I typically run on XP and have a fair number of occasions to run from the command line and close using ctrl-C, and haven't noticed this.  I'm going to go ahead and mark it resolved, but certainly feel free to reopen if you notice it again.  I wouldn't be at all surprised if in stopping the freight-train-mass that is SqueezeCenter and MySQL, a few cars break loose.

Perhaps overall system load, or some plugin-related DB activity right before the close exacerbated the problem?