V6.0.0 Zammad-rails return empty values

[pabloR_77]

• Used Zammad version: 6.0.0
• Used Zammad installation type: docker-compose
• Operating system: Ubuntu 22.04.2 LTS
• Browser + version: N/A

Expected behavior:

docker exec -it zammad-docker-compose-zammad-railsserver-1 sh
$ rails c
I, [2023-07-07T16:15:16.080217#91-5400] INFO – : Using the Redis back end for Zammad’s web socket session store.
Loading production environment (Rails 6.1.7.3)
irb(main):001:0> Ticket::Priority.pluck(:name)
=> [PRIORITIES ARRAY]
irb(main):002:0>

Actual behavior:

docker exec -it zammad-docker-compose-zammad-railsserver-1 sh
irb(main):001:0> Ticket::Priority.pluck(:name)
=> [] (EMPTY ARRAY)

Steps to reproduce the behavior:

Install lastest docker & docker compose version
git clone GitHub - zammad/zammad-docker-compose: Zammad Docker images for docker-compose
cd zammad-docker-compose
docker compose up -d
zammad initial configuration

Any rails get commads returns a empty values (no errors). And put commands dont works. ¿Any idea?

Regards

[fliebe92]

Hi @pabloR_77, did you wait long enough for the Zammad init container to be ready + shut down?

[pabloR_77]

@fliebe92

did you wait long enough for the Zammad init container to be ready + shut down

Hi fliebe92.

Yeah. The containers have been running for many hours. And zammad is working fine. But I cant use the rails console.

Thanks

[fliebe92]

Hi @pabloR_77. I was able to check this in a test environment, currently, I have no idea what’s going on there. I’ll try to clarify this in the next week.

[wwicak]

Hi all,

I can confirm this behaviour, tried to exec the different container and rails c, any commands issued return empty value

Ths

[fliebe92]

Please have a look here: Added postgres env data by Finnlife · Pull Request #357 · zammad/zammad-docker-compose · GitHub

You need to provide the correct credentials for the database, otherwise, the nulldb adapter is used and you’re not getting any results. Maybe this helps.

[wwicak]

Hi @fliebe92 , thank you for your swift responses,

For your suggestion, I modified the .env and docker-compose.yml (since I use external DB), because zammad wont running with the existing .env. Here is my container info

And rails console returns empty
Thanks

[pabloR_77]

Thanks @fliebe92 .

I have modified the docker-compose.yml file as explined in Added postgres env data by Finnlife · Pull Request #357 · zammad/zammad-docker-compose · GitHub.

And execute:
docker compose down
docker compose up -d

After that, the rails server docker still have this conf regarding nulldb:

And continue returning empty values.

Note: changes made:

Any idea?.

Thanks a lot!

[wwicak]

Hi @pabloR_77 , tried to exec to railserver container, edit the config/database.yml with my adapter and other information related to DB. It works, but I dont like the solution.

[pabloR_77]

@wwicak

I can confirm this behaviour, tried to exec

Hi. Thanks for your reply.

But I not sure about what adapter información I need to set. What adapter, or what databa info?

Any help were welcome.

Thanks.

Pablo R.

[wwicak]

I assume u’re using docker-compose.yml provided, so it is postgresql

[pabloR_77]

Hi.

Thanks @wwicak . Now it’s working.
Old config:

docker exec -u 0 -it zammad-docker-compose-zammad-railsserver-1 /bin/bash
apt-get update
apt-get install vim
vi config/database.yml

production:
adapter: postgresql
database: zammad_production
pool: 50
timeout: 5000
encoding: utf8
username: zammad
password: zammad
host: zammad-postgresql
port: 5432

¿Optional?: docker compose up -d

And magic, it works!..

[MrGeneration]

Just my 2 cents but you shouldn’t need to adjust the database.yml of Zammads docker-compose at all.
As far as I’m aware the init container is adjusting it itself already.

Not sure what’s going wrong here but this might be a bug.

[pabloR_77]

@MrGeneration

ust my 2 cents but you shouldn’t need to adjust the database.yml of Zammads docker-compose at all.
As far as I’m aware the init container is adjusting it itself already.

Not sure what’s going wrong here but this might be a bug.

Complety agree @MrGeneration.

These changes are only a work around til docker-compose.yml is been correcly modified.

Thanks