Bugzilla – Bug 5690
Installing SqueezeCenter still uses the SlimServer DB
Last modified: 2007-10-13 06:42:16 UTC
Windows XP 10/4 build. Installing SqueezeCenter on a system with SlimServer (6.5.4) installed uses the SlimServer DB instead of setting up its own. In the SlimServer/Cache folder there is now a file: squeezecenter-mysql.pid The log files and DB appear to be recently updated (10/6) and also refrence squeezecenter in the mysql-error-log.txt file. There doesn't appear to be a DB in the SqueezeCenter\MySQL folder and all files are dated 10/4 (the install date).
That's "by design": the renaming concentrates on elements which the user is getting in contact with. Renaming all the internals will take a little longer. We did therefore not yet rename the database, though this might make sense in mixed environments.
Actually, I was referring to the DB location - inside the old SlimServer folder, not the DB name, although this may still have the same response. Sorry if I wasn't completely clear. The reason that I noticed is that I went to delete my SlimServer folder after the install (in preperation for another reinstall test) and I couldn't get rid of it because many files were in use. Fortunately I had SqueezeCenter running or I would have deleted my entire DB and crashed the SC installation. Although I haven't tried this scenario yet, on a new install I would expect the DB to be located in the SqueezeCenter folder. When someone upgrades and installs to the SqueezeCenter folder it would be natural to assume that ALL of the new stuff is located in the SqueezeCenter folder and not some of each. Also, people will tend to want to clean up and get rid of "unused" directories, etc. so if their timing is bad they will have a lot of work to do to recover... Wouldn't not moving it just cause issues with later versions having to deal with the dbs being located all over the place? Could the install copy the DB over to the SqueezeCenter location along with the preferences to keep things a bit cleaner? Thanks
> Actually, I was referring to the DB location - inside the old SlimServer > folder, not the DB name, although this may still have the same response. I can't reproduce this: installed 6.5.4 on a clean machine. Then re-installed the latest SC7 on top of it. The installer removed the SS6 services, uninstalled SlimServer 6 and then installed SC7 in its new folder. The MySQL data is stored in SC7/Cache/MySQL, SS6/ is empty. Please update your SC7 as the installer has undergone some major changes. And please do so before reporting any bug, just to be sure the issue has not yet been resolved. > Although I haven't tried this scenario yet, on a new install I would expect the > DB to be located in the SqueezeCenter folder. That's correct. > When someone upgrades and > installs to the SqueezeCenter folder it would be natural to assume that ALL of > the new stuff is located in the SqueezeCenter folder and not some of each. Again correct.
I was under the impression that I was testing with the post rename install changes build. There were other install/operation issues over the weekend so I wasn't able to shift builds as I had originially planned - I will repull and verify. One difference, I had SS 7 installed prior to installing SS 6.5.4 and then going to SC 7. I thought that I had cleaned everything out of the registry, etc. but perhaps I missed something.
> I was under the impression that I was testing with the post rename install > changes build. The Windows installer has been partly rewritten a few days after the renaming. What you're seeing might be an issue with the intermediary version... Please let me know how things go with the latest version. Thanks!
Uninstalled SC 7 10/4. Reinstalled SS 6.5.4 Installed SC 7 10/8 Still use the DB from the SlimServer folder and did NOT create one in the SC folder. It/I must not be cleaning up everything - where in the registry (or elsewhere) is the location stored so I can make sure to clear it fully out?
Deleted everything I can think of again(see 5640). DB is still located in the SlimServer folder after upgrading from SS 6.5.4. If there is something that I can do different please let me know. Thanks.
Paths used by SlimServer <6.x & very early SC7: c:\program files\slimserver - installation folder c:\alluserdata\slimserver (or something) on Vista for the data, Cache etc. USER/Software/SlimDevices - Registry for user settings (startup options) LOCAL_MACHINE/Services/.../slimsvc - slimserver service LOCAL_MACHINE/Services/.../SlimServerMySQL - MySQL Paths used by SC7: c:\program files\squeezecenter - installation folder c:\alluserdata\squeezecenter (or something) on Vista for the data, Cache etc. USER/Software/Logitech/SqueezeCenter - Registry for user settings (startup options) LOCAL_MACHINE/Services/...squeezesvc - squeezecenter service LOCAL_MACHINE/Services/...squeezeMySQL - MySQL When updating from 6.x the installer will - copy the slimserver.prefs file to c:\program files\squeezecenter - launch uninstall auf slimserver 6 - try to stop SS6 services if still running - try to stop SC7 services if already available - install new SC7 in afore mentioned program folder - MySQL is using SC's cache folder The only reason I can imagine why you'd see this behaviour is if the cache folder preference is stored and migrated to SC7. I will have to check this.
I'll make sure that these new entries are removed as well and retest. Remember I did have SS 7, etc. installed on this box prior to starting all of the install testing so it isn't a completely clean environment - but I'm doing my best. Thanks for the additional info.
Change 13726 - I changed the installation so that the cachedir preference isn't migrated, but reset to SC's default value. This should prevent it from using the SS installation folder for its data.
Tested on Windows XP. Installed SS 6.5.4 Stopped SS. Stopped SlimTray Installed SC 7 It uninstalled SS 6.5.4 without hanging waiting for SlimTray to shutdown after "starting". The DB was installed into SC 7's area instead of being in the SS 6 area. The music and playlist folders were not from the SS 6 preferences - NEED TO CONFIRM THIS, I MAY HAVE MESSED UP THE SS6 INSTALL. It appeared to use the SC7 defaults instead of the specific settings put into ss6 (d:\music, d:\music playlists) instead of c:\my documents...
Windows XP, build 10/13. uninstalled previous SC. cleaned registry. installed SS 6.5.4 setup music/playlist folders, MusicIP, scanned, confirmed proper operation left SS 6.5.4 running installed SC 7 - 10/13 Still hangs waiting for a mouse movement before it finishes painting the language options screen. Properly and completely shuts down ss 6.5.4 Properly installs SC DB in SC folder - SS folder can be deleted after install finishes. Does NOT properly default Music folder to SS settings. Does NOT properly default Music Playlists folder to SS settings. Does NOT properly default MusicIP to ON in initial setup wizard. grey/white area on left/server side still appears during initial scanning and needs to be manually refreshed to clean up. Reported on another bug. I'll report the defaulting folders/setting on a different bug as well since this one is about the DB location.