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

Re: [webalizer] Re: No valid records found, for some virtual sites

Expand Messages
  • Bradford L. Barrett
    There are realy only 3 reasons why you get no valid records found ; 1) Trying to process an invalid log file. Caused by specifing the wrong filename for the
    Message 1 of 9 , Jul 2, 2005
    • 0 Attachment
      There are realy only 3 reasons why you get 'no valid records found';

      1) Trying to process an invalid log file. Caused by specifing the wrong
      filename for the log file to use. An indication of this is the totals
      (at the end of processing) showing a huge number of 'bad' records.

      2) There really were no records found. Caused by either trying to process
      an empty log file, or if using incremental mode, trying to process a
      log file that does not contain any new records since last processing.

      3) There is a configuration error that causes all records to be ignored.
      An indication of this is in the totals (at the end of processing)
      showing a huge number of 'ignored' records.

      From what you write, it would seem that #3 above would be the culprit.
      Examine your config file for obvious errors (or send a copy here so
      others might look).

      --
      On Sat, 2 Jul 2005, mtsu_charlie wrote:

      > Hello;
      >
      > That was a great idea to help get to the root of the problem. The
      > problem is not the log files because if I replace a working one with a
      > nonworking one, it works (and vise-versa).
      >
      > There is nothing unusual about the paths:
      >
      > /home/wynonna/logs/access_log
      > /home/ilovewink/logs/access_log
      >
      > any other ideas?
      >
      > thank you so much for helping!
      >
      > -charlie

      --
      Bradford L. Barrett brad@...
      A free electron in a sea of neutrons DoD#1750 KD4NAW

      The only thing Micro$oft has done for society, is make people
      believe that computers are inherently unreliable.
    • Enric Naval
      Then there are two options, mainly: 1- the names are not correct in the configuration, instead of ilovewink maybe you have put accidently llovewink or
      Message 2 of 9 , Jul 4, 2005
      • 0 Attachment
        Then there are two options, mainly:


        1- the names are not correct in the configuration,
        instead of "ilovewink" maybe you have put accidently
        "llovewink" or "il0vewink" or something similar and
        didn't notice. Try re-typing the names in the
        configuration program.


        2- the names are correct, but webalizer can't access
        the files because the permissions in the files are
        wrong. Maybe the "wyonna" directory has the
        permissions set so that only the owner of the
        directory can read the contents, so webalizer can't
        reach the "logs" directory inside "wyonna", even if
        "logs" is set to be readable by everyone. I would say
        this the most probable cause of the problem.


        Also, you know, maybe you should put all log files
        inside a "/logs" directory and name them as the
        website name ("/logs/wyonna_log",
        "/logs/ilovewink_log" and similar). This way clueless
        users won't be able to accidentaly delete their own
        logs and you can also set them to be owned by the same
        user, like apache.apache, and set them to be written
        only by their owner.


        --- mtsu_charlie <mtsu_charlie@...> wrote:

        > Hello;
        >
        > That was a great idea to help get to the root of the
        > problem. The
        > problem is not the log files because if I replace a
        > working one with a
        > nonworking one, it works (and vise-versa).
        >
        > There is nothing unusual about the paths:
        >
        > /home/wynonna/logs/access_log
        > /home/ilovewink/logs/access_log
        >
        > any other ideas?
        >
        > thank you so much for helping!
        >
        > -charlie
        >
        > --- In webalizer@yahoogroups.com, Enric Naval
        > <enventa2000@y...> wrote:
        > > Hello:
        > >
        > > The logs seem to be OK. However, they lack both
        > the
        > > referrer and the user agent. Look at this line:
        > >
        > > 216-155-90-241.bk2-dsl.surnet.cl - -
        > > [02/Jul/2005:21:01:21 +0200] "GET
        > > /i2004/BajarPonencia/50.pdf HTTP/1.1" 200 237623
        > >
        >
        "http://www.google.cl/search?hl=es&q=este+es+un+ejemplo+de+ortogonalidad&btnG=B%C3%BAsqueda&meta="
        > > "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
        > 5.1)"
        > >
        > > Your logfile lacks the last two fields, the
        > referrer
        > > field (with the google entry) and the user agent
        > (with
        > > the mozilla entry). However, this is not the
        > problem
        > > you're having, because then both logs would fail.
        > >
        > >
        > > Try this: look at the name of the logfiles and to
        > the
        > > directory path to the logfiles. Maybe the 20 logs
        > > failing have strange charaters in the logname,
        > like
        > > "*" or some unicode character like "ñ" or "ç" that
        > may
        > > be confusing webalizer.
        > >
        > > Try renaming one of the logfiles to the name of
        > one of
        > > the working logfiles and moving it to a folder
        > where
        > > the logs are working (make backups of the
        > directory
        > > first), or replace one working log with a
        > non-working
        > > one. Then use webalizer on it. If it works this
        > time,
        > > then the logfile was failing because webalizer
        > > couldn't process correctly the path to the file or
        > the
        > > name of the file itself, not because of the
        > contents
        > > of the file.
        > >
        > >
        > >
        > >
        > >
        > > --- mtsu_charlie <mtsu_charlie@y...> wrote:
        > >
        > > > Thanks for your help!
        > > >
        > > > Here is the first few lines of an access_log
        > that
        > > > works:
        > > >
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:33 -0500]
        > "GET /
        > > > HTTP/1.1" 200
        > > > 3342
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:34 -0500]
        > "GET
        > > > /images/home/bpi_white_right.jpg HTTP/1.1" 200
        > 29774
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:34 -0500]
        > "GET
        > > > /images/home/bp_white_left.jpg HTTP/1.1" 200
        > 26247
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:35 -0500]
        > "GET
        > > > /images/get_flash_player.gif HTTP/1.1" 200 1629
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:35 -0500]
        > "GET /
        > > > HTTP/1.1" 304 -
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:35 -0500]
        > "GET
        > > > /video/swf/Brad_Video1.swf HTTP/1.1" 200 78334
        > > > 82.148.97.67 - - [26/Jun/2005:04:02:37 -0500]
        > "GET
        > > > /favicon.ico
        > > > HTTP/1.1" 404 297
        > > > 144.134.81.105 - - [26/Jun/2005:04:03:03 -0500]
        > "GET
        > > > /images/home/bpi_white_right.jpg HTTP/1.1" 206
        > 2465
        > > > 144.134.81.105 - - [26/Jun/2005:04:03:03 -0500]
        > "GET
        > > > /images/get_flash_player.gif HTTP/1.1" 200 1629
        > > > 68.57.55.130 - - [26/Jun/2005:04:04:14 -0500]
        > "GET
        > > > /robots.txt
        > > > HTTP/1.1" 404 296
        > > > 67.40.20.104 - - [26/Jun/2005:04:04:49 -0500]
        > "GET
        > > > /favicon.ico
        > > > HTTP/1.1" 404 297
        > > > 83.197.166.204 - - [26/Jun/2005:04:04:49 -0500]
        > "GET
        > > > /home/home.htm
        > > > HTTP/1.1" 200 13216
        > > > 83.197.166.204 - - [26/Jun/2005:04:04:49 -0500]
        > "GET
        > > > /bp.css HTTP/1.1"
        > > > 200 605
        > > >
        > > > And here is the first few lines from one that
        > does
        > > > not work:
        > > >
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > / HTTP/1.1" 200
        > > > 12094
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /fade.js
        > > > HTTP/1.1" 404 285
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_news.gif HTTP/1.1" 200 3055
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/news_icon.gif HTTP/1.1" 200 669
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/background_ocean.jpg HTTP/1.1" 200 21696
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_spotlight.jpg HTTP/1.1" 200
        > > > 2932
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_background.gif HTTP/1.1"
        > 200
        > > > 116
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_footer.gif HTTP/1.1" 200
        > 464
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_tour.jpg HTTP/1.1" 200 2562
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_feature_list.jpg HTTP/1.1" 200 2821
        > > > 65.162.107.189 - - [30/Jun/2005:16:54:10 -0500]
        > "GET
        > > > /images/home_title_journey.jpg HTTP/1.1" 200
        > 2385
        > > > 65.162.107.189 - - [30/Jun/2005:17:14:39 -0500]
        > "GET
        > > > /?content=news
        > > > HTTP/1.1" 200 20591
        > > >
        > > > I also went through and checked the config files
        > and
        > > > there are no
        > > > entries for IgnoreURL or IgnoreUser either.
        > > >
        > > > thank you,
        > > > -charlie
        > > >
        > > > --- In webalizer@yahoogroups.com, Enric Naval
        > > > <enventa2000@y...>
        > > > wrote:
        > > > > Hello:
        > > > >
        > > > > I suggest you copy&paste the first ten lines
        > of
        > > > one of
        > > > > the logfiles that works and the first ten
        > lines of
        > > > a
        > > > > logfile that does NOT work, and then post them
        > > > here.
        > > > > This way we can compare and see if the problem
        > is
        > > > in
        > > > > the logfiles.
        > > > >
        > > > > Also, do you have any IgnoreURL line in your
        > > > > webalizer.conf file? Maybe you are ignoring so
        > > > many
        > > > > URLs that there is no line left, but I'm not
        > sure
        > > > this
        > > > > is the problem.
        > > > >
        > > > >
        > > > >
        > > > > --- mtsu_charlie <mtsu_charlie@y...> wrote:
        > > > >
        > > > > > Hello, we are hosting about 80 sites on a
        > redhat
        > > > > > server. Apache
        > > > > > creates individual log files for each of the
        > > > sites
        > > > > > and webalizer is
        > > > > > setup to read them. It only works on about
        > 60 of
        > > > the
        > > > > > sites. When I try
        > > > > > to run webalizer on any of the other 20, I
        > get
        > > > the
        > > > > > message "No valid
        > > > > > records found."
        > > > > >
        > > > > > All of the sites are setup exactly the same
        > > > > > way(using webadmin). The
        > > > > > log files are all there and can be viewed
        > with a
        > > > > > text editor. The
        > > > > > sizes vary from 300KB to 30MB, depending on
        > > > site.
        > > > > >
        > > > > > I have been working on this off and on over
        > a
        > > > week,
        > > > > > and have read
        > > > > > everything that I could find, and have no
        > more
        > > > > > ideas.
        > > > > >
        > > > > > I welcome all suggestions on what may be
        > causing
        > > > > > this, thanks!
        > > > > >
        > > > > > -charlie
        > > > > >
        > > > > >
        > > > > >
        > > > >
        > > > >
        > > > > Enric Naval
        > > > > Estudiante de Informática de Gestión en la Udl
        > > > (Lleida)
        > > > > GRIHO webalizer.conf
        > > > >
        > http://griho.udl.es/webalizer/webalizer.conf.txt
        > > > >
        > > > >
        > > > >
        > > > >
        > > >
        > ____________________________________________________
        > > >
        > > > > Yahoo! Sports
        > > > > Rekindle the Rivalries. Sign up for Fantasy
        > > > Football
        > > > > http://football.fantasysports.yahoo.com
        > > >
        > > >
        > > >
        > >
        > >
        > > Enric Naval
        > > Estudiante de Informática de Gestión en la Udl
        > (Lleida)
        > > GRIHO webalizer.conf
        > > http://griho.udl.es/webalizer/webalizer.conf.txt
        > >
        > > __________________________________________________
        > > Do You Yahoo!?
        > > Tired of spam? Yahoo! Mail has the best spam
        > protection around
        > > http://mail.yahoo.com
        >
        >
        >


        Enric Naval
        Estudiante de Informática de Gestión en la Udl (Lleida)
        GRIHO webalizer.conf
        http://griho.udl.es/webalizer/webalizer.conf.txt

        __________________________________________________
        Do You Yahoo!?
        Tired of spam? Yahoo! Mail has the best spam protection around
        http://mail.yahoo.com
      • Bradford L. Barrett
        ... [...] ... [...] Both of those would result in the program producing the error: Error: Can t open log file And terminating immediately. It would
        Message 3 of 9 , Jul 4, 2005
        • 0 Attachment
          Enric once said:
          > 1- the names are not correct in the configuration,
          [...]
          > 2- the names are correct, but webalizer can't access
          > the files because the permissions in the files are
          > wrong.
          [...]


          Both of those would result in the program producing the error:

          "Error: Can't open log file <name>"

          And terminating immediately. It would never get to the point of saying
          that no valid records were found, so neither of those conditions could
          cause the problem.

          --
          Bradford L. Barrett brad@...
          A free electron in a sea of neutrons DoD#1750 KD4NAW

          How do you give Microsoft the benefit of the doubt when you
          know that if you were to throw it in a room with truth, you'd
          risk a matter/anti-matter explosion? -- Nicholas Petreley IDG
        • mtsu_charlie
          Thanks for the help everyone! It looks like the problem is with Webmin, not Webalizer. We were able to run Webalizer directly from the command line and get
          Message 4 of 9 , Jul 5, 2005
          • 0 Attachment
            Thanks for the help everyone!

            It looks like the problem is with Webmin, not Webalizer.

            We were able to run Webalizer directly from the command line and get
            stats for accounts that were not working.

            Through Webmin, the accounts are set up to generate stats at various
            times throughout the night. The ones we were having a problem with
            were not doing that at all. When we select "generate" for any of them,
            nothing happens.

            -charlie


            --- In webalizer@yahoogroups.com, "Bradford L. Barrett" <brad@m...> wrote:
            >
            > Enric once said:
            > > 1- the names are not correct in the configuration,
            > [...]
            > > 2- the names are correct, but webalizer can't access
            > > the files because the permissions in the files are
            > > wrong.
            > [...]
            >
            >
            > Both of those would result in the program producing the error:
            >
            > "Error: Can't open log file <name>"
            >
            > And terminating immediately. It would never get to the point of saying
            > that no valid records were found, so neither of those conditions could
            > cause the problem.
            >
            > --
            > Bradford L. Barrett brad@m...
            > A free electron in a sea of neutrons DoD#1750 KD4NAW
            >
            > How do you give Microsoft the benefit of the doubt when you
            > know that if you were to throw it in a room with truth, you'd
            > risk a matter/anti-matter explosion? -- Nicholas Petreley IDG
          Your message has been successfully submitted and would be delivered to recipients shortly.