title: fabric appears to start apache2 but doesn't
body: <p>I'm using fabric to remotely start a micro aws server, install git and a git repository, adjust apache config and then restart the server.</p>
  
  <p>If at any point, from the fabfile I issue either</p>
  
  <p><code>sudo('service apache2 restart')</code> or <code>run('sudo service apache2 restart')</code> or a stop and then a start, the command apparently runs, I get the response indicating apache has started, for example</p>
  
  <pre><code>[ec2-184-73-1-113.compute-1.amazonaws.com] sudo: service apache2 start
  [ec2-184-73-1-113.compute-1.amazonaws.com] out:  * Starting web server apache2
  [ec2-184-73-1-113.compute-1.amazonaws.com] out:    ...done.
  [ec2-184-73-1-113.compute-1.amazonaws.com] out: 
  </code></pre>
  
  <p>However, if I try to connect, the connection is refused and if I ssh into the server and run 
  <code>sudo service apache2 status</code> it says that "<code>Apache is NOT running</code>"</p>
  
  <p>Whilst sshed in, if run 
  <code>sudo service apache start</code>, the server is started and I can connect. Has anyone else experienced this? Or does anyone have any tips as to where I could look, in log files etc to work out what has happened. There is nothing in <code>apache2/error.log</code>, <code>syslog</code> or <code>auth.log</code>.</p>
  
  <p>It's not that big a deal, I can work round it. I just don't like such silent failures.</p>