2 replies to this topic

[Chris Mackenzie]

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 ?

[CurtisZ]

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:

 

PROCESS STARTED Tue 05/06/2014 16:10:07.07

p4ExecTask returned: # out params 1, length 15, # out sysvars 0, length 0:

  recordCount=469

PROCESS COMPLETE Tue 05/06/2014 16:10:09.91

 

This might help as far as something that could be implemented. I'm not stating I'm a batch file expert, so if someone has any ways to write this better, please chime in. Without any more information about the given process, this is really the only advice I have.

[Chris Mackenzie]

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?