you either need to allow the user Mylar runs as (media, UID=816) to write to that dataset (Solution #1,3,4), or you need to change the user Mylar runs as (Solution #2).Looks like theres a permission issue. The jail cant create directories in the dataset I created...
does mylar use the transmission api to send it the torrent file? (you would be entering the transmission's IP, port, and username/pass if you have one). in that case, for passing the torrent file, permissions do not matter.Joshua, so it looks like Mylar(816) is attempting to hand a torrent file to Transmission(921). What's the best solution when one jail is trying to send another jail data?
I would double check the IP is for the transmission jail. usually where you enter the details there is a test buttonYes it does. So my diagnosis is incorrect.
Appreciate the reply, btw.
2017-02-20 14:21:46 ERROR incomplete format 2017-02-20 14:21:46 ERROR Unable to send torrent - check logs and settings (this would be marked as a BAD torrent if Failed Handling was enabled)
Transmission Host: (IPaddress:9091) Transmission Username: (blank as I do not have Auth required) Transmission Password: (blank as I do not have Auth required) Transmission Directory: /media/comics (matching my jail storage mapping)
Couldn't read "/var/db/mylar/cache/comicname.torrent": Permission denied (utils.c:258)
can you show 'ls -l /var/db/mylar/cache' in the transmission jail.And now it's broke again. Same errors on Mylar. I enabled logging on transmission and found this error when Mylar kicks a torrent over to Transmission:
Code:Couldn't read "/var/db/mylar/cache/comicname.torrent": Permission denied (utils.c:258)
That folder is owned by media:media. I added the transmission user to the media group and it still gives me that error.
can you show 'ls -l /var/db/mylar/cache' in the transmission jail.
root@transmission_1:/ # ls -l /var/db/mylar/cache total 70472 -rw------- 1 media media 494 Mar 8 21:24 .32p_cookies.dat -rw------- 1 media media 366673 Mar 8 20:55 96284.jpg -rw------- 1 media media 0 Mar 8 22:04 Clean-newreleases.txt -rw------- 1 media media 31886 Mar 8 21:24 Doctor_Aphra_2_2017.torrent -rw------- 1 media media 24273 Mar 8 21:09 Doctor_Aphra_5_2017.torrent -rw------- 1 media media 31886 Mar 8 21:24 Star_Wars_Doctor_Aphra_2_2017. torrent -rw------- 1 media media 24273 Mar 8 21:09 Star_Wars_Doctor_Aphra_5_2017. torrent -rw------- 1 media media 25052 Mar 8 22:04 newreleases.txt -rw------- 1 media media 2503504 Mar 8 20:51 temp.jpg -rwxrwxrwx 1 media media 69083502 Mar 8 20:51 temp.zip
mylar is writting those files in a way only the owner user can read/write them. I'm not sure if mylar chooses the permissions it writes with, or if these are just inherited by the directory it is in.Code:root@transmission_1:/ # ls -l /var/db/mylar/cache total 70472 -rw------- 1 media media 494 Mar 8 21:24 .32p_cookies.dat -rw------- 1 media media 366673 Mar 8 20:55 96284.jpg -rw------- 1 media media 0 Mar 8 22:04 Clean-newreleases.txt -rw------- 1 media media 31886 Mar 8 21:24 Doctor_Aphra_2_2017.torrent -rw------- 1 media media 24273 Mar 8 21:09 Doctor_Aphra_5_2017.torrent -rw------- 1 media media 31886 Mar 8 21:24 Star_Wars_Doctor_Aphra_2_2017. torrent -rw------- 1 media media 24273 Mar 8 21:09 Star_Wars_Doctor_Aphra_5_2017. torrent -rw------- 1 media media 25052 Mar 8 22:04 newreleases.txt -rw------- 1 media media 2503504 Mar 8 20:51 temp.jpg -rwxrwxrwx 1 media media 69083502 Mar 8 20:51 temp.zip
strange, one thing to try is to change the directory permissions and see if future torrent files follow that.
chmod 775 /var/db/mylar/cache
yeah, or the 'media' user.As root?
you tried a new download and the torrent file still had 600 permissions?no effect with chmod