Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-83938

admin log report download missing data

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.4.4
    • Logging
    • None
    • MOODLE_404_STABLE

      Since upgrading to 4.4, downloading the admin logs via the "Download table data as..." feature yields only a partial download of the data and appends HTML/javascript for a new page at the bottom.

      We generate 200,000 - 400,000 logs on a typical day and use the logstore_standard logreader. When I ask for a download of the data for yesterday in either CSV or JSON format, the report appears to complete normally and I save the file. When I open the file, I find the first 20-30,000 rows (the ones closest to midnight) and then:

      <!DOCTYPE html>

      <html dir="ltr" lang="en" xml:lang="en">
      <head>
      <title>Error</title>
      ...

      followed by what looks like most of the site admin search box (in HTML).

      When I ask for EXCEL data, it runs for several minutes and returns the error page "This site can't be reached". With PDF, I just get a 504 gateway timeout.

      Note: I can use the web interface to navigate through yesterday's 3512 pages of data without issue.

      Steps to reproduce:
      1. With 100,000 rows in today's (or yesterday's) log, view the first page of the logs
      2. Select CSV in the "Download table data as" pull-down.
      3. Click "Download"
      4. Open the resulting file in your favorite editor

      I expected:
      A CSV file with the 100,000 rows

      I received:
      A CSV file with 23,670 rows of data followed by the HTML and javascript of a moodle web page.

            Unassigned Unassigned
            Yellocorvette Dave Scott
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.