Zammad docker Failed to run CacheClearJob.perfom_now

MaikLehr · July 12, 2022, 9:54am

Used Zammad version: Docker 5.1.1-11
Used Zammad installation type: docker-compose
Operating system: Ubuntu 18.04.6 LTS | 14 cores, 100GB Ram (Many other Docker Container running on this system)
Browser + version: Firefox 102.0.1 / Google Chrome 103.0.5060.114 (Official Build)

Actual behavior:

The Monitoring says to use:
Failed to run scheduled job ‘Clean up cache.’. Cause: Failed to run CacheClearJob.perform_now after 10 tries #<NameError: uninitialized constant #Class:0x0000560103459ef8::CacheClearJob>
In the Logs from the container Sheduler it write the following:

I, [2022-07-12T09:43:47.627491 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 1)...
E, [2022-07-12T09:43:47.643399 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 1) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.066857077 seconds.
I, [2022-07-12T09:43:49.668255 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 2)...
E, [2022-07-12T09:43:49.683582 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 2) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.016552358 seconds.
I, [2022-07-12T09:43:52.701301 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 3)...
E, [2022-07-12T09:43:52.716556 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 3) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.011673752 seconds.
I, [2022-07-12T09:43:56.729790 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 4)...
E, [2022-07-12T09:43:56.743746 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 4) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.008917397 seconds.
I, [2022-07-12T09:44:01.798476 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 5)...
E, [2022-07-12T09:44:01.805766 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 5) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.050428881 seconds.
I, [2022-07-12T09:44:07.815446 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 6)...
E, [2022-07-12T09:44:07.826676 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 6) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.005772065 seconds.
I, [2022-07-12T09:44:14.849399 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 7)...
E, [2022-07-12T09:44:14.863973 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 7) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.016297272 seconds.
I, [2022-07-12T09:44:22.875217 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 8)...
E, [2022-07-12T09:44:22.885259 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 8) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.006677431 seconds.
I, [2022-07-12T09:44:31.904093 #1-887380]  INFO -- : execute CacheClearJob.perform_now (try_count 9)...
E, [2022-07-12T09:44:31.917414 #1-887380] ERROR -- : execute CacheClearJob.perform_now (try_count 9) exited with error #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob> in: 0.009965568 seconds.
E, [2022-07-12T09:44:31.922103 #1-887380] ERROR -- : Failed to run CacheClearJob.perform_now after 10 tries #<NameError: uninitialized constant #<Class:0x0000558f1ad9b760>::CacheClearJob>

The puma and railserver have a high cpu usage. I tried with the perfomance Tuning guide on the official wiki to perform our system. We use the Zammad with 13 Agents Online and about 1.000 customer. In the following my .env and my docker-compose file:

IMAGE_REPO=zammad/zammad-docker-compose
MEMCACHE_SERVERS=zammad-memcached:11211
POSTGRES_PASS=zammad
POSTGRES_USER=zammad
REDIS_URL=redis://zammad-redis:6379
RESTART=always
RAILS_ENV=production
VERSION=-5.1.1-11
ZAMMAD_SESSION_JOBS_CONCURRENT=12
ZAMMAD_PROCESS_DELAYED_JOBS_WORKERS=2
ZAMMAD_PROCCESS_SCHEDULED_JOBS_WORKERS=2
WEB_CONCURRENCY=5
ELASTICSEARCH_REINDEX=true

version: '3'

networks:
  default:
    driver: bridge
    ipam:
      config:
        - subnet: 1.1.92.0/24
  proxy:
    external: true

services:
  zammad-elasticsearch:
    environment:
      - discovery.type=single-node
      - "ES_JAVA_OPTS=-Xms10240m -Xmx10240m"
    image: ${IMAGE_REPO}:zammad-elasticsearch${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_elasticsearch-data:/usr/share/elasticsearch/data

  zammad-init:
    command: ["zammad-init"]
    depends_on:
      - zammad-postgresql
    environment:
      - MEMCACHE_SERVERS=${MEMCACHE_SERVERS}
      - POSTGRESQL_USER=${POSTGRES_USER}
      - POSTGRESQL_PASS=${POSTGRES_PASS}
      - REDIS_URL=${REDIS_URL}
    image: ${IMAGE_REPO}:zammad${VERSION}
    restart: on-failure
    volumes:
      - cortana_zammad-data:/opt/zammad

  zammad-memcached:
    command: memcached -m 256M
    image: memcached:1.6.10-alpine
    restart: ${RESTART}

  zammad-nginx:
    command: ["zammad-nginx"]
    container_name: cortana_nginx
    depends_on:
      - zammad-railsserver
    image: ${IMAGE_REPO}:zammad${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_zammad-data:/opt/zammad
      - ./nginx-default:/etc/nginx/sites-enabled/default:ro
      - ./docker-entrypoint.sh:/docker-entrypoint.sh
      - ./zelos:/zelos
    ports:
      - 8080:8080
    networks:
      - proxy
      - default

  zammad-php:
    image: nimmis/apache-php5
    volumes:
      - ./html:/var/www/html:cached

  zammad-postgresql:
    environment:
      - POSTGRES_USER=${POSTGRES_USER}
      - POSTGRES_PASSWORD=${POSTGRES_PASS}
    image: ${IMAGE_REPO}:zammad-postgresql${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_postgresql-data:/var/lib/postgresql/data
      - cortana_zammad-data:/opt/zammad
      - ./sql:/sql

  zammad-railsserver:
    command: ["zammad-railsserver"]
    depends_on:
      - zammad-memcached
      - zammad-postgresql
      - zammad-redis
    environment:
      - MEMCACHE_SERVERS=${MEMCACHE_SERVERS}
      - REDIS_URL=${REDIS_URL}
    image: ${IMAGE_REPO}:zammad${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_zammad-data:/opt/zammad

  zammad-redis:
    image: redis:6.2.5-alpine
    restart: ${RESTART}

  zammad-scheduler:
    command: ["zammad-scheduler"]
    depends_on:
      - zammad-memcached
      - zammad-railsserver
      - zammad-redis
    environment:
      - MEMCACHE_SERVERS=${MEMCACHE_SERVERS}
      - REDIS_URL=${REDIS_URL}
    image: ${IMAGE_REPO}:zammad${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_zammad-data:/opt/zammad

  zammad-websocket:
    command: ["zammad-websocket"]
    depends_on:
      - zammad-memcached
      - zammad-railsserver
      - zammad-redis
    environment:
      - MEMCACHE_SERVERS=${MEMCACHE_SERVERS}
      - REDIS_URL=${REDIS_URL}
    image: ${IMAGE_REPO}:zammad${VERSION}
    restart: ${RESTART}
    volumes:
      - cortana_zammad-data:/opt/zammad

volumes:
  cortana_elasticsearch-data:
    driver: local
  cortana_postgresql-data:
    driver: local
  cortana_zammad-data:
    driver: local

Steps to reproduce the behavior:

Every time when i restart the completed stack or click manually in zammad on “Restart failed jobs”

MaikLehr · July 13, 2022, 8:36pm

i found the problem. It was a failed update to 5.2.
After a completed Update it has no failures.

system · November 10, 2022, 8:37pm

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