All TagsNCSA input format (RSS)
  • Parse Errors in NSCA format -- can I do anything?

    The following line causes parse errors ("Log row terminates unexpectedly.") when the input format is NCSA. (IPs altered to protect the guilty.) 299.99.45.146 - - [25/Oct/2009:01:39:44 -0700] "GET /images/expert/spacer.gif\" HTTP/1.1" 404 11124 " http://www.website.com/lms...
    Posted to Forum by msdn_dave on 11-10-2009, 1:01 PM
  • RE: Replacing URL (request) with Friendly Names??

    FYI: Found the answer on SQL forums - This works...: select remotehostname, datetime, replace( replace( replace( replace( replace( replace( replace( replace(request,'GET /portal/site/marketintel/menuitem.6dc3d475ebbc54fca120231020248a0c/ HTTP/1.1','Home') , 'GET /portal/site/marketintel/menuitem.45dc4e7d2e1e54fca120231020248a0c...
    Posted to Forum by LogParser User : Greg C on 05-31-2007, 12:03 PM
  • Replacing URL (request) with Friendly Names??

    Hi, I'm using LogParser to import an Apache web server log into an MS SQL server db. I can't figure out how to clean up the URL's at the same time... My command: LogParser "SELECT RemoteHostName, DateTime, Request, StatusCode, BytesSent INTO MyTable FROM D:\IBMHTTPServer6\logs\access.log" -i:NCSA -o...
    Posted to Forum by LogParser User : Greg C on 05-30-2007, 1:38 PM
  • RE: NCSA Input format and the same as Output?

    Hi I did it....everything now is clear and the Logfile did it the way I want. For information the way I did it The sql-file: select RemoteHostName, UserName, DateTime, Request, StatusCode, BytesSent into oktober.log from wiseaccess311006.log WHERE DateTime > TO_TIMESTAMP('2006-10-15 00:00:00', 'yyyy...
    Posted to Forum by LogParser User : NickSoft on 11-16-2006, 3:07 AM
  • RE: NCSA Input format and the same as Output?

    Oops, NAT doesn't support multiplexing. Try using the TSV output instead. As long as you are only outputting one field, it shouldn't put any delimiters in and you should be alright. Are you sure you used the select statement I suggested instead of a *? SELECT FileNum, Text USING ...
    Posted to Forum by LogParser User : DEinspanjer on 11-14-2006, 9:13 AM
  • RE: NCSA Input format and the same as Output?

    Sounds good but doesn´t work Well I just try it and the only think is that LP is wrote a number in front of Line. The Line looks like this now: 1 C:\Programme\Log Parser 2.2\z2.log, 18547, 142.160.44.19, -, Anonymous, 11/14/2006, 5:45:01, GET /UNIFIL/gpers_img HTTP/1.0, 200, 479, http://www.flottenkdo...
    Posted to Forum by LogParser User : NickSoft on 11-14-2006, 2:43 AM
  • RE: NCSA Input format and the same as Output?

    If you use SELECT *, LP is going to output the filename and row number in addition to the other fields defined as NCSA. Try using this query and see if it works for you: logparser -i:TEXTLINE -o:NAT -headers FF "SELECT FileNum, Text USING ADD(1, DIV(Index, 1000)) AS FileNum INTO outfile-*.log FROM infile...
    Posted to Forum by LogParser User : DEinspanjer on 11-13-2006, 12:34 PM
  • RE: NCSA Input format and the same as Output?

    Hi me again I think I´ve found the problem why ma Web-Analyser isn´t able do evaluate the Information. It doesn´t matter which Outputformat I choose the LogParser always write something at the beginning of each line. The things he wrote in front of each line are: C:\Programme\Log Parser 2.2\wiseaccess311006...
    Posted to Forum by LogParser User : NickSoft on 11-13-2006, 3:40 AM
  • RE: NCSA Input format and the same as Output?

    Thx this sounds good Sometimes is it better then see it from another view....the new problem how I will give only the textline out? The Input data in textline is no problem also the text comparison but in which format I can make the output....the output formats are already the same then Input in NCSA...
    Posted to Forum by LogParser User : NickSoft on 11-13-2006, 2:10 AM
  • RE: NCSA Input format and the same as Output?

    If you just want to cut the file into smaller chunks so your web-analyzer is able to understand them then I wouldn't even bother with LP. There are plenty of programs that can chunk data like that or you could just write a simple Perl/Python/Ruby/Bash script to do it. If you want to use LP, I'd suggest...
    Posted to Forum by LogParser User : DEinspanjer on 11-10-2006, 10:53 AM
Page 1 of 5 (46 items) 1 2 3 4 5 Next >
Microsoft Communities