openmediavault-plugin-developers/openmediavault-minidlna

minidlna plugin for OpenMediaVault

openmediavault-minidlna

minidlna plugin for OpenMediaVault

openmediavault-minidlna's Issues

URGENT! minidlna change user:group of all /var/log

Hi,

I noticed today that all files and directories into /var/log have wrong permissions: minidlna:minidlna.
If I adjust with chown command, after restart minidlna again sets wrong permissions.
At the moment I have disabled the plugin.
Is possible to correct this bug?

tx

Minidlna not share

Dear All,

I need your help my minidlna not sharing my videos.
In the openmediavault it is look like fine but there is no file visible on the TV.

Please let me know how can solve it. Thank you.

logrotation of minidlna not working properly

Hey there,

I'm on Debian Wheezy 7.6 with openmediavault 1.0.28 and the plugin version 1.0.5 of minidlna, which provides minidlna 1.1.2

The logroation isn't working properly, therefore the daemon is logging in the old log (minidlna.log.1) after a initial logrotation by the logrotate daemon.

I tried some tweaks in /etc/logrotate.d/minidlna but can't get it working.

Any suggestions/fixes?

Thanks and best regards

lacunoc

mkv not recognized

Hi,

MiniDLNA works great (OMV 1.14), but sometimes files were not exposed to client, looking in log I found these entries :
[2015/03/14 20:38:29] metadata.c:700: warn: Opening /media/x/Video/xxxxxxxxxxxxxx.mkv failed! [Input/output error]
[2015/03/14 20:38:29] scanner.c:489: warn: Unsuccessful getting details for /media/x/Video/xxxxxxxxxxxxxx.mkv!

File is OK on many clients on Samba or CIFS, but not working with DLNA ?
The only thing I can suspect is a size more than 16Gb ? (18234813892)

Any Idea to resolve this ?

[improvement] preselected interface

Because of this line:

openmediavault-minidlna/srv/salt/omv/deploy/minidlna/files/etc-minidlna_conf.j2

Line 6 in 1f1e0ea

#network_interface=eth0

the daemon tries to send on all interfaces. This fails, because the second interface is a wireguard endpoint. This inteface is configured baremetal and does not show up in the interface section.

minissdp.c:324: error: sendto(udp_notify=10, 10.0.0.5): Required key not available
minissdp.c:324: error: sendto(udp_notify=10, 10.0.0.5): Required key not available
minissdp.c:324: error: sendto(udp_notify=10, 10.0.0.5): Required key not available

However, it is easy to activate this setting, but It would be nice if this line is active and prefilled with the interfaces that are configured through omv itself. Or even better, a select button for each interface.

Background: this error message get printed every second and fills up rapidly the folder2ram. This renders the complete system useless until a force shutdown.

Support DSD files

It would be great if these changes were included to support DSD files.

minidlna shows pictures and music even not chosen

