ES searchindex:rebuild fails after update to 4.x

MrGeneration · July 16, 2021, 12:26pm

You may have been affected by this bug:

github.com/zammad/zammad

The rebuild of the index is failing

opened 10:37AM - 24 Jun 21 UTC

closed 03:41PM - 24 Jun 21 UTC

Pamalosebi

bug chat verified prioritised by payment

### Infos: * Used Zammad version: zammad.x86_64 0:4.1.0-1623318856.fa8592c0.centos7 * Installation method (source, package, ..): Package (RPM with yum) * Operating system: CentOS 7.4 * Database + version: psql (PostgreSQL) 13.3 * Elasticsearch version: 7.13.2 * Browser + version: Chromium 91.0.4472.114 * Ticket: #1088629 ### Expected behavior: * When Zammad was updated the reindexing should still work. ### Actual behavior: * The rebuild of the index is failing, after it was updated to version zammad.x86_64 0:4.1.0-1624523276.7163a88f.centos7. (it was zammad.x86_64 0:4.1.0-1623318856.fa8592c0.centos7 before) ### Steps to reproduce the behavior: * Check behavior before Update: ``` > zammad run rake searchindex:rebuild drop indexes...done delete pipeline (pipeline)... done create indexes...done create pipeline (pipeline)... done reload data... reload Chat::Session - started at 2021-06-24 09:57:46 UTC 67/67 - took 1 seconds reload Cti::Log - started at 2021-06-24 09:57:48 UTC - took 0 seconds reload KnowledgeBase::Answer::Translation - started at 2021-06-24 09:57:48 UTC 67/67 - took 6 seconds reload KnowledgeBase::Category::Translation - started at 2021-06-24 09:57:54 UTC 36/36 - took 0 seconds reload KnowledgeBase::Translation - started at 2021-06-24 09:57:55 UTC 1/1 - took 0 seconds reload Ticket::Priority - started at 2021-06-24 09:57:55 UTC 3/3 - took 0 seconds reload Ticket::State - started at 2021-06-24 09:57:55 UTC 7/7 - took 0 seconds reload Group - started at 2021-06-24 09:57:55 UTC 6/6 - took 0 seconds reload Organization - started at 2021-06-24 09:57:55 UTC 26/26 - took 0 seconds reload StatsStore - started at 2021-06-24 09:57:56 UTC 81/81 - took 1 seconds reload Ticket - started at 2021-06-24 09:57:57 UTC 100/2248 200/2248 300/2248 400/2248 500/2248 600/2248 700/2248 800/2248 900/2248 1000/2248 1100/2248 1200/2248 1300/2248 1400/2248 1500/2248 1600/2248 1700/2248 1800/2248 1900/2248 2000/2248 2100/2248 2200/2248 2248/2248 - took 156 seconds reload User - started at 2021-06-24 10:00:34 UTC 100/556 200/556 300/556 400/556 500/556 556/556 - took 6 seconds ``` * then Upgrade: ``` > yum update zammad yum update zammad Geladene Plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile epel/x86_64/metalink | 34 kB 00:00:00 * base: mirror.fra10.de.leaseweb.net * epel: ftp-stud.hs-esslingen.de * extras: ftp.rz.uni-frankfurt.de * updates: centos.mirror.net-d-sign.de base | 3.6 kB 00:00:00 elasticsearch-7.x | 1.3 kB 00:00:00 epel | 4.7 kB 00:00:00 extras | 2.9 kB 00:00:00 updates | 2.9 kB 00:00:00 zammad/x86_64/signature | 473 B 00:00:00 zammad/x86_64/signature | 1.3 kB 00:00:00 (1/4): epel/x86_64/updateinfo | 1.0 MB 00:00:00 (2/4): epel/x86_64/primary_db | 6.9 MB 00:00:00 (3/4): zammad/x86_64/primary | 8.0 MB 00:00:01 ETA (4/4): zammad/x86_64/primary | 45 kB 00:00:00 zammad: [ ] 1/157 zammad: [############################################################################################## ] 156/157 zammad 157/157 AbhÃ¤ngigkeiten werden aufgelÃ¶st --> TransaktionsprÃ¼fung wird ausgefÃ¼hrt ---> Paket zammad.x86_64 0:4.1.0-1623318856.fa8592c0.centos7 markiert, um aktualisiert zu werden ---> Paket zammad.x86_64 0:4.1.0-1624523276.7163a88f.centos7 markiert, um eine Aktualisierung zu werden --> AbhÃ¤ngigkeitsauflÃ¶sung beendet AbhÃ¤ngigkeiten aufgelÃ¶st ================================================================================================================== Package Arch Version Paketquelle GrÃ¶ÃŸe ================================================================================================================== Aktualisieren: zammad x86_64 4.1.0-1624523276.7163a88f.centos7 zammad 122 M TransaktionsÃ¼bersicht ================================================================================================================== Aktualisieren 1 Paket Gesamte DownloadgrÃ¶ÃŸe: 122 M Is this ok [y/d/N]: y Downloading packages: No Presto metadata available for zammad zammad-4.1.0-1624523276.7163a88f.centos7.x 0% [ ] 0.0 B/s | 0 B --:--:-- ETA zammad-4.1.0-1624523276.7163a88f.centos7.x86_64.rpm | 122 MB 00:00:03 Running transaction check Running transaction test Transaction test succeeded Running transaction Aktualisieren : zammad-4.1.0-1624523276.7163a88f.centos7.x [ ] 1/2 Aktualisieren : zammad-4.1.0-1624523276.7163a88f.centos7.x [########################################## ] 1/2 Aktualisieren : zammad-4.1.0-1624523276.7163a88f.centos7.x86_64 1/2 # (Re)creating init scripts Nothing to do. Nothing to do. Nothing to do. # Enabling Zammad on boot # Stopping Zammad # database.yml found. Updating db... == 20210617051913 Issue3618GoogleCalendarUrlHttps: migrating ================== == 20210617051913 Issue3618GoogleCalendarUrlHttps: migrated (0.0040s) ========= # Updating translations... # Configuring Elasticsearch... -> removing [ingest-attachment]... -> Installing ingest-attachment -> Downloading ingest-attachment from elastic [ ] 1%Â Â [=================================================] 100%Â Â @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: plugin requires additional permissions @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ * java.lang.RuntimePermission accessClassInPackage.sun.java2d.cmm.kcms * java.lang.RuntimePermission accessDeclaredMembers * java.lang.RuntimePermission getClassLoader * java.lang.reflect.ReflectPermission suppressAccessChecks * java.security.SecurityPermission createAccessControlContext See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html for descriptions of what these permissions allow and the associated risks. -> Installed ingest-attachment -> Please restart Elasticsearch to activate any plugins installed # Starting Zammad # Creating webserver bootstart # Restarting webserver nginx #################################################################################### Add your fully qualified domain name or public IP to servername directive of nginx, if this installation is done on a remote server. You have to change: /etc/nginx/conf.d/zammad.conf and restart nginx process. Otherwise just open http://localhost/ in your browser to start using Zammad. Remember to enable selinux and firewall rules! Use the following commands: setsebool httpd_can_network_connect on -P firewall-cmd --zone=public --add-service=http --permanent firewall-cmd --zone=public --add-service=https --permanent firewall-cmd --reload #################################################################################### AufrÃ¤umen : zammad-4.1.0-1623318856.fa8592c0.centos7.x86_64 2/2 ÃœberprÃ¼fung lÃ¤uft: zammad-4.1.0-1624523276.7163a88f.centos7.x86_64 1/2 ÃœberprÃ¼fung lÃ¤uft: zammad-4.1.0-1623318856.fa8592c0.centos7.x86_64 2/2 Aktualisiert: zammad.x86_64 0:4.1.0-1624523276.7163a88f.centos7 Komplett! yum update zammad 64,30s user 9,01s system 38% cpu 3:08,97 total > systemctl restart elasticsearch.service ``` * And finally try to reindex again: [bug.txt](https://github.com/zammad/zammad/files/6708453/bug.txt) ``` /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bundler-1.17.3/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors' /opt/zammad/vendor/bundle/ruby/2.6.0/gems/bundler-1.17.3/exe/bundle:22:in `<top (required)>' /opt/zammad/bin/bundle:3:in `load' /opt/zammad/bin/bundle:3:in `<main>' Tasks: TOP => searchindex:rebuild (See full trace by running task with --trace) ``` Yes I'm sure this is a bug and no feature request or a general question.

Update to the latest available stable Zammad version to fix it and try again.