You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: