starred/s3fs-fuse

Fork 0

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

[GH-ISSUE #1228] Transport Endpoint is not connected #658

New issue

Closed

opened 2026-03-04 01:47:38 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:47:38 +03:00

Owner

Originally created by @tapanjo92 on GitHub (Jan 9, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1228

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

example: 1.00

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

example: 2.9.4

Kernel information (uname -r)

command result: uname -r

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

command result: cat /etc/os-release

s3fs command line used, if applicable

/etc/fstab entry, if applicable

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

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

So when trying to mount and debug it getting an ' Transport endpoint not connected' error

Originally created by @tapanjo92 on GitHub (Jan 9, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1228 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) _example: 1.00_ #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) _example: 2.9.4_ #### Kernel information (uname -r) _command result: uname -r_ #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _command result: cat /etc/os-release_ #### s3fs command line used, if applicable ``` ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue So when trying to mount and debug it getting an ' Transport endpoint not connected' error ![trasport endpoint](https://user-images.githubusercontent.com/49943773/72111267-5ef97200-338e-11ea-8e9f-33c3fbb672f2.png)

kerem

2026-03-04 01:47:38 +03:00

closed this issue
added the
need info
label

kerem commented

2026-03-04 01:47:39 +03:00

Author

Owner

@KaiSoellch commented on GitHub (Jan 23, 2020):

Same Problem here 😢

@KaiSoellch commented on GitHub (Jan 23, 2020): Same Problem here 😢

kerem commented

2026-03-04 01:47:39 +03:00

Author

Owner

@gaul commented on GitHub (Feb 2, 2020):

Try mounting with -f -d to see the debug logs.

@gaul commented on GitHub (Feb 2, 2020): Try mounting with `-f -d` to see the debug logs.

kerem commented

2026-03-04 01:47:39 +03:00

Author

Owner

@rallister commented on GitHub (Feb 6, 2020):

@tapanjo92 It probably failed to mount /tmp. try mounting the endpoint to a different folder. /tmp is unlikely to be empty and you have option nonempty and chances are it's already a mount for something else.

@rallister commented on GitHub (Feb 6, 2020): @tapanjo92 It probably failed to mount /tmp. try mounting the endpoint to a different folder. /tmp is unlikely to be empty and you have option nonempty and chances are it's already a mount for something else.

kerem commented

2026-03-04 01:47:39 +03:00

Author

Owner

@gaul commented on GitHub (Jun 5, 2020):

Closing due to inactivity. Please retest with 1.86 or master with the suggested flags if symptoms persist. Note that these symptoms have several potential causes so other reporters should open new issues.

@gaul commented on GitHub (Jun 5, 2020): Closing due to inactivity. Please retest with 1.86 or master with the suggested flags if symptoms persist. Note that these symptoms have several potential causes so other reporters should open new issues.

kerem referenced this issue

2026-03-04 02:01:12 +03:00

[PR #659] [MERGED] Do not fail updating directory when removing old-style object(ref #658) #1588

kerem referenced this issue

2026-03-04 02:01:12 +03:00

[PR #658] [CLOSED] Do not fail updating directory when removing old-style object #1589