I have been using syslogd/2 v2.01 (courtesy of Michael Greene) for SYSLOG functionality over several years now. All working great, some stuff is logged into my \tmp\log directory, a good chunk goes to my NAS box as well which is an aggregate of various LOGs from across various machines on my LAN.
Once a year I roll-over my various LOGs and file last year's into the ARCHIVE folder and carry on with the new year.
Yeah...so I'm a little late to the '2026 party', LOL, sure...but I'm filing stuff away and "lo' and behold" but my SYSLOG.LOG ended back on Dec 18th (there is an entry posted each time I re-boot), and indeed several other LOGs, such as SMARTD.LOG fail to show anything past Dec-24th.
Hmm???

So off I go investigating, turns out that my POPUPLOG.OS2 file starts showing SYSLOGD.EXE failing around Jan-10th, 2026...which presumably means that something has occured between Dec-24th and Jan-10th which eventually caused SYSLODG to die each and every time I attempt to start it up.
Specifically, POPUPLOG.OS2 shows:
03-15-2026 16:59:02 SYS3175 PID 0089 TID 0003 Slot 00cf
G:\TCPIP\BIN\SYSLOGD.EXE
c0000005
00023cd2
P1=00000001 P2=00000008 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=00000100 ECX=00000002 EDX=21000000
ESI=00000000 EDI=0004497c
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:00023cd2 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:001e6a88 SSACC=f0f3 SSLIM=ffffffff
EBP=001e6fe8 FLG=00010206
SYSLOGD.EXE 0002:00003cd2
...while CLI (syslogd -d) shows:
[G:\tcpip\bin]syslogd -d
Mar 15 16:59:02 syslogd: SYSLOGDMP: Running startup commands
Mar 15 16:59:02 syslogd: SYSLOGDMP: Hostname: NEUROBOX
Mar 15 16:59:02 syslogd: SYSLOGDMP: Base allocated memory
Mar 15 16:59:02 syslogd: SYSLOGIPC: IPC thread started
SYS1808:
The process has stopped. The software diagnostic
code (exception code) is 0005.
Unfortunately both of these are pretty generic and so I cannot tell what may actually be failing today.
I removed the tcpipforward setting in my syslog, but that had no impact.
Any ideas on how I could troubleshoot this further?
Thanks!