Tin Can Jukebox Error

[armorer1984]

I'm pulling my hair out on this one. Installed Tin Can and can't seem to get the catalog to update with any content. The error it gives me in the log is:

The user the web server runs under does not appear to have permissions to this directory.

I have used chmod -c -R on the directory and it still gives me that error. Any hints on what I'm missing here?

[bigfoot65]

Check to ensure the music directory is owned by your first admin user and permissions are 775.

[armorer1984]

Thanks for your help!

I double checked what you said to check. I have a single user on this box (myself) and I am a member of the "adm" group, I used chown to ensure that the directory is owned by me and used chmod to set the permissions (775) recursively in the directory. Did a reboot and I am still getting the same error from TinCan. Did I miss something?

[bigfoot65]

Not sure what the problem could be as it works fine for me. Did you change anything in the app settings?

[armorer1984]

The only thing I have changed is the media directory in the TinCan config. I have two drives, mount points are /media/2TB_Samsung1 and /media/2TB_Samsung2. I am using drive # 1 as the drive where everything is written, then I have a cron job set to duplicate every file to drive 2 for backup purposes.I have the fstab config set to mount the partitions this way at boot, eliminating any need for intervention or input on my part in case the server reboots itself when I am out of town.

I have my music share as '/media/2TB_Samsung1/Music' and this is where I pointed TinCan's config as the media directory. Does the drive need to be mounted in '/var/hda/files' or /var/hda/drives' for everything to work?

[bigfoot65]

If you pointed the app there, it should work. I use the default /var/hda/files/music for mine with no issues.

Not sure I understand your reason for mounting the drive differently. A reboot will not make a difference on the mount point.

[armorer1984]

I got an idea when you mentioned weird mount points. I had things screwed up, assuming it was OK since that was where Fedora mounted the drives. I followed the guide to add drives to Amahi and now it updates the catalog fine. Problem solved, thank you for your help!!

[bigfoot65]

Awesome. Its best to use the hda-diskmount script whenever adding drives or things might not work correctly. I typically disconnect drives when I install Fedora, then use the script to add them in once Amahi is installed and working.