Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck in Pending... #110

Closed
jbrooksuk opened this issue Oct 5, 2015 · 21 comments
Closed

Stuck in Pending... #110

jbrooksuk opened this issue Oct 5, 2015 · 21 comments
Labels

Comments

@jbrooksuk
Copy link
Contributor

I've upgraded to the latest master and now the jobs are stuck in pending. Logs seem to be fine.

@REBELinBLUE
Copy link
Owner

Hmm odd, investigating right now.

@REBELinBLUE
Copy link
Owner

OK I have not been able to recreate this so far. We had something similar happen at work on friday, but then turned out to be because beanstalkd died due to a lack of memory on the VM deployer was running on.

@jbrooksuk
Copy link
Contributor Author

Ah could be that. I'll take a look.

@REBELinBLUE
Copy link
Owner

I actually added a command to clean up the DB over the weekend php artisan deployer:cleanup so that new deployments can be queued

@jbrooksuk
Copy link
Contributor Author

I'll upgrade again and run that when I get a chance 👍

@REBELinBLUE
Copy link
Owner

👍

@REBELinBLUE
Copy link
Owner

And of course, now my latest deployment is doing the same thing

@jbrooksuk
Copy link
Contributor Author

Typical!

@REBELinBLUE
Copy link
Owner

Ah, just spotted something. I think it may be the broadcasting events, if I reload the deployment had actually run, did that happen for you?

@jbrooksuk
Copy link
Contributor Author

Looks like it.

@REBELinBLUE
Copy link
Owner

Ah, I think I've found the problem, can you take a look at .env and see SOCKET_URL I think it may have been reset, the previous config is in .env.prev

@REBELinBLUE REBELinBLUE added the Bug label Oct 5, 2015
@jbrooksuk
Copy link
Contributor Author

Nope, SOCKET_URL is fine.

@jbrooksuk
Copy link
Contributor Author

I've noticed that my .env was behind, so I've updated it.

@REBELinBLUE
Copy link
Owner

Did you run $ php artisan app:update? it adds any missing settings (although I am just thinking I should warn that a setting was missing/new so people are aware they might need to update it)

@jbrooksuk
Copy link
Contributor Author

app:update is not defined. Weird.

@REBELinBLUE
Copy link
Owner

😯 I assume app/Console/Commands/UpdateApp.php exists?

@jbrooksuk
Copy link
Contributor Author

PHP Parse error:  syntax error, unexpected '.', expecting ',' or ';' in /usr/share/nginx/html/app/Console/Commands/ClearStalledDeployment.php on line 29

@REBELinBLUE
Copy link
Owner

😕 Uh, OK now I'm very confused

vagrant@deployer:/var/www/deployer$ php -l app/Console/Commands/ClearStalledDeployment.php
No syntax errors detected in app/Console/Commands/ClearStalledDeployment.php

@jbrooksuk
Copy link
Contributor Author

I'm running PHP 5.5.9-ubuntu4.11 so it shouldn't be an issue...

@jbrooksuk
Copy link
Contributor Author

If I remove the concatenation of the $description variable, it's fine.

@REBELinBLUE
Copy link
Owner

Indeed with PHP 5.5.9-1ubuntu4.13 I get the same issue, turns out it is only supported in 5.6 https://bugs.php.net/bug.php?id=69343 so I've changed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants