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

Segmentation Fault after startup #1723

Closed
mohamed-essam opened this issue Nov 1, 2023 · 6 comments
Closed

Segmentation Fault after startup #1723

mohamed-essam opened this issue Nov 1, 2023 · 6 comments
Labels

Comments

@mohamed-essam
Copy link

Versions

Pi-hole version is v5.17.2 (Latest: v5.17.2)
web version is v5.20.2 (Latest: v5.20.2)
FTL version is v5.23 (Latest: v5.23)

Platform

  • OS and version: Ubuntu 22.04.1
  • Platform: VM
  • 2VCPUs, 2GB RAM

Expected behavior

Normal startup and activity

Actual behavior / bug

FTL Crashes with segmentation Fault after startup by a minute.

Steps to reproduce

Not sure how to exactly reproduce this issue, but I suspect the cause is the large size of clients.

Debug Token

Screenshots

N/A

Additional context

N/A

@yubiuser
Copy link
Member

yubiuser commented Nov 1, 2023

Could you please provide the part of ´/var/log/pihole/FTL.log that shows the crash?

@curtHendzell
Copy link

curtHendzell commented Nov 7, 2023

Getting similar.

pihole-FTL-partial.log

@DL6ER
Copy link
Member

DL6ER commented Nov 7, 2023

@curtHendzell This is a log from a Pi-hole with really many clients (> 24,000). Could you please provide a few lines from the initial start (before all the Resizing "FTL-clients" from ... to ... lines?

@curtHendzell
Copy link

@DL6ER Yup....firewall misconfiguration. Not great on a hosted Linode. Fixed it and no issues since.

@DL6ER
Copy link
Member

DL6ER commented Nov 26, 2023

Sounds like the underlying issue will be fixed by #1777

Copy link

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.

@github-actions github-actions bot added the stale label Dec 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants