PADD broken after latest updates

[Zathras]

Expected Behaviour:

PADD should be displaying stats and pi-hole status.
Using Buster on RPi 3b+

Actual Behaviour:

PADD shows Core down and DNS server off
pihole -c shows stats whereas padd doesn't.

---

|) /\ | | \ Pi-hole® v5.13, Web v5.16, FTL v5.18.2, PADD v3.8.0
| /--|/|__/ [✗] Core [✓] FTL [✗] Pi-hole's DNS server is off!

STATS =========================================================================
Blocking: 0 domains Piholed: [■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■] 0.0%
Clients: 0 out of 0 queries
Latest: 0
Top Ad:
Top Dmn:
Top Clnt:

Debug Token:

https://tricorder.pi-hole.net/2LxB6QR6/

[chrislph]

Same here after today's updates. I think it's related to this, not sure...

Remove references to deprecated `pihole-FTL.port` file

Looks like PADD's main data-gathering function uses that file

GetFTLData() {
  ftl_port=$(cat /run/pihole-FTL.port 2> /dev/null)
  ...

[chrislph]

You can work around it for now by editing PADD and making the following changes.

nano -l padd.sh

Modify the GetFTLData function, starting on line 109, to look like this

GetFTLData() {
      echo ">$1 >quit" | nc 127.0.0.1 4711
}

assuming FTL is running on port 4711 which is the standard. PADD works once again.

[Zathras]

Thanks. That did it. All good again.
Cheers.

[chrislph]

Bear in mind it's a workaround not a fix. Keep an eye out for an updated version.

Seems that .port file was being used to both determine the port and check it's even running. Second para here mentions reading the conf file directly as the proper way now, but in PADD I think that logic now translates into two tests, something like

if FTL is running then
  if FTLPORT is set in conf then
    set ftl_port to use that
    else ftl_port=4711
    send command to FTL
else if not running then echo 0

[rdwebdesign]

This was already fixed in development.

Get API port from pihole-FTL.conf instead of port file

It'll be shipped with the next release.

[Max-Mustermann]

Also core is showing up with error:

[Zathras]

@Max-Mustermann

Also core is showing up with error:

I mentioned that in the original post. Albeit without an image.

[Max-Mustermann]

ok, thanks for the info, I overlooked it

[bcutter]

Other symptoms:

Pihole -v says the system is up to date but the web interface indicates updates needed

Please follow the below template, it will help us to help you! *If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using I am running apache web server on this box to support ups units and other software. This pihole seems to be working fine, just the version on the web page seems wrong. Forgot to add system has been fully rebooted and I have tested in a browser that has never had the page cached. Expected Behaviour: I am running pihole on a P…

Latest v5.15.1 and further 2022-10-10 updates not refreshed in webinterface (version information not in sync)

I guess waiting for a fix shipped with a stable update is the actual thing to wait for.

[bcutter]

Seems to be waiting for an approving review to get merged.

Current/latest release still is v3.8.0.

[Max-Mustermann]

v3.8.1 out now and working fine / many thanks for the fix

[Zathras]

All good now with v3.8.1.
Also 'mega' screen fixed too. Did scroll up with v3.8.0 and top line on LCD no longer showed.

[Max-Mustermann]

as of today:

some magic ... switched back to ERROR ???

[Max-Mustermann]

puh, was a "user too stupid", my blocking was disabled .....

padd works as expected