Hello guys,
Let me say first We love the magic you did with this app. love it, really!
We are facing an issue with websocket with our installation (docker-compose) in AWS EC2 infraestructure.
- Used Zammad version: 4.1.x
- Used Zammad installation type: docker-compose
- Operating system: Linux
- Browser + version: Chrome Version 91.0.4472.101 (Official Build) (64-bit)
Expected behavior:
The Zammad plaform shoulw work properly in and EC2 Virtual Machine with EFS mountpoint
Actual behavior
We have mapped a EFS volum to /opt/zammad. When a websocket connection is needed, it doesn’t work raising this errors on log:
2021-08-31T13:26:07Z:client(47242089277060) problem:#<Errno::EBADF: Bad file descriptor @ rb_file_flock - /opt/zammad/tmp/websocket_production/47242089277060/send-1630416367.3056028>
Test We did:
1.- If We manually mount this EFS volume doesn’t work (same issue)
2.- If the map a local folder as a volume it works perfectly
3.- Doublechecked permision and ownership of the folders…
As a summary, Websocket doesn’t work in AWS platform when your volumes are EFS
Hope it is clear…
Steps to reproduce the behavior:
Install a docker-compose version in a AWS EC2 with EFS volume mapped to /opt/zammad
Thank you for your help!