I had a problem where Mylar had stopped fetching new issues. I hadn't had any new downloads in almost a month. I restarted Mylar and it fetched some newer (from last week) issues but there are still several issues from over the prior weeks that are not being fetched. I can search for them and find them in DogNZB.
I'm running git build 6a1f96167cf9cad6bf2e0ef7881b398e75b98169 on Python 2.7.15 on a Windows 10 VM
This is the excerpt from the log when i just tried a manual search for a wanted issue:
2019-07-17 09:11:24 INFO Update complete
2019-07-17 09:11:24 DEBUG ReScheduled job: DB Updater to 2019-07-17 13:16:24
2019-07-17 09:11:23 DEBUG Refresh sequence set to fire every 5 minutes for 7 day(s)
2019-07-17 09:06:24 INFO Update complete
2019-07-17 09:06:23 DEBUG ReScheduled job: DB Updater to 2019-07-17 13:11:23
2019-07-17 09:06:23 DEBUG Refresh sequence set to fire every 5 minutes for 7 day(s)
2019-07-17 09:02:41 INFO [WANTED-SEARCH] Now Queueing Star Wars (2015) #67 for search
2019-07-17 09:02:41 INFO Initiating manual search for Star Wars issue: 67
2019-07-17 09:02:41 DEBUG mode: want
2019-07-17 09:02:41 DEBUG ComicID: 79398
2019-07-17 09:02:05 DEBUG If you can read this message, debug logging is now working
2019-07-17 09:02:05 INFO Verbose (DEBUG) logging is enabled
I just did a complete restart of Mylar. Tried a manual search again and it found the Star Wars issue right away. It seems that there is something that is preventing the search from running properly after Mylar runs for some period of time. Could it be related to this viewtopic.php?f=8&t=2149
My Mylar still rarely finds any amount of comics. I had a thread about it, but figured it was the RAM, I changed it out and it seemed to work, but then the next week it still wasn't grabbing but a 5 or 10 copies at a time, then I'd have to restart Mylar in order for it to find anything again.
I ended up getting rid of the 4 sticks of RAM (16 GB total) and went to two 8 GB sticks. Then I ran into an issue where my video card died (didn't know that was the problem,seemed like the RAM issue again) and swapped out both cpu and motherboard.
And... nothing, still Mylar is the only one that doesn't work. I've kind of just resigned the fact that something is a miss. I download my issues that don't get downloaded with newsleecher and let the Post processing move the files.
Everything worked fine up until I think the changing of the folder names. when nothing with '/' would download and the program would hang trying to refresh files. Despite me going through every single title until I didn't have any of those any more. It still will only grab 5 or so files then do nothing. Reboot Mylar, and 5 or 10 files download. That was a bit much to manage so I just grab them manually once and be done with it.
None of the other programs I use have this issue, so I figured it was Mylar. Or more something to do with Python maybe? As sonarr, lidarr and radarr are not programed in Python. /shrug. I dunno what the real culprit is, and Evilhero, god bless him, he's tried to help but it just seems to be some random issue on my end possibly.
And I have updated Python a few times throughout. I'm not on the latest Python at the moment tho.
vmcosco - can you post the real log, rather than a copy/paste from the logs web page? There is a lot that makes the log on disk that gets filtered out of the web page (including everything needed to diagnose this problem)
Hmm. Weirdly, I have the same issues. Ever since I upgraded my installation from Evilhero/Mylar to Mylar3/Mylar (Python3 version), Mylar only performs a search for comics right after startup. After that, it no longer performs scheduled or manual searches, instead just giving me these messages every 5 minutes:
This thread is over a year old, and has been fixed since this issue was regarding the python2 version of Mylar.
As you haven't posted anything about which branch and commit you are running, or what version of python - all of these need to be addressed.
Please start a new thread with the relevant info, and post your carepackage file (with mylar in debug mode hopefully for a whole prior to this), so it can be looked into properly.
Thanks evilhero; I will, after doing some research first (I feel it's the RSS parser that crashes, so I disabled RSS feeds for now and want to check if the problem persists or not). Once I know more, I'll create a new thread will all the necessary info.