Can't add The Walking Dead

[suedester]

I've been trying to add this series for days but keep getting 500 errors. Any ideas? It actually seems to occur with any large series, 100 Bullets gives the same error for example. I'm running on a synology with the dev build.

Traceback (most recent call last): File "/volume1/@appstore/mylar/share/mylar/cherrypy/_cprequest.py", line 645, in respond response.body = self.handler() File "/volume1/@appstore/mylar/share/mylar/cherrypy/lib/encoding.py", line 188, in call self.body = self.oldhandler(_args, _kwargs) File "/volume1/@appstore/mylar/share/mylar/cherrypy/_cpdispatch.py", line 29, in call return self.callable(_self.args, _self.kwargs) File "/volume1/@appstore/mylar/share/mylar/mylar/webserve.py", line 116, in addComic gcdinfo=parseit.GCDScraper(comicname, comicyear, comicissues, comicid) File "/volume1/@appstore/mylar/share/mylar/mylar/parseit.py", line 153, in GCDScraper return GCDdetails(comseries=None, resultURL=resultURL, vari_loop=0, ComicID=ComicID, TotalIssues=TotalIssues, issvariation=issvariation, resultPublished=resultPublished) File "/volume1/@appstore/mylar/share/mylar/mylar/parseit.py", line 199, in GCDdetails soup = BeautifulSoup ( resp ) File "/volume1/@appstore/mylar/share/mylar/bs4/init.py", line 172, in init self._feed() File "/volume1/@appstore/mylar/share/mylar/bs4/init.py", line 185, in _feed self.builder.feed(self.markup) File "/volume1/@appstore/mylar/share/mylar/bs4/builder/_lxml.py", line 175, in feed self.parser.close() File "parser.pxi", line 1187, in lxml.etree._FeedParser.close (src/lxml/lxml.etree.c:88279) File "parsertarget.pxi", line 130, in lxml.etree._TargetParserContext._handleParseResult (src/lxml/lxml.etree.c:97442) File "lxml.etree.pyx", line 294, in lxml.etree._ExceptionContext._raise_if_stored (src/lxml/lxml.etree.c:8870) File "saxparser.pxi", line 259, in lxml.etree._handleSaxData (src/lxml/lxml.etree.c:93587) UnicodeDecodeError: 'utf8' codec can't decode byte 0xba in position 0: invalid start byte

Thanks.

[evilhero]

Try shutting down and restarting Mylar. That error involves the beautifulsoup parser which hasn't been having any problems recently.

[suedester]

Hmm, still not playing nice after a restart unfortunately.

[projectzero]

I was having the same issue as described above with the same comics (The Walking Dead/100 Bullets). I restarted Mylar, rebooted the nas, tried both the default install on synology AND the version Mylar updated to (Version: 1014f0c86c32694f60b5f07e6cb2d339b7531a62) and now instead of the above error, Mylar just crashes when adding the above comics and I have to restart it through the synology package manager. Any ideas?

[JohnyB666]

I am getting the exact same error on synology using version 1014f0c86c32694f60b5f07e6cb2d339b7531a62 when trying to add both comics. I tried restarting Mylar, shutting it down and starting it again and rebooting the entire NAS.

Still working under Windows 7 though...

[evilhero]

Why don't you do a manul git install of Mylar and see if that works. So many people thay are using the Synology package seem to be having problems and the issues arent appearing in normal installations.

[projectzero]

Just did a git install, got Version: 7531a62 now. Trying to add those comics still crashes the program with a Segmentation Fault. Running the same version of Mylar on my laptop in os x works just fine. The only difference I can see off the bat is my laptop runs python 2.6 and the synology runs 2.7 but I doubt it's that but who knows.

[evilhero]

Can you paste the mylar.log file contents so I can try to figure out why its faulting for you? Mylar was built on 2.7.2/2.7 3 so that's probably not the issue.

[projectzero]

This is the contents of the only mylar.log file I could find (located in the mylar directory under logs) after a brand new install and after the program crashed when trying to add 100 Bullets