Tried to "reset" and deleted the share - and reinstalled the plugin. same issue :(

very ressource CPU when minidlna work

I have installed the plugins minidlna

This service use 75% ressoure CPU always on the system
When i restart the service by command line, ressource cpu down to 15%
I use an base DB on minidlna.conf
the timeout base is 800s

it's normal ?

Minidlna does not start automatically even if enabled

Minidlna does not start automatically even if enabled.
It can still be started from the web gui.

Log file of MiniDLNA just bomb shelled my root

In a very short period of time the minidlna log file ate up the whole disk space of /

df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sdc1        37G     35G  340M  100% /


ls -l /var/log/minidlna/
insgesamt 30279652
-rw-r--r-- 1 minidlna minidlna 31006314496  3. Nov 22:43 minidlna.log
-rw-r--r-- 1 minidlna minidlna        7552 29. Okt 03:45 minidlna.log.1
-rw-r--r-- 1 minidlna minidlna         214 22. Okt 03:45 minidlna.log.2.gz
-rw-r--r-- 1 minidlna minidlna         330 15. Okt 03:45 minidlna.log.3.gz
-rw-r--r-- 1 minidlna minidlna         988  8. Okt 03:45 minidlna.log.4.gz

the content:

tail /var/log/minidlna/minidlna.log
minidlna.c:166: error: accept(http): Zu viele offene Dateien   (too many open files)
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien
minidlna.c:166: error: accept(http): Zu viele offene Dateien

and it filled very fast after purging:

echo "" >  /var/log/minidlna/minidlna.log
 ls -l /var/log/minidlna/
-rw-r--r-- 1 minidlna minidlna 5844898  3. Nov 22:44 minidlna.log

ls -l /var/log/minidlna/
-rw-r--r-- 1 minidlna minidlna 19963043  3. Nov 22:44 minidlna.log

these commands were apart some 10 to 20 seconds.

After stopping and purging the log, OMV stats showed this:

Is there a way to prevent this from taking down the whole system?

Resize Album Artwork

Is there a way to set a preferred size for album thumbnails? I'm fine breaking strict compliance if it means the artwork could be displayed at a higher available resolution.

Any upgrade plan to 1.3.0

Is there any plan to upgrade to 1.3.0 which is available for bullseye and sid, not for buster though?

Advanced/personnal options field

Hello,

In case of using of own build version of minidlna (with transcode version for example), it can implement new/unknown options.
Can you please add a button for advanced options that enable a text field where we can put own options to write in minidlna.conf file ?
Thanks

minidlna launches before the media directories are mounted

Description of issue/question

After a reboot, minidlna doesn't serve any content.

Steps to reproduce issue

Reboot the OMV server and try to access content through UPnP:

pi@omv-nas:~ $ service minidlna status 
● minidlna.service - MiniDLNA lightweight DLNA/UPnP-AV server
   Loaded: loaded (/lib/systemd/system/minidlna.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-12-13 20:03:51 CET; 1h 56min ago
     Docs: man:minidlnad(1)
           man:minidlna.conf(5)
  Process: 733 ExecStart=/usr/sbin/minidlnad -f $CONFIGFILE -P /run/minidlna/minidlna.pid $DAEMON_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 902 (minidlnad)
    Tasks: 2 (limit: 1430)
   CGroup: /system.slice/minidlna.service
           └─902 /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -r

Dec 13 20:03:47 omv-nas systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server...
Dec 13 20:03:51 omv-nas minidlnad[733]: [2020/12/13 20:03:51] minidlna.c:631: error: Media directory "V,/srv/dev-disk-by-label-omvmaster/Video/" not accessible [No such file or directory]
Dec 13 20:03:51 omv-nas minidlnad[733]: [2020/12/13 20:03:51] minidlna.c:631: error: Media directory "A,/srv/dev-disk-by-label-omvmaster/Music/" not accessible [No such file or directory]
Dec 13 20:03:51 omv-nas minidlnad[733]: [2020/12/13 20:03:51] minidlna.c:631: error: Media directory "P,/srv/dev-disk-by-label-omvmaster/Photos/" not accessible [No such file or directory]
Dec 13 20:03:51 omv-nas systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server.

Obviously the minidlna service should depend on the media directories to be available. Mine are on two external USB drives.

Versions report

versioninfo.txt

placement of Log files seems inconsistent.

OMV 5.5.23-1 (Usul)
miniDLNA 5.0.5

minidlna.conf:
log_dir=/var/log

but at some point logs have been created in
/var/log/minidlna (There are files there, date fit with my installation, but are not updated. )
minidlna can't write to /var/log minidlnad doesn't seem to have access.

OMV UI doesn't respect minidlna.conf log_dir entry.

So logs aren't created in expected locations, and created logs can't be read in UI.

File name problem: 90openmediavault-minidlna

Hello Guys,

One of a Hungarian OMV enthusiast found a problem. As he can't speak English, I try to translate his finding:
"I think there is problem with the file name. I guess it should look like that:
90-openmediavault-minidlna.conf
The problem is in the postinst and postrm scripts. It might be good at install time, when you specifically run sysctl with that parameter, but it won't be loading after a server restart because of the different file name.
Hope that it helps."
Adam

inotify warning in log

inotify.c:198: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [550] and I do not have permission to increase this limit. Please do so manually by writing a higher value into /proc/sys/fs/inotify/max_user_watches.

What does this mean / do?

When i nano /proc/sys/fs/inotify/max_user_watches there is only the value stated "8192"

fs.inotify.max_user_watches should be increased because otherwise MiniDLNA complains

With the MiniDLNA enabled in a fresh install of Kralizec (1.0), MiniDLNA complains about too low inotify limits:

[2014/11/16 20:29:40] inotify.c:198: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [2] and I do not have permission to increase this limit. Please do so manually by writing a higher value into /proc/sys/fs/inotify/max_user_watches.

Please increase this limit to 100000 (or anything in that magnitude) by default when activating MiniDLNA:
fs.inotify.max_user_watches = 100000

Steps to reproduce:

• install Kralizec
• install MiniDLNA
• setup MiniDLNA with a number of source directories
• in OMV web UI inspect System Logs/DLNA and find the quoted error message

New options support

Hi in latest Minidilna present where added some new configuration not yet supported by OVM configuration panel.

http://sourceforge.net/p/minidlna/git/ci/master/tree/minidlna.conf

It should be useful to add at least

force_sort_criteria

This setting will help people with panasonc Viera devices to set navigate files with different sorting.
Thanks

"received signal 15, good-bye"

I get this in my log and from what I have learned from google searches it is stopping miniDLNA. I am having issues with streaming to my samsung smart tv. It will stream from anywhere between 5-45 minutes then the service stops. I have to wait for it to start again and show up in my tv's sources list.