php artisan optimize times out only on composer install

Question

I'm running a laravel app on Azure. Things are moving in the right direction, composer install didn't use to work at all. Now however, the "php artisan optimize" command times out:

However, running "php artisan optimize" separately is no problem at all:

What could be the cause of this?

Edit:

Deleting the symfony-folder does not help, it is not present when I run the "Composer install"-command:

Increasing the timeout-limit does not help either, I increased it in both azure and in the composer.json file:

This still gives me a timeout, after installing the symfony-components again:

...

You could try increasing the timeout see http://stackoverflow.com/questions/18917768/why-composer-install-timeouts-after-300-seconds this may not be a solution but would be interesting to see if given more time does it actually complete or is it juts totally stuck. — Mark Davidson, Jan 21 '16 at 16:30
http://laravel.io/forum/09-15-2015-azure-webapps-laravel-5111-composer-install-fails looks like other people have encountered this before. — Mark Davidson, Jan 21 '16 at 16:33
Yes sorry, I should have mentioned that I have already tried this. I'm getting screenshots right now, just a sec. — Rkey, Jan 22 '16 at 08:23
Ok, currently waiting for the "Timed out after 2000 seconds"-message, it'll take some time X) — Rkey, Jan 22 '16 at 08:54

score 1 · Answer 1 · answered Jan 22 '16 at 03:05

As I deployed a new clean Laravel 5 application to Azure Web apps and tried to reproduce your issue, however, it worked fine on my side either I run the command php artisan optimize or composer install or composer update.

I installed the composer at the Site extensions at the KUDU console site of the application on Azure Web apps, the url should be like: https://<your_site_name>.scm.azurewebsites.net/SiteExtensions/#gallery

There are several solutions of other developers who occur the same issue with you, you can try these solutions:

try to increase the max_execution_time or set the value to 0, refer to https://azure.microsoft.com/en-us/documentation/articles/web-sites-php-configure/#how-to-change-the-built-in-php-configurations to change the PHP build-in configurations on Azure Web Apps. And you can change the process-timeout in Composer.json file :

"config" : { "process-timeout": 0 }
deleted the entire Symfony folder and try again. As the comments at PHP Artisan Optimize - Timed out? #1050, it seems the symfony dependencies raise the issue.

Ah, a poorly phrased question by me, my apologies. I have already tried both these things, I'll upload screenshots of them. Just a sec. — Rkey, Jan 22 '16 at 08:23

score 0 · Answer 2 · edited Jun 20 '20 at 09:12

0

@Rkey, According to my experience, I think the issue is more related to the symphony version/configuration. I suggest you can remove/edit the symphony configuration from the composer.lock file (NOTE: please backup this file if you cannot success, you also can recovery your environment). And then you can run this "composer install".

After installed component, You can see an alert window which shows that

your session is timeout, please refresh your browser.

You can see this information because the server is in initialization process. Any concerns, please feel free to let me know.

edited Jun 20 '20 at 09:12

Community

1
1

answered Jan 25 '16 at 10:21

Will Shao - MSFT

1,189
7
14

You are likely on to something, but I don't understand what you mean with "remove/edit the symphony configuration from the composer.lock file". The composer.lock file is over 3000 lines long, do you perhaps mean the composer.json file? In either case, what parts of the composer.lock/composer.json file are you talking about? – Rkey Jan 25 '16 at 15:26
@Rkey, I just wants to update the symphony components . Could you please try to use "composer update symfony/symfony" to update your components? And then you can use the "composer install" command. – Will Shao - MSFT Jan 26 '16 at 07:06
If I am in /home/site and run "composer.phar update symfony/symfony" it just gives me "process [9476] terminated! Press ENTER to start a new cmd process." =/ – Rkey Jan 26 '16 at 08:55
@Rkey, I will dig into this issue and reply you later. – Will Shao - MSFT Jan 27 '16 at 06:49
@Rkey, I have post a reply for pointing out current fact, should you have any further concerns, please feel free to let us know. – Ming Xu - MSFT Jan 30 '16 at 03:48

cabs · Answer 3 · 2016-01-27T06:53:01.467

0

I'm also having this problem. Will upgrading the plan help?

According to this upgrading to S3 helps... I haven't tried it though... Let me know if it really works.

edited Jan 27 '16 at 06:53

answered Jan 27 '16 at 06:21

cabs

710
7
14

@Rkey any any update on this?... I meant did you manage to get this working? I'm having the same issue. – cabs Jan 27 '16 at 07:49
I am quite sure they had a different issue. If just upgrading to S3 would help, increasing the max time for the timeout should also help. Timing out after 2000 seconds shouldn't happen even with really poor processing power, and since I can run optimize freely outside of the "composer install" command something else should be the problem. – Rkey Jan 27 '16 at 14:52

score 0 · Answer 4 · answered Jan 30 '16 at 03:46

0

@Rkey & @cabs, per my understanding on this question, I wanna point out that Composer is not fully supported on Azure. The issue is that it’s using Taskkill command which is blocked on Azure. We are aware of this and please feel free to submit an idea or suggestion based on the experience with Azure at https://feedback.azure.com/forums/34192--general-feedback.

answered Jan 30 '16 at 03:46

Ming Xu - MSFT

2,116
1
11
13

I'm even pretty sure I'm the one who pinpointed the problem that taskkill didn't work for Azure. I spent a couple of days with Azure support on that issue and I arrived at that conclusion and told them. However I think this might still be the answer. I think what happens is that optimize does finish, but the final step is to taskkill the installer. Since taskkill is blocked, the error message thinks we are still in optimize and says that's the operation that timed out – Rkey Feb 02 '16 at 09:48
Well I guess that sums it up for now then. There is no solution. – Rkey Feb 03 '16 at 09:20

score 0 · Answer 5 · answered Jan 28 '17 at 16:09

I have been stuck in this problem as well for a week. Have tried all solutions on forum but no success. This morning finally solved after reinstall XAMPP. It was problem on my previous PHP version 5.6.19. While using new XAMPP with PHP version 5.6.28, it worked fine.

php artisan optimize times out only on composer install

5 Answers5

Linked