Upgrade docker from 6.1 to 6.3, nginx waiting for init container to finish

rodinux · March 26, 2025, 5:33pm

Infos:

Used Zammad version: 6.3.1-196
Used Zammad installation type: docker-compose
Operating system: vm Debian 12 - Portainer
Browser + version:

Expected behavior:

Upgrade from version 6.2.0-1 should run the zammad-nginx container when the zammad-init is finished

Actual behavior:

The containers are upgraded but the container zammad-niginx is waiting for init container to finish…

Steps to reproduce the behavior:

Fist I change the docker-compose.yml with this one

docker-compose.ym for 6.3.1-196

version: '3.8'

x-shared:
  zammad-service: &zammad-service
    environment: &zammad-environment
      MEMCACHE_SERVERS: ${MEMCACHE_SERVERS}
      POSTGRESQL_DB: ${POSTGRES_DB}
      POSTGRESQL_HOST: ${POSTGRES_HOST}
      POSTGRESQL_USER: ${POSTGRES_USER}
      POSTGRESQL_PASS: ${POSTGRES_PASS}
      POSTGRESQL_PORT: ${POSTGRES_PORT}
      POSTGRESQL_OPTIONS: ${POSTGRESQL_OPTIONS}
      POSTGRESQL_DB_CREATE:
      REDIS_URL: ${REDIS_URL}
      # Backup settings
      BACKUP_DIR: "${BACKUP_DIR}"
      BACKUP_TIME: "${BACKUP_TIME}"
      HOLD_DAYS: "${HOLD_DAYS}"
      TZ: "${TZ}"
    image: ${IMAGE_REPO}:${VERSION}
    restart: ${RESTART:-always}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-storage:/opt/zammad/storage
    depends_on:
      - zammad-memcached
      - zammad-postgresql
      - zammad-redis

services:

  zammad-backup:
    <<: *zammad-service
    command: ["zammad-backup"]
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-backup:/var/tmp/zammad
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-storage:/opt/zammad/storage:ro
    user: 0:0

  zammad-elasticsearch:
    image: bitnami/elasticsearch:${ELASTICSEARCH_VERSION}
    restart: ${RESTART:-always}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/elasticsearch-data:/bitnami/elasticsearch/data

  zammad-init:
    <<: *zammad-service
    command: ["zammad-init"]
    depends_on:
      - zammad-postgresql
    restart: on-failure
    user: 0:0

  zammad-memcached:
    command: memcached -m 256M
    image: memcached:${MEMCACHE_VERSION}
    restart: ${RESTART:-always}

  zammad-nginx:
    <<: *zammad-service
    command: ["zammad-nginx"][details="docker-compose.ym for 6.3.1-196"]
    expose:
      - "${NGINX_PORT}"
    ports:
      - "${NGINX_EXPOSE_PORT}:${NGINX_PORT}"
    environment:
      NGINX_PORT: ${NGINX_PORT}
      NGINX_SERVER_SCHEME: ${NGINX_SERVER_SCHEME}
      VIRTUAL_HOST: ${VIRTUAL_HOST}
      NGINX_SERVER_NAME: ${NGINX_SERVER_NAME}
      RAILS_TRUSTED_PROXIES: ${RAILS_TRUSTED_PROXIES}
    depends_on:
      - zammad-railsserver

  zammad-postgresql:
    environment:
      POSTGRES_DB: ${POSTGRES_DB}
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASS}
    image: postgres:${POSTGRES_VERSION}
    restart: ${RESTART:-always}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/postgresql-data:/var/lib/postgresql/data

  zammad-railsserver:
    <<: *zammad-service
    command: ["zammad-railsserver"]
    extra_hosts:
      - "git.numericoop.fr:10.10.10.20"

  zammad-redis:
    image: redis:${REDIS_VERSION}
    restart: ${RESTART:-always}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/redis-data:/data

  zammad-scheduler:
    <<: *zammad-service
    command: ["zammad-scheduler"]

  zammad-websocket:
    <<: *zammad-service
    command: ["zammad-websocket"

Before I was using this one

docker-compose.ym for 6.2.0-1

version: '3.8'

x-shared:
  zammad-service: &zammad-service
    environment: &zammad-environment
      MEMCACHE_SERVERS: ${MEMCACHE_SERVERS}
      POSTGRESQL_DB: ${POSTGRES_DB}
      POSTGRESQL_HOST: ${POSTGRES_HOST}
      POSTGRESQL_USER: ${POSTGRES_USER}
      POSTGRESQL_PASS: ${POSTGRES_PASS}
      POSTGRESQL_PORT: ${POSTGRES_PORT}
      REDIS_URL: ${REDIS_URL}
    image: ${IMAGE_REPO}:${VERSION}
    restart: ${RESTART}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-storage:/opt/zammad/storage
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-var:/opt/zammad/var
    depends_on:
      - zammad-memcached
      - zammad-postgresql
      - zammad-redis

services:

  zammad-backup:
    command: ["zammad-backup"]
    depends_on:
      - zammad-railsserver
      - zammad-postgresql
    entrypoint: /usr/local/bin/backup.sh
    environment:
      <<: *zammad-environment
      BACKUP_TIME: "23:00"
      HOLD_DAYS: "10"
      TZ: Europe/Paris
    image: postgres:${POSTGRES_VERSION}
    restart: ${RESTART}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-backup:/var/tmp/zammad
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-storage:/opt/zammad/storage:ro
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-var:/opt/zammad/var:ro
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/scripts/backup.sh:/usr/local/bin/backup.sh:ro

  zammad-elasticsearch:
    image: bitnami/elasticsearch:${ELASTICSEARCH_VERSION}
    restart: ${RESTART}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/elasticsearch-data:/bitnami/elasticsearch/data

  zammad-init:
    <<: *zammad-service
    command: ["zammad-init"]
    depends_on:
      - zammad-postgresql
    restart: on-failure
    user: 0:0
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-storage:/opt/zammad/storage
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-var:/opt/zammad/var

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

  zammad-nginx:
    <<: *zammad-service
    command: ["zammad-nginx"]
    expose:
      - "$NGINX_PORT"
    ports:
      - "${ENV_NGINX_PORT}:${NGINX_PORT}"
    environment:
      NGINX_PORT: ${NGINX_PORT}
      NGINX_SERVER_SCHEME: ${NGINX_SERVER_SCHEME}
      VIRTUAL_HOST: ${VIRTUAL_HOST}
      NGINX_SERVER_NAME: ${NGINX_SERVER_NAME}
      RAILS_TRUSTED_PROXIES: ${RAILS_TRUSTED_PROXIES}
    depends_on:
      - zammad-railsserver
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/zammad-var:/opt/zammad/var:ro # required for the zammad-ready check file

  zammad-postgresql:
    environment:
      POSTGRES_DB: ${POSTGRES_DB}
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASS}
    image: postgres:${POSTGRES_VERSION}
    restart: ${RESTART}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/postgresql-data:/var/lib/postgresql/data

  zammad-railsserver:
    <<: *zammad-service
    command: ["zammad-railsserver"]
    extra_hosts:
      - "git.numericoop.fr:10.10.10.20"

  zammad-redis:
    image: redis:${REDIS_VERSION}
    restart: ${RESTART}
    volumes:
      - /mnt/${NAME_ENV}/${NAME_CLIENT}/${NAME_APP}/redis-data:/data

  zammad-scheduler:
    <<: *zammad-service
    command: ["zammad-scheduler"]

  zammad-websocket:
    <<: *zammad-service
    command: ["zammad-websocket"]

I understand some mount points are no more used for now…

I have try also copy the zammad.conf from the container

docker cp -a stack-zammad-pp-zammad-nginx-1:opt/zammad/contrib/nginx/zammad.conf .

edit this one with correct values with a customize NGINX_PORT and NGINX_EXPOSE_PORT, then it is a reverse-proxy which do the job. I try first on preprod environment where ports are different from production environment…

