Cannot select cusotmer when creating a ticket manually

Infos:

  • Used Zammad version: zammad_5.0.3-1646129126.fba5cdc8.focal_amd64
  • Used Zammad installation type: package
  • Operating system: ubuntu 20.04
  • Browser + version: google chrome 99.0.4844.51

Expected behavior:

when I create a ticket manually “incoming call” I can select the customer when typing a part of his name.

Actual behavior:

I cannot select a customer when creating a ticket “Incoming call”

Steps to reproduce the behavior:

The problem occurs after a week or two without any problems.
when I update Zammad it fixes the error temporarily.

This sounds like an issue with Elasticsearch. Can you uninstall and reinstall the ingest attachment?

sudo /usr/share/elasticsearch/bin/elasticsearch-plugin remove ingest-attachment
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment
sudo systemctl stop elasticsearch.service
sudo systemctl start elasticsearch.service

hi

I will try this as soon as the issue hits again.

I have seen this, its when elasticseach has a problem or is not running.
try sudo systemctl status elasticsearch

thx for the info, “sadly” it’s not happening currently (works for a few weeks after each update)

@compusurf
do you have an idea what I can do to fix it?

● elasticsearch.service - Elasticsearch
     Loaded: loaded (/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Thu 2022-03-31 06:06:04 CEST; 3 weeks 6 days ago
       Docs: https://www.elastic.co
   Main PID: 2511883 (code=killed, signal=KILL)

Mar 21 13:58:36 zammad systemd[1]: Starting Elasticsearch...
Mar 21 13:58:54 zammad systemd[1]: Started Elasticsearch.
Mar 31 06:06:04 zammad systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
Mar 31 06:06:04 zammad systemd[1]: elasticsearch.service: Failed with result 'signal'.

where should I look for hints?

I just updated the server as I always do to fix this… and it’s running again…

already happening again…

Does rebuilding the Elasticsearch index help?

zammad run rake searchindex:rebuild

I need to try this next time as I just updated again which fixed it temporarily