[opensuse] minidlna fails
Hi all, I would like to use on Tumbleweed/KDE minidlna to stream multimedia/pictures to the TV . I installed it from snap, and made some modifications to the minidlna.config file in /etc. However, I am not able to use it. When I ask its status, I get: berci@linux-h9qy:~> systemctl status minidlna ? minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-11-24 19:48:53 CET; 42s ago Process: 15219 ExecStart=/usr/sbin/minidlnad -S (code=exited, status=255/EXCEPTION) Main PID: 15219 (code=exited, status=255/EXCEPTION) Could you help what could go wrong? Thanks: Albert ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Tue, 24 Nov 2020 19:58:28 +0100 oszko@chem.u-szeged.hu wrote:
Hi all,
I would like to use on Tumbleweed/KDE minidlna to stream multimedia/pictures to the TV . I installed it from snap, and made some modifications to the minidlna.config file in /etc. However, I am not able to use it. When I ask its status, I get:
berci@linux-h9qy:~> systemctl status minidlna ? minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-11-24 19:48:53 CET; 42s ago Process: 15219 ExecStart=/usr/sbin/minidlnad -S (code=exited, status=255/EXCEPTION) Main PID: 15219 (code=exited, status=255/EXCEPTION)
Could you help what could go wrong?
If you want help, then I would suggest posting the contents of your config file, since you've changed it. You might also see what messages it has put in the journal and post those and/or run the daemon from the command line and post any output (hint, use the -v option)
Thanks: Albert
Idézet (Dave Howorth <dave@howorth.org.uk>):
On Tue, 24 Nov 2020 19:58:28 +0100 oszko@chem.u-szeged.hu wrote:
Hi all,
I would like to use on Tumbleweed/KDE minidlna to stream multimedia/pictures to the TV . I installed it from snap, and made some modifications to the minidlna.config file in /etc. However, I am not able to use it. When I ask its status, I get:
berci@linux-h9qy:~> systemctl status minidlna ? minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-11-24 19:48:53 CET; 42s ago Process: 15219 ExecStart=/usr/sbin/minidlnad -S (code=exited, status=255/EXCEPTION) Main PID: 15219 (code=exited, status=255/EXCEPTION)
Could you help what could go wrong?
If you want help, then I would suggest posting the contents of your config file, since you've changed it.
You might also see what messages it has put in the journal and post those and/or run the daemon from the command line and post any output (hint, use the -v option)
Thanks: Albert
openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Thanks for your suggestion, I copy here the config file, the journal output later - after work # port for HTTP (descriptions, SOAP, media transfer) traffic port=8200 # network interfaces to serve, comma delimited network_interface=enp2s0, wlp3s0 # specify the user account name or uid to run as user=root # set this to the directory you want scanned. # * if you want multiple directories, you can have multiple media_dir= lines # * if you want to restrict a media_dir to specific content types, you # can prepend the types, followed by a comma, to the directory: # + "A" for audio (eg. media_dir=A,/home/jmaggard/Music) # + "V" for video (eg. media_dir=V,/home/jmaggard/Videos) # + "P" for images (eg. media_dir=P,/home/jmaggard/Pictures) # + "PV" for pictures and video (eg. media_dir=PV,/home/jmaggard/digital_camera) media_dir=/home/berci/Letoltesek media_dir=P,/home/berci/Kepek # set this to merge all media_dir base contents into the root container # note: the default is no #merge_media_dirs=no # set this if you want to customize the name that shows up on your clients friendly_name=TumbleweedDLNA # set this if you would like to specify the directory where you want MiniDLNA to store its database and album art cache db_dir=/var/cache/minidlna # set this if you would like to specify the directory where you want MiniDLNA to store its log file log_dir=/var/log/minidlna # set this to change the verbosity of the information that is logged # each section can use a different level: off, fatal, error, warn, info, or debug #log_level=general,artwork,database,inotify,scanner,metadata,http,ssdp,tivo=warn # this should be a list of file names to check for when searching for album art # note: names should be delimited with a forward slash ("/") album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg # set this to no to disable inotify monitoring to automatically discover new files # note: the default is yes inotify=yes # set this to yes to enable support for streaming .jpg and .mp3 files to a TiVo supporting HMO enable_tivo=no # set this to beacon to use legacy broadcast discovery method # defauts to bonjour if avahi is available tivo_discovery=bonjour # set this to strictly adhere to DLNA standards. # * This will allow server-side downscaling of very large JPEG images, # which may hurt JPEG serving performance on (at least) Sony DLNA products. strict_dlna=no # default presentation url is http address on port 80 #presentation_url=http://www.mylan/index.php # notify interval in seconds. default is 895 seconds. notify_interval=900 # serial and model number the daemon will report to clients # in its XML description serial=12345678 model_number=1 # specify the path to the MiniSSDPd socket #minissdpdsocket=/var/run/minissdpd.sock # use different container as root of the tree # possible values: # + "." - use standard container (this is the default) # + "B" - "Browse Directory" # + "M" - "Music" # + "V" - "Video" # + "P" - "Pictures" # + Or, you can specify the ObjectID of your desired root container (eg. 1$F for Music/Playlists) # if you specify "B" and client device is audio-only then "Music/Folders" will be used as root root_container=B # always force SortCriteria to this value, regardless of the SortCriteria passed by the client #force_sort_criteria=+upnp:class,+upnp:originalTrackNumber,+dc:title # maximum number of simultaneous connections # note: many clients open several simultaneous connections while streaming #max_connections=50 # set this to yes to allow symlinks that point outside user-defined media_dirs. #wide_links=no ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
oszko@chem.u-szeged.hu wrote:
Idézet (Dave Howorth <dave@howorth.org.uk>):
If you want help, then I would suggest posting the contents of your config file, since you've changed it.
You might also see what messages it has put in the journal and post those and/or run the daemon from the command line and post any output (hint, use the -v option)
Log output, journal messages ? You could also try running it in the foreground, start it up like systemd would. -- Per Jessen, Zürich (2.6°C) Member, openSUSE Heroes
In data mercoledì 25 novembre 2020 12:37:34 CET, Stakanov ha scritto:
In data mercoledì 25 novembre 2020 08:30:17 CET, oszko@chem.u-szeged.hu ha scritto:
# specify the user account name or uid to run as user=root
Are you sure about this bit? minidlna AFAIK in Linux runs as nobody:nobody by default
And referring to a user in the debian support forum who got a problem to open sqlite:
looking in the services directory I found that minidlna.service file had "minidlna" as GROUP and USER parameters.> I modified the access rights as follows to access the database folder : sudo chown -R minidlna.minidlna /var/cache/minidlna
http://forums.debian.net/viewtopic.php?t=126831 (IMO 90% of minidlna problems are permission problems).
Idézet (Stakanov <stakanov@disroot.org>):
In data mercoledì 25 novembre 2020 12:37:34 CET, Stakanov ha scritto:
In data mercoledì 25 novembre 2020 08:30:17 CET, oszko@chem.u-szeged.hu ha scritto:
# specify the user account name or uid to run as user=root
Are you sure about this bit? minidlna AFAIK in Linux runs as nobody:nobody by default
And referring to a user in the debian support forum who got a problem to open sqlite:
looking in the services directory I found that minidlna.service file had "minidlna" as GROUP and USER parameters.> I modified the access rights as follows to access the database folder : sudo chown -R minidlna.minidlna /var/cache/minidlna
http://forums.debian.net/viewtopic.php?t=126831
(IMO 90% of minidlna problems are permission problems). _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Thanks for your hints, I am still struggling. In the meantime I took my old Linix Mint computer, and installed minidlna. Installed without a flaw. Albert ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
In data mercoledì 25 novembre 2020 19:09:11 CET, oszko@chem.u-szeged.hu ha scritto:
Idézet (Stakanov <stakanov@disroot.org>):
In data mercoledì 25 novembre 2020 12:37:34 CET, Stakanov ha scritto:
In data mercoledì 25 novembre 2020 08:30:17 CET, oszko@chem.u-szeged.hu ha scritto:
# specify the user account name or uid to run as user=root
Are you sure about this bit? minidlna AFAIK in Linux runs as nobody:nobody by default
And referring to a user in the debian support forum who got a problem to open sqlite:
looking in the services directory I found that minidlna.service file had "minidlna" as GROUP and USER parameters.> I modified the access rights as follows to access the database folder :
sudo chown -R minidlna.minidlna /var/cache/minidlna
http://forums.debian.net/viewtopic.php?t=126831
(IMO 90% of minidlna problems are permission problems). _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Thanks for your hints, I am still struggling. In the meantime I took my old Linix Mint computer, and installed minidlna. Installed without a flaw.
Albert Since I, apparently without me wanting an noticing it (call it a stochastic event) did create a aa-profile that made my life miserable with unbound:
If possible make sure all error possibilities are gone. So, provided you can try the machine in house with a local address, switch off firewall and AppArmor. Further: when running minidlna in a jail in freebsd, you need to make sure it has permissions to the target dataset. I think this is true also for Linux. So either nobody:nobody does have to have read rights (some clients need read and write rights) to the data pool or if you create a user with the name minidlna:minidlna (user:group) - which might be safer than nobody, if other daemons are or would be running as nobody, then the permissions for this user have to be set alike. And they should be inherited, otherwise you are going to create a new folder with new files and e.g. the client will not to be able to see them or at least not to traverse. Generally I found it useful having ACL as permissions. So in snap, I do not know if this behaves like a jail or a chroot. And were you have to set any permissions. For sure it could be that the directories and commands listed in /usr/local/etc/minidlna.conf are under snap different from the default. Check also the indications of "rc.d" (I do not know if it is the same under linux as free bsd) There: code: command_args="-P $pidfile -u $minidlna_uid -f /usr/local/etc/minidlna.conf" and add -R to make the line read Code: command_args="-R -P $pidfile -u $minidlna_uid -f /usr/local/etc/minidlna.conf" have a look also if there is a readme file that came with the package. The problem is I do not know how snap behaves with permissions, cannot help you on that.
Idézet (Stakanov <stakanov@disroot.org>):
In data mercoledì 25 novembre 2020 19:09:11 CET, oszko@chem.u-szeged.hu ha scritto:
Idézet (Stakanov <stakanov@disroot.org>):
In data mercoledì 25 novembre 2020 12:37:34 CET, Stakanov ha scritto:
In data mercoledì 25 novembre 2020 08:30:17 CET, oszko@chem.u-szeged.hu ha scritto:
# specify the user account name or uid to run as user=root
Are you sure about this bit? minidlna AFAIK in Linux runs as nobody:nobody by default
And referring to a user in the debian support forum who got a problem to open sqlite:
looking in the services directory I found that minidlna.service file had "minidlna" as GROUP and USER parameters.> I modified the access rights as follows to access the database folder :
sudo chown -R minidlna.minidlna /var/cache/minidlna
http://forums.debian.net/viewtopic.php?t=126831
(IMO 90% of minidlna problems are permission problems). _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Thanks for your hints, I am still struggling. In the meantime I took my old Linix Mint computer, and installed minidlna. Installed without a flaw.
Albert Since I, apparently without me wanting an noticing it (call it a stochastic event) did create a aa-profile that made my life miserable with unbound:
If possible make sure all error possibilities are gone. So, provided you can try the machine in house with a local address, switch off firewall and AppArmor. Further: when running minidlna in a jail in freebsd, you need to make sure it has permissions to the target dataset. I think this is true also for Linux. So either nobody:nobody does have to have read rights (some clients need read and write rights) to the data pool or if you create a user with the name minidlna:minidlna (user:group) - which might be safer than nobody, if other daemons are or would be running as nobody, then the permissions for this user have to be set alike. And they should be inherited, otherwise you are going to create a new folder with new files and e.g. the client will not to be able to see them or at least not to traverse. Generally I found it useful having ACL as permissions.
So in snap, I do not know if this behaves like a jail or a chroot. And were you have to set any permissions. For sure it could be that the directories and commands listed in /usr/local/etc/minidlna.conf are under snap different from the default. Check also the indications of "rc.d" (I do not know if it is the same under linux as free bsd) There: code: command_args="-P $pidfile -u $minidlna_uid -f /usr/local/etc/minidlna.conf" and add -R to make the line read Code: command_args="-R -P $pidfile -u $minidlna_uid -f /usr/local/etc/minidlna.conf"
have a look also if there is a readme file that came with the package.
The problem is I do not know how snap behaves with permissions, cannot help you on that. _______________________________________________ openSUSE Users mailing list -- users@lists.opensuse.org To unsubscribe, email users-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/users@lists.opensuse.org
Well, thanks for the tips, unfortunately none of them worked. So I removed minidlna and began to read. And finally found that the Tumbleweed Oss repo contains minidlna. Installed, started and voila! Sorry for bothering you. Albert ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
participants (4)
-
Dave Howorth -
oszko＠chem.u-szeged.hu -
Per Jessen -
Stakanov