8000 [FrameworkBundle][Process] server:run command exits after reload · Issue #20580 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

[FrameworkBundle][Process] server:run command exits after reload #20580

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.

Sign up for GitHub

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

Jump to bottom
Closed
derrabus opened this issue Nov 21, 2016 · 11 comments
Closed

[FrameworkBundle][Process] server:run command exits after reload #20580

derrabus opened this issue Nov 21, 2016 · 11 comments
Labels
Bug FrameworkBundle Process Unconfirmed

Comments

@derrabus
Copy link
Member

How to reproduce:

  • Check out the 3.2 branch of the symfony-standard repository
  • Update the vendors. (Symfony is at 2094715)
  • Run bin/console server:run
  • Point the browser to http://localhost.8000/
  • Hit reload.

If I do this, the command exits with the following output:

$ ./bin/console server:run -vvv
[2016-11-21 14:33:28] php.DEBUG: Warning: fsockopen(): unable to connect to 127.0.0.1:8000 (Connection refused) {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\SilencedErrorContext: {\"severity\":2,\"file\":\"/Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Command/ServerCommand.php\",\"line\":59})"}


 [OK] Server running on http://127.0.0.1:8000


 // Quit the server with CONTROL-C.

PHP 7.1.0RC6 Development Server started at Mon Nov 21 15:33:28 2016
Listening on http://127.0.0.1:8000
Document root is /Users/rabus/PhpstormProjects/symfony-standard/web
Press Ctrl-C to quit.
[Mon Nov 21 15:33:45 2016] 127.0.0.1:50789 [200]: /
[Mon Nov 21 15:33:46 2016] 127.0.0.1:50790 [200]: /_wdt/a92140
[Mon Nov 21 15:33:46 2016] 127.0.0.1:50791 [200]: /favicon.ico


  [Symfony\Component\Process\Exception\RuntimeException]
  The process has been signaled with signal "11".


Exception trace:
 () at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Process/Process.php:396
 Symfony\Component\Process\Process->wait() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Process/Process.php:210
 Symfony\Component\Process\Process->run() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Command/ServerRunCommand.php:135
 Symfony\Bundle\FrameworkBundle\Command\ServerRunCommand->execute() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Console/Command/Command.php:255
 Symfony\Component\Console\Command\Command->run() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:846
 Symfony\Component\Console\Application->doRunCommand() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:191
 Symfony\Component\Console\Application->doRun() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Console/Application.php:80
 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at /Users/rabus/PhpstormProjects/symfony-standard/vendor/symfony/symfony/src/Symfony/Component/Console/Application.php:122
 Symfony\Component\Console\Application->run() at /Users/rabus/PhpstormProjects/symfony-standard/bin/console:28

server:run [-p|--port PORT] [-d|--docroot DOCROOT] [-r|--router ROUTER] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command> [<address>]

If I downgrade Symfony to 3.1.6, everything's fine.

Environment: macOS 10.11.6, php 7.1 RC6
@fabpot
Copy link
Member
fabpot commented Nov 21, 2016

I think that this is a bug in PHP 7.1. I had the same issue and downgrading to PHP 7.0 fixed the issue.

@derrabus derrabus mentioned this issue Nov 21, 2016
Closed
@derrabus
Copy link
Member Author

I can confirm, that the issue is gone after switching to php 7.0.13.

@fabpot
Copy link
Member
fabpot commented Nov 21, 2016

Can you report this issue to PHP? And close this issue then.

@derrabus
Copy link
Member Author

https://bugs.php.net/73575

@derrabus
Copy link
Member Author

@fabpot You said, you could reproduce the problem as well? Did you also use the php packages from Homebrew? The thing is, if I force Homebrew to build php 7.1 RC6 from source, the problem is gone as well. As soon as I reinstall their binaries, the segfault is back.

@fabpot
Copy link
Member
fabpot commented Nov 22, 2016

Indeed, I installed PHP 7.1 via homebrew.

@alcaeus
Copy link
Contributor
alcaeus commented Nov 28, 2016

@derrabus if the problem only occurs when downloading binaries from homebrew-php, this could be fixed by recompiling the bottles. You could create a ticket at homebrew/homebrew-php for this.

@derrabus
Copy link
Member Author
derrabus commented Dec 3, 2016

The problem seems to be gone with Homebrew's php 7.1.0 binaries.

@fabpot
Copy link
Member
fabpot commented Dec 3, 2016

Great news!

@xiangjihan
Copy link

@derrabus Is my issue same as yours?
#20988

@derrabus
Copy link
Member Author

@xiangjihan I don't think so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug FrameworkBundle Process Unconfirmed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fabpot @javiereguiluz @alcaeus @derrabus @xiangjihan
0