22-Jan-2013 21:04:30 - INFO :: MainThread : cache set to : /volume1/@appstore/MylarM/cache 22-Jan-2013 21:04:30 - INFO :: MainThread : Checking to see if the database has all tables.... 22-Jan-2013 21:04:31 - INFO :: MainThread : Populating Base Exception listings into Mylar.... 22-Jan-2013 21:04:31 - INFO :: MainThread : Populating Custom Exception listings into Mylar.... 22-Jan-2013 21:04:31 - INFO :: MainThread : Ensuring DB integrity - Removing all Erroneous Comics (ie. named None) 22-Jan-2013 21:04:31 - INFO :: MainThread : Retrieving latest version information from github 22-Jan-2013 21:04:32 - INFO :: MainThread : Comparing currently installed version with latest github version 22-Jan-2013 21:04:32 - INFO :: MainThread : Mylar is up to date 22-Jan-2013 21:04:33 - INFO :: MainThread : Starting Mylar on port: 8085 22-Jan-2013 21:04:33 - INFO :: MainThread : Checking for existance of Weekly Comic listing... 22-Jan-2013 21:04:33 - INFO :: Thread-12 : Weekly pull list present - checking if it's up-to-date..

And that's it. After trying to add 100 Bullets/The Walking Dead Mylar just crashes completely. Not sure what changed but I used to get the error the OP described and I do rarely get the same thing but full crashes are the norm now. Here's a screenshot of terminal after it happens, the only thing it has that the log doesn't is the Segmentation Fault.

[evilhero]

Ok, that screenshot helps ALOT actually. I know exactly what the problem is....hang tight :)

projectzero: #169 has the identical problem. I just pushed the fix in the latest developmental commit.

[projectzero]

Just tested it, pulled the dev branch and am running version f0281bbc5 and still can't add those series. I got the below error once, but am now having Mylar crash just as before to a Segmentation Fault. I am able to add other comics, but it seems once they get past a certain number of issues then Mylar crashes. No idea if that's the case, or what the cutoff number is but here's a few examples:

Johnny the Homicidal Maniac (1995) - 7 issues - Added Lone Wolf and Cub (2000) - 28 issues - Added The Maxx (1993) - 36 issues - Added The Sandman (1989) - 75 issues - Crash 100 Bullets (1999) - 100 issues - Crash The Walking Dead (2003) - 105 issues - Crash Avengers Vs. X-Men (2012) - 13 issues - Crash (shoots my theory to hell now, but more examples are nice)

1 Time Error: Traceback (most recent call last): File "/volume1/@appstore/MylarD/cherrypy/_cprequest.py", line 645, in respond response.body = self.handler() File "/volume1/@appstore/MylarD/cherrypy/lib/encoding.py", line 188, in call self.body = self.oldhandler(_args, _kwargs) File "/volume1/@appstore/MylarD/cherrypy/_cpdispatch.py", line 29, in call return self.callable(_self.args, _self.kwargs) File "/volume1/@appstore/MylarD/mylar/webserve.py", line 118, in addComic gcdinfo=parseit.GCDScraper(comicname, comicyear, comicissues, comicid) File "/volume1/@appstore/MylarD/mylar/parseit.py", line 153, in GCDScraper return GCDdetails(comseries=None, resultURL=resultURL, vari_loop=0, ComicID=ComicID, TotalIssues=TotalIssues, issvariation=issvariation, resultPublished=resultPublished) File "/volume1/@appstore/MylarD/mylar/parseit.py", line 182, in GCDdetails soup = BeautifulSoup ( resp ) File "/volume1/@appstore/MylarD/bs4/init.py", line 172, in init self._feed() File "/volume1/@appstore/MylarD/bs4/init.py", line 185, in _feed self.builder.feed(self.markup) File "/volume1/@appstore/MylarD/bs4/builder/_lxml.py", line 175, in feed self.parser.close() File "parser.pxi", line 1187, in lxml.etree._FeedParser.close (src/lxml/lxml.etree.c:88279) File "parsertarget.pxi", line 130, in lxml.etree._TargetParserContext._handleParseResult (src/lxml/lxml.etree.c:97442) File "lxml.etree.pyx", line 294, in lxml.etree._ExceptionContext._raise_if_stored (src/lxml/lxml.etree.c:8870) File "saxparser.pxi", line 259, in lxml.etree._handleSaxData (src/lxml/lxml.etree.c:93587) UnicodeDecodeError: 'utf8' codec can't decode byte 0xdd in position 0: invalid continuation byte

On the plus side, looks like those few errors from my last screenshot were fixed which is great.

[suedester]

Looks very similar to the errors I'm having adding large series.

[evilhero]

