i installed the minidlna on my 5.0b12a testserver. After configuring i found that the server doen't start even though the unraid page says it is running. in the logfile i see:

 

2014/01/26 12:10:10] minidlna.c:1063: warn: Starting MiniDLNA version 1.1.0.

[2014/01/26 12:10:10] minidlna.c:323: fatal: ERROR: Failed to open sqlite database!  Exiting...

 

what can be wrong here, did i do something wrong?

 

i set the database and log directory to mnt/cache/minidlna

 

Is your minidlna share set to cache-only?

 

If you didn't create a minidlna share you have one anyway because any folder at the root of /mnt/disk* or /mnt/cache is automatically a share.

 

If it is not set to cache-only then mover will move it.

Is your minidlna share set to cache-only?

 

If you didn't create a minidlna share you have one anyway because any folder at the root of /mnt/disk* or /mnt/cache is automatically a share.

 

If it is not set to cache-only then mover will move it.

 

Thanks for the tip. Just checked and the minidlna share was indeed created. I din't create it myself thought.

 

The question remains:

 

Why doen't the server start? And why do I see the error in the log file?

Have you checked to see if it was moved?

 

ls -al /mnt/cache/minidlna

 

Have you checked to see if it was moved?

 

ls -al /mnt/cache/minidlna

 

i get this:

 

root@Hal-1:~# ls -al /mnt/cache/minidlna

total 4

drwxr-xr-t 2 root  root  80 Jan 25 16:22 ./

drwxrwx--- 9 nobody users 200 Jan 26 12:10 ../

-rw-r--r-- 1 root  root  870 Jan 26 17:44 minidlna.log

root@Hal-1:~#

 

in share settings use cache disk is set to no

 

Looks like your minidlna installation got moved like I said.

 

It is not a question of whether the share is set to use cache. If it is on the cache drive it will get moved unless it is in a cache-only share (or else a hidden .folder).

 

Most people have a cache-only apps share that they install everything into. A share that they created and set to Use Cache: Only

 

For example, instead of accidentally creating a minidlna share that got moved, you could have created a share named apps, set it to use cache only, and then set your minidlna installation to /mnt/cache/apps/minidlna.

 

Lots of discussion about this all over the forum.

 

You can probably find your minidlna folders on one of your data disks. Suggest you just delete them from there and start over with a cache-only apps share. If you have any other plugins running from cache you must have done something like this (or possibly started their folder name with '.' so mover wouldn't find it)

I tried again and set the directories to mn/cache/.minidlna. So with the leadin . . like I did with SABNZBD. I still see the same message appear in the log file and the server isn't running.

Is this a typo?

...set the directories to mn/cache/.minidlna. ...

 

Is this a typo?

...set the directories to mn/cache/.minidlna. ...

 

yes, my bad it is a typo. this time i copy the line from the unraid page:

 

/mnt/cache/.minidlna

ls -al /mnt/cache/.minidlna

What does this get now?

Typically, this problem is a permissions issue.

When the minidlna server starts, it first goes looking for it's media database.

If one doesn't exist, it tries to create it.

 

If it can't create it, you get the error message you are seeing.

 

You will need to ssh into the unraid box, and modify the permissions on the /mnt/cache/.minidlna directory.

 

I would suggest trying 'chmod 777 /mnt/cache/.minidlna' as a starting point.

If this works, then you can then refine the permissions as you see fit. You might also want to 'chown' the directory if you are planning to run minidlna as nobody.