paying client, but stats stopped a month ago

I'm a paying client. However my stats stopped in November. I have not received a response from my last message. Please have my stats restarted as soon as possible. Whatever the payments are, I will make them, but I don't want days missing or holes in the stats because my advertisers need reliable data.
Thanks you for your understanding.
Mike Campbell

Mike Campbell
Sunday, December 21, 2008

Strange. I did some research into your account, and your logs did stop arriving from Amazon on the 26th. Stranger still, checking your logging status and Access Control Policy, I don't see anything wrong with them. There should be nothing stopping logs from being delivered, yet they are stopped.

I would recommend that you post a request in the AWS S3 forum ( ) to see if you can get somebody from Amazon to look into this. Here is the information you'll need.

The Bucket Logging Status:

[BucketLoggingStatus xmlns="">[LoggingEnabled>[TargetBucket>glossika[/TargetBucket>[TargetPrefix>log/access_log-[/TargetPrefix>[/LoggingEnabled>[/BucketLoggingStatus>

The Access Control Policy for the bucket:

[AccessControlPolicy xmlns="">[Owner>[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Owner>[AccessControlList>[Grant>[Grantee xmlns:xsi="" xsi:type="CanonicalUser">[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Grantee>[Permission>FULL_CONTROL[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="CanonicalUser">[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Grantee>[Permission>WRITE_ACP[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="CanonicalUser">[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Grantee>[Permission>READ_ACP[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="CanonicalUser">[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Grantee>[Permission>WRITE[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="Group">[URI>[/URI>[/Grantee>[Permission>READ[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="CanonicalUser">[ID>6500e3932dd9dd8f57214a26adf0193fc6d1abd3dd202afc34862bb1196cf88c[/ID>[DisplayName>jackdkorea[/DisplayName>[/Grantee>[Permission>READ[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="Group">[URI>[/URI>[/Grantee>[Permission>WRITE[/Permission>[/Grant>[Grant>[Grantee xmlns:xsi="" xsi:type="Group">[URI>[/URI>[/Grantee>[Permission>READ_ACP[/Permission>[/Grant>[/AccessControlList>[/AccessControlPolicy>

I wish there was more that we could do from our end, but at the moment it seems to be an issue with S3.

Keep me posted with what you find out.

Sunday, December 21, 2008

After re-reading the message I sent you, I think I see the problem.

It looks like somebody has modified the BucketLoggingStatus for that bucket. If you look, you'll see that it's sent to deliver logfiles to a bucket called "glossika" rather than "". If you look in that "glossika" bucket, you'll find that the logfiles are indeed there.

If you'd like, I can access your S3 bucket manually and copy those files over to the correct bucket. From there, I could run a historical job to bring your reports up to date.

I make a point of not touching a customer bucket without explicit permission, so please let me know how you'd like to proceed.


Monday, December 22, 2008

[ reply to this topic ]   [ return to topic list ]

© 2023 Expat Software Back to Top