we have a scheduled job that sometimes crashes. We've been unable to make it crash with tracing/debugging enabled. How should we setup pro exectuables for gateway jobs to get useful info ?
capture crash on windows server
Posted 26 June 2014 - 02:58 PM
I typically write my bat file to output to a logfile. Whenever there are issues, I can see when things ran, and how long it ran. I can also see what was returned by PROIV.
ECHO PROCESS STARTED %date% %time%>>logfile.txt P4TASK /task:<task_info> /oper:<operator_credentials> /codiv:<company_info> /params:<parameters> >> logfile.txt ECHO PROCESS COMPLETE %date% %time%>>logfile.txt
This is a simple example of how I usually put together the piece of my bat file that executes the task.
Here is an example logfile:
Posted 27 June 2014 - 08:22 AM
that's quite similar to how our job runs. The logfile though doesn't help as the kernel has crashed. There is activity on the Windows server from proivsrv.exe and p4wks.exe. on linux there is strace - has anyone used "stracent" ? If I can catch that info then I have something useful to give pro-iv support.
we could start the server with "c:> stracent -- proivsrv.exe" or suchlike but how would that work for a gateway call?
of the poster and do not represent those of any organisation.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users