If / when you get anykind of traceback error or fault or the like you NEED to shutdown Mylar and restart it. Otherwise doing subsequent actions are very volatile and most likely won't work. Paste the mylar.log file contents for the adds that fail..it eill give more verbose info within and can try to figure things out from there.

[projectzero]

Just started from scratch in a new directory on my Synology with the below steps:

1. Transferred development branch to the NAS (have also done a GIT pull, makes no difference)
2. Updated to latest dev branch eecf06b4ef685cef0226312ab489d44e66e0b290
3. Configured settings for comic location, sabnzbd location, search provider, directory settings
4. Restart Mylar through the web gui
5. Searched for 100 Bullets and clicked "Add this Comic" on the result with 100 issues
6. Mylar crashed completely.

There is no option or way to reboot from here since it's completely down. The only way to get it back up is to re-run Mylar from terminal just like I was starting it for the first time. Here is the complete log from time of install to time of crash and at least to my untrained eye it shows nothing wrong. Is there a way to get debug logging? I do have verbose logging enabled but personally the below doesn't tell me anything.

23-Jan-2013 14:45:01 - INFO :: MainThread : cache set to : /volume1/@appstore/MylarDev/cache 23-Jan-2013 14:45:01 - INFO :: MainThread : Checking to see if the database has all tables.... 23-Jan-2013 14:45:02 - INFO :: MainThread : Populating Base Exception listings into Mylar.... 23-Jan-2013 14:45:02 - INFO :: MainThread : No Custom Exceptions found - Using base exceptions only. Creating blank custom_exceptions for your personal use. 23-Jan-2013 14:45:02 - INFO :: MainThread : Ensuring DB integrity - Removing all Erroneous Comics (ie. named None) 23-Jan-2013 14:45:02 - INFO :: MainThread : Retrieving latest version information from github 23-Jan-2013 14:45:03 - INFO :: MainThread : You are running an unknown version of Mylar. Run the updater to identify your version 23-Jan-2013 14:45:03 - INFO :: MainThread : Starting Mylar on port: 8090 23-Jan-2013 14:45:03 - INFO :: MainThread : Checking for existance of Weekly Comic listing... 23-Jan-2013 14:45:03 - INFO :: Thread-12 : Weekly pull list present - checking if it's up-to-date.. 23-Jan-2013 14:45:03 - INFO :: Thread-12 : Error Retrieving weekly pull list - attempting to adjust 23-Jan-2013 14:45:04 - INFO :: Thread-12 : Preparing to update to the new listing. 23-Jan-2013 14:45:04 - INFO :: Thread-12 : Populating the NEW Weekly Pull list into Mylar. 23-Jan-2013 14:45:04 - INFO :: Thread-12 : Weekly Pull List successfully loaded. 23-Jan-2013 14:45:04 - INFO :: Thread-12 : Checking the Weekly Releases list for comics I'm watching... 23-Jan-2013 14:45:04 - DEBUG :: Thread-12 : You are watching for: 0 comics 23-Jan-2013 14:45:04 - DEBUG :: Thread-12 : There are 0 comics this week to get! 23-Jan-2013 14:45:04 - INFO :: Thread-12 : Finished checking for comics on my watchlist. 23-Jan-2013 14:45:27 - INFO :: MainThread : Received signal: update 23-Jan-2013 14:45:32 - INFO :: MainThread : Mylar is updating... 23-Jan-2013 14:45:32 - INFO :: MainThread : Downloading update from: https://github.com/evilhero/mylar/tarball/development 23-Jan-2013 14:45:36 - INFO :: MainThread : Extracing file/volume1/@appstore/MylarDev/development 23-Jan-2013 14:45:37 - INFO :: MainThread : Deleting file/volume1/@appstore/MylarDev/development 23-Jan-2013 14:45:38 - INFO :: MainThread : Mylar is restarting... 23-Jan-2013 14:45:38 - INFO :: MainThread : Restarting Mylar with ['/usr/local/python/bin/python', '/volume1/@appstore/MylarDev/Mylar.py', '--nolaunch'] 23-Jan-2013 14:45:40 - INFO :: MainThread : cache set to : /volume1/@appstore/MylarDev/cache 23-Jan-2013 14:45:40 - INFO :: MainThread : Checking to see if the database has all tables.... 23-Jan-2013 14:45:40 - INFO :: MainThread : Populating Base Exception listings into Mylar.... 23-Jan-2013 14:45:40 - INFO :: MainThread : Populating Custom Exception listings into Mylar.... 23-Jan-2013 14:45:40 - INFO :: MainThread : Ensuring DB integrity - Removing all Erroneous Comics (ie. named None) 23-Jan-2013 14:45:40 - INFO :: MainThread : Retrieving latest version information from github 23-Jan-2013 14:45:41 - INFO :: MainThread : Comparing currently installed version with latest github version 23-Jan-2013 14:45:41 - INFO :: MainThread : Mylar is up to date 23-Jan-2013 14:45:42 - INFO :: MainThread : Starting Mylar on port: 8090 23-Jan-2013 14:45:42 - INFO :: MainThread : Checking for existance of Weekly Comic listing... 23-Jan-2013 14:45:42 - INFO :: Thread-12 : Weekly pull list present - checking if it's up-to-date.. 23-Jan-2013 14:45:42 - INFO :: Thread-12 : No new pull-list available - will re-check again in 24 hours. 23-Jan-2013 14:45:42 - INFO :: Thread-12 : Checking the Weekly Releases list for comics I'm watching... 23-Jan-2013 14:45:42 - DEBUG :: Thread-12 : You are watching for: 0 comics 23-Jan-2013 14:45:42 - DEBUG :: Thread-12 : There are 0 comics this week to get! 23-Jan-2013 14:45:42 - INFO :: Thread-12 : Finished checking for comics on my watchlist. 23-Jan-2013 14:47:24 - INFO :: MainThread : Received signal: restart 23-Jan-2013 14:47:29 - INFO :: MainThread : Mylar is restarting... 23-Jan-2013 14:47:29 - INFO :: MainThread : Restarting Mylar with ['/usr/local/python/bin/python', '/volume1/@appstore/MylarDev/Mylar.py', '--nolaunch'] 23-Jan-2013 14:47:30 - INFO :: MainThread : cache set to : /volume1/@appstore/MylarDev/cache 23-Jan-2013 14:47:30 - INFO :: MainThread : Checking to see if the database has all tables.... 23-Jan-2013 14:47:30 - INFO :: MainThread : Populating Base Exception listings into Mylar.... 23-Jan-2013 14:47:30 - INFO :: MainThread : Populating Custom Exception listings into Mylar.... 23-Jan-2013 14:47:31 - INFO :: MainThread : Ensuring DB integrity - Removing all Erroneous Comics (ie. named None) 23-Jan-2013 14:47:31 - INFO :: MainThread : Retrieving latest version information from github 23-Jan-2013 14:47:31 - INFO :: MainThread : Comparing currently installed version with latest github version 23-Jan-2013 14:47:32 - INFO :: MainThread : Mylar is up to date 23-Jan-2013 14:47:32 - INFO :: MainThread : Starting Mylar on port: 8090 23-Jan-2013 14:47:32 - INFO :: MainThread : Checking for existance of Weekly Comic listing... 23-Jan-2013 14:47:32 - INFO :: Thread-12 : Weekly pull list present - checking if it's up-to-date.. 23-Jan-2013 14:47:32 - INFO :: Thread-12 : No new pull-list available - will re-check again in 24 hours. 23-Jan-2013 14:47:32 - INFO :: Thread-12 : Checking the Weekly Releases list for comics I'm watching... 23-Jan-2013 14:47:32 - DEBUG :: Thread-12 : You are watching for: 0 comics 23-Jan-2013 14:47:32 - DEBUG :: Thread-12 : There are 0 comics this week to get! 23-Jan-2013 14:47:32 - INFO :: Thread-12 : Finished checking for comics on my watchlist.

