1
Setup & Installation / Troubleshooting process trap/dump...how?
« on: May 05, 2025, 05:51:12 am »
So I've got a weird problem that just seemingly has shown up about a couple of weeks ago: I've seen three separate RSYNC jobs die part-way through a LOCAL backup, and as best as I can tell my OS/2 box reboots at the same time.
Now the strange part is that I can't find anything listed in places like POPUPLOG.OS2 or as TRP files...so it's rather tough to figure out whether this is a hardware or a software issue. At the moment I am leaning towards this being a hardware thing.
Having said that, I know that this is not a CPU cooling problem as I am running a pretty capable setup here and that's something I've been through multiple times so I know there is spare room there...but it could be something else, such as memory, or even CPU/core problems.
Sooo...I went back to my CONFIG.SYS and re-enabled the system LOG stuff I had previously enabled:
Not sure though if there is anything else I should be looking at to try to maximize the data capture should RSYNC cause either that hardware or perhaps software fault again.
What have you used in your previous attempts to narrow this kind of a problem down?
Thanks!
Now the strange part is that I can't find anything listed in places like POPUPLOG.OS2 or as TRP files...so it's rather tough to figure out whether this is a hardware or a software issue. At the moment I am leaning towards this being a hardware thing.
Having said that, I know that this is not a CPU cooling problem as I am running a pretty capable setup here and that's something I've been through multiple times so I know there is spare room there...but it could be something else, such as memory, or even CPU/core problems.
Sooo...I went back to my CONFIG.SYS and re-enabled the system LOG stuff I had previously enabled:
Code: [Select]
...
DEVICE=G:\OS2\LOG.SYS /OFF
RUN=G:\OS2\SYSTEM\LOGDAEM.EXE /E:g:\tmp\trp
DUMPPROCESS=G:\tmp\trp /F=10240
RUN=G:\OS2\EPWDDR3.EXE
DEVICE=G:\OS2\EPWDD.SYS
...
Not sure though if there is anything else I should be looking at to try to maximize the data capture should RSYNC cause either that hardware or perhaps software fault again.
What have you used in your previous attempts to narrow this kind of a problem down?
Thanks!