Closed ggruening closed 1 year ago
I can confirm this is the case on Ubuntu 22.04/Docker version 24.0.2, build cb74dfc/Docker Compose version v2.18.
However, I notice that accessing the rails console doesn't seem to access the production database:
$ docker compose exec zammad-railsserver rails r "p Ticket.count"
I, [2023-06-28T23:39:27.950173 #2514] INFO -- : ActionCable is using the redis instance at redis://zammad-redis:6379.
I, [2023-06-28T23:39:27.971176#2514-5380] INFO -- : Using memcached as Rails cache store.
I, [2023-06-28T23:39:27.971698#2514-5380] INFO -- : Using the Redis back end for Zammad's web socket session store.
0
I believe this is because the entrypoint doesn't initialize the appropriate environment variables:
$ docker compose exec zammad-railsserver bash -c "echo \$ELASTICSEARCH_HOST"
$
It could be a case of adding an exec "$@"
line to the end of docker-entrypoint.sh
?
I could be wrong, of course :smile:
The following seems to work:
docker compose exec zammad-scheduler bash -c "source /docker-entrypoint.sh && rake zammad:searchindex:rebuild
"
So this confirms the console environment doesn't have the required environment variables runs when you add the entrypoint variables manually . I'm not sure if this is the case for previous versions, but I'm certain the following command used to work but now doesn't:
docker compose exec zammad-scheduler rake zammad:searchindex:rebuild
Hi there! Recently, there was a small change that could solve the reported behavior here: https://github.com/zammad/zammad/commit/6dc6b0fae5089a7a81b1a5f107f972b9ca279247
Should be fixed by #366
Infos
Expected behavior
Actual behavior
elasticsearch
seems to be gone afterzammad-init
is finished.zammad-init
does sucessfully rebuilding searchindexes,...zammad-elasticsearch
is still up and running without errors, but it seems, thatelasticsearch
is gone somehow:Steps to reproduce the behavior
Thanks in advance: for any hint and your fantastic work!
Gregor