[evilhero]

Yeah that's not the verbose logging from the mylar.log file I need to see. Make sure Verbose Logging is checked off in the configuration. 2nd tab (General)..restart Mylar after the change, try the add again and after it fails chexk although the logs arent persistent after a shutdown.

[projectzero]

I've done this test with verbose logging both checked and unchecked and nothing changes in regards to what is logged. I've even gone in and modified the config.ini directly from a 1 to 0 to 1 again for verbose logging and same thing. When adding any of the series I mentioned above that crash the program, that's exactly what happens, it crashes and doesn't write anything to the log. The only hint of an issue is in the first screenshot I posted which mentions Segmentation fault but that only appears in terminal and not the logfile.

Here is one error terminal gave me when trying to add a series, but again, did NOT appear in the log file

The below error turned up in the browser after trying to add either 100 Bullets or The Walking Dead and again, did NOT appear in the log file. After each error, I restarted the program and that did not help anything. Hopefully one of these errors helps point you in the right direction.

500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last): File "/volume1/@appstore/MylarDev/cherrypy/_cprequest.py", line 645, in respond response.body = self.handler() File "/volume1/@appstore/MylarDev/cherrypy/lib/encoding.py", line 188, in call self.body = self.oldhandler(_args, _kwargs) File "/volume1/@appstore/MylarDev/cherrypy/_cpdispatch.py", line 29, in call return self.callable(_self.args, _self.kwargs) File "/volume1/@appstore/MylarDev/mylar/webserve.py", line 118, in addComic gcdinfo=parseit.GCDScraper(comicname, comicyear, comicissues, comicid) File "/volume1/@appstore/MylarDev/mylar/parseit.py", line 153, in GCDScraper return GCDdetails(comseries=None, resultURL=resultURL, vari_loop=0, ComicID=ComicID, TotalIssues=TotalIssues, issvariation=issvariation, resultPublished=resultPublished) File "/volume1/@appstore/MylarDev/mylar/parseit.py", line 199, in GCDdetails soup = BeautifulSoup ( resp ) File "/volume1/@appstore/MylarDev/bs4/init.py", line 172, in init self._feed() File "/volume1/@appstore/MylarDev/bs4/init.py", line 185, in _feed self.builder.feed(self.markup) File "/volume1/@appstore/MylarDev/bs4/builder/_lxml.py", line 175, in feed self.parser.close() File "parser.pxi", line 1187, in lxml.etree._FeedParser.close (src/lxml/lxml.etree.c:88279) File "parsertarget.pxi", line 130, in lxml.etree._TargetParserContext._handleParseResult (src/lxml/lxml.etree.c:97442) File "lxml.etree.pyx", line 294, in lxml.etree._ExceptionContext._raise_if_stored (src/lxml/lxml.etree.c:8870) File "saxparser.pxi", line 259, in lxml.etree._handleSaxData (src/lxml/lxml.etree.c:93587) UnicodeDecodeError: 'utf8' codec can't decode byte 0xdd in position 1: invalid continuation byte

