Error when installing Zammad

Technical assistance
1

Expected behavior:

  • Working and configured Zammad

Actual behavior:

  • An 500 ERROR

Steps to reproduce the behavior:

  • Followed the step of the website on a deb12.
  • Obligated to installa elasticsearch.

Other

  • Returned error :

We’re sorry, but something went wrong.

<% else %>

<%= @exception.message %>

<% if @exception.backtrace %>

<% @exception.backtrace.each {|row| %>
  <%= row %>
<% } %>

<% end %> <% end %>

About system

  • Debian 12
  • PHP 8.2.7
2

Hi @Sotoamino. You should check your production.log file.

3

Hi @fliebe92

i have many info

INFO -- : ActionCable is using the redis instance at redis://localhost:6379.
INFO -- : Using Zammad's file store as Rails cache store.
INFO -- : Using the File back end for Zammad's web socket session store.

and in Apache2 logs :

[proxy:error] [pid 806548] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1:3000) failed
[proxy_http:error] [client XXX.XXX.XXX.XXX:XXX] AH01114: HTTP: failed to make connection to backend: 127.0.0.1

I don’t really understand the problem,

4

Well, if an error with code 500 appears in Zammad, there is also an error logged in your production.log. The given information is not helpful at all, I’m sorry.

5

I restarted Zammad service and i got a 503 now.

When looking deeper in the log, i got a fatal error :

ActiveRecord: :ConnectionNotEstablished (connection to server on socket "/var/run/postgresql/.S.PGSQL.5432" failed: FATAL: could not open file "base/16389/1259": No suck file or directory

I checked the folder, and PGSQL never create the file 1259

6

How did you install Zammad?

7

I followed all the steps of the site (adding the repo, installing with apt…)

the step i followed : Install from source — Zammad documentation

8

So, you have a source install? No package install?

9

My bad, i don’t get the good link

the good link : Install from package — Zammad documentation

10

Maybe restarting the services helps: Install from package — Zammad documentation

11

If the databases socket is not there, your database server most likely is not running. Double check if postgresql is up and running and if not check the logs to solve the issue

1 Like
12

I retry, but with install from source this time, and i encounter an error with rake db:create command :

zammad@XXXXXXXXXX:~$ rake db:create
rake aborted!
LoadError: cannot load such file -- listen
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `block in require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:299:in `load_dependency'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/evented_file_update_checker.rb:6:in `<main>'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `block in require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:299:in `load_dependency'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `require'
/opt/zammad/config/environments/development.rb:63:in `block in <main>'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/railtie.rb:234:in `instance_eval'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/railtie.rb:234:in `configure'
/opt/zammad/config/environments/development.rb:3:in `<main>'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `block in require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:299:in `load_dependency'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/engine.rb:571:in `block (2 levels) in <class:Engine>'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/engine.rb:570:in `each'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/engine.rb:570:in `block in <class:Engine>'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:32:in `instance_exec'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:32:in `run'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:61:in `block in run_initializers'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:50:in `each'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:50:in `tsort_each_child'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/initializable.rb:60:in `run_initializers'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/application.rb:391:in `initialize!'
/opt/zammad/config/environment.rb:7:in `<main>'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `block in require'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:299:in `load_dependency'
/usr/local/rvm/gems/ruby-3.1.3/gems/activesupport-6.1.7.6/lib/active_support/dependencies.rb:332:in `require'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/application.rb:367:in `require_environment!'
/usr/local/rvm/gems/ruby-3.1.3/gems/railties-6.1.7.6/lib/rails/application.rb:533:in `block in run_tasks_blocks'
/usr/local/rvm/gems/ruby-3.1.3/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/usr/local/rvm/gems/ruby-3.1.3/bin/ruby_executable_hooks:22:in `eval'
/usr/local/rvm/gems/ruby-3.1.3/bin/ruby_executable_hooks:22:in `<main>'
Tasks: TOP => db:create => db:load_config => environment
(See full trace by running task with --trace)

Do you know a solution to solve that ?

13

5th reset of the server with a complete reinstall in source installation, and i can confirm it’s not working anymore.

The only edit i made on the commande :

$ gem install pg -v ‘1.2.3’ – --with-pg-config=/usr/pgsql-14/bin/pg_config → gem install pg -v ‘1.2.3’ – --with-pg-config=/usr/lib/postgresql/15/bin/pg_config

and

$ vi config/database.yml → nano config/database.yml

And rake error. I guess something is no more supported.

14

No issue on my server. This needs to be related to your server/environment.

15

I restarted, but on a debian 11 this time and no problem. Maybe DEB12 gived by OVH have been modified and something went wrong

16

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