I put the variables on a env in portainer, is it the problem ?

Then I have try copy the zammad.conf and also have the symbolic link for nginx

docker cp zammad.conf stack-zammad-pp-zammad-nginx-1:/etc/nginx/sites-available/
docker cp zammad.conf stack-zammad-pp-zammad-nginx-1:/etc/nginx/sites-available/
docker exec -it -u root stack-zammad-pp-zammad-nginx-1 chown 1000:1000 /etc/nginx/sites-available/zammad.conf
docker exec -it -u root stack-zammad-pp-zammad-nginx-1 ln -s /etc/nginx/sites-available/zammad.conf /etc/nginx/sites-enabled/zammad.conf

Then try upgrade from Portainer my code witg the variables edited on the portainer env

But anyway, the container is waiting zammad-init to finish, but the zammad-init have finish his job.

What’s wrong ?

Can I mount the folder /etc/nginx/ to edit the files if necessary ? Or is not recommanded ?

Perhaps it’s not possible do an upgarde from 6.2 to this last patch 6.3.1-196 ??

can someone help me ?

containers logs

docker logs stack-zammad-pp-zammad-nginx-1
waiting for init container to finish install or update...
waiting for init container to finish install or update...
waiting for init container to finish install or update...
waiting for init container to finish install or update...
waiting for init container to finish install or update...
waiting for init container to finish install or update...
waiting for init container to finish install or update...

