You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using s3 to host RPM repo. I was using s3fs without any problems previously
# sudo createrepo .
Directory walk started
Directory walk done - 3 packages
Temporary output repo path: ./.repodata/
Preparing sqlite DBs
Critical: Cannot open ./.repodata//primary.sqlite: Can not open SQL database: disk I/O error
C_CREATEREPOLIB: Warning: cr_remove_dir_cb: Cannot remove: ./.repodata/filelists.xml.gz: Operation not permitted
Relevant log output
No errors other than these:
Nov 21 14:56:16 ip-10-231-0-5 mount-s3[387334]: [INFO] awscrt::http-connection: id=0x7f385c06c290: Shutting down connection with error code 14347 (AWS_ERROR_S3_CANCELED).
Nov 21 14:56:16 ip-10-231-0-5 mount-s3[387334]: [ERROR] awscrt::S3MetaRequest: id=0x7f383801b160 Meta request cannot recover from error 14347 (Request successfully cancelled). (request=0x7f385c06d530, response status=0)
Nov 21 14:56:16 ip-10-231-0-5 mount-s3[387334]: [INFO] awscrt::http-connection: id=0x7f385c06c290: Shutting down connection with error code 0 (AWS_ERROR_SUCCESS).
Nov 21 14:56:16 ip-10-231-0-5 mount-s3[387334]: [INFO] awscrt::http-connection: 0x7f385c06c290: Client shutdown completed with error 14347 (AWS_ERROR_S3_CANCELED).
The text was updated successfully, but these errors were encountered:
Hi @JamesUoM, I haven't looked at createrepo in detail, but I suspect it is trying to perform some operation that is not supported by Mountpoint (see semantics doc), most likely writing out of order. If that is the case, you should be able to verify it from the logs. You can see some examples in the troubleshooting doc.
Mountpoint for Amazon S3 version
mount-s3 1.10.0
AWS Region
eu-west-2
Describe the running environment
ec2 with profile to allow access to s3 bucket running alma8
Mountpoint options
mount-s3 --allow-other --allow-overwrite --allow-delete --uid ### --gid ## bucket /var/www/bucket
What happened?
Using s3 to host RPM repo. I was using s3fs without any problems previously
Relevant log output
The text was updated successfully, but these errors were encountered: