Infos:
- Used Zammad version: 5.0.0-7 to 6.0.0-131
- Used Zammad installation type: docker-compose
- Operating system: Ubuntu 24.04
- Browser + version: Chrome N/A
I’m updating from 5.0.0-7 to 6.0.0-131 using the latest docker-compose version with an external Postgres 7.4
My zammand-init container is running fine but exits silently after the log below.
All the other containers are stuck with waiting for init container to finish install or update...
zammad-init-1 | Dropping indexes... done.
zammad-init-1 | Deleting pipeline... done.
zammad-init-1 | Creating indexes... done.
zammad-init-1 | Creating pipeline... I, [2025-05-07T03:01:54.376524#31-6180] INFO -- : Setting.set('es_pipeline', "zammadade3e156-42db-4660-be2d-3711b22fa2a7")
zammad-init-1 | done.
zammad-init-1 | Reloading data...
zammad-init-1 | - Chat::Session...
done in 0 seconds.
zammad-init-1 | - Cti::Log...
done in 0 seconds.
zammad-init-1 | - Group...
done in 0 seconds.
zammad-init-1 | - KnowledgeBase::Answer::Translation...
done in 0 seconds.
zammad-init-1 | - KnowledgeBase::Category::Translation...
done in 0 seconds.
zammad-init-1 | - KnowledgeBase::Translation...
done in 0 seconds.
zammad-init-1 | - Organization...
done in 0 seconds.
zammad-init-1 | - StatsStore...
done in 1 seconds.
zammad-init-1 | - Ticket::Priority...
done in 0 seconds.
zammad-init-1 | - Ticket::State...
done in 0 seconds.
zammad-init-1 | - Ticket...
done in 2699 seconds.
zammad-init-1 | - User...
done in 148 seconds.
Here it jus stops. The behavior repeats when restarting zammand-init
Seems like it’s creating data for Elastic Search? When Elastic Search is disabled I get the following log before zammand-init stops.
Complete Log (else it’s before the above log as well):
zammad-init-1 | initialising / updating database...
zammad-init-1 | I, [2025-05-07T16:59:25.282427 #15] INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
zammad-init-1 | I, [2025-05-07T16:59:25.327037#15-5380] INFO -- : Using memcached as Rails cache store.
zammad-init-1 | I, [2025-05-07T16:59:25.327246#15-5380] INFO -- : Using the Redis back end for Zammad's web socket session store.
zammad-init-1 | I, [2025-05-07T16:59:26.257434#15-5380] INFO -- : Setting.set('product_logo', "89657974c596d6862555924cd855a9eb.png")
zammad-init-1 | I, [2025-05-07T16:59:29.583899#15-5380] INFO -- : Setting.set('models_searchable', ["Chat::Session", "KnowledgeBase::Answer::Translation", "Organization", "Ticket", "User"])
zammad-init-1 | I, [2025-05-07T16:59:33.324928 #17] INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
zammad-init-1 | I, [2025-05-07T16:59:33.365994#17-6180] INFO -- : Using memcached as Rails cache store.
zammad-init-1 | I, [2025-05-07T16:59:33.366219#17-6180] INFO -- : Using the Redis back end for Zammad's web socket session store.
zammad-init-1 | I, [2025-05-07T16:59:34.315686#17-6180] INFO -- : Setting.set('product_logo', "89657974c596d6862555924cd855a9eb.png")
zammad-init-1 | I, [2025-05-07T16:59:37.304554#17-6180] INFO -- : Setting.set('models_searchable', ["Chat::Session", "KnowledgeBase::Answer::Translation", "Organization", "Ticket", "User"])
zammad-init-1 | changing settings...
zammad-init-1 | I, [2025-05-07T16:59:40.730967 #19] INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
zammad-init-1 | I, [2025-05-07T16:59:40.776981#19-5380] INFO -- : Using memcached as Rails cache store.
zammad-init-1 | I, [2025-05-07T16:59:40.777194#19-5380] INFO -- : Using the Redis back end for Zammad's web socket session store.
zammad-init-1 | I, [2025-05-07T16:59:41.618571#19-5380] INFO -- : Setting.set('product_logo', "89657974c596d6862555924cd855a9eb.png")
zammad-init-1 | I, [2025-05-07T16:59:44.665298#19-5380] INFO -- : Setting.set('models_searchable', ["Chat::Session", "KnowledgeBase::Answer::Translation", "Organization", "Ticket", "User"])
zammad-init-1 | I, [2025-05-07T16:59:45.772704#19-5380] INFO -- : Setting.set('es_url', "")
Any Idea to further debug the issue?