Symfony 2 production env constant errors - symfony

I developed my Symfony 2.8 project locally on dev enviroment.
Than i needed to upload it to a server and run it on production.
I did all the steps:
1. Checked it out with git on the server
2. Ran composer install
3. Cleared cache, doctrine cache, installed the assets
4. Configured my database
Saying this ... I`m still getting problems like:
Internel server errors like
No route found for "GET ..
And for some reason it makes requests from time to time to app_dev.php - my ht access clearly states that directory index is app.php and etc
I get double template rendering - the same view is loaded two times - two menu section ... two content section
I am really frustrated, cause ive tried everything i know. Could someone help me, ill provide additional info if needed.
I need any suggestions, ideas and etc that could help me.
My .htaccess file - http://pastebin.com/4XHetMPV

First, try to remove your cache manually and clean your logs :
rm -rf app/cache/* && rm app/logs/prod.log
Then, try to browse a route of your application.
If you still have an error, open your log using cat app/logs/prod.log and find the last error.
If it's a php error caused by a vendor, remove your /vendor directory and run composer update
If you are not able to fix your problem, add to your question the error log and code of the method called by your route that is not working.

As chalasr said, cleaning prod cache manually works after the app.php setup.
I think a command like :
php app/console cache:clear --env=prod --no-debug
should work too.

Related

Symfony - botched project with cache:clear

I have a little problem concerning cache:clear following a tutorial that told me if I have an error while running the command, I could delete the dev folder by hand in var/cache/dev
So when running the command to clear the cache, I got this error:
[Symfony\Component\Filesystem\Exception\IOException]
Failed to remove file "/var/www/html/Symfony/var/cache/de~/profiler/26/75/2d7526":
So as the error appeared I decided to delete the dev folder in /var/dev
But then I couldn't go anymore on my browser checking if everything worked fine. This error came up.
RuntimeException in ClassCollectionLoader.php line 309: Failed to write cache file "/var/www/html/Symfony/var/cache/dev/classes.php".
I have no idea as how to make it work again.
My dev and prod cache folders are back in my cache folder as expected, but that doesn't do anything. It won't work anymore.
So I'm a bit desperate.
Have you setup correctly the file permissions for the var folder?
See this link: http://symfony.com/doc/current/setup/file_permissions.html

How to permanently resolve Symfony2 twig_upper_filter error?

Situation:
Production mode
Change a file
One of the pages on the site returns the following 500 internal error.
Run composer update, and the error goes away.
Change a file and the problem returns.
The code calling the twig_upper_filter is buried deep inside the now embedded in symfony bootstrap templates.
What does composer update do that might fix this? It is repeatable (on one server only).
UndefinedFunctionException: "Attempted to call function
"twig_upper_filter" from the global namespace." at
Symfony 2.6.
Because at the end of composer update it does a cache clear, everytime you change something somewhere you need to clear the cache for the change to be visible in the production enviroment.
This is automatic on the development enviroment.
You need to run this from console:
cd /your/symfony/app
php ./app/console cache:clear --env=prod
Letting the web server build the cache resolved the problem. The command line environment must not be exactly the same as the web server php. On this server it is difficult to actually run command line scripts as the web server user.
Therefore, clearing the cache on the command line with no warmup is the work around:
php ./app/console cache:clear --no-warmup --env=prod

I cannot clear the cache (because the cache is outdated)

Trying to deploy my updated Symfony2 application, I ran into the following problem.
(note that my application uses the new Symfony 3 directory structure. replace bin/console with app/console and var/cache with app/cache if you're using the current directory structure)
I have recently renamed one of my service classes (VariantSlugListener). When deploying the application on the staging server, I got the following error when running bin/console assetic:dump --env=prod:
PHP Fatal error: Class 'MyBundle\Listener\VariantSlugListener' not
found in
/var/www/example.com/staging/var/cache/prod/appProdProjectContainer.php
on line 494
Line 494 of appProdProjectContainer.php contains the following code:
return $this->services['3f288d4f09c9906944ba7e17358f669b942397baf9d79d5ff0737bb756df7023_1'] = new \MyBundle\Listener\VariantSlugListener();
It is no surprise that \MyBundle\Listener\VariantSlugListener can not be found, since it has been renamed to \MyBundle\EventListener\VariantSlugSubscriber with the latest update. The solution would be to simply clear Symfony's cache.
However, when trying to clear the cache (using bin/console cache:clear --env=prod) I get the exact same error as with the assetic:dump command. So I get an error because my Symfony cache is outdated, but I can not clear the cache because of the error.
I can probably get around this by manually deleting the contents of the var/cache directory, but that doesn't feel like the best solution.
Am I missing something?
Probably you are triggering some events that are handled in your VariantSlugListener when doing 'cache:clear'. So your only choice is to just remove contents of the cache directory or to replace the value manually and then run cache:clear to warm up the cache.

Cannot access Sylius admin or view styled login, register or account pages

I'm looking to use Sylius for a new e-commerce site and wanted to have a play around first as it looks awesome but after installing all seems to work well on the front end but as soon as I view the login or register page, any kind of template or styling is missing. In fact there are no stylesheets or Javascript files set. All that appears are the raw unstyled forms and literally nothing else.
If I try to log in using the credentials at the end of the app/console sylius:install step, I receive the following error:
"An exception has been thrown during the rendering of a template ("None of the chained routers were able to generate route: Route 'cmf_create_put_document_base' not found") in CmfCreateBundle::includejsfiles-create.html.twig at line 17.”
If I complete an order as a new customer and then view my account all I see printed to my screen is who I’m logged in as together with my username and email address and a logout link. That’s it.
Given I’ve had a play with the demo at http://demo.sylius.org/ this is not how I see it working.
If I grep the dev.log file, I find the following errors in addition to the one mentioned above:
[2014-12-11 10:07:29] assetic.ERROR: The template "CmfCreateBundle::includejsfiles-hallo-coffee.html.twig" contains an error: Unable to find file "#CmfCreateBundle/Resources/public/vendor/hallo/src/hallo.coffee". [] []
[2014-12-11 10:07:29] assetic.ERROR: The template "CmfCreateBundle::includejsfiles-ckeditor.html.twig" contains an error: Unable to find file "#CmfCreateBundle/Resources/public/vendor/ckeditor/ckeditor.js". [] []
If I look for the paths #CmfCreateBundle/Resources/public/vendor/hallo/src/hallo.coffee or #CmfCreateBundle/Resources/public/vendor/ckeditor/ckeditor.js I can verify they don’t exist in the vendor/symfony-cmf/create-bundle/Resources/public/vendor/ directory.
Install steps are:
composer create-project -s dev sylius/sylius-standard:v0.11.0 www, also tried composer
create-project -s dev sylius/sylius-standard www
cd www
chmod -R 775 web/media/ app/cache app/logs
chmod 664 app/configs/parameters.yml
composer run-script post-install-cmd as step 1 fails when trying to clear cache
app/console sylius:install with fixtures added
Of note, I’ve tried installing on VMWare (Ubuntu 12.04, PHP5.5) and an Amazon EC2 instance (Ubuntu 14.04, PHP5.6) and while I’m familiar with PHP and ZF2, I have zero Symfony 2 or Sylius experience.
Thanks in advance
I also just experienced this issue. To resolve it, simply add the following line to app/config/routing.yml:
symfony_cmf:
resource: #CmfCreateBundle/Resources/config/routing/rest_no_locale.xml
I'm investigating why the install didn't take care of this.
Although I couldn't get v0.11 working to get to the backend, installing v0.12, which was has just been released has resolved the issue. See more at http://sylius.org/blog/sylius-0-12-0-with-faceted-search.
Did you follow the steps here:
http://symfony.com/doc/current/cmf/bundles/create/introduction.html#installation
I followed #avolkman trick with adding a routing rule:
symfony_cmf:
resource: #CmfCreateBundle/Resources/config/routing/rest_no_locale.xml
But this only fixed problem with missing js files but not fixed problem with missing template on login page.
I'm using new version 0.12 (Sylius Standard) and still have this issue.
To solve the error :
php app/console cmf:create:init-hallo-devel
clear the cache or remove it as usual
php app/console ca:c --env=prod and php app/console ca:c
rebuild assets (you'll see now hallo-coffee.js)
php app/console assetic:dump --env=prod --no-debug
Done ! No more errors

Symfony2 Composer Install

I am trying to install Symfony 2.1.3 (latest). I am running composer and installs everything okay. The only error that I get is:
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache
handling the post-install-cmd event terminated with an exception
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'" command.
It's being installed under www folder. I am running nginx and followed the composer approach. I read on internet that apache should be run manually not as a service, however I am using nginx instead. Does apache still have any bearing on it? I'm using debian squeeze.
Edit: As per AdrienBrault's suggestion the error was because the timezone was not set in the php.ini. Only with --verbose I could see the warning. Thanks guys.
Apache is not related - PHP is called via command line.
Most likely is the permission in the cache folder: did you check if the user that runs the composer update can actually write the cache folder?
Try to manually run rm -Rf app/cache/dev (for production environment replace dev with prod) and see if you get any permission error.
Also you will get this error if the default.timezone setting is not configured in php when running in CLI. To verify just run
php --info | grep timezone
and check that the setting date.timezone is correctly configured.
On the security side, setting 777 to the folder is not the optimal solution - if you have ACL enabled you could use that to correctly set up the permission for the cache and logs folder. Read more at the Symfony2 official installation page
I had this same issue for a while and after hours of face to brick wall pounding I realized... I have a .gitmodule in my project, and on initial checkout these submodules are NOT initialized and as such are not there for your composer to update, which results in the above error.
Make sure you run the following
git submodule update --init src/Acme/Sadness/Bundle
of course replace src/Acme/Sadness/Bundle with YOUR project namespace.
Hope this helps someone not go through the same pain I just did.
If you have vendor folder already I would remove it and install symfony 2.1.3 again via "composer.phar install". Problem might be coming from outdated version of composer
I had the same problem and I resolve in this way.
execute this on the console
and you should see something like this
$ locate php.ini
/etc/php5/apache2/php.ini
/etc/php5/cli/php.ini
/etc/php5/fpm/php.ini
the first line is probably your php.ini that appear when you do a phpinfo();
the problem is that when you execute composer update this no check the same php.ini
in my case the second line
all my sites work fine but always I had problems not now
after edit the second file and put the same time zone that you set in the first one
run
$ sudo service apache2 reload
and now
$ composer update
I hope that this work for you like work for me
regards
Emiliano

Resources