[NAS-2579] Much "Invalid tld" logspam Created: 02/Nov/16 Updated: 24/Apr/18 Resolved: 02/Feb/18 |
|
| Status: | Closed |
| Project: | NetarchiveSuite |
| Component/s: | Common |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.3, 5.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Colin Rosenthal | Assignee: | Søren Vejrup Carlsen (Inactive) |
| Resolution: | Fixed | ||
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.5h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| External reference: | https://sbprojects.statsbiblioteket.dk/jira/projects/NARK/issues/NARK-1428 |
||||||||
| Sprint: | NAS 5.4 | ||||||||
| Description |
|
Many lines like
|
| Comments |
| Comment by Søren Vejrup Carlsen (Inactive) [ 12/Jan/18 ] |
|
After the patch the spam is much reduced 2018-01-12 14:00:29.575 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!www.ck', ignoring 2018-01-12 14:00:29.579 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.kawasaki.jp', ignoring 2018-01-12 14:00:29.579 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.kitakyushu.jp', ignoring 2018-01-12 14:00:29.579 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.kobe.jp', ignoring 2018-01-12 14:00:29.580 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.nagoya.jp', ignoring 2018-01-12 14:00:29.580 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.sapporo.jp', ignoring 2018-01-12 14:00:29.580 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.sendai.jp', ignoring 2018-01-12 14:00:29.580 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!city.yokohama.jp', ignoring 2018-01-12 14:00:29.593 WARN dk.netarkivet.common.utils.TLD - Invalid tld '!teledata.mz', ignoring 2018-01-12 14:00:29.646 INFO dk.netarkivet.common.utils.TLD - Read 7975 TLDs from public suffix file |
| Comment by Søren Vejrup Carlsen (Inactive) [ 09/Jan/18 ] |
|
A new patch has been added that ignores all starred dns records like *.kh |
| Comment by Colin Rosenthal [ 09/Mar/17 ] |
|
Actually not fixed - reassigning to a later release. |
| Comment by Colin Rosenthal [ 03/Mar/17 ] |
|
Believed fixed. |