Dashboard stats isn't displaying anything

Hello there,

I’m currently running a manual installation of Zammad. I have installed elastic search and all the required package.

My problem is that the dashboard stats page displays nothing even though I have activities going on.

Here you can see that there are indeed open tickets:

At first I thought that elasticsearch isn’t working. However the rake searchindex:rebuild seems to be running fine:

$ rake searchindex:rebuild
drop indexes...done
delete pipeline (pipeline)... done
create indexes...done
create pipeline (pipeline)... done
reload data...
 reload Chat::Session
  - started at 2018-10-18 14:48:15 UTC
  - took 0 seconds
 reload Organization
  - started at 2018-10-18 14:48:15 UTC
  - took 0 seconds
 reload Ticket
  - started at 2018-10-18 14:48:16 UTC
  - took 58 seconds
 reload User
  - started at 2018-10-18 14:49:14 UTC
  - took 15 seconds

Thanks for your help!

  • Used Zammad version: 2.6.x
  • Used Zammad installation source: (source, package, …): custom install from the stable-sms branch
  • Operating system: Ubuntu 16.04
  • Browser + version: Chromium 70

please check websocket-server.rb and scheduler.rb in running

start:

bundle exec script/websocket-server.rb start &
bundle exec script/scheduler.rb start &

Here you go:

$ sudo service zammad-websocket status
● zammad-websocket.service - Zammad websocket
   Loaded: loaded (/etc/systemd/system/zammad-websocket.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-10-18 14:33:13 UTC; 29min ago
 Main PID: 48880 (ruby)
    Tasks: 2
   Memory: 153.6M
      CPU: 14.523s
   CGroup: /system.slice/zammad-websocket.service
           └─48880 script/websocket-server.rb -b 127.0.0.1 -p 6042 start                                                             

Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:15Z:client(87316440) send data to client
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:15Z:client(83021380) send data to client
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:30Z:client(-) check unused idle connections...
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:30Z:client(-) Status: websocket clients: 2
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:30Z:client(87316440) working...
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:30Z:client(83021380) working...
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:30Z:client(-) Status: ajax clients: 0
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:50Z:client(-) Status: websocket clients: 2
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:50Z:client(87316440) working...
Oct 18 14:59:50 Uliza-Answers bash[48880]: 2018-10-18T14:59:50Z:client(83021380) working...
lines 1-20/20 (END)
$ sudo service zammad-scheduler status
● zammad-scheduler.service - Zammad scheduler
   Loaded: loaded (/etc/systemd/system/zammad-scheduler.service; disabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-10-18 15:02:24 UTC; 1min 23s ago
  Process: 57088 ExecStart=/bin/bash -l -c ${BUNDLE_BINARY} exec script/scheduler.rb start (code=exited, status=0/SUCCESS)
 Main PID: 57225 (ruby)
    Tasks: 12
   Memory: 296.2M
      CPU: 15.260s
   CGroup: /system.slice/zammad-scheduler.service
           └─57225 scheduler                                                                                                         

Oct 18 15:02:15 Uliza-Answers systemd[1]: Starting Zammad scheduler...
Oct 18 15:02:24 Uliza-Answers bash[57088]: scheduler: process with pid 57225 started.
Oct 18 15:02:24 Uliza-Answers systemd[1]: Started Zammad scheduler.

look good. but scheduler just run 1min 23s ago? maybe you can wait a moment.

I have restarted a couple of times, and that issue has been ongoing for a long time.
Is the dashboard connected to elastic search?

No, elastic search just for Ticket Search and Report.

I see, so what could I be missing then?

Have any ERROR in log/production.log ?

Oh wait, now it seems to be working…
Sorry to have wasted your time.

Looks like restarting both websocket server and the scheduler did it

You are welcome, enjoy the zammad way~

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.