BigGreenOgre

We are having a similar issue. Aptly has been in use for 2 years. We recently started testing using the API (with -no-lock) and are encountering this issue doing snapshot/db...

Looks like the db got corrupted yesterday, jobs failed overnight based on this error: `aptly@fulcrum-1:~$ aptly publish list ERROR: unable to load list of repos: snapshot with uuid 66ed3ea5-2931-4e91-8c8d-8a0f6255de0c not...

Note: Re:- "stale NFS file handle" messages The db is NOT on an NFS file system but on a GLUSTERFS file system with NFS specifically disabled. I don't think this...

I have not. I'm afraid I don;t have any experience with GO or how to build it. I also need the fix for the S3/MD5SUM issue. Is there a quick...

Our application is deployed as a group of containers that exist within an "appliance". The "appliance" could be a physical or virtual machine, local or remote, VmWare, KVM or any...

Thanks tylerjl, I have submitted an upstream bug report at https://github.com/elastic/elasticsearch/issues/27236 I will be out of town next week with limited access to email, apologies in advance if I'm slow...