@norvik-it
Ah, ok, nice example of taking care of a sick person with a shotgun.
I use pfBlockerng-devel with dnsbl myself. It's web server doesn't "stop" like that every minute.
The PID is here (according to the info found in the pfBlockerng-devel lighty webserver config file here /var/unbound/pfb_dnsbl_lighty.conf ) : /var/run/dnsbl.pid
The process number is in that file : does it really stops every minute ?
All the others : SquidGuard, ntopng iperf ClamAV ICAP are part of the 'do not belong on a firewall anyway (my opinion).
I've installed this 'Service Watchdog' package and added a task :
d9a1111e-b619-4028-9580-7a90f6642019-image.png
Unselecting the notification box will stop sending you mails.
The issue is now a bit solved.
Next step : check if the service is really stopped.
And if so, why / by who / what reasons ?!
Example :
[22.05-RELEASE][admin@pfSense.xxxxx.net]/root: cat /var/run/dnsbl.pid
4622
[22.05-RELEASE][admin@pfSense.xxxxx.net]/root: ps ax | grep '4622'
4622 - S 0:00.02 /usr/local/sbin/lighttpd_pfb -f /var/unbound/pfb_dnsbl_lighty.conf
35843 1 S+ 0:00.00 grep 4622
So the process running.
If all these process are really killed on your system every minute, I can advise you to do one thing :
Remove / disable all these packages.
Or, as stated above, find the reason why they are dying on your pfSense, or are getting killed.
Remove the issue for each of them.
Example : if free RAM gets low, the system will kill processes, this is known as the OOM (Out Of Memory) event. Restarting them in that case is a really bad idea.