FTL_db warn: STATUS should be within [0,8] but is 9

seh2000 · February 20, 2020, 8:32pm

Hi,

Had a look at the pihole-FTL.log in the log I see 100s of entries like the below

wonder why, the reason and how to fix...

Steen

pihole-FTL.log 20 Feb 2020.txt (11.5 KB)

DL6ER · February 20, 2020, 8:55pm

This is a solely cosmetic issue because we forgot to add the new CNAME blocking status to the database sourcing. Please try whether this fix resolves the warnings:

pihole checkout ftl fix/incorrect_db_warning

github.com/pi-hole/FTL

Fix incorrect database warnings

pi-hole:release/v5.0 ← pi-hole:fix/incorrect_db_warning

opened 08:56PM - 20 Feb 20 UTC

DL6ER

+3 -3

**By submitting this pull request, I confirm the following:** - [X] I have re…ad and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md). - [X] I have checked that [another pull request](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist. - [X] I have considered, and confirmed that this submission will be valuable to others. - [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [X] I give this submission freely, and claim no ownership to its content. **How familiar are you with the codebase?:** ## 10 --- Fix incorrect database warning when imporint new CNAME blocked queries.

seh2000 · February 20, 2020, 11:33pm

Looks like the command fixed it, will check in the morning to be sure

seh2000 · February 21, 2020, 5:48pm

Looks ok...

DL6ER · February 21, 2020, 6:15pm

Thanks, please go back to the main beta branch to continue receiving future updates. The change has already been merged.

pihole checkout ftl release/v5.0

seh2000 · February 22, 2020, 1:11pm

Thanks for the help and I am now back on the main beta branch.
Steen