AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Comment history

Versions of a comment on [Self-hosted] Uploads fail with Access Denied when the SeaweedFS bucket is missing, newest first.

Current version | Edited by Rex
Changes
- /mnt/data/fluxer/seaweedfs:/data:rw```Removed: also, in my particular case, _all_ the buckets failed to be created, not just the `fluxer` bucket. Manually creating the buckets using [@Hacker6329](https://github.com/Hacker6329)'s method worked fine and I could upload icons and other media after.Added: also, in my particular case, _all_ the buckets failed to be created, not just the `fluxer` bucket. Manually creating the buckets using @Hacker6329's method worked fine and I could upload icons and other media after.however, this issue _does not_ show up if I leave the defaults and therefore the data volume gets located on my internal NVME instead.
Show
Seems to be an issue with seaweedfs-init. However, on my end, the issue only shows up when the data volume for seaweedfs is mounted somewhere else (in my case, a partition on an internal HDD). this is the output from docker compose logs -f seaweedfs-init: 
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | buckets ready
using this configuration for seaweedfs in docker-compose.yml: 
seaweedfs:
    image: chrislusf/seaweedfs:4.34
    restart: unless-stopped
    networks: [fluxer]
    command: ["server", "-s3", "-dir=/data"]
    volumes:
      - /mnt/data/fluxer/seaweedfs:/data:rw
also, in my particular case, all the buckets failed to be created, not just the fluxer bucket. Manually creating the buckets using @Hacker6329's method worked fine and I could upload icons and other media after. however, this issue does not show up if I leave the defaults and therefore the data volume gets located on my internal NVME instead. my very naive guess is that seaweedfs-init is starting up before seaweedfs is actually finished setting up completely and the slower r/w speed on the HDD is exacerbating the problem. Just a guess though 🫠.
Original by Rex
Show
Seems to be an issue with seaweedfs-init. However, on my end, the issue only shows up when the data volume for seaweedfs is mounted somewhere else (in my case, a partition on an internal HDD). this is the output from docker compose logs -f seaweedfs-init: 
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | error: get filer configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp: missing address"
seaweedfs-init-1  | buckets ready
using this configuration for seaweedfs in docker-compose.yml: 
seaweedfs:
    image: chrislusf/seaweedfs:4.34
    restart: unless-stopped
    networks: [fluxer]
    command: ["server", "-s3", "-dir=/data"]
    volumes:
      - /mnt/data/fluxer/seaweedfs:/data:rw
also, in my particular case, all the buckets failed to be created, not just the fluxer bucket. Manually creating the buckets using @Hacker6329's method worked fine and I could upload icons and other media after. however, this issue does not show up if I leave the defaults and therefore the data volume gets located on my internal NVME instead. my very naive guess is that seaweedfs-init is starting up before seaweedfs is actually finished setting up completely and the slower r/w speed on the HDD is exacerbating the problem. Just a guess though 🫠.