docker logs stack-zammad-pp-zammad-init-1
initialising / updating database...
Clearing cache...
I, [2025-03-26T17:09:31.279201 #22]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:09:31.309736#22-6080]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:09:31.309962#22-6080]  INFO -- : Using the Redis back end for Zammad's web socket session store.
Executing migrations...
I, [2025-03-26T17:09:37.807686 #30]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:09:37.826856#30-6900]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:09:37.827154#30-6900]  INFO -- : Using the Redis back end for Zammad's web socket session store.
Synchronizing locales...
I, [2025-03-26T17:09:43.502733 #38]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:09:43.519072#38-6080]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:09:43.519302#38-6080]  INFO -- : Using the Redis back end for Zammad's web socket session store.
Synchronizing translations...
I, [2025-03-26T17:09:50.177328 #46]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:09:50.192973#46-6080]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:09:50.193181#46-6080]  INFO -- : Using the Redis back end for Zammad's web socket session store.
changing settings...
I, [2025-03-26T17:10:29.305911 #54]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:10:29.321248#54-6080]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:10:29.321472#54-6080]  INFO -- : Using the Redis back end for Zammad's web socket session store.
I, [2025-03-26T17:10:32.827876#54-6080]  INFO -- : Setting.set('es_url', "http://zammad-elasticsearch:9200")
I, [2025-03-26T17:10:36.034664 #62]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T17:10:36.049835#62-6080]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T17:10:36.050031#62-6080]  INFO -- : Using the Redis back end for Zammad's web socket session store.
I, [2025-03-26T17:10:39.956281#62-6080] nano zammad.conf

docker logs stack-zammad-pp-zammad-railsserver-1
starting railsserver... with WEB_CONCURRENCY=0
Puma starting in single mode...
* Puma version: 6.4.3 (ruby 3.2.4-p170) ("The Eagle of Durango")
*  Min threads: 5
*  Max threads: 30
*  Environment: production
*          PID: 1
I, [2025-03-26T16:35:27.862337 #1]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T16:35:27.885763#1-6900]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T16:35:27.886191#1-6900]  INFO -- : Using the Redis back end for Zammad's web socket session store.
* Listening on http://[::]:3000
Use Ctrl-C to stop

docker logs stack-zammad-pp-zammad-postgresql-1

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-03-26 15:34:48.709 UTC [1] LOG:  starting PostgreSQL 15.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, 64-bit
2025-03-26 15:34:48.710 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-03-26 15:34:48.710 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-03-26 15:34:48.776 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-26 15:34:48.918 UTC [30] LOG:  database system was shut down at 2025-03-26 15:34:23 UTC
2025-03-26 15:34:49.030 UTC [1] LOG:  database system is ready to accept connections
2025-03-26 15:34:49.763 UTC [34] LOG:  incomplete startup packet
2025-03-26 15:39:48.974 UTC [28] LOG:  checkpoint starting: time
2025-03-26 15:39:55.575 UTC [28] LOG:  checkpoint complete: wrote 62 buffers (0.4%); 0 WAL file(s) added, 0 removed, 0 recycled; write=6.142 s, sync=0.222 s, total=6.602 sB
2025-03-26 15:44:48.676 UTC [28] LOG:  checkpoint starting: time
2025-03-26 15:44:49.134 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.224 s, sync=0.071 s, total=0.459 s;B
2025-03-26 15:49:48.195 UTC [28] LOG:  checkpoint starting: time
2025-03-26 15:49:48.625 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.221 s, sync=0.044 s, total=0.431 s;B
2025-03-26 15:54:48.721 UTC [28] LOG:  checkpoint starting: time
2025-03-26 15:54:49.370 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.521 s, sync=0.022 s, total=0.650 s;B
2025-03-26 15:59:48.433 UTC [28] LOG:  checkpoint starting: time
2025-03-26 15:59:49.416 UTC [28] LOG:  checkpoint complete: wrote 8 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.716 s, sync=0.100 s, total=0.983 s;B
2025-03-26 16:04:48.510 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:04:48.952 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.227 s, sync=0.065 s, total=0.443 s;B
2025-03-26 16:09:21.096 UTC [118] LOG:  incomplete startup packet
2025-03-26 16:09:49.045 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:09:49.525 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.229 s, sync=0.047 s, total=0.480 s;B
2025-03-26 16:14:49.622 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:14:50.340 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.526 s, sync=0.053 s, total=0.719 s;B
2025-03-26 16:19:49.403 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:19:49.834 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.218 s, sync=0.074 s, total=0.432 s;B
2025-03-26 16:24:49.898 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:24:50.731 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.524 s, sync=0.116 s, total=0.833 s;B
2025-03-26 16:29:49.831 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:29:50.589 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.535 s, sync=0.059 s, total=0.759 s;B
2025-03-26 16:34:49.688 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:34:50.078 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.224 s, sync=0.034 s, total=0.390 s;B
2025-03-26 16:39:49.177 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:39:49.637 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.220 s, sync=0.038 s, total=0.460 s;B
2025-03-26 16:44:49.697 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:44:50.463 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.523 s, sync=0.072 s, total=0.767 s;B
2025-03-26 16:49:49.561 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:49:50.124 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.226 s, sync=0.134 s, total=0.563 s;B
2025-03-26 16:54:49.222 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:54:49.977 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.521 s, sync=0.069 s, total=0.755 s;B
2025-03-26 16:59:50.067 UTC [28] LOG:  checkpoint starting: time
2025-03-26 16:59:50.973 UTC [28] LOG:  checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.531 s, sync=0.132 s, total=0.906 s;B
2025-03-26 17:04:51.062 UTC [28] LOG:  checkpoint starting: time
2025-03-26 17:04:51.500 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.227 s, sync=0.045 s, total=0.439 s;B
2025-03-26 17:09:51.579 UTC [28] LOG:  checkpoint starting: time
2025-03-26 17:09:52.082 UTC [28] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.226 s, sync=0.053 s, total=0.503 s;B

docker logs stack-zammad-pp-zammad-websocket-1
starting websocket server...
I, [2025-03-26T16:35:28.802153 #1]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T16:35:28.828034#1-6160]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T16:35:28.828386#1-6160]  INFO -- : Using the Redis back end for Zammad's web socket session store.

 docker logs stack-zammad-pp-zammad-websocket-1
starting websocket server...
I, [2025-03-26T16:35:28.802153 #1]  INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2025-03-26T16:35:28.828034#1-6160]  INFO -- : Using memcached as Rails cache store.
I, [2025-03-26T16:35:28.828386#1-6160]  INFO -- : Using the Redis back end for Zammad's web socket session store.

docker logs stack-zammad-pp-zammad-redis-1
1:C 26 Mar 2025 15:34:48.222 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failur.
1:C 26 Mar 2025 15:34:48.222 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 26 Mar 2025 15:34:48.222 * Redis version=7.4.1, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 26 Mar 2025 15:34:48.222 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 26 Mar 2025 15:34:48.224 * monotonic clock: POSIX clock_gettime
1:M 26 Mar 2025 15:34:48.227 * Running mode=standalone, port=6379.
1:M 26 Mar 2025 15:34:48.229 * Server initialized
1:M 26 Mar 2025 15:34:48.229 * Loading RDB produced by version 7.4.1
1:M 26 Mar 2025 15:34:48.229 * RDB age 26 seconds
1:M 26 Mar 2025 15:34:48.229 * RDB memory usage when created 1.02 Mb
1:M 26 Mar 2025 15:34:48.229 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 26 Mar 2025 15:34:48.229 * DB loaded from disk: 0.001 seconds
1:M 26 Mar 2025 15:34:48.229 * Ready to accept connections tcp

docker logs stack-zammad-pp-zammad-scheduler-1

I, [2025-03-26T18:19:32.007275#1-149120]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2025-03-26T18:19:32.007338#1-149120]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2025-03-26T18:19:42.009283#1-149120]  INFO -- : ProcessScheduledJobs running...
I, [2025-03-26T18:19:42.011976#1-149120]  INFO -- : Running job thread for 'Check 'Channel' streams.' (Channel.stream) status is: sleep
I, [2025-03-26T18:19:42.012103#1-149120]  INFO -- : Running job thread for 'Generate 'Session' data.' (Sessions.jobs) status is: sleep
I, [2025-03-26T18:19:42.012347#1-149120]  INFO -- : Running job thread for 'Check channels.' (Channel.fetch) status is: sleep
I, [2025-03-26T18:19:42.012453#1-149120]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2025-03-26T18:19:42.012585#1-149120]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2025-03-26T18:19:47.602461#1-149180]  INFO -- : execute Channel.fetch (try_count 0)...
I, [2025-03-26T18:19:47.604319#1-149180]  INFO -- : fetching imap (yuno.numericoop.fr/zammadpreprod port=993,ssl=true,starttls=false,folder=INBOX,keep_on_server=false,auth_type=LOGIN)
I, [2025-03-26T18:19:48.008430#1-149180]  INFO -- :  - no message
I, [2025-03-26T18:19:48.027945#1-149180]  INFO -- : ended Channel.fetch took: 0.468875178 seconds.
I, [2025-03-26T18:19:52.014499#1-149120]  INFO -- : ProcessScheduledJobs running...
I, [2025-03-26T18:19:52.016640#1-149120]  INFO -- : Running job thread for 'Check 'Channel' streams.' (Channel.stream) status is: sleep
I, [2025-03-26T18:19:52.016787#1-149120]  INFO -- : Running job thread for 'Generate 'Session' data.' (Sessions.jobs) status is: sleep
I, [2025-03-26T18:19:52.017063#1-149120]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2025-03-26T18:19:52.017163#1-149120]  INFO -- : Running job thread for 'Check channels.' (Channel.fetch) status is: sleep
I, [2025-03-26T18:19:52.017259#1-149120]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2025-03-26T18:20:02.019734#1-149120]  INFO -- : ProcessScheduledJobs running...
I, [2025-03-26T18:20:02.022552#1-149120]  INFO -- : Running job thread for 'Check 'Channel' streams.' (Channel.stream) status is: sleep
I, [2025-03-26T18:20:02.022689#1This text will be hidden-149120]  INFO -- : Running job thread for 'Generate 'Session' data.' (Sessions.jobs) status is: sleep
I, [2025-03-26T18:20:02.022972#1-149120]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2025-03-26T18:20:02.023055#1-149120]  INFO -- : Running job thread for 'Check channels.' (Channel.fetch) status is: sleep
I, [2025-03-26T18:20:02.023133#1-149120]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2025-03-26T18:20:12.025505#1-149120]  INFO -- : ProcessScheduledJobs running...
I, [2025-03-26T18:20:12.027854#1-149120]  INFO -- : Running job thread for 'Check 'Channel' streams.' (Channel.stream) status is: sleep
I, [2025-03-26T18:20:12.027972#1-149120]  INFO -- : Running job thread for 'Generate 'Session' data.' (Sessions.jobs) status is: sleep
I, [2025-03-26T18:20:12.028249#1-149120]  INFO -- : Running job thread for 'Process ticket escalations.' (Ticket.process_escalation) status is: sleep
I, [2025-03-26T18:20:12.028349#1-149120]  INFO -- : Running job thread for 'Check channels.' (Channel.fetch) status is: sleep
I, [2025-03-26T18:20:12.028418#1-149120]  INFO -- : Running job thread for 'Execute planned jobs.' (Job.run) status is: sleep
I, [2025-03-26T18:20:18.113473#1-149180]  INFO -- : execute Channel.fetch (try_count 0)...
I, [2025-03-26T18:20:18.115982#1-149180]  INFO -- : fetching imap (yuno.numericoop.fr/zammadpreprod port=993,ssl=true,starttls=false,folder=INBOX,keep_on_server=false,auth_type=LOGIN)
I, [2025-03-26T18:20:18.382730#1-149180]  INFO -- :  - no message
I, [2025-03-26T18:20:18.404568#1-149180]  INFO -- : ended Channel.fetch took: 0.375431213 seconds.

docker logs stack-zammad-pp-zammad-elasticsearch-1
[2025-03-26T15:35:42,419][INFO ][o.e.x.s.c.f.PersistentCache] [da278cc0f8d6] persistent cache index loaded
[2025-03-26T15:35:42,420][INFO ][o.e.x.d.l.DeprecationIndexingComponent] [da278cc0f8d6] deprecation component started
[2025-03-26T15:35:42,573][INFO ][o.e.t.TransportService   ] [da278cc0f8d6] publish_address {172.30.0.4:9300}, bound_addresses {0.0.0.0:9300}
[2025-03-26T15:35:43,870][INFO ][o.e.c.c.ClusterBootstrapService] [da278cc0f8d6] this node is locked into cluster UUID [Rmtqd8maS-up-DHpscMduA] and will not attempt further cluster bootstrapping
[2025-03-26T15:35:44,182][INFO ][o.e.c.s.MasterService    ] [da278cc0f8d6] elected-as-master ([1] nodes joined in term 36)[_FINISH_ELECTION_, {da278cc0f8d6}{fz4O13OxSn2w7IC0trNG0Q}{Nco0IsA4RpGrs3U}
[2025-03-26T15:35:44,628][INFO ][o.e.c.s.ClusterApplierService] [da278cc0f8d6] master node changed {previous [], current [{da278cc0f8d6}{fz4O13OxSn2w7IC0trNG0Q}{Nco0IsA4RpGrs3Unt00ejw}{da278cc0f8d}
[2025-03-26T15:35:44,701][INFO ][o.e.c.c.NodeJoinExecutor ] [da278cc0f8d6] node-join: [{da278cc0f8d6}{fz4O13OxSn2w7IC0trNG0Q}{Nco0IsA4RpGrs3Unt00ejw}{da278cc0f8d6}{172.30.0.4}{172.30.0.4:9300}{cdf]
[2025-03-26T15:35:44,712][INFO ][o.e.h.AbstractHttpServerTransport] [da278cc0f8d6] publish_address {172.30.0.4:9200}, bound_addresses {0.0.0.0:9200}
[2025-03-26T15:35:44,742][INFO ][o.e.n.Node               ] [da278cc0f8d6] started {da278cc0f8d6}{fz4O13OxSn2w7IC0trNG0Q}{Nco0IsA4RpGrs3Unt00ejw}{da278cc0f8d6}{172.30.0.4}{172.30.0.4:9300}{cdfhilm}
{"@timestamp":"2025-03-26T15:35:45.726Z", "log.level": "WARN",  "data_stream.dataset":"deprecation.elasticsearch","data_stream.namespace":"default","data_stream.type":"logs","elasticsearch.event.c}
[2025-03-26T15:35:46,113][INFO ][o.e.l.ClusterStateLicenseService] [da278cc0f8d6] license [139c9a25-1309-49e6-b0a1-60caf4cc104f] mode [basic] - valid
[2025-03-26T15:35:46,120][INFO ][o.e.c.f.AbstractFileWatchingService] [da278cc0f8d6] starting file watcher ...
[2025-03-26T15:35:46,130][INFO ][o.e.g.GatewayService     ] [da278cc0f8d6] recovered [15] indices into cluster_state
[2025-03-26T15:35:46,131][INFO ][o.e.c.f.AbstractFileWatchingService] [da278cc0f8d6] file settings service up and running [tid=44]
[2025-03-26T15:35:46,138][INFO ][o.e.r.s.FileSettingsService] [da278cc0f8d6] setting file [/opt/bitnami/elasticsearch/config/operator/settings.json] not found, initializing [file_settings] as empty
[2025-03-26T15:35:49,015][INFO ][o.e.h.n.s.HealthNodeTaskExecutor] [da278cc0f8d6] Node [{da278cc0f8d6}{fz4O13OxSn2w7IC0trNG0Q}] is selected as the current health node.
[2025-03-26T15:35:49,018][ERROR][o.e.i.g.GeoIpDownloader  ] [da278cc0f8d6] exception during geoip databases update org.elasticsearch.ElasticsearchException: not all primary shards of [.geoip_databe
        at org.elasticsearch.ingest.geoip@8.15.2/org.elasticsearch.ingest.geoip.GeoIpDownloader.updateDatabases(GeoIpDownloader.java:141)
        at org.elasticsearch.ingest.geoip@8.15.2/org.elasticsearch.ingest.geoip.GeoIpDownloader.runDownloader(GeoIpDownloader.java:293)
        at org.elasticsearch.ingest.geoip@8.15.2/org.elasticsearch.ingest.geoip.GeoIpDownloaderTaskExecutor.nodeOperation(GeoIpDownloaderTaskExecutor.java:162)
        at org.elasticsearch.ingest.geoip@8.15.2/org.elasticsearch.ingest.geoip.GeoIpDownloaderTaskExecutor.nodeOperation(GeoIpDownloaderTaskExecutor.java:61)
        at org.elasticsearch.server@8.15.2/org.elasticsearch.persistent.NodePersistentTasksExecutor$1.doRun(NodePersistentTasksExecutor.java:34)
        at org.elasticsearch.server@8.15.2/org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:984)
        at org.elasticsearch.server@8.15.2/org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)

[2025-03-26T15:35:49,774][INFO ][o.e.i.g.DatabaseNodeService] [da278cc0f8d6] successfully loaded geoip database file [GeoLite2-Country.mmdb]
[2025-03-26T15:35:49,850][INFO ][o.e.i.g.DatabaseNodeService] [da278cc0f8d6] successfully loaded geoip database file [GeoLite2-ASN.mmdb]
[2025-03-26T15:35:50,829][INFO ][o.e.i.g.DatabaseNodeService] [da278cc0f8d6] successfully loaded geoip database file [GeoLite2-City.mmdb]
[2025-03-26T15:35:57,787][INFO ][o.e.c.r.a.AllocationService] [da278cc0f8d6] current.health="YELLOW" message="Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[zammad"

phoenix · April 7, 2025, 6:04am

mark , i also want to know how to backup or restore after update the zammad (docker-compose)