Hi, We've setup an Amazon S3 bucket with nearly wide open permissions. We supplied all the parameters as per documentation. When we start a test backup job it seems to queue and then enter a "running" state for a long period of time with no obvious failures or error codes/messages. After the job has been running for a few minutes, a subsequent check of messages from the bconsole CLI shows that a mount request exists for the S3 volume because the mount was not automatic. We then honor the S3 volume mount request using console "mount" command only to see another mount request. Has anyone experienced this "mount request loop" when testing the bareos-storage-droplet S3 addon package? Any general recommendations on what configuration options are causing this repeating mount request behavior when attempting to write to an S3 object store? Any recommendations on AWS S3 bucket attributes on the Amazon side that may fix this? Thanks, Pat
-- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