[evilhero]

Actually it does help believe it or not. The screenshot error you got I was able to replicate so I can work through it tonight. The 500 error though seems to be an encoding error as it's trying to decode latin-1 as utf8 and failing...I'll have to run thru some tests to see if I can find what it is (if I were to guess I'd say it was the issue title that's causinhg a problem with encoding as I came across that before).

[suedester]

I think all my 500 errors reference the utf8 problem.

[projectzero]

Just updated to the latest dev version 4d1b61846b5e2d8021a237edf715d211d5b7f884 and here's what is happening now. When I tried to add 100 Bullets Mylar didn't crash right away but I did get this error in terminal and Mylar sat at (Comic information is currently being loaded)

I was able to delete the series out of Mylar and continue as normal. A few times when adding The Walking Dead, it looked as if it would load up like it should but terminal just sat at "INFO :: Thread-13 : Now adding/updating: The Walking Dead". When trying to navigate to any other page in Mylar it turns out it had fully crashed. Upon re-running the program, terminal threw this error

I proceeded to restart the program as advised earlier in this thread when hitting a traceback error and I still have the above described issues. I really appreciate your work on these errors and can't wait to be able to run the program fulltime.

[suedester]

I have now successfully added The Walking Dead using the latest commit. It was stuck at loading like projectzero but i went in and told it to reload and all is now well. Not having quite the same luck with 100 Bullets but will keep on trying to see if that works using the same method.

[rnoack]

I have the same problem when trying to add Fables. Also running on synology nas, development branch, latest commit.

[rnoack]

Ok, so the latest commit, it still doesn't seem to correctly add the series, but when it does crash it does now remove the failed series so its no longer showing in the list. The issue does seem to be on larger series though. I'm not sure how to get the very verbose logging.

27-Jan-2013 10:24:08 - INFO :: CP Server Thread-5 : Quick match success..continuing. 27-Jan-2013 10:24:08 - DEBUG :: Thread-13 : number of issues I counted: 60 27-Jan-2013 10:24:08 - DEBUG :: Thread-13 : number of issues CV says it has: 60 27-Jan-2013 10:24:08 - DEBUG :: Thread-13 : vari is set to: no 27-Jan-2013 10:24:08 - INFO :: Thread-13 : Now adding/updating: Transmetropolitan < complete crash >

