PADD error after running for several hours

pi-hole / PADD

PADD (formerly Chronometer2) is a more expansive version of the original chronometer.sh that is included with Pi-Hole. PADD provides in-depth information about your Pi-hole.

1.37k stars 121 forks source link

PADD error after running for several hours #134

Closed scuk23 closed 1 year ago

scuk23 commented 4 years ago

Before submitting a bug report, are you using a test version of Pi-hole? If so, PADD doesn‘t support beta versions of Pi-hole! Newest version - non beta

Describe the bug Everything starts and works perfectly. But, I'll come back and look at the display a few hours later and see this error.

To Reproduce Steps to reproduce the behavior:

... Start and run PADD.
... Wait.

Expected behavior Errors occur - pictured in screenshot.

Screenshots https://i.imgur.com/caTrsnC.jpg

Additional context I was asked to post this here. This discussion started on this reddit thread, https://www.reddit.com/r/pihole/comments/j3sjuj/padd_error_after_running_for_a_few_hours/

zangaby commented 3 years ago

Same issue for me after I updated PADD to the latest version.

ghost commented 3 years ago

Same error generated for me, its displayed on screen 6 times. Happend after 8 hours 30 mins up time. Running: Pi-hole v5.2.1 Web Interface v5.2.1 FTL v5.3.2 PADD v3.4

Edit: This was a fresh install of PADD, never installed on this Pi before.

kevin25761 commented 3 years ago

I am also receiving this error after installing a new 3.5" display
https://www.amazon.com/gp/product/B07S695VQM/ http://www.lcdwiki.com/MHS-3.5inch_RPi_Display

Pi-hole 5.2.1 Web interface 5.2.1 FTL 5.3.2 PADD 3.4

Error message - ./padd.sh: line 126: /dev/tcp/localhost/4711: Connection refused ./padd.sh: connect: Connection refused

Previously I was using a 2.8" Adafruit display and never received the error. https://www.adafruit.com/product/3974

Edit - 11 Dec 2020

Using htop I found and killed the erroneous padd process running under the pi user.

I then restarted padd > ./padd.sh > tty1

It has been running fine overnight with no errors.

Something else I noticed. When the error occurs the CPU temp goes up to 75+ degrees C. After restarting padd CPU drops to ~54 degrees C

dasher7320 commented 3 years ago

Hi there,

After using PH with PADD for over 2 years, this issue has suddenly popped up, randomly every few days.

I can also confirm the CPU Temp increase, maxed out memory, screen looks the same as the top screenshot. I can connect with Putty and do the reboot command, restarts fine till next time it occurs, only warning i get is internet goes down, also note tonight's case happened at about the same time i disabled PiHole via the web interface for 5 mins to test a connection issue (to see if i needed to whitelist a domain).

Any updates on the fix?

Thanks

Dash

thomasmerz commented 2 years ago

There's no problem at my installation running padd.sh for a week or sometimes two weeks (if no maintenance with restart/reboot was neccessary of Pi-hole or operation system)… 🤷🏻‍♂️

So is this still an issue for you?

gooperlooper commented 2 years ago

Not me, but I recently had the same issue start up with me. No idea what's caused it.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.