Why am I unable to find an object after a message that indicates that the object is uploaded is displayed?
Problem description
After a message that indicates that an object is uploaded, I cannot find the object in the bucket to which the object is uploaded.
Solution
Perform the following steps:
Check whether the
objectNameis valid. TheobjectName, which is the path of the object, must use a single forward slash (/) to separate path segments and must not start or end with a forward slash. If theobjectNamecontains consecutive forward slashes (//), such asabc//123.jpg, the object is uploaded successfully but appears in the OSS console as a hidden subfolder named/, so you cannot locate the object directly. If theobjectNameis invalid, change it to the standard format, such asabc/123.jpg, upload the object again, and then confirm that the object is visible in the object list in the OSS console.Enable logging for the bucket and check whether the object is uploaded based on the logs. For information about how to enable logging for a bucket, see Configure logging. If the object fails to be uploaded, troubleshoot the error based on the logs. Offline logs are delayed. If you want to use real-time logs, you must enable real-time logging. For information about how to enable real-time logging, see Query real-time logs.
If the error can be reproduced, you can capture the data packets that are generated when you upload the object and save the data packets as a pcapng file.
NoteYou must change an HTTPS endpoint to an HTTP endpoint because HTTPS packets are encrypted and cannot be decrypted.
If you use OSS SDKs to upload the object, you can print the ID of the request that is sent when you call an operation to upload the object.
Applicable scope
OSS