When running a search we run into the issue that a specific Ticket is not indexed. We tested to rebuild the index but still the Ticket is not (re)added to the search.
- Used Zammad version: 6.4.1
- Used Zammad installation type: Package
- Operating system: Debian GNU/Linux 11 (bullseye)
- Elasticsearch Version 7.10.2
- PostgreSQL 13.18 (Debian 13.18-0+deb11u1)
- Browser + version: Chrome Version 131.0.6778.140 (Official Build) (arm64)
Expected behavior:
When searching all tickets should be accessible / indexed via ticket number and title
Actual behavior:
The ticket can be accessed via URL: https://zammad.x/#ticket/zoom/3016 but for this ticket content don’t show up in the search.
The ticket is quite extensive: multiple messages and has multiple .pdf attached in various replies. Could this lead to index issues?
Steps to reproduce the behavior:
- All toher tickets are correctly shown in Zammad search.
- the following commands have already been executed:
- We did rebuild the index: sudo zammad run rake zammad:searchindex:rebuild[8] --trace
Does anybody have a suggestion what to check? Thanks!
Based on other posts, I tried: sudo zammad run rails r "p Ticket.find(3016).search_index_update_backend
Where others return true, this one spits out a long array with a base64 encoded element and payload size: 168M
Could the size of the ticket just be too big to get indexed? And what would be the way forward 
…
MUU4MUMxRDkyQTdGRj5dPj4NCnN0YXJ0eHJlZg0KMTE2DQolJUVPRg0K"}]}]}
Payload size: 168M
from /opt/zammad/lib/search_index_backend.rb:151:in add' from /opt/zammad/app/models/concerns/has_search_index_backend.rb:154:in search_index_update_backend’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/runner/runner_command.rb:46:in <main>' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/runner/runner_command.rb:46:in eval’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/runner/runner_command.rb:46:in block in perform' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/activesupport-7.1.4.1/lib/active_support/execution_wrapper.rb:92:in wrap’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/commands/runner/runner_command.rb:45:in perform' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/thor-1.3.2/lib/thor/command.rb:28:in run’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/thor-1.3.2/lib/thor/invocation.rb:127:in invoke_command' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/command/base.rb:178:in invoke_command’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/thor-1.3.2/lib/thor.rb:538:in dispatch' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/command/base.rb:73:in perform’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:71:in block in invoke' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:149:in with_argv’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/command.rb:69:in invoke' from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/railties-7.1.4.1/lib/rails/commands.rb:18:in ’
from internal:/opt/zammad/vendor/ruby-3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb:38:in require' from <internal:/opt/zammad/vendor/ruby-3.2.4/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in require’
from /opt/zammad/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' from /opt/zammad/bin/rails:4:in ’