Hi, Thank you for the suggestion, but I found that the best I could do was to redirect standard output to a file. Currently I am going to use:
REM Sets up the STAF environment variables and starts STAFProc setlocal call "C:\STAF\STAFEnv.bat" set here=%cd% if not exist %here%\logs mkdir %here%\logs if "201" == "%DATE:~0,3%" set rnow=%DATE:~0,4%%DATE:~5,2%%DATE:~8,2%% TIME:~0,2%%TIME:~3,2% if not "201" == "%DATE:~0,3%" set rnow=%DATE:~10,4%%DATE:~4,2%%DATE:~7,2%% TIME:~0,2%%TIME:~3,2% set rnow=%rnow: =0% set outputlist=%here%\logs\StafOutput%rnow%.log start "Start STAF 3.4.2" /min "CMD /C C:\STAF\bin\STAFProc.exe >%outputlist%" endlocal This will keep logs going back awhile, and require me to 'cleanup' logs to some extent. I found I could not use '2>&1' on the redirection because the command line parsing for STAFProc failed. So the above is the best I could do. I still need to understand if I will need the trace code on service usage. regards, Richard "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." R. P. Feynman, "Report of the Presidential Commission on the Space Shuttle Challenger Accident" "Rene Slowenski" <rene.slowen...@ingres.com> 12/10/2010 04:10 AM To Sharon Lucas/Austin/i...@ibmus, Richard Pitkin/Westford/i...@lotus cc <staf-users@lists.sourceforge.net> Subject Re: [staf-users] How to collect data on failure Hello! It's just a suggestion, but I think it would be better to use: STAFProc > C:\staf\stafproc.out 2>&1 This way you make sure that both STDOUT and STDERR are redirected to the file. I am not currently sure if STAFProc writes anything to STDERR, though. Regards, René Slowenski Ingres QA Von: Sharon Lucas [mailto:luc...@us.ibm.com] Gesendet: Do 09.12.2010 16:33 An: Richard Pitkin Cc: staf-users@lists.sourceforge.net Betreff: Re: [staf-users] How to collect data on failure When you say that "staf appeared to just quit", are you saying that STAFProc was terminated on machine afw2008r2a ? If so, you should check STAFProc's output to see if there is any error messages about why it died. You can redirect STAFProc's output to a file when you start STAFProc on afw2008r2a to make sure STAFProc's output is saved. For example: STAFProc > C:\staf\stafproc.out Let me know what STAFProc's output contains when it has been killed. -------------------------------------------------------------- Sharon Lucas IBM Austin, luc...@us.ibm.com (512) 286-7313 or Tieline 363-7313 From: Richard Pitkin/Westford/i...@lotus To: staf-users@lists.sourceforge.net Date: 12/09/2010 09:15 AM Subject: [staf-users] How to collect data on failure Hi, We have a system that uses staf to run client/server testing. We had a failure where during a multi-hour run, staf appeared to just quit. In particular we received the following output: 13393 Error 20101209-02:13:26 afclient34....runTestSuite getOtherOSType: Failure looking for OSName using the 'STAF VAR' service on target machine 'afw2008r2a...'! RC=16 STAFResult=STAFConnectionProviderConnect: Error performing test read on connected endpoint: recv() RC=111: 22, Endpoint: tcp://afw2008r2a... 13394 Fail 20101209-02:13:26 afclient34....runTestSuite getOtherOSType: Terminating function. Error: Failure looking for OSName using the 'STAF VAR' service on target machine 'afw2008r2a....'! RC=16 STAFResult=STAFConnectionProviderConnect: Error performing test read on connected endpoint: recv() RC=111: 22, Endpoint: tcp://afw2008r2a.... 13395 Error 20101209-02:13:26 killDomino: BTN3: Server1(afw2008r2a...): Terminating function - Error: Failure looking for OSName using the 'STAF VAR' service on target machine 'afw2008r2a....'! RC=16 STAFResult=STAFConnectionProviderConnect: Error performing test read on connected endpoint: recv() RC=111: 22, Endpoint: tcp://afw2008r2a.... The job started at 20101208-11:58:06 so we know that this worked for quite awhile. The failing system is W2008r2 and the controller machine of the client and servers is Linux. The W2008r2 has version: staf afw2008r2a misc version Response -------- 3.3.4 The controller is: staf product-la misc version Response -------- 3.3.4.1 I checked the staf directories for information to see if there was any dumps of the jvm but there did not seem to be anything. Suggestions on what logging to enable to try and find out what the root issue is that we need to correct would be helpful. We often have jobs that last 24 hours, and this has happened before, so I am looking for a process that will be able to gather relevant information to resolve this. Thanks in advance, "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." R. P. Feynman, "Report of the Presidential Commission on the Space Shuttle Challenger Accident"[attachment "smime.p7s" deleted by Sharon Lucas/Austin/IBM] ------------------------------------------------------------------------------ This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
