'No S3QL filesystem was found' error when adding cloud storage - Connect IT Community

/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

'No S3QL filesystem was found' error when adding cloud storage - Connect IT Community | Kaseya

SUMMARY

If this error occurs with cloudadm 1.67, update to cloudadm 1.69 or later.

ISSUE

Symptoms
See this error message when trying to connect to CloudHook storage:

cmc_nas execution failed.
No S3QL filesystem was found at
s3://unitrends-free-aws/offsite-backups/
ERROR: Failed to mount directory unitrends-free-aws/offsite-backups/ on /backups/Cloud_Storage.

You can verify the version of cloudadm by running this command from a PuTTY/ssh command line:

cloudadm status

cloudadm version 1.74
CLOUD TYPE      | STORAGE       |ONLINE| MAX_GB |USED_GB
...

RESOLUTION

When trying to add or connect to CloudHook storage, sometimes an earlier error may have been masked and the S3QL cloud filesystem did not get created. The resolution is to upgrade the cloudadm binary to version 1.69 or later.

Steps to apply the hotfix from a PuTTY/ssh command line:

wget ftp://ftp.unitrends.com/support/Hotfixes/cloudadmc6-174
chmod +x cloudadmc6-174
cp /usr/bp/bin/cloudadm /usr/bp/bin/cloudadm-orig
cp -f cloudadmc6-174 /usr/bp/bin/cloudadm

CAUSE

If you are receiving this error message and already have cloudadm 1.69 or later, then please examine the /usr/bp/logs.dir/cloudadm.log for any error messages preceding the 'No S3QL filesystem' error to determine the cause.