Can't start S3 service

[TheHour]

Hello,

I can't start the S3 service.

S3 service failed to start.

I checked the logs and it says

ERROR Unable to initialize backend: Unable to write to the backend
> Please ensure MinIO binary has write permissions for the backend
HINT:
Verify if MinIO binary is running as the same user who has write permissions for the backend

I'm new to FreeNas so not sure where to check the MiniIO binary permissions.

Thanks

 

[Kris Moore]

Interesting, what directory did you share out to Minio? Can you send a screenshot of how the S3 service is configured?

 

[TheHour]

Sorry, I actually solved it now. When you said the directory I suddenly released I probably should put it on a new dataset and it works.

However now if I go to https://SERVER I get

This site can’t provide a secure connection

http connection works great. I have added a valid certificate in the S3 service.

 

[lmigo]

Similar issue on my FreeNAS-11.3-U5.

S3 service configuration.


Dataset permissions.


Can't start the S3 service.

S3 service failed to start.

Logs (/var/log/minio.log).

ERROR Unable to initialize backend: Unable to write to the backend
> Please ensure MinIO binary has write permissions for the backend
HINT:
Use 'sudo chown minio /mnt/pool-1/s3storage && sudo chmod u+rxw /mnt/pool-1/s3storage' to provide sufficient permissions.

When I run the HINT I get this.

Sorry, user root is not allowed to execute '/usr/sbin/chown minio /mnt/pool-1/s3store' as root on freenas-ke.xyz.com.

Any ideas?

 

[lmigo]

root@freenas-ke[~]# ls -lh /mnt/pool-1/
total 11
-rw-r--r-- 1 root wheel 0B May 9 2019 .apple
-rw-rw-rw- 1 root wheel 0B May 9 2019 .mac
drwxrwx--- 4 root 1io-office 6B Dec 10 12:53 backups
drwxr-xr-x 9 root wheel 11B Mar 3 2020 iocage
drwxrwxr-x 2 minio minio 2B Dec 10 13:39 s3storage

 

[Simon Greener]

I had problems starting the S3 service, and in my case it turned out to be the Access Key and Secret Key containing "illegal characters". I discovered that was possible when I attempted to start the S3 service on a second, remote TrueNAS core server, which displayed the error on the web console. Why the local TrueNAS core server did not show me the error (same version of server) I don't know.

So I removed all special characters (a KeePass generated random 20 character key) and the S3 service stated. Sure enough, I tried the same on my local TrueNAS core server's S3 config and it started too.

So - HOURs wasted for me because it is not clear that [!"£$%^&*(){};':@#~,.<>/?\|`¬].* are not valid in the keys.