Menu

#322 minidlna.c:613: error: Media directory ... [Permission denied]

v1.0 (example)
open
nobody
None
5
2019-02-26
2019-02-10
sanyix
No

I've moved my system to a new pc, and i got the minidlna.c:613: error: Media directory ... [Permission denied] errors when i start minidlna daemon, which set to use minidlna user, and group. minidlna user is added to my own group, which is the owner of the media directory, and have 770 rights.
Everything is owned by that group, recursively. Then i done a minidlnad -R it indexed the "permission denied" files, and when i started the daemon, it worked... until the next reboot, after that again permission denied.

Discussion

  • Shrimpkin

    Shrimpkin - 2019-02-18

    Which version are you using? Any patches? The minidlna.c:613 error is not maching up with v1.2.1. Post the full error messages.

    A couple things to consider: Double check all your permissions. Check your init or systemd settings, configs, and scripts.

     
  • daxter852

    daxter852 - 2019-02-25

    Hi, I spent the last couple of hours trying to figure out the problem. Add this file called /etc/systemd/system/minidlna.service .

    [Unit]
    Description=minidlna server
    After=network.target
    
    [Service]
    Type=simple
    User=minidlna
    Group=minidlna
    ExecStart=/usr/bin/minidlnad -S
    ProtectSystem=full
    PrivateDevices=on
    NoNewPrivileges=on
    
    [Install]
    WantedBy=multi-user.target
    

    I removed "ProtectHome=on" from the default systemd configuration. This should not be on by default!!!!!!

     
  • daxter852

    daxter852 - 2019-02-25

    I would call this a bug. If it works when launched manually, it should work when launched with systemd.

     
    • Shrimpkin

      Shrimpkin - 2019-02-25

      I removed "ProtectHome=on" from the default systemd configuration. This should not be on by default!!!!!!

      Report systemd configuration issues with your distro.

      I would call this a bug.

      I would call systemd a bug too. Remove it and use another init system.
      https://suckless.org/sucks/systemd
      http://without-systemd.org

       
      • daxter852

        daxter852 - 2019-02-25

        I would call systemd a bug too. Remove it and use another init system.
        https://suckless.org/sucks/systemd
        http://without-systemd.org

        I like it so far.

        Report systemd configuration issues with your distro.

        I'm on Arch Linux (new install as of last week).

         
        • Shrimpkin

          Shrimpkin - 2019-02-25

          I like it so far.

          Your problem is related to a systemd security feature.

          I'm on Arch Linux (new install as of last week).

          You should learn to use your distro's wiki.
          https://wiki.archlinux.org/index.php/ReadyMedia#Troubleshooting

           
          • daxter852

            daxter852 - 2019-02-25

            Your problem is related to a systemd security feature.
            Yes, which was enabled for no reason in your shitty project.

             
            👍
            1
            • Shrimpkin

              Shrimpkin - 2019-02-26

              which was enabled for no reason

              ProtectHome feature protects the home/user directory. According to ArchWiki, ProtectHome=on is default for *all* services.

              I removed "ProtectHome=on" from the default systemd configuration. This should not be on by default!!!!!!

              Your distro's forum is your best option to try to change the default.

              Edit: Arch Linux provides the systemd configuration for minidlna.service. Voice your concerns to Arch Linux package maintainer.
              https://www.archlinux.org/packages/community/x86_64/minidlna/

               

              Last edit: Shrimpkin 2019-02-27

Log in to post a comment.