Loading ...
Sorry, an error occurred while loading the content.

W3C logfile.

Expand Messages
  • lintadsl
    hi all, I have a little problem with IIS logfile. My current Webalizer does not read IIS log file correctly. I have no problem if I convert to NCSA format.
    Message 1 of 8 , Feb 5, 2002
    • 0 Attachment
      hi all,

      I have a little problem with IIS logfile. My current Webalizer does
      not read IIS log file correctly. I have no problem if I convert to
      NCSA format. But I would like to use W3C format, this way I don't
      have to convert. Here is the message I am getting.

      Using logfile C:\TEST\log\www\ex020102.log (IIS-W3C (IIS4,IIS5,...))
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Warning: Truncating oversized Agent field
      Warning: Truncating oversized Agent field
      Using logfile C:\TEST\log\www\ex020103.log (IIS-W3C (IIS4,IIS5,...))
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Skipping Microsof IIS header record
      Skipping bad record (27198)
      Skipping bad record (27199)
      Skipping bad record (27200)
      Skipping bad record (27201)

      Here is my config file.
      ExtentionLog log
      ConvertTime yes
      FolderLog C:\TEST\log\www\
      LogFile C:\TEST\log\www\ex*.log
      LogType iis
      OutputDir c:\test\webalizer\stats\

      Please let me know if you find wrong conf and should be addressed.
      Thank you in advanced.

      Sunny,
    • Waitman C. Gobble, II
      check out http://wcg2.com/_Articles@webalizer_nt the info is old but there are better links on that page. i believe a current version of webalizer nt reads iis
      Message 2 of 8 , Feb 5, 2002
      • 0 Attachment
        check out http://wcg2.com/_Articles@webalizer_nt

        the info is old but there are better links on that page.

        i believe a current version of webalizer nt reads iis logs.

        best,

        Waitman C. Gobble, II

        EMK Design
        5681 Beach Blvd Ste 101
        Buena Park CA 90621

        Toll Free (877) 290-2768
        Toll Free Fax (877) 290-2768
        Telephone (714) 522-2528

        ----- Original Message -----
        From: "lintadsl" <lintadsl@...>
        To: <webalizer@yahoogroups.com>
        Sent: Tuesday, February 05, 2002 1:47 PM
        Subject: [webalizer] W3C logfile.


        > hi all,
        >
        > I have a little problem with IIS logfile. My current Webalizer does
        > not read IIS log file correctly. I have no problem if I convert to
        > NCSA format. But I would like to use W3C format, this way I don't
        > have to convert. Here is the message I am getting.
        >
        > Using logfile C:\TEST\log\www\ex020102.log (IIS-W3C (IIS4,IIS5,...))
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Warning: Truncating oversized Agent field
        > Warning: Truncating oversized Agent field
        > Using logfile C:\TEST\log\www\ex020103.log (IIS-W3C (IIS4,IIS5,...))
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Skipping Microsof IIS header record
        > Skipping bad record (27198)
        > Skipping bad record (27199)
        > Skipping bad record (27200)
        > Skipping bad record (27201)
        >
        > Here is my config file.
        > ExtentionLog log
        > ConvertTime yes
        > FolderLog C:\TEST\log\www\
        > LogFile C:\TEST\log\www\ex*.log
        > LogType iis
        > OutputDir c:\test\webalizer\stats\
        >
        > Please let me know if you find wrong conf and should be addressed.
        > Thank you in advanced.
        >
        > Sunny,
        >
        >
        >
        >
        > To unsubscribe from this group, send an email to:
        > webalizer-unsubscribe@egroups.com
        > Webalizer homepage: http://www.webalizer.org
        > Webalizer for NT: http://www.medasys-lille.com/webalizer/
        >
        >
        >
        >
        > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
        >
        >
      • Waitman C. Gobble, II
        oops, duh. i mis-read your original email sorry. looks like you are having another issue. i ll look into it. waitman ... From: lintadsl
        Message 3 of 8 , Feb 5, 2002
        • 0 Attachment
          oops, duh. i mis-read your original email sorry.
          looks like you are having another issue. i'll look into it.

          waitman

          ----- Original Message -----
          From: "lintadsl" <lintadsl@...>
          To: <webalizer@yahoogroups.com>
          Sent: Tuesday, February 05, 2002 1:47 PM
          Subject: [webalizer] W3C logfile.


          > hi all,
          >
          > I have a little problem with IIS logfile. My current Webalizer does
          > not read IIS log file correctly. I have no problem if I convert to
          > NCSA format. But I would like to use W3C format, this way I don't
          > have to convert. Here is the message I am getting.
          >
          > Using logfile C:\TEST\log\www\ex020102.log (IIS-W3C (IIS4,IIS5,...))
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Warning: Truncating oversized Agent field
          > Warning: Truncating oversized Agent field
          > Using logfile C:\TEST\log\www\ex020103.log (IIS-W3C (IIS4,IIS5,...))
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Skipping Microsof IIS header record
          > Skipping bad record (27198)
          > Skipping bad record (27199)
          > Skipping bad record (27200)
          > Skipping bad record (27201)
          >
          > Here is my config file.
          > ExtentionLog log
          > ConvertTime yes
          > FolderLog C:\TEST\log\www\
          > LogFile C:\TEST\log\www\ex*.log
          > LogType iis
          > OutputDir c:\test\webalizer\stats\
          >
          > Please let me know if you find wrong conf and should be addressed.
          > Thank you in advanced.
          >
          > Sunny,
          >
          >
          >
          >
          > To unsubscribe from this group, send an email to:
          > webalizer-unsubscribe@egroups.com
          > Webalizer homepage: http://www.webalizer.org
          > Webalizer for NT: http://www.medasys-lille.com/webalizer/
          >
          >
          >
          >
          > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
          >
          >
        • Kees de Keizer
          ... Normal behaviour. IIS header records are no log entries. ... Blame the browser builder. ... Is this your current open logfile. These last lines are very
          Message 4 of 8 , Feb 6, 2002
          • 0 Attachment
            On Tue, 5 Feb 2002, lintadsl wrote:

            >I have a little problem with IIS logfile. My current Webalizer does
            >not read IIS log file correctly. I have no problem if I convert to
            >NCSA format. But I would like to use W3C format, this way I don't
            >have to convert. Here is the message I am getting.
            >
            >Using logfile C:\TEST\log\www\ex020102.log (IIS-W3C (IIS4,IIS5,...))
            >Skipping Microsof IIS header record
            >Skipping Microsof IIS header record
            >Skipping Microsof IIS header record
            >Skipping Microsof IIS header record

            Normal behaviour. IIS header records are no log entries.

            >Warning: Truncating oversized Agent field
            >Warning: Truncating oversized Agent field

            Blame the browser builder.

            >Using logfile C:\TEST\log\www\ex020103.log (IIS-W3C (IIS4,IIS5,...))
            >Skipping bad record (27198)
            >Skipping bad record (27199)
            >Skipping bad record (27200)
            >Skipping bad record (27201)

            Is this your current open logfile. These last lines are very
            normal. IIS always add a block of 64KB to an open logfile and
            replaces the empty data with log entries. If you run webalizer
            on an open log file, it sees this empty data as log entries,
            but because there's no data it's interpreted as a bad record.
            Nothing to worry about.
            --
            Kees de Keizer NT Administrator T: +31-10-2448344
            Wirehub! Internet PGP: 0x24E3770B F: +31-10-2448356
            http://www.wirehub.net/ mailto:kees.de.keizer@...
          • lintadsl
            The IIS server and Webalizer runs on seperate machine. I just copy logfiles to it and run Webalizer. So it shouldn t be open open logfile. Pus as you see the
            Message 5 of 8 , Feb 6, 2002
            • 0 Attachment
              The IIS server and Webalizer runs on seperate machine. I just copy
              logfiles to it and run Webalizer. So it shouldn't be open open
              logfile. Pus as you see the date of the logfile, it made quite ago.

              If you don't see any thing wrong on my configuration, I guess I am in
              big trouble. Some thing wrong my logfile?

              Sunny,


              --- In webalizer@y..., Kees de Keizer <kees.de.keizer@w...> wrote:
              > On Tue, 5 Feb 2002, lintadsl wrote:
              >
              > >I have a little problem with IIS logfile. My current Webalizer
              does
              > >not read IIS log file correctly. I have no problem if I convert to
              > >NCSA format. But I would like to use W3C format, this way I don't
              > >have to convert. Here is the message I am getting.
              > >
              > >Using logfile C:\TEST\log\www\ex020102.log (IIS-W3C
              (IIS4,IIS5,...))
              > >Skipping Microsof IIS header record
              > >Skipping Microsof IIS header record
              > >Skipping Microsof IIS header record
              > >Skipping Microsof IIS header record
              >
              > Normal behaviour. IIS header records are no log entries.
              >
              > >Warning: Truncating oversized Agent field
              > >Warning: Truncating oversized Agent field
              >
              > Blame the browser builder.
              >
              > >Using logfile C:\TEST\log\www\ex020103.log (IIS-W3C
              (IIS4,IIS5,...))
              > >Skipping bad record (27198)
              > >Skipping bad record (27199)
              > >Skipping bad record (27200)
              > >Skipping bad record (27201)
              >
              > Is this your current open logfile. These last lines are very
              > normal. IIS always add a block of 64KB to an open logfile and
              > replaces the empty data with log entries. If you run webalizer
              > on an open log file, it sees this empty data as log entries,
              > but because there's no data it's interpreted as a bad record.
              > Nothing to worry about.
              > --
              > Kees de Keizer NT Administrator T: +31-10-2448344
              > Wirehub! Internet PGP: 0x24E3770B F: +31-10-2448356
              > http://www.wirehub.net/ mailto:kees.de.keizer@w...
            • Kees de Keizer
              ... Have you checked your logfile? If it ends with a lot of spaces you ve copied a logfile which was still in use. When IIS opens a new logfile it closes the
              Message 6 of 8 , Feb 6, 2002
              • 0 Attachment
                On Wed, 6 Feb 2002, lintadsl wrote:

                > The IIS server and Webalizer runs on seperate machine.
                > I just copy logfiles to it and run Webalizer. So it
                > shouldn't be open open logfile. Plus as you see the date
                > of the logfile, it made quite ago.

                > If you don't see any thing wrong on my configuration, I guess
                > I am in big trouble. Some thing wrong my logfile?

                Have you checked your logfile? If it ends with a lot of spaces
                you've copied a logfile which was still in use. When IIS opens
                a new logfile it closes the old one and removes trailing spaces
                from the old logfile.
                --
                Kees de Keizer NT Administrator T: +31-10-2448344
                Wirehub! Internet PGP: 0x24E3770B F: +31-10-2448356
                http://www.wirehub.net/ mailto:kees.de.keizer@...
              • lintadsl
                Well, if this is open file, is there a way to fix? I don t see that lots of space at the end of each line. Shoud I convert to NCSA and get the report? Thank
                Message 7 of 8 , Feb 6, 2002
                • 0 Attachment
                  Well, if this is open file, is there a way to fix?
                  I don't see that lots of space at the end of each line.
                  Shoud I convert to NCSA and get the report?

                  Thank you in advance.

                  Here is a couple of lins from one of logfiles.

                  2002-01-03 00:11:50 209.163.3.205 216.46.230.177
                  GET /graphics/micondown0.gif - 200 359 Java+1.1 -
                  2002-01-03 00:11:50 209.163.3.205 216.46.230.177 GET /favicon.ico -
                  404 3415 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1) -
                  2002-01-03 00:11:50 209.163.3.205 216.46.230.177
                  GET /graphics/sicondown5.gif - 200 337 Java+1.1 -
                  2002-01-03 00:15:23 216.46.253.17 216.46.230.177 GET /index.asp - 200
                  22875 Mozilla/4.0+(compatible;MSIE+5.0;+Windows+NT) -
                  2002-01-03 00:24:49 24.159.235.139 216.46.230.177
                  GET /graphics/About_Us_Bar-01-01.gif - 200 8148 Mozilla/4.0+
                  (compatible;+MSIE+6.0;+Windows+98;+Q312461)
                  http://www.midwestsecurity.com/aboutus/history.asp
                  2002-01-03 00:24:49 24.159.235.139 216.46.230.177
                  GET /graphics/About_Us_Bar-01-02.gif - 200 2172 Mozilla/4.0+
                  (compatible;+MSIE+6.0;+Windows+98;+Q312461)
                  http://www.midwestsecurity.com/aboutus/history.asp
                  2002-01-03 00:24:49 24.159.235.139 216.46.230.177
                  GET /graphics/spacer.gif - 200 1044 Mozilla/4.0+
                  (compatible;+MSIE+6.0;+Windows+98;+Q312461)
                  http://www.midwestsecurity.com/aboutus/history.asp
                  2002-01-03 00:24:52 24.159.235.139 216.46.230.177
                  GET /aboutus/history.asp - 200 28145 Mozilla/4.0+
                  (compatible;+MSIE+6.0;+Windows+98;+Q312461)
                  http://search.msn.com/spbasic.htm?MT=midwest%20security%
                  20administrators
                  2002-01-03 00:24:57 24.159.235.139 216.46.230.177
                  GET /inc/slidem.class - 200 20888 Java+1.1 -

                  --- In webalizer@y..., Kees de Keizer <kees.de.keizer@w...> wrote:
                  > On Wed, 6 Feb 2002, lintadsl wrote:
                  >
                  > > The IIS server and Webalizer runs on seperate machine.
                  > > I just copy logfiles to it and run Webalizer. So it
                  > > shouldn't be open open logfile. Plus as you see the date
                  > > of the logfile, it made quite ago.
                  >
                  > > If you don't see any thing wrong on my configuration, I guess
                  > > I am in big trouble. Some thing wrong my logfile?
                  >
                  > Have you checked your logfile? If it ends with a lot of spaces
                  > you've copied a logfile which was still in use. When IIS opens
                  > a new logfile it closes the old one and removes trailing spaces
                  > from the old logfile.
                  > --
                  > Kees de Keizer NT Administrator T: +31-10-2448344
                  > Wirehub! Internet PGP: 0x24E3770B F: +31-10-2448356
                  > http://www.wirehub.net/ mailto:kees.de.keizer@w...
                • Kees de Keizer
                  ... These lines looke fine to me. ... I was talking about the end of the file. The bad records you refered to were at lines 27198-27201. ... No need to. For my
                  Message 8 of 8 , Feb 6, 2002
                  • 0 Attachment
                    On Wed, 6 Feb 2002, lintadsl wrote:

                    >Here is a couple of lins from one of logfiles:
                    >2002-01-03 00:11:50 209.163.3.205 216.46.230.177
                    >GET /graphics/micondown0.gif - 200 359 Java+1.1 -
                    >2002-01-03 00:11:50 209.163.3.205 216.46.230.177 GET /favicon.ico -
                    >404 3415 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1) -

                    These lines looke fine to me.

                    >Well, if this is open file, is there a way to fix?
                    >I don't see that lots of space at the end of each line.

                    I was talking about the end of the file. The bad records
                    you refered to were at lines 27198-27201.

                    >Shoud I convert to NCSA and get the report?

                    No need to. For my own server I run Webalizer every hour and
                    get those messages too. In my case it's because my logfiles
                    are opened by IIS. You might want to reconsider the moment
                    you copy those logfiles.
                    --
                    Kees de Keizer NT Administrator T: +31-10-2448344
                    Wirehub! Internet PGP: 0x24E3770B F: +31-10-2448356
                    http://www.wirehub.net/ mailto:kees.de.keizer@...
                  Your message has been successfully submitted and would be delivered to recipients shortly.