Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression bug on excessive ARPA lookups in DNS? #259

Open
thefunkygibbon opened this issue Sep 1, 2024 · 6 comments
Open

Regression bug on excessive ARPA lookups in DNS? #259

thefunkygibbon opened this issue Sep 1, 2024 · 6 comments

Comments

@thefunkygibbon
Copy link

This happened a year or so ago and it was deduced that it was a bug and was resolved, but i've come to check my DNS logs (pihole) and i'm seeing the same as last time

image

@thefunkygibbon thefunkygibbon changed the title Regression bug on excessive ARP lookups in DNS? Regression bug on excessive ARPA lookups in DNS? Sep 1, 2024
@jokob-sk
Copy link

jokob-sk commented Sep 1, 2024

Please close this issue and open it at the correct github repo. Look at #235 and #237

@mrcsrplln
Copy link

@thefunkygibbon I had the same issues and received help from the great guys at PiHole - https://discourse.pi-hole.net/t/sudden-increase-in-local-ptr-queries-from-localhost-pihole-itself/72110/3

In my case it was indeed PiAlert (Docker Container jokobsk/pi.alert:latest) that started spamming PTR queries every other minute.

@thefunkygibbon
Copy link
Author

thefunkygibbon commented Sep 4, 2024

thanks, maybe I'm missing something since I've only just awoken, but I don't see any "help" as such or any way of fixing the issue , other than "turning it off" which isn't a great solution if you use the software lol.

@mrcsrplln
Copy link

thanks, maybe I'm missing something since I've only just awoken, but I don't see any "help" as such or any way of fixing the issue , other than "turning it off" which isn't a great solution if you use the software lol.

Indeed, I was just confirming the issue you experienced. I ended up removing Pi Alert Docker Container as I haven't been using it at all.

@thefunkygibbon
Copy link
Author

ah fair enough, I was trying to use it as a replacement for "fing" but its not got anywhere the amount of features that fing does so i've barely used it either. guess i'll just ditch it. shame really.

thanks for the confirmation though dude, and sorry if my above message came across as a bit abrupt.

@jokob-sk
Copy link

Hey @thefunkygibbon - can you close this issue as you switched to the NetAlertX fork?

ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
Testing a possibility to realize an automatic backup.

