Closed DrSeussFreak closed 6 years ago
/media/comics/Avatar/Crossed Plus One Hundred Mimic [2018] has 777 permissions owned by nobody:users and the files underneath are the same.
Renaming works without issue, so it clearly has permissions.
Does metatagging work with other issues or just this one in particular ? If it's for everything, then the odds are good that it's still a permissions issue of some kind. You'd have to check the /opt/Mylar/cache/ folder that's being used for the particular tagging to see if/what any files exist therein. If it's failing to extract there would be just the .cbr, if it's failing to convert there should be a cbr and a folder full of jpgs (or the .cbz partially). It hasn't gotten to the moving to the final destination part as that happens after the actual tagging occurs, which is after conversion.
How are you running the metatagging option ?
It could still be permissions - since it copies/moves the file from the source location to the destination (/opt/Mylar/cache/) folder for tagging and then attempts to move it out thereafter. Renaming also doesn't move the file from point A to point B, but simply renames the file itself. Permissions don't come into play since the source and destination are the same.
It is every issue, I used that as an example. I have run the following numerous times, and it has stuck.
chown -R mylar:mylar /opt/Mylar && chmod -R 777 /opt/Mylar
I am click on an individual issue, the metatag option there, to do it. This was for a file I manually donwloaded (the name didn't meet with the configured convention, so I did it manually), but for issues Mylar grabbed and moved itself, this also failed. It was able to move the files, no problem, renaming them in the process, but it was unable to convert it.
So it may be a permissions issue, but I am not sure how or what.
Can you try something with permissions in the source location? Can you change the perms on the file you're metatagging to be mylar:mylar instead of nobody:users and making sure that the perms are set to at least 775 for testing purposes. Then try the metatagging again on that specific issue and see what happens
So /media is a CFIS share to my NAS, the users don't map, hence the nobody:user ownership. /SabNZBd is a NFS share to another Ubuntu box, and it is able to copy comics from /SabNZBd to /media, renaming them & setting permissions in the process. If I su - to mylar, I can create a file, and remove it in /media/comics/Avatar/*
Which box does the mylar application reside on?
If it can't create a file with the proper perms, it will default to your CIFS default perm settings which I'm guessing might not be set for default usage (most people dont set it unless they're having problems)
mylar sits on "media-01" (Ubuntu 18.04) sabnzbd sites on "sabnzbd-01" (Ubuntu 18.04) /media is on NAS "nx-01" (Synology)
/etc/fstab is configured as follows
//nx-01/comics /media/comics cifs credentials=/home/dsf/.smbcredentials,uid=nobody,gid=users,iocharset=utf8,noperm,sec=ntlm,vers=1.0 0 0
Tagging in on this given that I run CIFS and evilhero doesnt... it sounds like you're able to create files but not update them. Sounds weird, I know, but CIFS does allow that possibility...
What's the real ACL on \\nx-01\comics (both the share ACL and the filesystem ACL)? What's in your .smbcredentials file (dont post the password)?
on NX-01, it is all GUI based, and it is mapped to the dsf user as r/w permissions, there is nothing special there. As for Ubuntu, not sure what you are looking for on media-01, as nothing special is configured, I just added the mylar (and sonarr and radarr) users to the users group.
/home/dsf/.smbcredentials contains
username=dsf password=NotMyRealPW
In CIFS there's a concept of a dropbox - you can write a file once but never modify it again. That's what I was hoping to see in the ACL.
Just for giggles - can you create a text file in /media/comics while sudo'ed to the mylar user, and save it? then try and edit/save the same file and see if it sticks...
Just created a file, saved/quit, opened it, changed it, saved/quit - 4 times over, no problems.
I have sonarr and radarr running on the same machine (same setup but with radarr and sonarr accounts), they have no problems changing anything on the /media CIFS share
okay... sounds like it's not a dropbox...
Another thought - on your mylar ubuntu box, you do have unrar & rar installed and in the mylar user's path - right?
root@media-01:~# which rar /usr/bin/rar root@media-01:~# which unrar /usr/bin/unrar
Where would I add this to the users path?
HAH, ok, so I had just installed both, I had not thought of it, re-ran the post-processing step and it worked perfectly! Nice catch, thanks :)
great to hear!
I am running the latest release - Version: 5e6b861fadcbd6a43412e0a4e8a7cdee6e8e945c (development) and CBR --> CBZ keeps failing with this error
/opt/Mylar/cache is owned by the mylar user and group, which is the user to run Mylar, and the permissions are 777.
Debug log entry is below