502 bad gateway with zammad-scheduler

Hello everyone,

I am getting 502 bad gateway.
The problem is for me to start zammad-scheduler service.

It fails with following errors
[root@zmd4 zammad]# systemctl start zammad-scheduler
Job for zammad-scheduler.service failed because the control process exited with error code. See “systemctl status zammad-scheduler.service” and “journalctl -xe” for details.

[root@zmd4 zammad]# systemctl status zammad-scheduler.service
● zammad-scheduler.service - Zammad scheduler
Loaded: loaded (/etc/systemd/system/zammad-scheduler.service; disabled; vendor preset: disabled)
Active: activating (start) since Thu 2021-08-05 19:12:30 UTC; 2s ago
Main PID: 30446 (code=exited, status=0/SUCCESS); : 15993 (ruby)
CGroup: /system.slice/zammad-scheduler.service
└─15993 script/scheduler.rb start

Aug 05 19:12:30 zmd4.voipe.cc systemd[1]: zammad-scheduler.service holdoff time over, scheduling restart.
Aug 05 19:12:30 zmd4.voipe.cc systemd[1]: Stopped Zammad scheduler.
Aug 05 19:12:30 zmd4.voipe.cc systemd[1]: Starting Zammad scheduler…

[root@zmd4 zammad]# journalctl -xe
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in register' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in require_with_bootsnap_lfi’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in require' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in block in require’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:257:in load_dependency' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in require’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/railties-5.2.4.6/lib/rails/all.rb:3:in <main>' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in require’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in block in require_with_bootsnap_lfi' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in register’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in require_with_bootsnap_lfi' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in require’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in block in require' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:257:in load_dependency’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in require' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /opt/zammad/config/application.rb:5:in <top (required)>’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /opt/zammad/config/environment.rb:4:in require_relative' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: /opt/zammad/config/environment.rb:4:in <top (required)>’
Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: script/websocket-server.rb:15:in require' Aug 05 19:13:03 zmd4.voipe.cc bash[19598]: script/websocket-server.rb:15:in <top (required)>’
Aug 05 19:13:03 zmd4.voipe.cc systemd[1]: zammad-websocket.service failed.
Aug 05 19:13:03 zmd4.voipe.cc systemd[1]: zammad-rails.service failed.
Aug 05 19:13:03 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:04 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:04 zmd4.voipe.cc systemd[1]: Failed to start Zammad scheduler.
– Subject: Unit zammad-scheduler.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit zammad-scheduler.service has failed.

– The result is failed.
Aug 05 19:13:04 zmd4.voipe.cc systemd[1]: zammad-scheduler.service failed.
Aug 05 19:13:04 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:04 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:05 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:05 zmd4.voipe.cc systemd[1]: start request repeated too quickly for zammad-websocket-1.service
Aug 05 19:13:05 zmd4.voipe.cc systemd[1]: Failed to start zammad-websocket-1.service.
– Subject: Unit zammad-websocket-1.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit zammad-websocket-1.service has failed.

– The result is failed.
Aug 05 19:13:05 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: bundler: failed to load command: script/rails (script/rails)
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: Errno::EACCES: Permission denied - bs_fetch:atomic_write_cache_file:open
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/compile_cache/iseq.rb:37:in fetch' Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/compile_cache/iseq.rb:37:in load_iseq’
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in require' Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in block in require_with_bootsnap_lfi’
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in register' Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in require_with_bootsnap_lfi’
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in require' Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in block in require’
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:257:in load_dependency' Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: /usr/local/rvm/gems/ruby-2.6.6/gems/activesupport-5.2.4.6/lib/active_support/dependencies.rb:291:in require’
Aug 05 19:13:06 zmd4.voipe.cc bash[20023]: script/rails:8:in `<top (required)>’
Aug 05 19:13:06 zmd4.voipe.cc systemd[1]: zammad-rails.service failed.
Aug 05 19:13:07 zmd4.voipe.cc systemd[1]: zammad-websocket.service failed.
Aug 05 19:13:07 zmd4.voipe.cc systemd[1]: start request repeated too quickly for zammad-websocket-1.service
Aug 05 19:13:07 zmd4.voipe.cc systemd[1]: Failed to start zammad-websocket-1.service.
– Subject: Unit zammad-websocket-1.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit zammad-websocket-1.service has failed.

– The result is failed.
Aug 05 19:13:07 zmd4.voipe.cc systemd[1]: zammad-websocket-1.service failed.

I am not sure what happened.
Please kindly teach me.

Thanks in advance,
Maksym

HTTP/502 and Scheduler issues do not belong together.
Please update your first post so that log lines are living in code tags.

Other wise others are having a bad time reading the console outputs.
I’ve given up trying.

While you’re at it, kindly also provide at least used installation type and Zammad version as this is crucial information.

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