- Used Zammad version: 5.2.x
- Used Zammad installation type: package
- Operating system: Ubuntu 20.04
- Browser + version: Brave 1.39.11
I have issues in Monitoring for Current Status:
- Channel: Microsoft365::Account in is active but not fetched for about 2 hours
- scheduler may not run (last execution of ImportJob.start_registered about 3 hours ago) - please contact your system administrator
How can I fix this or solve these issues? can anyone help, please?
okey, I have solved these issues by rebooting server, increasing CPU, clearing cache in zammad, increasing parameters in conf file of postgres and rebuilding the indexes in elasticsearch
clear cache files:
$ systemctl stop zammad
$ zammad run rails r ‘Rails.cache.clear’
to increase params in conf file of postgres
Raise maximum allowed number of connections
$ sed -i “/max_connections/c\max_connections = 2000”
$ sed -i “/shared_buffers/c\shared_buffers = 2GB”
$ sed -i “/temp_buffers/c\temp_buffers = 256MB”
$ sed -i “/work_mem/c\work_mem = 10MB”
$ sed -i “/max_stack_depth/c\max_stack_depth = 5MB”
rebuild the indexes in elasticsearch
first check if ingest-attachment is instaled
$ /usr/share/elasticsearch/bin/elasticsearch-plugin list
To install ingest-attachment
$ /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment
force zammad to drop and rebuild the elasticsearch indexes
$ zammad run rake zammad:searchindex:rebuild
$ systemctl restart elasticsearch
Apply changes by restarting postgresql and Zammad (in this order)
$ systemctl restart postgresql zammad
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
The monitoring message indicates a crashed brackground worker / scheduler.
So restarting Zammad would be anything that’s needed.
Expecting that one followed Configure Database server — Zammad documentation already.