Reports Missing Data

Infos:

  • Used Zammad version: 5.0.x
  • Used Zammad installation type: (source, package, docker-compose, …) package
  • Operating system: Ubuntu 20
  • Browser + version: firefox 99.0.1

I noticed that some of my report profiles are missing data. I have a profile that selects all open tickets and a large number of tickets are missing. I created a new profile selecting state of open and a specific organization and I can see the tickets in the preview pane

But when I go to the reporting menu and select that report profile that I just created, it is empty

Am I doing something wrong and or how do I resolve this ?

I went searching on reports and I ran across a couple of posts that mentioned rebuilding the elasticsearch search index. I used he following command on the linux command line sudo zammad run rake searchindex:rebuild

Nothing jumped out at me BUT it does seem that the my report does show the missing data. Should I put this in CRONTAB and preform it every so often ???

sudo zammad run rake searchindex
drop indexes...done
delete pipeline (pipeline)... done
create indexes...done
create pipeline (pipeline)... done
reload data...
 reload Group
  - started at 2022-04-18 16:44:58 UTC
        7/7
  - took 0 seconds
 reload Ticket
  - started at 2022-04-18 16:44:58 UTC
        42/42
  - took 7 seconds
 reload Organization
  - started at 2022-04-18 16:45:06 UTC
        26/26
  - took 0 seconds
 reload Chat::Session
  - started at 2022-04-18 16:45:06 UTC
  - took 0 seconds
 reload Ticket::State
  - started at 2022-04-18 16:45:06 UTC
        7/7
  - took 0 seconds
 reload Ticket::Priority
  - started at 2022-04-18 16:45:07 UTC
        3/3
  - took 0 seconds
 reload User
  - started at 2022-04-18 16:45:07 UTC
        31/31
  - took 0 seconds
 reload KnowledgeBase::Category::Translation
  - started at 2022-04-18 16:45:07 UTC
        2/2
  - took 0 seconds
 reload KnowledgeBase::Translation
  - started at 2022-04-18 16:45:07 UTC
        1/1
  - took 0 seconds
 reload KnowledgeBase::Answer::Translation
  - started at 2022-04-18 16:45:07 UTC
        3/3
  - took 0 seconds
 reload Cti::Log
  - started at 2022-04-18 16:45:08 UTC
  - took 0 seconds
 reload StatsStore
  - started at 2022-04-18 16:45:08 UTC
        6/6
  - took 0 seconds

Crontab the elasticserach index rebuild good idea Yeah Nay if Yeah how often ?

P.S. I have not had another incident of reports not working

Jfyi, I have a similar issue with elasticsearch:
https://community.zammad.org/t/elasticsearch-forgets-results-from-attachments-over-time/

Maybe the underlaying problem is the same.
Anyway, yes, although not a real solution cron does help. :slightly_smiling_face:

I’m not sure why my index disappeared and luckily I only had to rebuild it once. I do know that some (if not all) of the tickets created had .pdf attachments

If it becomes a problem for me I’ll add your crontab solution

# elasticsearch attachments index workaround  At minute 7 past every 3rd hour
7 */3  * * *   root    zammad run rake searchindex:rebuild > /dev/null

Just don’t.
Like really. It’s no solution and brings more issues than solving issues.

:ok_hand: I’ll only do it if searches and reports don’t work

1 Like