121 reputation
4
bio website
location
age
visits member for 5 years
seen Jul 15 at 14:03

Jul
27
comment DNS to an Amazon S3 bucket suddenly stopped working
Yes, the problem has somehow corrected itself.
Jul
27
comment DNS to an Amazon S3 bucket suddenly stopped working
I think the problem may be correcting itself because, although I still cannot reach the file, pingdom has stopped telling me the file is down and I found that I CAN reach the file if I go through a proxy.
Jul
27
comment DNS to an Amazon S3 bucket suddenly stopped working
I can possibly explain that. I first suspected that the DNS entry was somehow changed or corrupted. The zoneedit tool would not let me just republish the current definition. So I changed it to x.guiders.iguiders.com.s3.amazonaws.com, published, and then seconds later changed it back. Maybe the change back didn't make it to the second nameserver yet. In any case, the problem did not change in any way when I broke the DNS record or when I set it back. But your post did teach me a new tool, "dig"
Jul
27
asked DNS to an Amazon S3 bucket suddenly stopped working
Aug
15
comment Deleting MySQL rows causes lock table error
I ran your query and I got this result: innodb_buffer_pool_size 8388608. I assume that means I should not be having that problem right?
Aug
15
awarded  Student
Aug
13
awarded  Editor
Aug
13
revised Deleting MySQL rows causes lock table error
added 107 characters in body
Aug
13
comment Deleting MySQL rows causes lock table error
My config file doesn't have that constant in it. But if the file runs once, isn't that proof there's enough ram allocated?
Aug
13
asked Deleting MySQL rows causes lock table error
Jul
31
asked Created an EBS volume from a snapshot, but can't mount it?
Feb
17
awarded  Supporter
Jan
26
awarded  Tumbleweed