it works for a minute, try to ssh in and update pi -up, errors. try sudo apt update, nothing. admin page 503 internal error
changing dns from custom upstream to google...now it works, update and all the good stuff, run the updates. Next day, its back to the upstream dns on its own, and nothing works. reboot. boom back to 32%...but it isnt working and cant connect through ssh. every command ends in an error. I have not fucked with any settings in years but since 11/17 i have had a too many connections diagnosis that will not delete(also results in error)
It only works for a bit...after pulling the plug.(long enough to get a debug token and forget about it) is this the clock? windows update I feel had something to do with this
This is not a Debug Token. This is the path where your log is saved, but only you can access it.
Please execute pihole -d again.
When the log is finished it will ask if you want to upload it. Answer Yes (Y).
After the log is uploaded, a token will be generated and showed on the screen.
Copy and paste it here only the token.
Note:
I asked for a debug log to try to help, but if you can't connect via ssh, then this is probably an OS problem unrelated to Pi-hole.
Would you like to upload the log? [y/N] y
* Log will NOT be uploaded to tricorder.
* A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
[✗] There was an error uploading your debug log.
Please try again or contact the Pi-hole team for assistance.
A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
The initial part is showing text from a different log, not related to Pi-hole (this could indicate a filesystem issue):
Nov 11 00:00:21 raspberrypi systemd[1]: Started CUPS Scheduler.
Nov 11 00:00:21 raspberrypi systemd[1]: Started Make remote CUPS printers available locally.
Nov 11 00:00:21 raspberrypi systemd[1]: logrotate.service: Succeeded.
(...)
Many sections are missing.
I can't even say what is your OS or which Pi-hole version you are running.
There are strange characters all over the log (another indication of a filesystem issue):
Sort of
It says its "skipping" which is coud be an indication that the journal logs are corrupted too (it tries to skip over the corrupted bits).
The docs I linked before used to have a section that described a lightning bolt icon appearing in the top right corner when under voltage/brownouts occur.
Similar like below:
Like described in the link and depending AC adapter model, a bad USB cable for power can cause brownouts too.
Also when too many power hungry USB devices are connected (like an unpowered USB SSD drive).
But the current install is probably corrupted beyond repair.
Or would be difficult to repair with fsck and reinstalling files that cant be fixed by fsck.
EDIT:
$ man journalctl
[..]
--verify
Check the journal file for internal consistency. If the
file has been generated with FSS enabled and the FSS
verification key has been specified with --verify-key=,
authenticity of the journal file is verified.
I've got one too but probaly not bc of bad power but incorrect shutdown or crash:
$ sudo journalctl --verify
[..]
PASS: /var/log/journal/f8651c48bd594bad8b5be06a1666cafb/user-1001.journal
PASS: /var/log/journal/f8651c48bd594bad8b5be06a1666cafb/system@61508e3f591740fbb2e4aec573e355a9-0000000000011783-000616c25d17937c.journal
3786d8: Data object references invalid entry at 4fae30
File corruption detected at /var/log/journal/f8651c48bd594bad8b5be06a1666cafb/system@00061ba9dc7b9717-95f704e86e74d224.journal~:4fad20 (of 8388608 bytes, 62%).
FAIL: /var/log/journal/f8651c48bd594bad8b5be06a1666cafb/system@00061ba9dc7b9717-95f704e86e74d224.journal~ (Bad message)
