Issues with ddl and post processing

[Hellers]

I've just installed a fresh copy of Mylar3 in docker on my new Qnap NAS. I got everything configured, added a few titles and downloaded a few issues via ddl. For some reason they're sitting in the cache folder and not being moved to the correct place.

I can see an entry in the logs like this for each issue
22-Sep-2023 17:08:25 - INFO :: mylar.ddl_downloader.3224 : DDL-QUEUE : Now loading request from DDL queue: Catwoman #1 (2018)
22-Sep-2023 17:08:26 - INFO :: mylar.ddl_downloader.3262 : DDL-QUEUE : Catwoman 001 (2018) (2 covers) (Digital) (Oracle-SWA)[__675948__].cbr successfully downloaded - now initiating post-processing for /config/mylar/cache/Catwoman 001 (2018) (2 covers) (Digital) (Oracle-SWA)[__675948__].cbr

But then nothing else happens. I'm not entirely sure how to put Mylar in debug mode on the QNap yet. Still looking. Can you think of anything simple that might be causing it?

I've got storage attached to the container and Mylar will create the series folders no problem.

[Hellers]

I turned on debug logs but it's not showing anything. I ran a manual post process on the cache folder and that seems to work. So I'm not sure why it's not happening automatically

[Hellers]

Some log examples (It does nothing after this)

2023-09-22 17:46:43 INFO Hawkgirl 01 (of 06) (2023) (digital) (Son of Ultron-Empire)[__1001513__].cbr successfully downloaded - now initiating post-processing for /config/mylar/cache/Hawkgirl 01 (of 06) (2023) (digital) (Son of Ultron-Empire)[__1001513__].cbr
2023-09-22 17:46:31 DEBUG remote filesize: 111533142
2023-09-22 17:46:31 DEBUG filename: Hawkgirl 01 (of 06) (2023) (digital) (Son of Ultron-Empire)[__1001513__].cbr
2023-09-22 17:46:30 INFO Now loading request from DDL queue: Hawkgirl #1 (HD-Digital)
2023-09-22 17:46:29 DEBUG I found Hawkgirl #1
2023-09-22 17:46:29 DEBUG findit = found!
2023-09-22 17:46:29 INFO findit: {'status': True, 'provider': 'DDL(GetComics)', 'lastrun': 1695404772.62214, 'info': {'nzbid': '309641', 'nzbname': 'Hawkgirl #1 (2023)', 'sent_to': 'is downloading it directly via DDL(GetComics)', 'SARC': None, 'alt_nzbname': None, 't_hash': None}}
2023-09-22 17:46:29 DEBUG booktype:None / chktpb: 0 / findloop: 99
2023-09-22 17:46:29 INFO [UPDATER] Updated the status (Snatched) complete for Hawkgirl Issue: 1
2023-09-22 17:46:29 DEBUG [UPDATER] Provider is DDL(GetComics)
2023-09-22 17:46:29 INFO [UPDATER] Updating status to snatched
2023-09-22 17:46:29 DEBUG [UPDATER] issueid: 1001513
2023-09-22 17:46:29 DEBUG [UPDATER] comicid: 152245
2023-09-22 17:46:29 INFO setting the nzbid for this download grabbed by DDL(GetComics) in the nzblog to : 309641
2023-09-22 17:46:29 DEBUG Found matching comic...preparing to send to Updater with IssueID: 1001513 and nzbname: Hawkgirl #1 (2023)

[Hellers]

I've changed my ddl_location to the folder I use for monitoring. Now stuff post processes but after it finished the last one the folder gets deleted.

[Hellers]

Ah. That's fine. Both sabnzbd and Mylar will recreate it as needed. Problem resolved for me. Thanks for your reply to the other guy having the same problem recently. That seems to have fixed things for me. Cheers

[evilhero]

I've changed my ddl_location to the folder I use for monitoring. Now stuff post processes but after it finished the last one the folder gets deleted.

Don't set you ddl_location to your folder monitor location, like ever. What will happen is the monitor will kick off while it's trying to post-process something and cause a race condition and then fail to process at all (or leave a broken file in its place). There are checks in place to try and stop it from happening cause people still try to do it, instead of figuring out what the actual problem is - resulting in partially downloaded files or constant errors during post-processing.

The folder monitor should only used for items that you want post-processed that you've obtained outside of mylar.

If it's not post-processing during a download via ddl, then the issue is the perms on the cache are too stringent most likely. Or you have enforce perms turned on which you shouldn't do if you're using synology since they have their own messed up way of enforcing permissions.