-
Notifications
You must be signed in to change notification settings - Fork 84
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
Unable to start isc-agent on fully updated pi 5 #287
Comments
looks like your system has trouble resolving "www4.dshield.org" Could you try the following command: curl https://www4.dshield.org/api/myip ? it should return your IP address if all works well. |
It returns my ip indeed. |
try a reboot. The "agent" will affect only the weblogs. If the agent doesn't run after a reboot, check https://github.com/DShield-ISC/dshield/blob/main/docs/install-instructions/troubleshooting.md |
I tried the troubleshooting steps you provided. The isc-agent.err atill gives the same error. DEBUG :: 2024-02-12 21:42:44,952 :: <PID 1435:MainProcess> :: main :: L:13 :: ISC Agent starting |
The output from isc-agent.py looks good. No error shown. The error.txt file above shows that the name resolution for www4.dshield.org fails. Which is odd... in particular if the curl request for https://www4.dshield.org/api/myip succeeds. The root cause appears to be DNS. I can't come up with a scenario right now that would cause DNS to fail for the isc-agent, but not for "curl". Maybe try to add a host file entry. Add this line to /etc/hosts on the Raspberry Pi:
|
Adding the ip to the hostfile doesn't resolve the issue. |
reinstalled on a pi3, works just fine. |
I used the manual here to install dshield on a rapberry pi 5.
Raspberry pi 5 was fully updated and running the lastest PIOS light.
There is a naming resolution error in the log, but the pi can ping wesites.
I'v ereinstalled twice now, i get the same error.
status.txt
error.txt
The text was updated successfully, but these errors were encountered: