Browser Frontend crashes while opening

Infos:

  • Used Zammad version: 5.2.?
  • Used Zammad installation type: Package-> deb
  • Operating system: 20.04
  • Browser + version: Appears in any browser

Expected behavior:

Opening the Login page

Actual behavior:

Does not show the Login page

Steps to reproduce the behavior:

rds@zammad:/var/log/zammad$ uname -r
5.4.0-137-generic
rds@zammad:/var/log/zammad$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.5 LTS
Release: 20.04
Codename: focal

apt update && apt upgrade latest packages - obviously changes database tables or connection to it?

Zammad seems to work! but the Webinterface cannot load some Tables?

Here’s some debug text from production.log when trying to login:

I, [2023-01-13T08:52:14.172201 #2918-112280] INFO – : Started GET “/” for 192.168.1.46 at 2023-01-13 08:52:14 +0000
I, [2023-01-13T08:52:14.179038 #2918-112280] INFO – : Processing by InitController#index as HTML
I, [2023-01-13T08:52:14.185200 #2918-112280] INFO – : Rendered init/index.html.erb within layouts/application (Duration: 0.1ms | Allocations: 69)
I, [2023-01-13T08:52:14.186163 #2918-112280] INFO – : Rendered layout layouts/application.html.erb (Duration: 1.1ms | Allocations: 680)
I, [2023-01-13T08:52:14.187581 #2918-112280] INFO – : Completed 200 OK in 8ms (Views: 1.5ms | ActiveRecord: 1.8ms | Allocations: 3098)
I, [2023-01-13T08:52:14.543443 #2934-111340] INFO – : ProcessScheduledJobs running…
I, [2023-01-13T08:52:14.546331 #2934-111340] INFO – : Running job thread for ‘Process ticket escalations.’ (Ticket.process_escalation) status is: sleep
I, [2023-01-13T08:52:14.546470 #2934-111340] INFO – : Running job thread for ‘Check channels.’ (Channel.fetch) status is: sleep
I, [2023-01-13T08:52:14.546746 #2934-111340] INFO – : Running job thread for ‘Generate ‘Session’ data.’ (Sessions.jobs) status is: sleep
I, [2023-01-13T08:52:14.546858 #2934-111340] INFO – : Running job thread for ‘Check ‘Channel’ streams.’ (Channel.stream) status is: sleep
I, [2023-01-13T08:52:14.547977 #2934-111340] INFO – : Running job thread for ‘Execute planned jobs.’ (Job.run) status is: sleep
I, [2023-01-13T08:52:14.660435 #2918-112340] INFO – : Started POST “/api/v1/signshow” for 192.168.1.46 at 2023-01-13 08:52:14 +0000
I, [2023-01-13T08:52:14.667452 #2918-112340] INFO – : Processing by SessionsController#show as JSON
I, [2023-01-13T08:52:14.667538 #2918-112340] INFO – : Parameters: {“fingerprint”=>“-139893395”}
E, [2023-01-13T08:52:14.683156 #2918-112340] ERROR – : PG::UndefinedTable: ERROR: relation “user_overview_sortings” does not exist
LINE 8: WHERE a.attrelid = ‘“user_overview_sortings”’::regclass
^
(ActiveRecord::StatementInvalid)
lib/session_helper/collection_base.rb:11:in session' lib/session_helper.rb:25:in block in default_collections’
lib/session_helper.rb:23:in each' lib/session_helper.rb:23:in default_collections’
lib/session_helper.rb:5:in json_hash' app/controllers/sessions_controller.rb:45:in show’
app/controllers/application_controller/has_download.rb:21:in block (4 levels) in <module:HasDownload>' app/controllers/application_controller/has_download.rb:20:in block (3 levels) in module:HasDownload
app/controllers/application_controller/has_download.rb:19:in block (2 levels) in <module:HasDownload>' app/controllers/application_controller/handles_transitions.rb:16:in handle_transaction’
I, [2023-01-13T08:52:14.686693 #2918-112340] INFO – : Completed 422 Unprocessable Entity in 19ms (Views: 0.2ms | ActiveRecord: 4.9ms | Allocations: 7714)

--------------- end of log ------------------
i was just trying to open the login page.
192.168.1.46 is the machine i’m trying to access zammad from
here the zammad nginx log from accessing the machine:

192.168.1.46 - - [13/Jan/2023:08:52:14 +0000] “GET / HTTP/1.1” 200 1569 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0”
192.168.1.46 - - [13/Jan/2023:08:52:14 +0000] “POST /api/v1/signshow HTTP/1.1” 422 202 “http://192.168.1.38/” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0”
so accessing the zammad virtual machine seems ok (http 200)

seems the error is:
[2023-01-13T08:52:14.683156 #2918-112340] ERROR – : PG::UndefinedTable: ERROR: relation “user_overview_sortings” does not exist
LINE 8: WHERE a.attrelid = ‘“user_overview_sortings”’::regclass

Possible a db con problem?

no errors in:
/var/log/nginx/zammad.error.log

Did you change any credential information eventually?

Do you have any clue what was happening during the last updates?

Thank you

i figured out, elastic search isn’t running due to a possible version conflict.

here’s the journalctl -xe output
– A start job for unit elasticsearch.service has begun execution.

– The job identifier is 1313.
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: uncaught exception in thread [main]
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: java.lang.IllegalArgumentException: Plugin [ingest-attachment] was built for Elasticsearch version 7.17.6 but version 7.17.8 is running
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.plugins.PluginsService.verifyCompatibility(PluginsService.java:391)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.plugins.PluginsService.loadBundle(PluginsService.java:700)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.plugins.PluginsService.loadBundles(PluginsService.java:533)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.plugins.PluginsService.(PluginsService.java:170)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.node.Node.(Node.java:411)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.node.Node.(Node.java:309)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:234)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.cli.Command.main(Command.java:77)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80)
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: For complete error details, refer to the log at /var/log/elasticsearch/elasticsearch.log
Jan 13 09:14:45 zammad systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE
– Subject: Unit process exited
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– An ExecStart= process belonging to unit elasticsearch.service has exited.

– The process’ exit code is ‘exited’ and its exit status is 1.
Jan 13 09:14:45 zammad systemd[1]: elasticsearch.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– The unit elasticsearch.service has entered the ‘failed’ state with result ‘exit-code’.
Jan 13 09:14:45 zammad systemd[1]: Failed to start Elasticsearch.
– Subject: A start job for unit elasticsearch.service has failed
– Defined-By: systemd
– Support: Enterprise open source support | Ubuntu

– A start job for unit elasticsearch.service has finished with a failure.

– The job identifier is 1313 and the job result is failed.
Jan 13 09:14:45 zammad sudo[4004]: pam_unix(sudo:session): session closed for user root
Jan 13 09:15:01 zammad CRON[4260]: pam_unix(cron:session): session opened for user root by (uid=0)
Jan 13 09:15:01 zammad CRON[4261]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 09:15:01 zammad CRON[4260]: pam_unix(cron:session): session closed for user root
Jan 13 09:15:06 zammad sudo[4263]: rds : TTY=pts/1 ; PWD=/var/log/zammad ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jan 13 09:15:06 zammad sudo[4263]: pam_unix(sudo:session): session opened for user root by rds(uid=0)
Jan 13 09:15:31 zammad sudo[4263]: pam_unix(sudo:session): session closed for user root
Jan 13 09:15:35 zammad sudo[4271]: rds : TTY=pts/1 ; PWD=/var/log/zammad ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jan 13 09:15:35 zammad sudo[4271]: pam_unix(sudo:session): session opened for user root by rds(uid=0)

------ end of log ----

elasticsearch.log:
[2023-01-13T09:14:45,448][ERROR][o.e.b.Bootstrap ] [zammad] Exception
java.lang.IllegalArgumentException: Plugin [ingest-attachment] was built for Elasticsearch version 7.17.6 but version 7.17.8 is running
at org.elasticsearch.plugins.PluginsService.verifyCompatibility(PluginsService.java:391) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.loadBundle(PluginsService.java:700) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.loadBundles(PluginsService.java:533) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.(PluginsService.java:170) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.node.Node.(Node.java:411) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.node.Node.(Node.java:309) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:234) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434) [elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169) [elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160) [elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) [elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) [elasticsearch-cli-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.Command.main(Command.java:77) [elasticsearch-cli-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) [elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [elasticsearch-7.17.8.jar:7.17.8]
[2023-01-13T09:14:45,456][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [zammad] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: Plugin [ingest-attachment] was built for Elasticsearch version 7.17.6 but version 7.17.8 is running
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:173) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:160) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:77) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:112) ~[elasticsearch-cli-7.17.8.jar:7.17.8]
at org.elasticsearch.cli.Command.main(Command.java:77) ~[elasticsearch-cli-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:125) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) ~[elasticsearch-7.17.8.jar:7.17.8]
Caused by: java.lang.IllegalArgumentException: Plugin [ingest-attachment] was built for Elasticsearch version 7.17.6 but version 7.17.8 is running
at org.elasticsearch.plugins.PluginsService.verifyCompatibility(PluginsService.java:391) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.loadBundle(PluginsService.java:700) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.loadBundles(PluginsService.java:533) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.plugins.PluginsService.(PluginsService.java:170) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.node.Node.(Node.java:411) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.node.Node.(Node.java:309) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap$5.(Bootstrap.java:234) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:234) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:434) ~[elasticsearch-7.17.8.jar:7.17.8]
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:169) ~[elasticsearch-7.17.8.jar:7.17.8]
… 6 more

so the error seems to be.
Jan 13 09:14:45 zammad systemd-entrypoint[4013]: java.lang.IllegalArgumentException: Plugin [ingest-attachment] was built for Elasticsearch version 7.17.6 but version 7.17.8 is running

i know this is a lot … but maybe you could provide a fix for that version conflict? or should i just downgrade ? and how to downgrade ingest-attachment? help :frowning:

and btw:
i did everything according to the topic:

sudo /usr/share/elasticsearch/bin/elasticsearch-plugin remove ingest-attachment
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment

i also run /opt/zammad/contrib/packager.io/postinstall.sh

Elasticsearch service is now running! but it still doesn’t connect (frontend<->backend)

My Solution

Holy Moly! I did it !

wasn’t that easy … → i tried a lot: due to zammad runs in a virtualbox vm environment, i had a lot of retrypossibilities :smiley:

first of all, i tried to downgrade to ingest-attachment for ES 7.17.6 / that didn’t work of course - then i also tried to downgrade ES from 7.17.8 → 7.17.6 but i first had to purge the whole install - but with no way getting it working (unable to downgrade ES .8 to .6 etc…)
finally i just tried # dpkg-reconfigure zammad which absolutely works now.
oh dear - i will never again upgrade zammad :smiley:

Please don’t.

This is the reason - it indicates at least one non successful database migration:

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