(What happen to) Intra-day Logs File (Delivery)

Dear Staff,
I joined/activated my (S3STAT) account at 05-13 afternoon (3:20pm). I was able to see partial report on 05-14 moring. But I am not able to see the intra-day log files anymore. Here is screen shot of log directory:

http://s3.amazonaws.com/Tentoe-Stage/log/S3-Log.jpg

I could not see any log file on or after 4:36pm (PST) on 05-13 and non of intra-day log files for today (05-14).

Your assitance is greatly appreciated.

sp-eng
Wednesday, May 14, 2008




It looks like you've changed the access control list for that log bucket so that the LogDelivery group no longer has access (and thus can't deliver logfiles). Likely you didn't do it intentionally, since there are a few tools (S3fox being the most visible) that will clobber your LogDelivery ACL settings by default.

I'd be happy to fix this for you from our side. Alternately, you can modify the bucket's ACL directly or do it from S3stat by disabling/re-enabling log delivery from your My Account page.

Jason

Jason
Thursday, May 15, 2008




That's too bad we lose one day worth of logs (600MB). I do use S3Fox (Firefox Plug-in) a lot but I have never experienced ACL attributes got modified by S3Fox. BTW, I have also been using S3Backup Windows application. Anyway, I would be watching logs file more closely to make sure they are delivered routinely.

I also learned S3STAT does NOT process old log files that are stored in the same log directory which S3STAT is accessing to and from. Our account was created on 05-13 and I uploaded gigabytes of logs from 05-10 to 05-12 to the S3STAT log location.

sp-eng
Thursday, May 15, 2008




We've sent bug reports to the S3fox team, complete with steps-to-reproduce this issue, but so far haven't heard back from them. In the most common case, that tool will rename READ_ACP permissions to READ.

Another possible culprit is the RightAWS ruby library, which will reset permissions entirely if you open a bucket for reading in the wrong manner.

Regardless, it looks like you've done the necessary fixes from your end, since I'm seeing new logfiles present in your bucket today.

I'd be happy to do a historical run of your logs if you'd like. Go ahead and drop those old logfiles back into the /log/ folder. Let me know when they're there (and how far back they go) and I'll run a script to bring you up to speed.

Jason

Jason
Thursday, May 15, 2008




Dear Staff,
Our log file delivery got stopped again on Friday (morning). Is it possible to have log file delivered to separated bucket? I have been using S3Fox for over 1 year and it has never 'massed' with ACL of existing buckets/keys/objects. Before I joined/activated S3STAT, our logs files were delivered to a separated bucket (SellPointLog). We could not afford to lose anymore logs...

sp-eng
Friday, May 16, 2008




Sorry to hear that. I'm afraid that there's not much that we can do from our end to help you. We don't have the capability to report on logs delivered to custom bucket names.

The S3fox problem happens when you change the ACL on a bucket that has a permision set to READ_ACP. Evidently, S3fox does not recognize that setting, so it changes it to READ when it saves an ACL for that bucket. You can try it yourself to confirm that this happens.

The solution, it would seem, would be to set the permissions to that bucket manually (through some other tool), and then leave them alone.

Anyway, I apologize again for the inconvenience you've had this week. If you absolutely need a solution that allows reporting on custom buckets, I'd be happy to discuss a consulting arrangement. Please send an email to info@s3stat.com if you are interested.

Jason
Friday, May 16, 2008




Hi Jason,
I have observed log files delivery were stopped right after S3STAT finished combining intra-day logs into one single log for the day:

http://s3.amazonaws.com/Tentoe-Stage/log/Capture_S3_Log.jpg

S3STAT finished its job at around 1:45am(PST) (http://s3.amazonaws.com/Tentoe-Stage/log/ex080516.log). I checked the log files around 3:35am and I did NOT see any log files delivered after 1:45am. I (re-)enabled logging and started to see log files after 3:45am.

Thanks for your help.

sp-eng
Saturday, May 17, 2008




Strange. The screenshot you've attached shows log delivery stopping at 3pm the day before S3stat ran. I'd suggest you look for activity that might have touched your bucket around that time. Regardless, we don't modify ACLs or log delivery settings except when you request it through the bucket setup utilities.

If you still can't track down why log delivery is stopping at your end, you might want to post a message in Amazon's S3 developer forums. Amazon is very responsive to issues like this, and they may be able to offer some insight into why you are seeing problems with your logs.

Jason
Sunday, May 18, 2008




Hi Jason,
Thanks for your reply. I have sent email to info@expatsoftware.com.

sp-eng
Sunday, May 18, 2008

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

© 2021 Expat Software Back to Top