[GH-ISSUE #2511] Socket Connection to server was not read from or written to within the timeout period. Idle connections will be closed. #1226

New issue

Open

opened 2026-03-04 01:52:23 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:52:23 +03:00

Owner

Originally created by @skumar19822 on GitHub (Aug 13, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2511

Additional Information

Version of s3fs being used (`s3fs --version`) - V1.92 & V1.93

Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)

Kernel information (`uname -r`)

GNU/Linux Distribution, if applicable (`cat /etc/os-release`)

How to run s3fs, if applicable

[] command line
[] /etc/fstab

s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`)

Details about issue

we are using s3fs-fuse version 1.92 and 1.93 as well,
mounted well using libs3fsawscredi.so -o readwrite_timeout=600 -o connect_timeout=600 -o retries=20.

it's running fine while transferring 800M file but we are getting an exception very rarely

Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.

but s3fs mount alive and it is working fine.

Kindly suggest what could be done to fix this issue, can we give -o readwrite_timeout=1800 -o connect_timeout=1200 would that help. Please advise on this.

Originally created by @skumar19822 on GitHub (Aug 13, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2511  ### Additional Information #### Version of s3fs being used (`s3fs --version`) - V1.92 & V1.93  #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)  #### Kernel information (`uname -r`)  #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`)  #### How to run s3fs, if applicable  [] command line [] /etc/fstab  ``` ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`)  ``` ``` ### Details about issue  we are using s3fs-fuse version 1.92 and 1.93 as well, mounted well using libs3fsawscredi.so -o readwrite_timeout=600 -o connect_timeout=600 -o retries=20. it's running fine while transferring 800M file but we are getting an exception very rarely **Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.** but s3fs mount alive and it is working fine. Kindly suggest what could be done to fix this issue, can we give **-o readwrite_timeout=1800 -o connect_timeout=1200** would that help. Please advise on this.

kerem commented

2026-03-04 01:52:23 +03:00

Author

Owner

@ggtakec commented on GitHub (Aug 17, 2024):

@skumar19822 Thank you for reporting this.
However, this issue is about libs3fsawscred, not s3fs-fuse, so please repost this s3fs-fuse-awscred-lib.

To confirm why the timeout is occurring, set the LogLevel to the same as this explanation to obtain more information.
Please post an issue s3fs-fuse-awscred-lib with the results of your investigation.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Aug 17, 2024): @skumar19822 Thank you for reporting this. However, this issue is about libs3fsawscred, not s3fs-fuse, so please repost this [s3fs-fuse-awscred-lib](https://github.com/ggtakec/s3fs-fuse-awscred-lib/issues). To confirm why the timeout is occurring, set the LogLevel to the same as [this explanation](https://github.com/ggtakec/s3fs-fuse-awscred-lib?tab=readme-ov-file#credlib_opts) to obtain more information. Please post an issue [s3fs-fuse-awscred-lib](https://github.com/ggtakec/s3fs-fuse-awscred-lib/issues) with the results of your investigation. Thanks in advance for your assistance.