title: Trouble with errors in local Sugar instance
body: <p>I'm having a problem with setting up a local Sugar instance on localhost in a vagrant VM. I created a local host instance from a backup file, which worked well the first time I tried it. But, after restarting vagrant about two weeks later, I get an empty grey screen and an error in the PHP log:</p>
  
  <pre><code>PHP Fatal error: Uncaught Error: Class 'Ramsey\\Uuid\\Uuid' not found in /vagrant/src/Cache/Middleware/MultiTenant/KeyStorage/Configuration.php:44
  </code></pre>
  
  <p>I deleted this instance and created another one from a different backup file. Again, it worked well initially. But after restarting vagrant today, I got the same error. This time, I looked into this error in more detail and managed to fix it by changing the use statement in <code>Cache/Middleware/MultiTenant/KeyStorage/Configuration.php</code> to "<code>use Rhumsaa\Uuid\Uuid</code>" (<a href="https://github.com/ramsey/uuid/issues/217" rel="nofollow noreferrer">https://github.com/ramsey/uuid/issues/217</a>). But now I'm getting a new error: </p>
  
  <pre><code>Uncaught Error: Class 'LoggerManager' not found in /vagrant/include/entryPoint.php:121\nStack trace:\n#0 /vagrant/index.php(17): require_once()\n#1 {main}\n thrown in /vagrant/include/entryPoint.php on line 121
  </code></pre>
  
  <p>This leads to 3 issues that confuse me at this point:</p>
  
  <p>1) Why is this error thrown when a <code>LoggerManager</code> class does exist in <code>include/SugarLogger/LoggerManager.php</code>?</p>
  
  <p>2) It seems that there is a more fundamental problem with this instance that prevents it from finding existing classes. I was thinking it might be a permissions issue and ran the <a href="https://support.sugarcrm.com/Knowledge_Base/Platform_Management/Required_File_System_Permissions_on_Linux/#Setting_Permissions_Via_Command_Line" rel="nofollow noreferrer">commands</a> to set the required permissions (using vagrant:vagrant instead of apache:apache), but it had no effect on the error. What else can I try to troubleshoot this?</p>
  
  <p>3) Why did this instance work well initially and started throwing errors after restarting vagrant?</p>
  
  <p>Thank you for any help!</p>