Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s3fs: software caused connection abort #100

Open
tongyangyeyue opened this issue Jul 18, 2024 · 1 comment
Open

s3fs: software caused connection abort #100

tongyangyeyue opened this issue Jul 18, 2024 · 1 comment

Comments

@tongyangyeyue
Copy link

tongyangyeyue commented Jul 18, 2024

version: v1.2.0-rc.2
kubernetes version: v1.23.17
mounter: s3fs

We use this version to mount Minio S3. But when we used different passwords to mount, we found the problem of mounting errors:
software caused connection abort。

K8s events :
Events:
  Type     Reason                  Age               From                     Message
  ----     ------                  ----              ----                     -------
  Normal   SuccessfulAttachVolume  25s               attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-7f5e238b-fe55-4014-840f-ac88498ebe91"
  Warning  FailedMount             2s (x6 over 18s)  kubelet                  MountVolume.SetUp failed for volume "pvc-7f5e238b-fe55-4014-840f-ac88498ebe91" : rpc error: code = Unknown desc = stat /var/lib/kubelet/pods/dc4e633a-9e8a-4abf-8d22-c795e629da45/volumes/kubernetes.io~csi/pvc-7f5e238b-fe55-4014-840f-ac88498ebe91/mount: software caused connection abort

By querying s3fs commands and csi-s3 source code,We found differences between csi-s3 password files and manual mounting methods
csi-s3 container : password file (/root/.passwd-s3fs) in csi-s3-nfb2x
image
manual write passoword file
image

so we guess password file is wrong , and we change password file (/root/.passwd-s3fs) in container csi-s3-nfb2x

mv .passwd-s3fs .passwd-s3fs_bak
echo minioadmin:minioadmin >>  .passwd-s3fs
chmod 600 .passwd-s3fs

Afterwards, the mount was successful, and our deployments was also able to run successfully。
We are going to submit a PR to solve this problem。

@tongyangyeyue
Copy link
Author

pr: #101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant