Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nchan lock the files in client_body_temp #672

Open
KamranBiglari opened this issue Jul 24, 2023 · 1 comment
Open

nchan lock the files in client_body_temp #672

KamranBiglari opened this issue Jul 24, 2023 · 1 comment

Comments

@KamranBiglari
Copy link

I have an issue with nchan while I'm publishing via websocket. ( I never close the WS connection on publisher side and it's always connected )
The message size is 37k and nginx create a temp file in client_body_temp_path.
I change these configuration to avoid nginx to create temp files but there is not luck.

client_max_body_size 10m; # Also to 0 
client_body_timeout 2s;
client_body_buffer_size 10m; # Also to 0 
client_body_in_file_only clean; # Also on / off
send_file on; # off as well

The temp files have been disappeared after a while but in background they are all exists since when I check the iNodes the nginx consume the inodes and files are locked!
If I close the WS connection the nginx/nchan permanently delete the files and release the inodes and locks on files.

Can anyone help me to fix this issue because after a while the system run out of inodes ! @slact

Openresty: 1.21.4.1-0-jammy
nchan: 1.3.6

@slact
Copy link
Owner

slact commented Jul 25, 2023

Please show me the whole Nginx config. Redact anything you need to for privacy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants