MiniDLNA plugin
-
-
The image that ryecoaaron chose is more up-to-date and has many more downloads than that.
Do you want to try to do the guide? The truth is that I don't have much experience with dlna.
-
The image that ryecoaaron chose is more up-to-date and has many more downloads than that.
Do you want to try to do the guide? The truth is that I don't have much experience with dlna.
NO, but please consider to test both dockers, using a minidlna.yaml file into "stack" on Portainer is the easy way to depoly a container.
In the case of lordpedal docker that I suggest is a copy & Paste and edit few lines.
-
NO
Then to my to-do list. At some point I will.
but please consider to test both dockers
I don't see the advantage of trying both. I prefer to choose the most accepted and up-to-date one, then fine-tune it to make it work well.
using a minidlna.yaml file into "stack" on Portainer is the easy way to depoly a container
I know thanks.
-
NO, but please consider to test both dockers, using a minidlna.yaml file into "stack" on Portainer is the easy way to depoly a container.
In the case of lordpedal docker that I suggest is a copy & Paste and edit few lines.What is your reasoning for wanting the lordpedal image? When I selected image for the plugin, I tested a bunch of them to come up with my selection.
-
What is your reasoning for wanting the lordpedal image? When I selected image for the plugin, I tested a bunch of them to come up with my selection.
my reason: have more config enviroment variables that help me to configure properly in my sytem:
Code
Alles anzeigenversion: "2" services: minidlna: image: lordpedal/minidlna container_name: miniDLNA network_mode: host environment: - MINIDLNA_MEDIA_DIR_1=AVP,/media/Descargas - MINIDLNA_MEDIA_DIR_2=A,/media/Musica - MINIDLNA_MEDIA_DIR_3=V,/media/Videos - MINIDLNA_MEDIA_DIR_4=P,/media/Imagenes - MINIDLNA_FRIENDLY_NAME=Lordpedal DLNA - MINIDLNA_INOTIFY=yes - MINIDLNA_ROOT_CONTAINER=B - MINIDLNA_MAX_CONNECTIONS=7 - MINIDLNA_SERIAL=15161881 - MINIDLNA_MODEL_NUMBER=1 - MINIDLNA_PORT=8200 volumes: - '~/docker/minidlna/Descargas:/media/Descargas' - '~/docker/minidlna/Musica:/media/Musica' - '~/docker/minidlna/Videos:/media/Videos' - '~/docker/minidlna/Imagenes:/media/Imagenes' restart: always
I can change port, friendly name, and define several multimedia paths in a logical structure
and have support for several structures (AMD64, arm)
Thats all
-
Thats all
As I see it. You are right on ARM support, vladgh is not. Variables can also be set in vladgh, although I think it has to be done in CLI. What doesn't convince me about Lordpedal is that it is a single developer who published a year ago and hasn't updated since. On the contrary, Vladgh has a team of 7 people who publish versions and have active development.
What I do not know is if it is worth all this. Jellyfin, and I suppose Plex too, have a built-in DLNA server. It does not work well?
-
I have no need to convince you, I only ask you that try both and recommend the one that you think works best when post how to install minidlna in a docker
PD: I use plex as a DLNA server, and test Minidlna to see if works for me, but I do not use it on my NAS
And consider best to use Plex, jellyfin or emby than MiniDLNA, but some old TV only can use DLNA.
-
but some old TV only can use DLNA.
Those TVs can't watch content from Jellyfin, Plex, or Emby DLNA server? These apps are supposed to have DLNA for these cases. If a device does not have the full client, they serve it content with DLNA.
-
Those TVs can't watch content from Jellyfin, Plex, or Emby DLNA server? These apps are supposed to have DLNA for these cases. If a device does not have the full client, they serve it content with DLNA.
It's a matter of taste (not sure well traslate = Es una cuestión de gustos).
I mean, that if you have a good ordered biblio with subfolders for section like films/western, film/drama, and same for series.
MiniDLNA can show only file structure not a plain folder with all the films ordered by /age/name/date/etc...) like DLNA on PLEX, Jejyfin, emby does.
The point is that those DLNA embeded on that apps, are really too complex for a well orderer folder, and I prefer how the MiniDLNA show it.
PD: As I say previosly I use Plex by default , not DLNA on Plex or MiniDLNA today, but I use miniDLNA until 2015
-
The point is that those DLNA embeded on that apps, are really too complex for a well orderer folder
Sometimes I want to write to you in Spanish, we would both finish sooner
I don't know if I understand this. Does this mean that the content appears cluttered?
-
I think I will not be able to do this guide. I have an old TV with a raspberry with Kodi as a client and I thought I had a chance to test DLNA on it. Unfortunately, I just checked that it doesn't have DLNA and my other TVs have Android built in. So I can't test DLNA. I am not going to write a guide for something that I cannot test how it works.
-
have more config enviroment variables that help me to configure properly in my sytem:
I don't really care which container anyone uses. I don't understand why people use dlna at all. But I see the exact same environment variables for both images. Anyway, I think we have killed this topic.
-
Sometimes I want to write to you in Spanish, we would both finish sooner
I don't know if I understand this. Does this mean that the content appears cluttered?
the content appears ordered like DLNA wants, not like I wants.
Imagine all your multimedia show in one folder ordered by name , mixing films and series by example.
-
-
...skipping...
-- Journal begins at Sat 2021-10-30 12:29:41 BST, ends at Tue 2021-11-16 14:24:06 GMT. --
Nov 14 11:24:04 raspberrypi systemd[1]: /lib/systemd/system/minidlna.service:4: Failed to add dependency on autofs, ignoring: Invalid argument
Nov 14 11:24:04 raspberrypi systemd[1]: /lib/systemd/system/minidlna.service:4: Failed to add dependency on autofs, ignoring: Invalid argument
-- Boot c3ce2c4e235d4a7db85740b62bfa536a --
Nov 14 13:30:19 raspberrypi systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server.
Nov 14 13:30:25 raspberrypi minidlnad[720]: minidlna.c:1028: fatal: Failed to open log file '/var/log/minidlna.log': Permission denied
Nov 14 13:30:25 raspberrypi systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 14 13:30:25 raspberrypi systemd[1]: minidlna.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
log file support is not available (press RETURN)
I am expecting a similar behaviour after an unfortunate chain of events, as already stated in this post.
Here is the result from journalctl -u minidlna and systemctl is-enabled minidlna
Code
Alles anzeigenroot@########:~# journalctl -u minidlna -- Logs begin at Fri 2022-03-04 03:10:28 -03, end at Fri 2022-03-04 15:17:01 -03. -- Mar 04 03:10:29 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 03:10:30 ######## minidlnad[543]: [2022/03/04 03:10:30] minidlna.c:631: error: Media directory "/srv/dev-disk-by-uuid-fdaf14bb-4869-47d6-b2e0-c452d9469664/media/" not accessible [No such file or directory] Mar 04 03:10:30 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 03:10:31 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 03:10:31 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 08:02:30 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 08:02:30 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 08:02:30 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 08:02:30 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 08:03:31 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 08:03:31 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 08:03:31 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 08:03:31 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 08:04:06 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 08:04:06 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 08:04:06 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 08:04:06 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 14:51:04 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 14:51:04 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 14:51:05 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 14:51:05 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 14:51:40 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 14:51:40 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 14:51:41 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 14:51:41 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 14:54:04 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 14:54:04 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 14:54:04 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 14:54:04 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 15:01:42 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 15:01:42 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 15:01:43 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 15:01:43 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 15:02:15 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 15:02:15 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 15:02:15 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 15:02:15 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 15:10:59 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 15:10:59 ######## systemd[1]: minidlna.service: Can't open PID file /run/minidlna/minidlna.pid (yet?) after start: No such file or directory Mar 04 15:10:59 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 15:10:59 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 15:10:59 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'. Mar 04 15:12:27 ######## systemd[1]: Starting MiniDLNA lightweight DLNA/UPnP-AV server... Mar 04 15:12:27 ######## systemd[1]: Started MiniDLNA lightweight DLNA/UPnP-AV server. Mar 04 15:12:27 ######## systemd[1]: minidlna.service: Main process exited, code=exited, status=255/EXCEPTION Mar 04 15:12:27 ######## systemd[1]: minidlna.service: Failed with result 'exit-code'.
I already tried a plethora of actions and none succeeded. Any chance of an easy fix for this?Best regards.
-
Any chance of an easy fix for this?
Using something else is probably your best bet...
First I would try to see if it gives you better errors:
sudo /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r
If nothing useful, I would delete the database and config file then re-run the salt code.
sudo rm /var/cache/minidlna/files.db /etc/minidlna.conf
sudo omv-salt deploy run minidlna
-
Using something else is probably your best bet...
First I would try to see if it gives you better errors:
sudo /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r
If nothing useful, I would delete the database and config file then re-run the salt code.
sudo rm /var/cache/minidlna/files.db /etc/minidlna.conf
sudo omv-salt deploy run minidlna
Zitatroot@########:~# sudo /usr/sbin/minidlnad -f /etc/minidlna.conf -P /run/minidlna/minidlna.pid -S -r
minidlna.c:133: error: bind(http): Address already in use
minidlna.c:1100: fatal: Failed to open socket for HTTP. EXITING
Got this.
Will proceed with the file cleaning and post the results.
Best regards.
-
So there is another process already running using the port you confgured for minidlna. It uses 8200 if I remember correctly. Check what else you installed.
or netstat -tulpen (may need installing)
-
So there is another process already running using the port you confgured for minidlna. It uses 8200 if I remember correctly. Check what else you installed.
or netstat -tulpen (may need installing)
Odd! Look who is there!
Best regards.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!