mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1167] Transport endpoint is not connected and force to create new handler #613
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#613
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bigheh on GitHub (Oct 11, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1167
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: [IAM role=qulp-testssm]
Oct 11 03:49:00 ip-10-123-72-84 s3fs[31710]: Pool empty: force to create new handler
Oct 11 03:49:00 ip-10-123-72-84 kernel: s3fs[31711]: segfault at 7ff4e09b5f00 ip 00007ff4e5359737 sp 00007ff4e09b5e20 error 6 in libc-2.26.so[7ff4e52fe000+1ad000]
Above is the problem log.
@simonmandlik commented on GitHub (Nov 8, 2019):
The same thing happens to me
@simonmandlik commented on GitHub (Nov 8, 2019):
Using a previous version as described in https://github.com/s3fs-fuse/s3fs-fuse/issues/1162 solves the issue for the time being for me.
@gaul commented on GitHub (Feb 2, 2020):
Please try running s3fs under Valgrind or using gdb and attach a backtrace.
@gaul commented on GitHub (Apr 22, 2020):
Please reopen if symptoms persist.