# Vagrant based server failing on db:migrate

**URL:** <https://meta.discourse.org/t/vagrant-based-server-failing-on-db-migrate/34566>\
**Category:** Bug\
**Created:** [15. Oktober 2015 um 18:28 UTC](https://meta.discourse.org/t/vagrant-based-server-failing-on-db-migrate/34566 "2015-10-15T18:28:05Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [21. Oktober 2015 um 22:57 UTC](https://meta.discourse.org/t/vagrant-based-server-failing-on-db-migrate/34566/8 "2015-10-21T22:57:07Z")

</div>

I’ve tracked down the problem: the `rails_multisite` gem has restrictive permissions on some of the files, and so the vagrant user can’t read them (and hence can’t load the code).

While @sam is unavailable to make a new (fixed) release of `rails_multisite`, the simplest workaround is to run the following:

```
sudo chmod -R a+r /var/lib/gems/2.2.0/gems/rails_multisite-1.0.2

```

That’ll fix the permissions and you’ll be off and running.

---

_[View the full topic](https://meta.discourse.org/t/vagrant-based-server-failing-on-db-migrate/34566)._