StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19307119
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-10-10T22:11:19.237
FavoriteCount
0
LastActivityDate
2013-10-11T17:28:43.787
LastEditDate
2013-10-11T17:28:43.787
LastEditorUserId
1260322
OwnerUserId
1260322
ParentId
19307056
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<p>Basically you need to handle STDERR in the same way as STDOUT.</p> <h2>Pipe it in cron</h2> <pre><code>0 0 * * * (/usr/bin/time /path/to/mysqlbackup.sh 2&>1) | /bin/mail -s "MySQL Backup" "admin@example.com" </code></pre> <p>This works on Ubuntu, you reported it doesn't work for you (empty mail body). I'd be interested to dig into that so more, but in the meantime...</p> <h2>Adjust your script</h2> <p>You can make your script only print to STDOUT by redirecting STDERR (at least for that one command to STDOUT)</p> <pre><code>echo "Starting backup at $(date)" mysql -u potato -e "show status" 2>&1 # produces error we want, so redirect it FILE="/path/to/file.bak" FILESIZE=`du -h $FILE | cut -f1` echo $FILESIZE </code></pre> <p>If you want any error in your script to be sent to STDOUT, you can globally redirect STDERR to STDOUT by adding this at the top of your script:</p> <pre><code>exec 2>&1 </code></pre> <h3>Toy example</h3> <p><code>job.sh</code> </p> <pre><code>#prints out to STDOUT and STDERR echo good echo error >&2 echo good </code></pre> <p><code>script.sh</code></p> <pre><code>#this runs job.sh redirecting STDERR to STDOUT sh job.sh 2>&1 </code></pre> <p>Now running job.sh, with various redirections shows its printing to STDOUT and STDERR</p> <pre><code>$sh job.sh > /dev/null error $sh job.sh 2> /dev/null good good </code></pre> <p>running script.sh shows its only printing to STDOUT even though job.sh is printing to STDERR</p> <pre><code>$sh script.sh > /dev/null $sh script.sh 2> /dev/null good error good </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPipe cronjob errors to mail
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAmir T
UserOwnerUserId
1. USAmir T
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPipe cronjob errors to mail
  singulars
  PostTypePostTypeId
  PTQuestion
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
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId

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.