Comment history

On a fresh instance using default settings uploading media does not work at all for me. Changing my avatar used to work, but I just deleted all the docker volumes after pulling the latest images, and now that doesn't work either. Error messages I'm seeing when trying to change my avatar: Error messages when trying to upload media i.e. sending an image to myself via notes: As far as I can see all my buckets are present: `fluxer size:0 chunk:0 fluxer-downloads size:0 chunk:0 fluxer-harvests size:0 chunk:0 fluxer-reports size:0 chunk:0 fluxer-uploads size:0 chunk:0` EDIT: Managed to get it to work by adding "-volume.max=100" to the command line under seaweedfs: section in the docker compose, deleting the seaweed volume, and then restarting everything(I also had to recreate the fluxer bucket per previously provided instructions) That said, I really have no idea how weedfs or any other object oriented storage really works for that matter and added the command solely because an LLM told me to, I don't know if this might have some other undesirable consequences. It will still error out after the first upload, but all subsequent uploads seem to work without issue after that.

On a fresh instance using default settings uploading media does not work at all for me. Changing my avatar used to work, but I just deleted all the docker volumes after pulling the latest images, and now that doesn't work either. Error messages I'm seeing when trying to change my avatar: Error messages when trying to upload media i.e. sending an image to myself via notes: `seaweedfs-1 | I0630 23:05:36.009682 master_grpc_server_volume.go:140 volume grow &{Option:{"collection":"fluxer-uploads","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign} seaweedfs-1 | I0630 23:05:36.009765 node.go:220 topo failed to pick 1 from 0 node candidates seaweedfs-1 | I0630 23:05:36.009779 volume_growth.go:140 create 7 volume, created 0: Not enough data nodes found! seaweedfs-1 | I0630 23:05:36.198569 master_grpc_server_volume.go:96 volume grow request for dc:DefaultDataCenter rack:DefaultRack failed: only 0 volumes left, not enough for 2 seaweedfs-1 | I0630 23:05:36.210742 master_grpc_server_volume.go:140 volume grow &{Option:{"collection":"fluxer-uploads","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign} ` As far as I can see all my buckets are present: `fluxer size:0 chunk:0 fluxer-downloads size:0 chunk:0 fluxer-harvests size:0 chunk:0 fluxer-reports size:0 chunk:0 fluxer-uploads size:0 chunk:0` EDIT: Managed to get it to work by adding "-volume.max=100" to the command line under seaweedfs: section in the docker compose, deleting the seaweed volume, and then restarting everything(I also had to recreate the fluxer bucket per previously provided instructions) That said, I really have no idea how weedfs or any other object oriented storage really works for that matter and added the command solely because an LLM told me to, I don't know if this might have some other undesirable consequences. It will still error out after the first upload, but all subsequent uploads seem to work without issue after that.

On a fresh instance using default settings uploading media does not work at all for me. Changing my avatar used to work, but I just deleted all the docker volumes after pulling the latest images, and now that doesn't work either. Error messages I'm seeing when trying to change my avatar: `seaweedfs-1 | I0630 23:20:38.927918 node.go:220 topo failed to pick 1 from 0 node candidates seaweedfs-1 | I0630 23:20:38.927932 volume_growth.go:140 create 7 volume, created 0: Not enough data nodes found! seaweedfs-1 | I0630 23:20:39.128866 master_grpc_server_volume.go:140 volume grow &{Option:{"collection":"fluxer","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc as` Error messages when trying to upload media i.e. sending an image to myself via notes: `seaweedfs-1 | I0630 23:05:36.009682 master_grpc_server_volume.go:140 volume grow &{Option:{"collection":"fluxer-uploads","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign} seaweedfs-1 | I0630 23:05:36.009765 node.go:220 topo failed to pick 1 from 0 node candidates seaweedfs-1 | I0630 23:05:36.009779 volume_growth.go:140 create 7 volume, created 0: Not enough data nodes found! seaweedfs-1 | I0630 23:05:36.198569 master_grpc_server_volume.go:96 volume grow request for dc:DefaultDataCenter rack:DefaultRack failed: only 0 volumes left, not enough for 2 seaweedfs-1 | I0630 23:05:36.210742 master_grpc_server_volume.go:140 volume grow &{Option:{"collection":"fluxer-uploads","replication":{},"ttl":{"Count":0,"Unit":0},"version":3} Count:0 Force:false Reason:grpc assign} ` As far as I can see all my buckets are present: `fluxer size:0 chunk:0 fluxer-downloads size:0 chunk:0 fluxer-harvests size:0 chunk:0 fluxer-reports size:0 chunk:0 fluxer-uploads size:0 chunk:0` EDIT: Managed to get it to work by adding "-volume.max=100" to the command line under seaweedfs: section in the docker compose, deleting the seaweed volume, and then restarting everything(I also had to recreate the fluxer bucket per previously provided instructions) That said, I really have no idea how weedfs or any other object oriented storage really works for that matter and added the command solely because an LLM told me to, I don't know if this might have some other undesirable consequences. It will still error out after the first upload, but all subsequent uploads seem to work without issue after that.