StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12776381
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-08T06:29:26.173
FavoriteCount
0
LastActivityDate
2012-10-08T06:29:26.173
LastEditDate
LastEditorUserId
0
OwnerUserId
703144
ParentId
12114746
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Like others have mentioned, the problem appears to be your system running low on RAM and MySQL is blowing up due to that. Below is how to go about narrowing down where your system's memory is being used and how to recover from the database going down. Take a look at <a href="http://collectd.org/index.shtml" rel="nofollow">collectd</a> and its plugins. Some of the applicable ones may be the <a href="http://collectd.org/wiki/index.php/Plugin%3aProcesses" rel="nofollow">processes plugin</a> and the <a href="http://collectd.org/wiki/index.php/Plugin%3aMemory" rel="nofollow">memory plugin</a>. With those you can see your systems' memory usage and what processes are taking up most of it. Depending on how you are running Django, you can configure the worker processes to only process a certain number of requests and then terminate. That way if there is some sort of memory leak in your application it will not persist past that number of requests. For example, if you use <a href="http://gunicorn.org/" rel="nofollow">Gunicorn</a>, you can use the <a href="http://gunicorn.org/configure.html#max-requests" rel="nofollow">--max-requests</a> option. Setting it to 500 will drop the worker after it has processed 500 requests. The above combined with stats collection will show you some interesting memory usage trends. As for the database going down, you can setup process supervision so that if MySQL does die, it will be relaunched automatically. MySQL in latest version of Ubuntu uses Upstart to do just that. If the process dies, Upstart will bring it back up immediately. If you're using another distro that doesn't have this built-in, take a look at <a href="http://supervisord.org/" rel="nofollow">Supervisor</a>. While this doesn't fix the problem it will at least mitigate its effects. This should not be seen as the fix but rather a way to keep your application running in case something does go wrong.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmysqld service stops once a day on ec2 server
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USberto
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.