Cheers (I was born and raised in Duesseldorf), I moved to Vancouver in 2009
I have met Campino a couple of times and was a NOKIA VIP guest of that legendary Leningrad Cowboys Concert/Hockey game in the 90s
Now it works! I had to uninstall Python 3 before I could reinstall SABnzbd. Before reinstalling Python 3, you have to configure SBAnzbd; otherwise, it won’t start.
Ah, okay. I’m Austrian… I live in southern Styria.
I got into Die Toten Hosen through my girlfriend at the time. She’s been gone for a long time, but the Hosen have stayed… 
We need an ‘off topic’ section, so I can move our ‘blerp’ posts there.
Sorry @OnceCD for garbaging up up your topic
1 Like
No worries mate, I’ve done worse. 
1 Like
@jimpoison @campino76 I’ve removed the various available Python QPKGs as conflicts, and am testing the new packages now.
I added these a while back out of an abundance of caution, but - after re-examining this - I don’t think the other Python packages will really cause an issue.
There will be a new package release today with updated QPKG versions. 
1 Like
It works like a charm now. Thank you very much!
1 Like
I just updated sherpa and SABnzbd after the most recent upgrade and everything worked fine. I then noticed that nzbToMedia had a new version so I upgraded that as well.
Today I could see that SABnzbd had grabbed a file, but it was still in my download folder and hadn’t been processed by nzbToMedia.
SABnzbd still points to the correct script folder, but all script categories are set to default, and worse, the folder where I kept the nzbToMedia cfg files is empty. The nzbToMedia.prev folder is also empty except for an empty folder named nzbToMedia.
This was not an issue yesterday before running the upgrades, and I have no clue which program did this.
I can see the original files, all with the timestamp when it happened yesterday, in the repo-cache folder, and I can see autoProcessMedia.cfg in the same folder with my settings, but I have no idea how to get it back in a working condition.
Hi @FoP , let’s see if we can get this fixed.
What is the path to script_dir in your SABnzbd config?
getcfg misc script_dir -f $(getcfg SABnzbd Install_Path -f /etc/config/qpkg.conf)/config/config.ini
And where is your nzbToMedia QPKG installed?
getcfg nzbToMedia Install_Path -f /etc/config/qpkg.conf
/share/Download/nzbToMedia and /share/MD0_DATA/.qpkg/nzbToMedia respectively
Let’s try re-creating the symlink:
ln -sf /share/MD0_DATA/.qpkg/nzbToMedia /share/Download/nzbToMedia
Done. In the /share/Download/nzbToMedia, I now see the folder /nzbToMedia
Is there anything in that second nzbToMedia directory?
If not, delete it.
Sorry, should have mentioned that it contains everything as seen when looking directly in the /.qpkg/nzbToMedia folder, ie /repo-cache, /pip-cache etc.
Oops, my bad: that symlink we created needs adjustment.
Try this one instead:
ln -sf /share/MD0_DATA/.qpkg/nzbToMedia/repo-cache /share/Download/nzbToMedia
OK, so there’s now /repo-cache in the /Download/nzbToMedia folder, with all the contents
Excellent. So, should be OK now?
Well not really, as /share/Download/nzbToMedia originally had all the config files for setting up processing for SABnzbd, and now there are just two symlinks: one to /share/MD0_DATA/.qpkg/nzbToMedia and one to /share/MD0_DATA/.qpkg/nzbToMedia/repo-cache.
I’m wondering if I should just copy anything from the /repo-cache back as that was what it used to be.
And also, what is the /repo-cache folder, as it seems to have been created exactly when I ran one of the updates.
Both /pip-cache and /repo-cache exists in all the other qpkgs I’ve installed through sherpa, and I’m not really sure what they are. If I have my configs directly in that folder, can I risk them getting overwritten next time I upgrade?
This is a long-standing issue with nzbToMedia.
Its config and application files are all kept in the same location. Makes it hard to manage during clean, upgrade, etc… 
I’m presently working on a new nzbToMedia QPKG that will hopefully be a bit more stable, and handle upgrades better.
For your config, do what you need-to to get it running. The script files in repo-cache must be visible to SABnzbd as the “Scripts Folder”.
Those paths are used to store a local copy of the nzbToMedia repository files from GitHub, and Python modules from PyPI.
Everything in both paths is removed during an upgrade (and/or clean), so don’t store your own files and configs there.
In the new nzbToMedia, I’ll include a config path for that.