Update init.d to work with MusicCabinet

[rubbersoul]

I just installed MusicCabinet and I'm loving the improvements this provides. One thing I'm having trouble with is starting/stopping/restarting the service. i used to use the convenient "service subsonic restart" or similar, but that doesn't seem to be working with MusicCabinet installed; this is to be expected I suppose, but isn't ideal. I can get the service to start just fine by running the subsonic.sh script provided, but i'm wondering how one would go about changing the subsonic init.d file to work with MusicCabinet so that starting, stopping and restarting the service becomes as trivial as it is with subsonic from the command line.

Sorry this is as much of a linux question than it is specific to MusicCabinet, but I'm having a hard time figuring out how to make this work.

Thanks!

[shadow.8]

What distro are you running? Are you getting an error message you could post? I'm using Arch Linux with systemd here and stopping and starting using the default Subsonic scripts works fine. I don't believe there is any issue with using Music Cabinet on top of Subsonic in regards to stopping/starting services. I haven't tried the init.d scripts but I'll help if I can.

[rubbersoul]

Thank you for the response, I am using debian.

I actually don't get any error messages when i run the service commands, but they don't seem to be working. For example, I can run: "sudo service subsonic stop" then when i visit MusicCabinet everything is working as normal even though it should be stopped.

[shadow.8]

I just checked the default init.d script and it points to /var/subsonic/subsonic.sh, is there where Subsonic/Music Cabinet is currently installed?

EDIT: Just realized you probably installed the .deb file, which appears to install to /usr/share/subsonic. I'm guessing Music Cabinet installs to /var/subsonic, maybe that's the issue?

[hakko]

Where did you unzip the MusicCabinet files? Did you overwrite your previous Subsonic install or did you just put them into a new directory?

[rubbersoul]

Thanks to your help, I've almost got it.

The problem I was having was I thought the installation was in var/subsonic (because there is such a folder with the jetty setup in there) I had originally placed the standalone MusicCabinet in its own /var/musiccabinet folder. The /usr/share/subsonic location has the original .jar and .war files in it however, so I've copied the MusicCabinet versions of those files as well as the .sh and .bat files to /usr/share/subsonic. I left the old subsonic.war and .jar files in there since the names are different for the MusicCabinet versions. I've renamed the old subsonic.sh to subsonic.sh.old.

Now when I run service subsonic start/stop/restart it seems to work fine. The problem I'm having now, is I can't log into the server. I've tried logging in with my regular username/password as well as the default admin/admin and I always get an incorrect username/password combo. The same happens on my mobile app.

[hakko]

Check your startup script for the parameter -Dsubsonic.home and make sure it points the correct directory (where you store your settings, including users and their log in credentials).

[rubbersoul]

I haven't moved any settings files from their default location to my knowledge. I'm not sure where the user list and passwords are kept at, but I assume it is in var/subsonic.

What I did to fix the problem was run the old subsonic.sh script. From the old interface there is a "forgot password" button. I clicked that and reset the password. Then I killed the process and relaunched subsonic with the MusicCabinet script. Everything is working just peachy now.

Thanks for the guidance everyone, I'm not well versed with linux. For the most part this server sits running and I don't have to mess with it much