Created Cron jobs to restart syslogd in my pfsense firewall with FreeBSD 15.0-CURRENT at home twice daily

Subject: Created Cron jobs to restart syslogd in my pfsense firewall with F=
reeBSD 15.0-CURRENT at home twice daily

Good day from Singapore,

[2.8.1-RELEASE][[email protected]]/root: uname -a
FreeBSD pfSense.teo-en-ming-corp.com 15.0-CURRENT FreeBSD 15.0-CURRENT #21 =
RELENG_2_8_1-n256095-47c932dcc0e9: Thu Aug 28 16:27:48 UTC 2025     root@pf=
sense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSe=
nse-CE-snapshots-2_8_1-main/obj/amd64/AupY3aTL/var/jenkins/workspace/pfSens=
e-CE-snapshots-2_8_1-main/sources/FreeBSD-src-RELENG_2_8_1/amd64.amd64/sys/=
pfSense amd64
[2.8.1-RELEASE][[email protected]]/root: cat /etc/os-relea=
se
cat: /etc/os-release: No such file or directory
[2.8.1-RELEASE][[email protected]]/root:

My pfsense firewall at home had stopped logging a few times or several time=
s in the recent past few months. Not sure whether it is the work of Advance=
d Persistent Threats (APT) hackers.

The most recent incident occurred on 24 Mar 2026 at about 3.00 PM Singapore=
 Time. syslogd logging had stopped for 1 week (7 days). I have totally no f=
irewall logs at all for 1 week.
Upon discovery, I had restarted syslogd in the firewall webGUI on 31 Mar 20=
26 at about 1.00 PM Singapore Time.

To prevent logging from completely stopping on my pfsense firewall at home,=
 I have created 2 Cron jobs to restart syslogd service twice daily.

0=093=09*=09*=09*=09root=09service syslogd restart
0=0915=09*=09*=09*=09root=09service syslogd restart

Hopefully with the above workaround, my pfsense firewall at home will not s=
top logging again.

The above Cron jobs were created on 7 Apr 2026 Tuesday at about 1.02 am Sin=
gapore Time.

Regards,

Mr. Turritopsis Dohrnii Teo En Ming
Extremely Democratic People's Republic of Singapore
8 Apr 2026 Wednesday 1.11 pm Singapore Time