starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-24 21:06:02 +03:00

[GH-ISSUE #2798] Ambiguous/Missing error connecting to non-aws buckets #1302

New issue

Open

opened 2026-03-04 01:52:56 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @andrewdscott12 on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2798

Additional Information

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

V1.95 and up

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

2.9.9

Provider (`AWS`, `OVH`, `Hetzner`, `iDrive E2`, ...)

IBM ICOS

Kernel information (`uname -r`)

5.14.0-503.40.1.el9_5.s390x

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

RHEL9.5

How to run s3fs, if applicable

[] command line
[X] /etc/fstab
rhui /var/lib/rhi fuse.s3fs _netdev,noatime,nonempty, allow_other,url=https://providerendpoint 0 0

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

Details about issue

Ambiguous/missing errors. Checked against current version of s3fs_check_service function, and omission still appears to exist. s3fs-fuse does not provide a useful error when failing to connect due to a certificate validation issue. If Certificate validation errors from curl were passed through to the error generated by s3fs-fuse, user experience would be dramatically improved. Currently, failures due to cert validations are essentially silent. It simply won't mount the bucket and the message in the log is null.

Originally created by @andrewdscott12 on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2798  ### Additional Information #### Version of s3fs being used (`s3fs --version`)  V1.95 and up #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)  2.9.9 #### Provider (`AWS`, `OVH`, `Hetzner`, `iDrive E2`, ...)  IBM ICOS #### Kernel information (`uname -r`)  5.14.0-503.40.1.el9_5.s390x #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`)  RHEL9.5 #### How to run s3fs, if applicable  [] command line [X] /etc/fstab rhui /var/lib/rhi fuse.s3fs _netdev,noatime,nonempty, allow_other,url=https://providerendpoint 0 0  ``` ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`)  ``` s3fs.cpp:s3fs_check_service(4503): Failed to check bucket and directory for mount point: Unable to connect(host=https://providerendpoint, message=) ``` ### Details about issue  Ambiguous/missing errors. Checked against current version of s3fs_check_service function, and omission still appears to exist. s3fs-fuse does not provide a useful error when failing to connect due to a certificate validation issue. If Certificate validation errors from curl were passed through to the error generated by s3fs-fuse, user experience would be dramatically improved. Currently, failures due to cert validations are essentially silent. It simply won't mount the bucket and the message in the log is null.

kerem commented

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

Author

Owner

@andrewdscott12 commented on GitHub (Feb 2, 2026):

Don't know why log message not in post

when failure occurs, message in syslog:

s3fs.cpp:s3fs_check_service(4503): Failed toc heck bucket and directory for mount point : Unable to connect(host=https://providerendpoint, message=)

@andrewdscott12 commented on GitHub (Feb 2, 2026): Don't know why log message not in post when failure occurs, message in syslog: s3fs.cpp:s3fs_check_service(4503): Failed toc heck bucket and directory for mount point : Unable to connect(host=https://providerendpoint, message=)

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (Feb 4, 2026):

@andrewdscott12 Could you please specify the curldbg option?
This should allow you to get the messages curl outputs.

@ggtakec commented on GitHub (Feb 4, 2026): @andrewdscott12 Could you please specify the `curldbg` option? This should allow you to get the messages curl outputs.

kerem commented

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

Author

Owner

@andrewdscott12 commented on GitHub (Feb 4, 2026):

What prompted this issue was a support analyst beating their head against a wall for several days. In a corporate environment, such an analyst is often not allowed to make changes to the system, including adding debug switches to software invocations. They have to run them as-is and read the logs. In that kind of environment, A certificate validation error is a serious failure with a relatively simple remedy. If that could be surfaced without having to set a debug option, that would ideal.

@andrewdscott12 commented on GitHub (Feb 4, 2026): What prompted this issue was a support analyst beating their head against a wall for several days. In a corporate environment, such an analyst is often not allowed to make changes to the system, including adding debug switches to software invocations. They have to run them as-is and read the logs. In that kind of environment, A certificate validation error is a serious failure with a relatively simple remedy. If that could be surfaced without having to set a debug option, that would ideal.

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (Feb 8, 2026):

@andrewdscott12 I created #2799 PR for this issue.
This should display the curl error message at startup.
Could you try to check this PR's code?

@ggtakec commented on GitHub (Feb 8, 2026): @andrewdscott12 I created #2799 PR for this issue. This should display the curl error message at startup. Could you try to check this PR's code?

kerem commented

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

Author

Owner

@andrewdscott12 commented on GitHub (Feb 8, 2026):

Code looks good. I'll compile the branch and test it Monday or Tuesday when I get back to work.

@andrewdscott12 commented on GitHub (Feb 8, 2026): Code looks good. I'll compile the branch and test it Monday or Tuesday when I get back to work.