[GH-ISSUE #2434] Set a custom endpoint connection port ? #1198

New issue

Closed

opened 2026-03-04 01:52:09 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @Alakadoo on GitHub (Mar 12, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2434

Additional Information

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

v1.90

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

2.9.9

Kernel information (`uname -r`)

5.15.0-100-generic

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

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

How to run s3fs, if applicable

[X] command line

s3fs buckets3 /buckets3 -o passwd_file=/etc/passwd-s3fs -o url=http://isilonendpoint.com:9020 -o use_path_request_style -o dbglevel=info -f -o retries=1 -o connect_timeout=60

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

> 2024-03-12T09:44:45.570Z [INF] s3fs version 1.90(unknown) : s3fs -o passwd_file=/etc/passwd-s3fs -o url=http://isilonendpoint.com:9020 -o use_path_request_style -o dbglevel=info -f -o retries=1 -o connect_timeout=60 buckets3 /buckets3
> 2024-03-12T09:44:45.570Z [CRT] s3fs_logger.cpp:LowSetLogLevel(240): change debug level from [CRT] to [INF]
> 2024-03-12T09:44:45.570Z [INF]     s3fs.cpp:set_mountpoint_attribute(4093): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
> 2024-03-12T09:44:45.572Z [INF] curl.cpp:InitMimeType(434): Loaded mime information from /etc/mime.types
> 2024-03-12T09:44:45.572Z [INF] fdcache_stat.cpp:CheckCacheFileStatTopDir(79): The path to cache top dir is empty, thus not need to check permission.
> 2024-03-12T09:44:45.572Z [INF] s3fs.cpp:s3fs_init(3382): init v1.90(commit:unknown) with GnuTLS(gcrypt)
> 2024-03-12T09:44:45.572Z [INF] s3fs.cpp:s3fs_check_service(3516): check services.
> 2024-03-12T09:44:45.572Z [INF]       curl.cpp:CheckBucket(3388): check a bucket.
> 2024-03-12T09:44:45.572Z [INF]       curl_util.cpp:prepare_url(254): URL is http://isilonendpoint.com:9020/buckets3/
> 2024-03-12T09:44:45.572Z [INF]       curl_util.cpp:prepare_url(287): URL changed is http://isilonendpoint.com:9020/buckets3/
> 2024-03-12T09:44:45.572Z [INF]       curl.cpp:insertV4Headers(2680): computing signature [GET] [/] [] []
> 2024-03-12T09:44:45.572Z [INF]       curl_util.cpp:url_to_host(331): url is http://isilonendpoint.com:9020
> 2024-03-12T09:45:45.573Z [ERR] curl.cpp:RequestPerform(2406): ### CURLE_OPERATION_TIMEDOUT
> 2024-03-12T09:45:47.573Z [INF] curl.cpp:RequestPerform(2515): ### retrying...
> 2024-03-12T09:45:47.573Z [INF]       curl.cpp:RemakeHandle(2107): Retry request. [type=5][url=http://isilonendpoint.com:9020/buckets3/][path=/]
> 2024-03-12T09:45:47.573Z [ERR] curl.cpp:RequestPerform(2533): ### giving up
> 2024-03-12T09:45:47.573Z [ERR] curl.cpp:CheckBucket(3421): Check bucket failed, S3 response:
> 2024-03-12T09:45:47.573Z [CRT] s3fs.cpp:s3fs_check_service(3597): unable to connect(host=http://isilonendpoint.com:9020) - result of checking service.
> 2024-03-12T09:45:47.573Z [INF] curl_handlerpool.cpp:ReturnHandler(110): Pool full: destroy the oldest handler
> 2024-03-12T09:45:47.573Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(3372): Exiting FUSE event loop due to errors
> 
> 2024-03-12T09:45:47.575Z [INF] s3fs.cpp:s3fs_destroy(3440): destroy

Details about issue

I'm trying to mount my s3 bucket created on my isilon storage.
Isilon is only listening on port 9020 and 9021 for s3 buckets, however even by setting :9020 at the end of url option, I can see on my network trace that my client is still trying to connect to the isilonendpoint on port 80, resulting in an access denied.
Is there a way to set a custom port ? I didn't see any option related in the documentation.

Originally created by @Alakadoo on GitHub (Mar 12, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2434  ### Additional Information #### Version of s3fs being used (`s3fs --version`) v1.90 #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) 2.9.9 #### Kernel information (`uname -r`) 5.15.0-100-generic #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy #### How to run s3fs, if applicable  [X] command line  s3fs buckets3 /buckets3 -o passwd_file=/etc/passwd-s3fs -o url=http://isilonendpoint.com:9020 -o use_path_request_style -o dbglevel=info -f -o retries=1 -o connect_timeout=60 #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`) ``` > 2024-03-12T09:44:45.570Z [INF] s3fs version 1.90(unknown) : s3fs -o passwd_file=/etc/passwd-s3fs -o url=http://isilonendpoint.com:9020 -o use_path_request_style -o dbglevel=info -f -o retries=1 -o connect_timeout=60 buckets3 /buckets3 > 2024-03-12T09:44:45.570Z [CRT] s3fs_logger.cpp:LowSetLogLevel(240): change debug level from [CRT] to [INF] > 2024-03-12T09:44:45.570Z [INF] s3fs.cpp:set_mountpoint_attribute(4093): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) > 2024-03-12T09:44:45.572Z [INF] curl.cpp:InitMimeType(434): Loaded mime information from /etc/mime.types > 2024-03-12T09:44:45.572Z [INF] fdcache_stat.cpp:CheckCacheFileStatTopDir(79): The path to cache top dir is empty, thus not need to check permission. > 2024-03-12T09:44:45.572Z [INF] s3fs.cpp:s3fs_init(3382): init v1.90(commit:unknown) with GnuTLS(gcrypt) > 2024-03-12T09:44:45.572Z [INF] s3fs.cpp:s3fs_check_service(3516): check services. > 2024-03-12T09:44:45.572Z [INF] curl.cpp:CheckBucket(3388): check a bucket. > 2024-03-12T09:44:45.572Z [INF] curl_util.cpp:prepare_url(254): URL is http://isilonendpoint.com:9020/buckets3/ > 2024-03-12T09:44:45.572Z [INF] curl_util.cpp:prepare_url(287): URL changed is http://isilonendpoint.com:9020/buckets3/ > 2024-03-12T09:44:45.572Z [INF] curl.cpp:insertV4Headers(2680): computing signature [GET] [/] [] [] > 2024-03-12T09:44:45.572Z [INF] curl_util.cpp:url_to_host(331): url is http://isilonendpoint.com:9020 > 2024-03-12T09:45:45.573Z [ERR] curl.cpp:RequestPerform(2406): ### CURLE_OPERATION_TIMEDOUT > 2024-03-12T09:45:47.573Z [INF] curl.cpp:RequestPerform(2515): ### retrying... > 2024-03-12T09:45:47.573Z [INF] curl.cpp:RemakeHandle(2107): Retry request. [type=5][url=http://isilonendpoint.com:9020/buckets3/][path=/] > 2024-03-12T09:45:47.573Z [ERR] curl.cpp:RequestPerform(2533): ### giving up > 2024-03-12T09:45:47.573Z [ERR] curl.cpp:CheckBucket(3421): Check bucket failed, S3 response: > 2024-03-12T09:45:47.573Z [CRT] s3fs.cpp:s3fs_check_service(3597): unable to connect(host=http://isilonendpoint.com:9020) - result of checking service. > 2024-03-12T09:45:47.573Z [INF] curl_handlerpool.cpp:ReturnHandler(110): Pool full: destroy the oldest handler > 2024-03-12T09:45:47.573Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(3372): Exiting FUSE event loop due to errors > > 2024-03-12T09:45:47.575Z [INF] s3fs.cpp:s3fs_destroy(3440): destroy ``` ### Details about issue  I'm trying to mount my s3 bucket created on my isilon storage. Isilon is only listening on port 9020 and 9021 for s3 buckets, however even by setting :9020 at the end of url option, I can see on my network trace that my client is still trying to connect to the isilonendpoint on port 80, resulting in an access denied. Is there a way to set a custom port ? I didn't see any option related in the documentation.

kerem closed this issue

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

kerem commented

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

Author

Owner

@gaul commented on GitHub (Mar 12, 2024):

Using other ports works -- look at test/integration-test-common.sh which sets S3Proxy to port 8080 as an example.

@gaul commented on GitHub (Mar 12, 2024): Using other ports works -- look at `test/integration-test-common.sh` which sets S3Proxy to port 8080 as an example.

kerem commented

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

Author

Owner

@Alakadoo commented on GitHub (Mar 12, 2024):

Yes it works I can see now in my network trace that port 9020 is being used, I must have failed something in my first command, thanks !

@Alakadoo commented on GitHub (Mar 12, 2024): Yes it works I can see now in my network trace that port 9020 is being used, I must have failed something in my first command, thanks !