restart, and it is no longer in the list.

Tried adding fables again, mylar did not crash, but it just sits there forever with Comic ID: ... and never actually finishes the update

[evilhero]

verbose logging is set to on by default. Everything gets logged to your mylar.log file in your logs directory. Are you using a straight git install or the synpkg?

[evilhero]

I just tried adding Fables:

27-Jan-2013 11:14:48 - INFO :: Thread-13 : Now adding/updating: Fables
27-Jan-2013 11:14:57 - INFO :: Thread-13 : Sucessfully retrieved details for Fables
27-Jan-2013 11:14:57 - INFO :: Thread-13 : Directory successfully created at: /Co                    mics/Fables-(2002)
27-Jan-2013 11:14:58 - INFO :: Thread-13 : Sucessfully retrieved cover for Fables
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Sucessfully retrieved issue details for Fables
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Now adding/updating issues for Fables
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Checking directory for existing issues.
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Now checking files for Fables (2002) in /Comics/Fables-(2002)
27-Jan-2013 11:14:59 - INFO :: Thread-13 : I've found 0 / 125 issues.
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Updating complete for: Fables
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Checking this week's pullist for new issues of Fab                    les
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Checking the Weekly Releases list for comics I'm w                    atching...
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Finished checking for comics on my watchlist.
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Attempting to grab wanted issues for : Fables
27-Jan-2013 11:14:59 - INFO :: Thread-13 : Shhh be very quiet...I'm looking for Fables issue:                     125.00(2013) using newznab
27-Jan-2013 11:15:00 - INFO :: Thread-13 : Found Fables (2013) issue: 125 using newznab
27-Jan-2013 11:15:00 - INFO :: Thread-13 : Successfully sent nzb file to SABnzbd
27-Jan-2013 11:15:00 - INFO :: Thread-13 : Updating now complete for Fables issue: 125.00
27-Jan-2013 11:15:00 - INFO :: Thread-13 : Finished grabbing what I could.
27-Jan-2013 11:15:20 - INFO :: CP Server Thread-7 : Starting postprocessing for : Fables 125                     (2013) (c2c) (theProletariat-Novus)
27-Jan-2013 11:15:20 - INFO :: CP Server Thread-7 : Now checking files for Fables (2002) in /                    Comics/Fables-(2002)
27-Jan-2013 11:15:20 - INFO :: CP Server Thread-7 : I've found 1 / 125 issues.
27-Jan-2013 11:15:20 - INFO :: CP Server Thread-7 : Post-Processing completed for: Fables iss                    ue: 125.00

Not only did it find it with no issues whatsoever, it even pulled the latest issue from the weekly pull list!

If your machine is a little older or it can't dedicate the processing power, pulling down information might take awhile (a few minutes, but not longer).On my old box (which as an amd 1700+) it would take 10-15 minutes to pull down a series like Action Comics, and a few minutes for The Walking Dead. On a fairly recent system (i3 it takes maybe 30s.

[rnoack]

I originally installed on the NAS with the synocommunity package, then I changed to the development branch by editing the file like someone else had posted. After that I was able to update the the latest commit. I think verbose logging might be turned off by default on the NAS package, because I don't see much more than what I posted there.

I don't think it's just taking a long time, the main reason being that sometimes it fully crashes out, and sometimes it does not, but just gets stuck in updating state. I think maybe the same sort of error is happening, just sometimes it is not causing the process to terminate and sometimes it is (?). Are there more known differences between the synocommunity package and the regular install?

[evilhero]

From what I know there are several having probs with the pkg for whatever reason. Try doing a manual install of Mylar using git and running that instead of hacking the synopkg. From some other comments doing the straight git install and avoiding the pkg entirely solves many problems.

[rnoack]

Ok, I tried installing the latest dev branch on my ubuntu machine. It added everything find and correctly, so something is definitely wrong with the nas. I have a different issue now that it just isn't downloading anything from newznab, it is added correctly, but the search for wanted issues is just finishing immediately as if it never even searched. I'm not sure if it's my error or not, I feel like it probably is, but I also think all the settings are correct... so i'm not sure and I'm going to have to go over everything again and figure it out.

But, the original problem does seem isolated to the package for some reason.

[evilhero]

Well that's one part down at least ;)

