so it seems logrotate stopped processing this file on 7 July.
I have inspected /opt/pihole/piholeLogFlush.sh and could find no reference to dnsmasq.log. Many of the files in /opt/pihole, including this one, were touched on 7 July. Some files in /etc/pihole were touched at the same time.
I can find no reason why dnsmasq.log is treated differently to the other pihole logs.
How do I enable logrotate on dnsmasq.log? Is there any way of detecting what changed on 7 July?
Raspberry Pi 3B running Raspbian GNU/Linux 12 (bookworm).
My Pi-hole v6 has no such log at that path. I do not remember if v5 had such a log. Are you on v5? Or perhaps upgraded to v6 from v5, which might explain the lack of rotation now? You might check the /etc/logrotate.d/pihole file for the current configuration on your system.
Pi-hole uses /var/log/pihole/pihole.log instead of /var/log/pihole/dnsmasq.log as a default for files.log.dnsmasq. You can inspect the logrotate file at /etc/pihole/logrotate (pre core v6.4.3) or /etc/logrotate.d/pihole (core v6.4.3+)
Edit: looking at commit Merge commit from fork · pi-hole/pi-hole@18002bf · GitHub which changed the location of the logrotate file, there doesn’t seem to be any migration of the old config. Instead, always the default config is installed. I suspect you had previously edited /etc/pihole/logrotate, which is no longer used. The release of this commit, with core v6.4.3, happened on the sixth of July. This lines up with your reported date of the seventh of July. You will need to change the path to your custom path inside /etc/logrotate.d/pihole