Infos:
Used Zammad version: 3.1
Used Zammad installation source: package
Operating system: Ubuntu 18.04.2
Browser + version: Chrome + Firefox
Expected behavior:
Quick response to customer name query when starting a ticket.
Actual behavior:
Very slow response ~10-15 seconds before it finishes searching, or trying to search for a customer.
Steps to reproduce the behavior:
New ticket. Start to type customer name in the customer name field.
Additional information:
Is there anything I can do to improve these speeds?
We don’t have thousands of customers either. I’m admittedly not sure how to count them all, but I would be surprised if we had more than 600 total.
Any advice would be appreciated, thank you.
What’s your host storage based on? Slower hdd or rather ssd?
Maybe have a friendly grep within your logfile with the following keywords:
- ERROR
- WARN
- DeadLock
Warnings normally can be ignored, however, Errors and Deadlocks can’t.
Currently I expect your system to run with a postgresql server, so you might want to ensure you have set max_connections to at least 200.
Thanks for Replying MrGeneration.
We are running on a slower platter drive.
Increased the connections to 200, also allocated more ram to the shared buffer for postgresql.conf
I am getting an error https://geo.zammad.com/lookup?ip=xxxxxxxxxx: #<RuntimeError: ERROR: 0/>
Only one other error shows up a single time, and I can see that it’s missing a file…
E, [2020-02-24T16:55:12.848548 #837-69966586167500 ] ERROR – : No such file or directory @ rb_file_s_rename - (/opt/zammad/tmp/cache_file_store_production/.User%3A%3Aauthorizations%3A%3A5920200224-837-1y1jmwz, /opt/zammad/tmp/cache_file_store_production/A76/B50/User%3A%3Aauthorizations%3A%3A59) (Errno::ENOENT)rename' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/core_ext/file/atomic.rb:50:in block in atomic_write’open' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/core_ext/file/atomic.rb:24:in atomic_write’write_entry' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/cache/strategy/local_cache.rb:150:in write_entry’block in write' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/cache.rb:663:in block in instrument’instrument' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/cache.rb:663:in instrument’write' /opt/zammad/lib/cache.rb:32:in write’assets' /opt/zammad/app/controllers/search_controller.rb:77:in block in search_generic’each' /opt/zammad/app/controllers/search_controller.rb:71:in search_generic’send_action' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/abstract_controller/base.rb:194:in process_action’process_action' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/abstract_controller/callbacks.rb:42:in block in process_action’run_callbacks' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/abstract_controller/callbacks.rb:41:in process_action’process_action' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_controller/metal/instrumentation.rb:34:in block in process_action’block in instrument' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/notifications/instrumenter.rb:23:in instrument’instrument' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_controller/metal/instrumentation.rb:32:in process_action’process_action' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activerecord-5.2.3/lib/active_record/railties/controller_runtime.rb:24:in process_action’process' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionview-5.2.3/lib/action_view/rendering.rb:32:in process’dispatch' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_controller/metal.rb:252:in dispatch’dispatch' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/routing/route_set.rb:34:in serve’block in serve' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/journey/router.rb:35:in each’serve' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/routing/route_set.rb:840:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call!' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/omniauth-1.9.0/lib/omniauth/strategy.rb:169:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/rack-2.0.7/lib/rack/tempfile_reaper.rb:15:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/rack-2.0.7/lib/rack/conditional_get.rb:25:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/http/content_security_policy.rb:18:in call’context' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/rack-2.0.7/lib/rack/session/abstract/id.rb:226:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/callbacks.rb:28:in block in call’run_callbacks' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/callbacks.rb:26:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/show_exceptions.rb:33:in call’call_app' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/rack/logger.rb:26:in block in call’block in tagged' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/activesupport-5.2.3/lib/active_support/tagged_logging.rb:28:in tagged’tagged' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/railties-5.2.3/lib/rails/rack/logger.rb:26:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/request_id.rb:27:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/rack-2.0.7/lib/rack/runtime.rb:22:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/actionpack-5.2.3/lib/action_dispatch/middleware/executor.rb:14:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/rack-2.0.7/lib/rack/sendfile.rb:111:in call’call' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/puma-3.12.1/lib/puma/configuration.rb:227:in call’handle_request' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/puma-3.12.1/lib/puma/server.rb:474:in process_client’block in run' /opt/zammad/vendor/bundle/ruby/2.5.0/gems/puma-3.12.1/lib/puma/thread_pool.rb:135:in block in spawn_thread’
Ensure your host can reach and resolve geo.zammad.com (or just deactivate geo-ip services within System => Services-Tab.
Errors about missing files within temporary directories is technically an error, but not a huge issue. You can safely ignore it.zammad run rails r 'Cache.clear' and see if the issue keeps persisting or if it gets better.
Normally it’s not a regular visitor in your logfile (so not every minute or so)
system
June 25, 2020, 7:25pm
5
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.