Did you execute the omv-mkconf minidlna command?
The 192 address is in a comment.
The 172 address is an openvpn address.
The 127 address is localhost.
Did you execute the omv-mkconf minidlna command?
The 192 address is in a comment.
The 172 address is an openvpn address.
The 127 address is localhost.
yes I did execute the command. It ran and returned to the prompt. No errors displayed.
What about:
cat /etc/openmediavault/config.xml | awk '/<minidlna>/,/<\/minidlna>/'
root@homesrvr:~# cat /etc/openmediavault/config.xml | awk '/<minidlna>/,/<\/mini
dlna>/'
<minidlna>
<enable>0</enable>
<name>MiniDLNA Server on OpenMediaVault</name>
<port>8200</port>
<strict>0</strict>
<tivo>0</tivo>
<shares/>
</minidlna>
root@homesrvr:~#
Did you enable the plugin and then save/apply?
It's still giving me that error:
An error has occured
communication failure
Here is the contents of the log that I downloaded:
[2014/08/12 08:04:55] minidlna.c:1004: warn: Starting MiniDLNA version 1.1.2.
[2014/08/12 08:04:55] minidlna.c:354: warn: Creating new database at /var/cache/minidlna/files.db
[2014/08/12 08:04:55] minidlna.c:1043: warn: HTTP listening on port 8200
[2014/08/12 08:04:55] scanner.c:702: warn: Scanning /var/lib/minidlna
[2014/08/12 08:04:55] scanner.c:789: warn: Scanning /var/lib/minidlna finished (0 files)!
[2014/08/12 08:04:55] playlist.c:125: warn: Parsing playlists...
[2014/08/12 08:04:55] playlist.c:256: warn: Finished parsing playlists.
[2014/08/12 08:04:56] sql.c:117: warn: sql_get_int_field: step failed: SQL logic error or missing database
SELECT count(*) from DETAILS where MIME glob 'a*'
[2014/08/12 08:04:56] 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.
[2014/08/12 11:45:15] minidlna.c:153: warn: received signal 15, good-bye
[2014/08/12 11:47:49] minidlna.c:1004: warn: Starting MiniDLNA version 1.1.2.
[2014/08/12 11:47:49] minidlna.c:1043: warn: HTTP listening on port 8200
[2014/08/12 11:47:49] 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.
[2014/08/12 11:59:21] minidlna.c:153: warn: received signal 15, good-bye
[2014/08/12 12:01:50] minidlna.c:1004: warn: Starting MiniDLNA version 1.1.2.
[2014/08/12 12:01:50] minidlna.c:1043: warn: HTTP listening on port 8200
[2014/08/12 12:01:50] 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.
[2014/08/12 17:15:18] minidlna.c:153: warn: received signal 15, good-bye
[2014/08/12 17:17:59] minidlna.c:1004: warn: Starting MiniDLNA version 1.1.2.
[2014/08/12 17:17:59] minidlna.c:1043: warn: HTTP listening on port 8200
[2014/08/12 17:17:59] 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.
[2014/08/12 18:28:55] minidlna.c:153: warn: received signal 15, good-bye
[2014/08/12 18:31:34] minidlna.c:1004: warn: Starting MiniDLNA version 1.1.2.
[2014/08/12 18:31:34] minidlna.c:1043: warn: HTTP listening on port 8200
[2014/08/12 18:31:34] 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.
Alles anzeigen
All I have left is putting engined in debug mode
monit stop omv-engined
omv-engined -df
Then try and enable the plugin. Post any errors from engined.
Its generating lots of data and scrolling through it I don't see anything that looks ominous. I'll rebuild the box again from here as this is the development box/test rig but I want to check a few more things first like why I can't connect to Plex from the outside although the ports are open etc. I'll start a new thread for that.
I also want to explore nginx and set up a small website or two dnsmasq etc. I like this solution it's the best that I've explored and seems to have everything that I'm looking for except a mailserver (which I have running in a VM at the moment and that's running fine).
Kudos to you guys!! A brilliant effort and work. I'll have a lot more questions as I explore so bear with me.
Hello all
I've recently gone to version 1 (1.08) and am now setting up my system again.
After installing the Mini DLNA I also have the problem " An error has occured, Communication failure".
The version of Mini DLNA version is 1.04.. I've already uninstalled it, rebooted the system, installed it, rebooted the system but this has no effect.
output dpkg -l | grep minidlna:
ii minidlna 1.1.2+dfsg-1.1 amd64 lightweight DLNA/UPnP-AV server targeted at embedded systems
ii openmediavault-minidlna 1.0.4 all OpenMediaVault miniDLNA (DLNA server) plugin
Output for cat /etc/minidlna.conf:
# This is the configuration file for the MiniDLNA daemon, a DLNA/UPnP-AV media
# server.
#
# Unless otherwise noted, the commented out options show their default value.
#
# On Debian, you can also refer to the minidlna.conf(5) man page for
# documentation about this file.
# Specify the user name or uid to run as.
#user=minidlna
# Path to the directory you want scanned for media files.
#
# This option can be specified more than once if you want multiple directories
# scanned.
#
# If you want to restrict a media_dir to a specific content type, you can
# prepend the directory name with a letter representing the type (A, P or V),
# followed by a comma, as so:
# * "A" for audio (eg. media_dir=A,/var/lib/minidlna/music)
# * "P" for pictures (eg. media_dir=P,/var/lib/minidlna/pictures)
# * "V" for video (eg. media_dir=V,/var/lib/minidlna/videos)
media_dir=/var/lib/minidlna
# Path to the directory that should hold the database and album art cache.
#db_dir=/var/cache/minidlna
# Path to the directory that should hold the log file.
#log_dir=/var/log
# Type and minimum level of importance of messages to be logged.
#
# The types are "artwork", "database", "general", "http", "inotify",
# "metadata", "scanner", "ssdp" and "tivo".
#
# The levels are "off", "fatal", "error", "warn", "info" or "debug".
# "off" turns of logging entirely, "fatal" is the highest level of importance
# and "debug" the lowest.
#
# The types are comma-separated, followed by an equal sign ("="), followed by a
# level that applies to the preceding types. This can be repeated, separating
# each of these constructs with a comma.
#
# The default is to log all types of messages at the "warn" level.
#log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=warn
# Use a different container as the root of the directory tree presented to
# clients. The possible values are:
# * "." - standard container
# * "B" - "Browse Directory"
# * "M" - "Music"
# * "P" - "Pictures"
# * "V" - "Video"
# If you specify "B" and the client device is audio-only then "Music/Folders"
# will be used as root.
#root_container=.
# Network interface(s) to bind to (e.g. eth0), comma delimited.
# This option can be specified more than once.
#network_interface=
# IPv4 address to listen on (e.g. 192.0.2.1/24).
# If omitted, the mask defaults to 24. The IPs are added to those determined
# from the network_interface option above.
# This option can be specified more than once.
#listening_ip=
# Port number for HTTP traffic (descriptions, SOAP, media transfer).
# This option is mandatory (or it must be specified on the command-line using
# "-p").
port=8200
# URL presented to clients (e.g. [url]http://example.com:80[/url]).
#presentation_url=/
# Name that the DLNA server presents to clients.
# Defaults to "hostname: username".
#friendly_name=
# Serial number the server reports to clients.
# Defaults to 00000000.
serial=681019810597110
# Model name the server reports to clients.
#model_name=Windows Media Connect compatible (MiniDLNA)
# Model number the server reports to clients.
# Defaults to the version number of minidlna.
#model_number=
# Automatic discovery of new files in the media_dir directory.
#inotify=yes
# List of file names to look for when searching for album art.
# Names should be delimited with a forward slash ("/").
# This option can be specified more than once.
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
# Strictly adhere to DLNA standards.
# This allows server-side downscaling of very large JPEG images, which may
# decrease JPEG serving performance on (at least) Sony DLNA products.
#strict_dlna=no
# Support for streaming .jpg and .mp3 files to a TiVo supporting HMO.
#enable_tivo=no
# Notify interval, in seconds.
#notify_interval=895
# Path to the MiniSSDPd socket, for MiniSSDPd support.
#minissdpdsocket=/run/minissdpd.sock
Alles anzeigen
It isn't writing your config file for some reason. You are second person to have this happen. I will have to look at it more...
...And here I am, the third one: I had all the problems reported above, applied all the fixes and still no response from the DLNA page.
The good thing is that once the error popup shows itself, you can close it, enable the service and press apply. Yes, you will still get the loading mask, but after the timeout error the DLNA will be enabled in xml:
output:
<minidlna>
<enable>1</enable>
<name>MiniDLNA su OpenMediaVault</name>
<port>8200</port>
<strict>0</strict>
<tivo>0</tivo>
<shares>
<share>
<uuid>4e764e17-4ab7-4563-aac2-06e208d35566</uuid>
<sharedfolderref>72613d1d-d552-4b0f-97ea-746e218d9ca8</sharedfolderref>
<mtype>V</mtype>
</share>
</shares>
</minidlna>
Alles anzeigen
The "weird" thing is that you can't see from the WebGUI whether DLNA is enabled or not. You can even select the "shares" tab with no problems and set everything up, as you can see from my "share" above.
OMV 1.0.8 running on Debian Wheezy ARMHF (UDOO Quad)
Try 1.0.5 in the repo now.
After installing 1.08 on a spare disk and still having the same problem I got fed up with it.
I placed my previous disk back and installed 1.09. After that the problem was gone, so I think it is a problem in 1.08
NB: I've NOT tried the 1.05 version of DLNA in OMV 1.08!
The problem was the minidlna plugin not OMV.
openmediavault-minidlna-1.0.4 was using the boolvalEx function which is available in openmediavault 1.0.9. That is why you have it working now.
openmediavault-minidlna-1.0.5 does not use boolvalEx so it should work on 1.0.8
It's working now!
Thank you very much!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!