A freshly installed pihole on a debian proxmox container doesn't auto-start on container boot, and takes several minutes to start via systemctl start pihole-FTL.
There is nothing obvious in the logs like errors, and CPU/RAM usage appears low.
Unfortunately I have power cuts that outlast my UPS, so I need a setup that auto-starts on reboot.
There is a warning about NTP - I checked the pre-requisites and installation documentation and didn't see anything about installing an NTP server, when I tried to load the host localtime on LLM-advice I had various complaints so gave up on that.
2025-04-08 09:43:36.596 UTC [1041/T1042] ERROR: Error NTP client: Failed to adjust time during NTP sync: Insufficient permissions
2025-04-08 09:43:36.596 UTC [1041/T1042] INFO: Local time is too inaccurate, retrying in 3596 seconds before launching NTP server
Ok so after another outtage, some frustrating chat with an LLM, old-fashioned Google yielded the issue and answer.
Basically, I noticed that the networking service was hanging, and it turns out it was dhclient -6 which didn't complete. This then prevented the pihole-FTL service from loading. I was fixing it accidentally by killing various processes.
In proxmox, there is a setting to use SLAAC instead of DHCP, as per this post: