#1463 STAFConnectionRead error during LOG QUERY

Win32::Win2003
closed-works-for-me
Sharon Lucas
5
2012-06-12
2012-06-11
Geza Geleji
No

I am trying to view a large (~80MB) log file using the log viewer in STAX Monitor. In response to selecting the "Display Job User Log" menu item from the "Display" menu, I get a dialog box stating that "The log query request failed with RC=22, Result=STAFConnectionRead: ReadFile, osRC=233: 10". The request string was "STAF hostname1 LOG QUERY ALL MACHINE hostname1 LOGNAME STAX_Job_123_User FROM 20120601@15:49:13". Looking at the list of Windows error codes on MSDN reveals that 233 stands for ERROR_PIPE_NOT_CONNECTED -- No process is on the other end of the pipe.

Trying to run a similar request ("STAF hostname1 LOG QUERY MACHINE hostname1 LOGNAME STAX_Job_123_User FROMRECORD 1 TORECORD 3200 ALL" ) from the command line results in the exact same error. However, if I change the value after "TORECORD" to 800, I get the list of log entries as expected.

Discussion

  • Geza Geleji
    Geza Geleji
    2012-06-11

    • summary: STAFConnectionRead during LOG QUERY --> STAFConnectionRead error during LOG QUERY
     
  • Sharon Lucas
    Sharon Lucas
    2012-06-11

    What version of STAF are you using on the machine where this STAF log file is located? e.g. What's the output from

    STAF hostname1 MISC VERSION

    Are you submit this LOG QUERY request on the machine where this STAF log file is located (submitting the request to local) as follows, do you get the same error?

    STAF local LOG QUERY MACHINE hostname1 LOGNAME STAX_Job_123_User FROMRECORD 1 TORECORD 3200 ALL

    My guess is that there is some "bad" data in one (or more) of the records between record 801 and record 3200. Can you do some more queries to track down the "bad" records (e.g. by changing the FROM/TORECORD values to determine the bad data record(s)?

     
  • Geza Geleji
    Geza Geleji
    2012-06-11

    Sorry for not including this earlier, I am using STAF 3.4.8.

    If I use 'STAF local LOG QUERY MACHINE ...', I still get the same error. Also, I managed to retrieve the contents of the whole log by doing it in four parts: 'FROMRECORD 1 TORECORD 800', 'FROMRECORD 801 TORECORD 1600', 'FROMRECORD 1601 TORECORD 2400', and 'FROMRECORD 2401 TORECORD 3200'. All of these four commands worked fine, and concatenating their outputs got me what I was looking for. Even 'FROMRECORD 1 TORECORD 2000' and 'FROMRECORD 1501 TORECORD 3500' seemed to work as expected. However, 'FROMRECORD 1 TORECORD 3000' fails with osRC 233.

     
  • Sharon Lucas
    Sharon Lucas
    2012-06-11

    Can you provide this log file to me (e.g. provide FTP access to it since it is large) so I can track down the offending record(s) which will hopefully provide more information about the cause of the problem?

    Also, provide the output from the following:

    STAF hostname1 VAR LIST

    where hostname1 is the name of the machine where this log file is located.

     
  • Sharon Lucas
    Sharon Lucas
    2012-06-11

    Ok, so no bad data in the log file. What is the output from:

    STAF hostname1 LOG LIST SETTINGS

     
  • Sharon Lucas
    Sharon Lucas
    2012-06-11

    In thinking about this more, the problem you were having trying to query all the records in a 80MB log file may have been due to simply running out of memory to process and/or return the result (as it is a single string containing all the data). If so, then there's not really anything we ca do to "fix" this issue -- other than to suggest to access the log in chunks (using the various LOG QUERY options provided) as you already have.

     
  • Sharon Lucas
    Sharon Lucas
    2012-06-11

    • assigned_to: nobody --> slucas
     
  • Geza Geleji
    Geza Geleji
    2012-06-12

    • status: open --> open-works-for-me
     
  • Geza Geleji
    Geza Geleji
    2012-06-12

    Executing "STAF hostname1 LOG QUERY MACHINE hostname1 LOGNAME STAX_Job_123_User FROMRECORD 1 TORECORD 3200 ALL" from a host with more physical RAM works fine.

     
  • Geza Geleji
    Geza Geleji
    2012-06-12

    • status: open-works-for-me --> closed-works-for-me