If I can see your config, or the mylar.log file where it creates the send-to-sab link (remove the api's) I can probably help you get it going.

I know with personal newznabs, if you don't have Sphinx running you won't get as many hits. I know that Sphinx is recommended to be used with only 'large' db's...but some others were having the same issues with not finding anything on their newznabs, and enabling sphinx resulted in really good results.

[projectzero]

Just updated to the latest dev e8efcfac794c4c951086079c128fd2a694735520 and received the following errors:

When adding The Walking Dead, Mylar didn't crash and I was able to use as normal but the series never loaded.

When adding 100 Bullets, I received the below error and it did crash Mylar

[evilhero]

Yeah there's the problem - you're on ANSI...it's screwing up the process. Are you running Mylar from a manual git install or are you using the synpkg in any way for Mylar ?

Type in 'locale' or 'locale -a' in a shell prompt and see what comes up.

For reference, http://www.chainsawonatireswing.com/2012/01/08/set-up-the-synology-diskstation-ds411j-to-support-utf-8/

[projectzero]

I'm running a manual git install of the Mylar dev branch. If Mylar relies on utf-8 then that sounds like the root problem everyone has with running the synology package. I have to wait until my headphones finishes up adding all my music before I can give the above fix a shot since it involve rebooting the nas but it seems very promising.

[projectzero]

It's been a while but I have some updates. I'm running dev 105a4dc46f86f6c3404f6babf60ebf2b110d3900 and have installed UTF-8 onto my Synology. When attempting to add 300 bullets, Mylar just crashed. When attempting to add The Walking Dead, I received the following errors

As you can see, it states that it sees my system as using UTF-8 coding:

After the above error, when trying to go back to the mylar homepage, I received:

[evilhero]

The second error is because it errored out when adding and left an incomplete comic. Restarting Mylar will clear it up and clean out the incomplete comic. First issue..I still haven't a clue. This is still trying it from a straight git install (no pkg?) Do a locale on your command line and see what the output is..if your on utf8 you shouldnt get a msg saying its going to replace invalid chars.

[projectzero]

Just did a fresh git pull (all stated above issues had been git pulls, not packages) into a new directory. Running version 105a4dc46f86f6c3404f6babf60ebf2b110d3900

Received the below errors while trying to add The Walking Dead a few different times. It's interesting that in the first error, it states I'm on UTF-8 but then goes on the next line stating there are UTF-8 errors.

[evilhero]

As a follow-up, see #228 - you need to install a different version of Python than what is included with the Synology Package from what I can understand.

[projectzero]

Installed another version of python per the linked thread and am able to add all my problem series now in the dev Mylar branch.

[sydlexius]

I'm experiencing a similar issue on a Windows 7 amd64 / Python 2.7.3 machine. In attempting to add "The Walking Dead" I get the following error in the logs:

Exception in thread Thread-14: Traceback (most recent call last): File "C:\Python27\Lib\threading.py", line 551, in bootstrap_inner self.run() File "C:\Python27\Lib\threading.py", line 504, in run self.__target(_self.args, *_self.__kwargs) File "C:\bin\mylar\mylar\importer.py", line 95, in addComictoDB gcdinfo=parseit.GCDScraper(comic['ComicName'], comic['ComicYear'], comic['Co micIssues'], comicid) File "C:\bin\mylar\mylar\parseit.py", line 160, in GCDScraper return GCDdetails(comseries=None, resultURL=resultURL, vari_loop=0, ComicID= ComicID, TotalIssues=TotalIssues, issvariation=issvariation, resultPublished=res ultPublished) File "C:\bin\mylar\mylar\parseit.py", line 211, in GCDdetails pyeartxt = pyearit.find(text=re.compile(r"Series")) AttributeError: 'NoneType' object has no attribute 'find'

[evilhero]

Are you running the master or developmental branch?

[sydlexius]

I'm running a fresh pull of the development branch. On Mar 31, 2013 7:48 PM, "evilhero" notifications@github.com wrote:

Are you running the master or developmental branch?

— Reply to this email directly or view it on GitHubhttps://github.com/evilhero/mylar/issues/170#issuecomment-15702427 .

[evilhero]

Try enabling the Synology fix in the configuration, save the settings and restart Mylar (you need to restart after ANY config changes). Delete the series and then try readding the series. Is it jusy The Walking Dead or is it any comix you try to add?

[evilhero]

Closing this as the move to a single online db has removed this from the entire process.