Regarding to pucherot#259
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
- The update check of the GeoIP database now also displays the size of the database on Github
- Translation work
- Continuation of the attempt to implement automatic backups  (pucherot#259)
- Database path hidden in the status box of the settings page as a test
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
New:
* Add current and remote GeoDB filesize to updatecheck
* Add Scheduled backups (pucherot#259)
* Add Database info to system info page
* Crontabs that are configured in pialert.conf are displayed on the System Info page

Fixed:
* Translation (#290 and report via Mail)

Updated:
* DeviceDetails: Show the corresponding number in the drop-down list next to the Uplink Target (#286)
* Documenation: NETWORK_RELATIONSHIP
* Font-Awesome from 6.5.1 to 6.5.2
* Add new variables to update script
* Language files and changed some wordings

Changed:
* Database path moved from the status box of the settings page to the system info page
* Move setting_* files from "pialert/db" to "pialert/config" folder
* Add variable with crontab syntax to speedtest (SPEEDTEST_TASK_HOUR will be deprecated)
* Instead of a hard-coded time at which the update check took place, a variable has now been introduced that can be used to configure the time in the crontab syntax

Removed:
* Older config-file updates from update script

Note:
* Since some "settings files" are now used in a different directory, I tried to move the existing files to the new directory in the update script. The "setting_*" files from the "pialert/db/" directory are moved to the "pialert/config/" directory
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
New:
* Add current and remote GeoDB filesize to updatecheck
* Add Scheduled backups (pucherot#259)
* Add Database info to system info page
* Crontabs that are configured in pialert.conf are displayed on the System Info page

Fixed:
* Translation (#290 and report via Mail)

Updated:
* DeviceDetails: Show the corresponding number in the drop-down list next to the Uplink Target (#286)
* Documenation: NETWORK_RELATIONSHIP
* Font-Awesome from 6.5.1 to 6.5.2
* Add new variables to update script
* Language files and changed some wordings

Changed:
* Database path moved from the status box of the settings page to the system info page
* Move setting_* files from "pialert/db" to "pialert/config" folder
* Add variable with crontab syntax to speedtest (SPEEDTEST_TASK_HOUR will be deprecated)
* Instead of a hard-coded time at which the update check took place, a variable has now been introduced that can be used to configure the time in the crontab syntax

Removed:
* Older config-file updates from update script

Note:
* Since some "settings files" are now used in a different directory, I tried to move the existing files to the new directory in the update script. The "setting_*" files from the "pialert/db/" directory are moved to the "pialert/config/" directory
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
New:
* Add current and remote GeoDB filesize to updatecheck
* Add Scheduled backups (pucherot#259). The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).
* Add Database info to system info page
* Crontabs that are configured in pialert.conf are displayed on the System Info page

Fixed:
* Translation (#290 and report via Mail)

Updated:
* DeviceDetails: Show the corresponding number in the drop-down list next to the Uplink Target (#286)
* Documenation: NETWORK_RELATIONSHIP
* Font-Awesome from 6.5.1 to 6.5.2
* Add new variables to update script
* Language files and changed some wordings

Changed:
* Database path moved from the status box of the settings page to the system info page
* Move setting_* files from "pialert/db" to "pialert/config" folder
* Add variable with crontab syntax to speedtest (SPEEDTEST_TASK_HOUR will be deprecated). The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).
* Instead of a hard-coded time at which the update check took place, a variable has now been introduced that can be used to configure the time in the crontab syntax. The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).

Removed:
* Older config-file updates from update script

Note:
* Since some "settings files" are now used in a different directory, I tried to move the existing files to the new directory in the update script. The "setting_*" files from the "pialert/db/" directory are moved to the "pialert/config/" directory
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
New:
* Add current and remote GeoDB filesize to updatecheck
* Add Scheduled backups (pucherot#259). The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).
* Add Database info to system info page
* Crontabs that are configured in pialert.conf are displayed on the System Info page
* After recreating the pialert.conf by saving via webGUI, a note regarding the cronjobs is added.

Fixed:
* Translation (#290 and report via Mail)

Updated:
* DeviceDetails: Show the corresponding number in the drop-down list next to the Uplink Target (#286)
* Documenation: NETWORK_RELATIONSHIP
* Font-Awesome from 6.5.1 to 6.5.2
* Add new variables to update script
* Language files and changed some wordings

Changed:
* Database path moved from the status box of the settings page to the system info page
* Move setting_* files from "pialert/db" to "pialert/config" folder
* Add variable with crontab syntax to speedtest (SPEEDTEST_TASK_HOUR will be deprecated). The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).
* Instead of a hard-coded time at which the update check took place, a variable has now been introduced that can be used to configure the time in the crontab syntax. The shortest interval is 3 minutes. All larger intervals must be integer multiples of 3 minutes (15, 30, 36, etc).

Removed:
* Older config-file updates from update script

Note:
* Since some "settings files" are now used in a different directory, I tried to move the existing files to the new directory in the update script. The "setting_*" files from the "pialert/db/" directory are moved to the "pialert/config/" directory
ademol pushed a commit to ademol/Pi.Alert that referenced this issue Nov 28, 2024
New:
* Cleanup auto backups
* Exclude devices from ICMP monitoring (#296)
* Automatic deletion of old backups (pucherot#259)
* Add a connection type "Fibre" (#298)
* Added a parameter to define how many automatic backups are kept
* A link to the systeminfo page added to the settings page status box

Fixed:
* File permissions of the backups created by auto backup function (pucherot#259)
* Initial cronjob corrected according to documentation
* various typos
* Includes HOTFIX Version 2024-04-15
* Crontab parsing. Deviation of days or months by -1 (pucherot#259)
* Minor fixes and tweaks

Updated:
* Improve the network overview and the network settings page (#297)
* Language files

Changed:
* ICMP Monitoring: The hostname is displayed before the ip
* Get backup info (status box on settings page) via ajax call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants