Error Code 128 about nzbtomedia HOT 13 OPEN

if you moved from NZBGet to SABnzbd is this the same nzbToMedia setup?
Do NZBGet and SABnzbd run as different users? if so, that could explain most of the issues.

I would recommend doing a chown -R to the nzbToMedia directory to set the ownership tot he user that runs SABnzbd.

from nzbtomedia.

if you moved from NZBGet to SABnzbd is this the same nzbToMedia setup? Do NZBGet and SABnzbd run as different users? if so, that could explain most of the issues.

I would recommend doing a chown -R to the nzbToMedia directory to set the ownership tot he user that runs SABnzbd.

The docker container is new, but I was able to copy over the autoProcessMedia.cfg from nzbget to sabnzbd.
I spun up the old docker-nzbget container (haven't deleted it yet) to compare permissions/ownership of the nzbToMedia folder and they seem to be the same as docker-sabnzbd.
I used this guide to create a user that's limited to docker.
The docker .yaml is set to launch the container and run as uid 1028 / gid 100 which is the dockerlimited user as per the guide.

When I go into the console of the container I get this:
root@50aad48a40e7:/# id
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)

from nzbtomedia.

so inside the container, when sabnzbd is running, what user does sabnzbd run as?
If this is dockerlimited, then that should be the owner of the nzbToMedia directory

Try the following from the console of the container.
chown -R dockerlimited:user /config/scripts/nzbToMedia

or
chown -R 1028:100 /config/scripts/nzbToMedia

from nzbtomedia.

I might talk it over with "Dr. Frankenstein" - the author of the guides. I've got him on my Discord. Will get back to you.

Would this make sense that it's user: abc ?

root@9c9fb9667027:/# ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 204 20 ? Ss Mar01 0:00 /package/admin/s6/command/s6-svscan -d4 -- /run/servic
root 15 0.0 0.0 208 8 ? S Mar01 0:00 s6-supervise s6-linux-init-shutdownd
root 24 0.0 0.0 196 0 ? Ss Mar01 0:00 /package/admin/s6-linux-init/command/s6-linux-init-shu
root 37 0.0 0.0 208 12 ? S Mar01 0:00 s6-supervise s6rc-oneshot-runner
root 38 0.0 0.0 208 16 ? S Mar01 0:00 s6-supervise s6rc-fdholder
root 39 0.0 0.0 208 12 ? S Mar01 0:00 s6-supervise svc-sabnzbd
root 47 0.0 0.0 184 0 ? Ss Mar01 0:00 /package/admin/s6/command/s6-ipcserverd -1 -- /package
abc 134 2.3 0.2 130064 98348 ? Ssl Mar01 8:26 python3 /app/sabnzbd/SABnzbd.py --config-file /config
root 182 0.0 0.0 2596 488 pts/0 Ss+ Mar01 0:00 bash
root 501 0.0 0.0 2596 1732 pts/1 Ss+ Mar01 0:00 bash
root 528 0.0 0.0 2600 1820 pts/2 Ss+ Mar01 0:00 bash
root 1241 0.0 0.0 2596 2284 pts/3 Ss+ Mar01 0:00 bash
root 1421 0.0 0.0 2600 2324 pts/4 Ss+ Mar01 0:00 bash
root 1592 0.0 0.0 2596 2276 pts/5 Ss+ Mar01 0:00 bash
root 1647 0.0 0.0 2596 2324 pts/6 Ss+ 01:59 0:00 bash
root 1804 0.0 0.0 2588 2272 pts/7 Ss 04:52 0:00 bash
root 1814 0.0 0.0 1708 840 pts/7 R+ 04:52 0:00 ps -aux

from nzbtomedia.

ok... so the user is abc... and that is the owner of nzbToMedia.
So I can't see why that is detecting a dubious ownership.

the other thing to try is
git config --global --add safe.directory /config/scripts/nzbToMedia
this should ignore those warnings and keep doing the git check. Hopefully this also completes the git cleanup.

from nzbtomedia.

I know - strange isn't it?
I've tried the git config line - no change on this.
That error doesn't go away either on the 2nd run.

from nzbtomedia.

Perhaps if this was cloned as root, the ownership hasn't been set for the .git directory?
what is the ownership of /config/scripts/nzbToMedia/.git

perhaps try chown -R abc:abc /config/scripts/nzbToMedia/.git

from nzbtomedia.

I did chown -R abc:abc /config/scripts/nzbToMedia

Here's the output now:

`/app/sabnzbd/scripts/nzbToMedia/libs/common/beets/mediafile.py:19: UserWarning: beets.mediafile is deprecated; use mediafile instead
warnings.warn("beets.mediafile is deprecated; use mediafile instead")
[05:09:05] [INFO]::MAIN: Loading config from [/app/sabnzbd/scripts/nzbToMedia/autoProcessMedia.cfg]
[05:09:05] [INFO]::MAIN: Python v3.10 will reach end of life in 1309 days.
[05:09:05] [INFO]::MAIN: Checking database structure...
[05:09:05] [INFO]::MAIN: Database upgrade required: Initial Schema
[05:09:05] [INFO]::MAIN: Version checking is disabled, not checking for the newest version
[05:09:05] [INFO]::MAIN: nzbToMedia Version:12.1.11 Branch:master (Linux 4.4.180+)
[05:09:05] [INFO]::MAIN: #########################################################
[05:09:05] [INFO]::MAIN: ## ..::[nzbToMedia.py]::.. ##
[05:09:05] [INFO]::MAIN: #########################################################
[05:09:05] [INFO]::MAIN: Script triggered from SABnzbd 3.7.2.
[05:09:05] [INFO]::MAIN: Auto-detected SECTION:Radarr
[05:09:05] [INFO]::MAIN: Calling Radarr:movies to post-process:M3gan.2022.UNRATED.720p.WEB.h264-SKYFiRE
[05:09:05] [INFO]::MAIN: Attemping imdbID lookup for M3gan.2022.UNRATED.720p.WEB.h264-SKYFiRE
[05:09:05] [INFO]::MAIN: Searching folder and file names for imdbID ...
[05:09:05] [INFO]::MAIN: Searching IMDB for imdbID ...
[05:09:06] [INFO]::MAIN: Found imdbID [tt8760708]
[05:09:06] [POSTPROCESS]::RADARR: Starting DownloadedMoviesScan scan for M3gan.2022.UNRATED.720p.WEB.h264-SKYFiRE
[05:09:06] [POSTPROCESS]::RADARR: Checking for status change, please stand by ...
[05:10:06] [POSTPROCESS]::RADARR: Checking for status change, please stand by ...
[05:10:06] [INFO]::MAIN: The /app/sabnzbd/scripts/nzbToMedia/nzbToMedia.py script completed successfully.
Changing to directory: /app/sabnzbd/scripts/nzbToMedia

-- Cleaning bytecode --
b'Removing pycache/\n'
b'Removing pycache/\n'

-- Cleaning folders: ['libs', 'core'] --
No folders to clean

Returning to directory: /app/sabnzbd

-- Cleanup finished --

Radarr: Successfully post-processed M3gan.2022.UNRATED.720p.WEB.h264-SKYFiRE!`

from nzbtomedia.

@clinton-hall is the above log output a "successful" one?

from nzbtomedia.

it looks successful from what I can see. I note that it did not check git version.
In autoProcessMedia.cfg it looks like you must have

[General]
    version_notify = 0

to check and update you would need to set

[General]
    version_notify = 1

from nzbtomedia.

@clinton-hall I updated the .cfg file and it is now checking for updates.

However, I am intrigued by what this is:
/app/sabnzbd/scripts/nzbToMedia/libs/common/beets/mediafile.py:19: UserWarning: beets.mediafile is deprecated; use mediafile instead
warnings.warn("beets.mediafile is deprecated; use mediafile instead")

Future update coming?

from nzbtomedia.

yeah potentially: #1959
the issue is we can't move to mediafile until python2.7 is dropped.

from nzbtomedia.