Cache_file_store_production inodes usage

  • Used Zammad version: 3.0
  • Installation method (source, package, …): package
  • Operating system: Linux
  • Database + version: Postgres 9.6

Expected behavior:

  • /opt/zammad/tmp/cache_file_store_production should cleaned up automaticly

Actual behavior:

  • inodes usage for path /opt/zammad/tmp/cache_file_store_production is growing

Steps to reproduce the behavior:

root@witte-zammad:/# for i in /opt/zammad/tmp/*; do echo $i; find $i | wc -l | sort ; done

/opt/zammad/tmp/cache 1
/opt/zammad/tmp/cache_file_store_production 77617
/opt/zammad/tmp/heroku-buildpack-release-step.yml 1
/opt/zammad/tmp/pids 3
/opt/zammad/tmp/sessions 1
/opt/zammad/tmp/sockets 1
/opt/zammad/tmp/websocket_production 31

U see there are 77617 and is growing and growing.

Did someone have a idea?

Thx

I was about to say that Rails would probably automatically take care of cleaning this up, but the documentation actually says:

https://guides.rubyonrails.org/caching_with_rails.html#activesupport-cache-filestore

As the cache will grow until the disk is full, it is recommended to periodically clear out old entries.

So you might be on to something here. Someone from the Zammad team probably knows better than me if this should be a bug report on github.

zammad-docker-compose at least isn’t affected, because it uses memcached instead :slight_smile:

yes clear rails cache is helping:

root@zammad:~# zammad run rails c
Loading production environment (Rails 5.1.7)
irb(main):001:0> Rails.cache.clear

thx!

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