Fixing MySQL replication that is stuck

If your MySQL replication is stuck for example on
(or few others) because for example for the tables that already exist on the slave, there’s quick fix that can be applied on MySQL slave:
This will force slave to skip one command (that is causing it to stop) and then replication is started back again.
Depending on the root cause of the problem of stopped replication there are other solutions – but this works in the case described above.

Attaching to BOINC project from Linux console

So my AWS EC2 free instance is running, for now I’ll use it as a Boinc maching, what is boinc?
The Berkeley Open Infrastructure for Network Computing (BOINC) is an open sourcemiddleware system for volunteer and grid computing. It was originally developed to support the [email protected] project before it became useful as a platform for other distributed applications in areas as diverse as mathematics, medicine, molecular biology, climatology, and astrophysics. The intent of BOINC is to make it possible for researchers to tap into the enormous processing power of personal computers around the world.
I try to put it everywhere I can, and I have figured out few simple steps to get it working.
  1. <span style=“line-height: 14px;”>Install boinc on your server: apt-get install boinc-client (This works for Ubuntu / Debian)</span>
  2. Attach to boinc project, in my case: boinccmd  –project_attach ac33820b6d74de35682d2ad98e7cede ( Your project key will be different)
  3. Add this entry to crontab (I have noticed that boinc process sometimes stops):
  4. 0 1 * * * root /etc/init.d/boinc-client restart