Symfony2 post-update-cmd gives "An error occurred when generating the bootstrap file"

Question

I am currently on Symfony2 2.3.7. When I run the composer update command. In the post-update-cmd a script is run to update symfony2. But it fails: ``` Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap handling the post-update-cmd event terminated with an exception [RuntimeException] An error occurred when generating the bootstrap file. update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-plugins] [--no-custom-installers] [--no-scripts] [--no-progress] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [packages1] ... [packagesN] ``` Any idea why this is happening? I tried to run: ``` composer update --no-scripts ``` .. and that runs fine. The following is also working fine: ``` php vendor/sensio/distribution-bundle/Sensio/Bundle/DistributionBundle/Resources/bin/build_bootstrap.php ``` But everytime I try the normal composer update the post script fails. Running the update with --verbose gives the follow…

Accepted Answer

How to solve install/update Symfony 2 issues

One important Symfony requirement is that the `app/cache` and `app/logs` directories must be writable both by the web server and the command line user.

On Linux and macOS systems, if your web server user is different from your command line user, you need to configure permissions properly to avoid issues. There are several ways to achieve that:

The most common solution :

In a terminal execute following commands :

```
rm -rf bin
rm -rf vendor
composer install
# or if your didn't install composer
php composer.phar install
```

It should work now! For more informations see Symfony installation.

If you still have this error : «`An error occurred when generating the bootstrap file`» It means that you have file permission issue. See below procedure for solve the problem ↓

Setting up or Fixing File Permissions :

In a terminal execute following commands :

```
rm -rf app/cache/*
rm -rf app/logs/*
```

On macOS systems, the `chmod` command supports the `+a` flag to define an ACL. Use the following script to determine your web server user and grant the needed permissions:

On most Linux and BSD distributions don't support `chmod +a`, but do support another utility called `setfacl`. You may need to install `setfacl` and enable ACL support on your disk partition before using it. Then, use the following script to determine your web server user and grant the needed permissions:

If none of the previous methods work for you

Change the umask so that the cache and log directories are group-writable or world-writable (depending if the web server user and the command line user are in the same group or not). To achieve this, put the following line at the beginning of the `app/console`, `web/app.php` and `web/app_dev.php` files:

```
umask(0002); // This will let the permissions be 0775
// or
umask(0000); // This will let the permissions be 0777
```

Note : Changing the umask is not thread-safe, so the ACL methods are recommended when they are available.

For more information see official documentation : Symfony file permissions

Symfony2 post-update-cmd gives "An error occurred when generating the bootstrap file"

Solution

Problem