starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #2176] Transport endpoint is not connected #1106

New issue

Closed

opened 2026-03-04 01:51:26 +03:00 by kerem · 7 comments

kerem commented

2026-03-04 01:51:26 +03:00

Owner

Originally created by @dbartenstein on GitHub (May 30, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2176

Additional Information

Version of s3fs being used (`s3fs --version`)

V1.89 (commit:unknown)

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

2.9.9-5

Kernel information (`uname -r`)

5.10.0-23-cloud-amd64

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

Debian GNU/Linux 11 (bullseye)

How to run s3fs, if applicable

[x] /etc/fstab

s3fs#prod.media.zemtu   /var/www/zemtu/public/media     fuse    _netdev,allow_other,use_path_request_style,use_cache=/tmp,uid=1001,gid=1002,umask=0022,url=https://sos-ch-dk-2.exo.io/,passwd_file=/root/.passwd-s3fs,comment=cloudconfig  0       0

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

syslog
[Errno 107] Transport endpoint is not connected

May 29 09:16:58 prod-main-zemtu s3fs[2017306]: s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected

Details about issue

After two weeks without any issues, the mountpoint suddenly stopped working. We had to execute:

sudo fusermount -uz /var/www/zemtu/public/media
sudo mount -a

I already commented another similar issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/725#issuecomment-1568047863
Hint: we’re using Exoscale, not AWS.

An option I came across is nodnscache (disable DNS cache) - what exactly happens when the dnscache is enabled (default)? Will s3fs pick up DNS changes automatically, e.g. when the URL suddenly points to a CNAME instead of an A record?

Thanks a lot!

Originally created by @dbartenstein on GitHub (May 30, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2176  ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.89 (commit:unknown) #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) 2.9.9-5 #### Kernel information (`uname -r`) 5.10.0-23-cloud-amd64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) Debian GNU/Linux 11 (bullseye) #### How to run s3fs, if applicable  [x] /etc/fstab  ``` s3fs#prod.media.zemtu /var/www/zemtu/public/media fuse _netdev,allow_other,use_path_request_style,use_cache=/tmp,uid=1001,gid=1002,umask=0022,url=https://sos-ch-dk-2.exo.io/,passwd_file=/root/.passwd-s3fs,comment=cloudconfig 0 0 ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`)  ``` syslog [Errno 107] Transport endpoint is not connected May 29 09:16:58 prod-main-zemtu s3fs[2017306]: s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected ``` ### Details about issue After two weeks without any issues, the mountpoint suddenly stopped working. We had to execute: ``` sudo fusermount -uz /var/www/zemtu/public/media sudo mount -a ``` I already commented another similar issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/725#issuecomment-1568047863 Hint: we’re using [Exoscale](https://www.exoscale.com/), not AWS. An option I came across is `nodnscache (disable DNS cache)` - what exactly happens when the dnscache is enabled (default)? Will s3fs pick up DNS changes automatically, e.g. when the URL suddenly points to a CNAME instead of an A record? Thanks a lot!

kerem closed this issue

2026-03-04 01:51:26 +03:00

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@dbartenstein commented on GitHub (May 31, 2023):

Update: we have just upgraded to s3fs 1.92 and will continue monitoring the situation.

But we still wonder what nodnscache (disable DNS cache) exactly does. For how long is DNS cached when the option is not used? Thanks!

@dbartenstein commented on GitHub (May 31, 2023): Update: we have just upgraded to s3fs 1.92 and will continue monitoring the situation. But we still wonder what` nodnscache (disable DNS cache)` exactly does. For how long is DNS cached when the option is not used? Thanks!

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@ggtakec commented on GitHub (Jun 10, 2023):

@dbartenstein Thanks for testing with the latest code(v1.92).

s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected

You are reporting this error in your logs, is this error preventing s3fs from starting?
If s3fs does not start due to the above error, it means that the mount point(/var/www/zemtu/public/media) could not be accessed by the s3fs effective user.

If the error above and the reason s3fs doesn't start are different, we need to await other log/report by your environment.
Thanks in advance for your assistance.

@ggtakec commented on GitHub (Jun 10, 2023): @dbartenstein Thanks for testing with the latest code(v1.92). ``` s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected ``` You are reporting this error in your logs, is this error preventing s3fs from starting? If s3fs does not start due to the above error, it means that the mount point(`/var/www/zemtu/public/media`) could not be accessed by the s3fs effective user. If the error above and the reason s3fs doesn't start are different, we need to await other log/report by your environment. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@dbartenstein commented on GitHub (Jun 12, 2023):

@dbartenstein Thanks for testing with the latest code(v1.92).
s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected
You are reporting this error in your logs, is this error preventing s3fs from starting? If s3fs does not start due to the above error, it means that the mount point(/var/www/zemtu/public/media) could not be accessed by the s3fs effective user.

If the error above and the reason s3fs doesn't start are different, we need to await other log/report by your environment. Thanks in advance for your assistance.

@ggtakec
s3fs had been running for two weeks and then it suddenly stopped with the "Transport endpoint is not connected" error. Only after executing the following lines, the end point was back again:

sudo fusermount -uz /var/www/zemtu/public/media
sudo mount -a

But we still wonder what nodnscache (disable DNS cache) exactly does. For how long is DNS cached when the option is not used? Thanks!

What exactly is the option nodnscache doing?

Thanks!

@dbartenstein commented on GitHub (Jun 12, 2023): > @dbartenstein Thanks for testing with the latest code(v1.92). > > ``` > s3fs: unable to access MOUNTPOINT /var/www/zemtu/public/media: Transport endpoint is not connected > ``` > > You are reporting this error in your logs, is this error preventing s3fs from starting? If s3fs does not start due to the above error, it means that the mount point(`/var/www/zemtu/public/media`) could not be accessed by the s3fs effective user. > > If the error above and the reason s3fs doesn't start are different, we need to await other log/report by your environment. Thanks in advance for your assistance. @ggtakec s3fs had been running for two weeks and then it suddenly stopped with the "Transport endpoint is not connected" error. Only after executing the following lines, the end point was back again: ``` sudo fusermount -uz /var/www/zemtu/public/media sudo mount -a ``` > But we still wonder what nodnscache (disable DNS cache) exactly does. For how long is DNS cached when the option is not used? Thanks! What exactly is the option `nodnscache` doing? Thanks!

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@ggtakec commented on GitHub (Jun 12, 2023):

@dbartenstein
In your environment, it seems better to turn on the nodnscache option.

s3fs uses its own DNS cache as default for better performance.
If nodnscache is specified, it will not be used and libcurl's default will work. (libcurl keeps the DNS cache for 60 seconds.)
Thus, you can still adjust this option for your environment.

@ggtakec commented on GitHub (Jun 12, 2023): @dbartenstein In your environment, it seems better to turn on the `nodnscache` option. s3fs uses its own DNS cache as default for better performance. If `nodnscache` is specified, it will not be used and libcurl's default will work. (libcurl keeps the DNS cache for 60 seconds.) Thus, you can still adjust this option for your environment.

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@gaul commented on GitHub (Sep 8, 2023):

Please reopen if symptoms persist.

@gaul commented on GitHub (Sep 8, 2023): Please reopen if symptoms persist.

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@uncdubdiver commented on GitHub (Sep 15, 2023):

Can I request we reopen this? It's still happening to me constantly.

@uncdubdiver commented on GitHub (Sep 15, 2023): Can I request we reopen this? It's still happening to me constantly. ![image](https://github.com/s3fs-fuse/s3fs-fuse/assets/7240221/b279cf3b-2277-4184-98af-0131a09409a4)

kerem commented

2026-03-04 01:51:27 +03:00

Author

Owner

@gaul commented on GitHub (Sep 15, 2023):

This is a generic symptom that indicates a crash. Please open a new issue for your symptom.

@gaul commented on GitHub (Sep 15, 2023): This is a generic symptom that indicates a crash. Please open a new issue for your symptom.

kerem referenced this issue

2026-03-04 02:02:18 +03:00

[PR #1106] [MERGED] Fixed filter-suite-log.sh for on osx #1816