Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1143 Long analysis appears to fail

1.090
open
Jamie Cameron
5
2003-05-22
2003-05-22
Mark Edwards
No

I'm trying to set up a periodic webalizer analysis with DNS lookups. If
I choose "Generate Report" from within webmin, my browser times out
after a certain period of time, and the report never seems to be
generated.

A report does get generated at the regular intervals, but only about
3% of the DNS lookups seem to get added to the report.

If I generate a report from the command-line using the same config
as webmin (/usr/local/etc/webalizer.conf) the report gets generated
fine, along with all DNS lookups intact.

What gives?

Discussion

  • Jamie Cameron
    Jamie Cameron
    2003-05-22

    Logged In: YES
    user_id=129364

    This is really a browser bug - some (like IE) close the
    connection after a certain period of inactivity, causing the
    process on the server to be killed as well. The only work-
    around is to have the reported generated on schedule by a
    cron job, which the module can set up as well.

     
  • Logged In: NO

    Actually, this doesn't appear to have anything to do with
    the browser. The browser times out, yes, but the webalizer
    process actually completes (I didn't realize this at first).
    Regardless of how the analysis is done, via the browser or
    via cron, DNS lookups are not working properly.

    However, as I said, when I run webalizer via the command
    line using the same .conf file as webmin is using, the
    analysis works fine. Something is preventing webalizer from
    properly handling dns lookups when triggered via the webmin
    mechanism.

     
  • Jamie Cameron
    Jamie Cameron
    2003-05-23

    Logged In: YES
    user_id=129364

    Webmin uses a command like
    webalizer -c /path/to/config/file -o /output/dir -p /path/to/log
    to create the report. The actual config file path is either the
    global config, or a .conf file in /etc/webmin/webalizer
    corresponding to the log file. Try that at the command line
    and see if it works ..

    Make sure that any such file in /etc/webmin/webalizer is
    deleted to force the user of the global config when generating
    from within webmin.