-
Notifications
You must be signed in to change notification settings - Fork 4
/
FAQ.txt
68 lines (49 loc) · 3.47 KB
/
FAQ.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Some common mistakes/errors people encounter.
Q: Sabnzbd is not working.
A: Make sure you have the sabnzbd/ in the url.
Q: Sickbeard/Couchpotato are not working.
A: Make sure they are not https.
Q: I do not see any releases unless I click on ALL.
A: Go to http://localhost/profileedit untick the 4 checkmarks, click save profile.
Q: I'm not getting any covers or x type of release are not being post processed.
A: Make sure your keys are good, all the keys that come with nZEDb are tested and work. It is still preferable to use your own keys. We do not supply a trakt key.
Q: How do I test the amazon keys?
A: There is a script in the misc/testing/Dev_testing folder. Read the whole output if you get an error (most people are only reading the bottom part).
Q: I'm having x issue after converting from newznab +.
A: We will not support newznab + conversions, the script is there if you want to use it, use at your own will.
Q: I'm getting lots of spam, or small files.
A: Use blacklists. removeCrapReleases script, size settings for groups etc..
Q: The scripts and my site is slow.
A: You will need to tune MYSQL, there are many guides for this online, look at tools like mysqltuner.
If your hardware is not powerful enough it will be slow regardless.
Q: Sabnzbd says I have problems with extra lines in the NZB.
A: There is a script in misc/testing/Dev_testing to fix those NZB files.
Q: I'm getting many releases with unusable names.
A: There is a script in misc/testing/Release_scripts called fixReleaseNames.php
Do not expect miracles...
Q: How do I run x script?
A: type php name-of-the-script.php , most of the scripts tell you how to use them if you run them like that.
Q: My parts/binaries/collections tabls are very large.
A: Article collections with poorly named subjects or incomplete collections are created 2 hours after the last time we have downloaded an article for that collection,
if you keep backfilling, your parts/binaries/collections tables will get large obviously...
Q: I'm having x issue not in the readme or FAQ.
A: Please do some research first. If you can't solve the issue, we have a channel on IRC, server : synirc, channel #nZEDB
Q: I have converted my mysql tables to InnoDB and the ibdata file keeps getting bigger, even after I optimize the tables?
A: You should follow the recommendations found on these 2 webpages.
http://stackoverflow.com/questions/3927690/howto-clean-a-mysql-innodb-storage-engine/4056261#4056261
http://www.mysqlperformanceblog.com/2011/11/06/improved-innodb-fast-index-creation
Percona Server as of versions 5.1.56 and 5.5.11 allows utilizing fast index creation for all of the above cases, which can potentially speed them up greatly.
Be sure to add to you InnoDB section: expand_fast_index_creation = 1
innodb_merge_sort_block_size = 1G
Q: I'm having issues with the PREDB backfill script.
A: https://github.com/nZEDb/pre-info
Q: Can I have some information on collections/binaries/parts?
A: http://s12.postimg.org/ity5z1xnf/Untitled.jpg
Q: I'm having issues with the PREDB backfill script.
A: https://github.com/nZEDb/pre-info
Q: Can I have some information on collections/binaries/parts?
A: http://s12.postimg.org/ity5z1xnf/Untitled.jpg
Please do not open issues on github if the question is already asked. Take a few minutes to look at the titles of other issues.
Do not expect us to implement requested features in a short amount of time.
Some requested features we will not implement, you are free to clone the git.
More to come...