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

Starting a server does not work #30328

Closed
kix opened this issue Feb 21, 2019 · 6 comments

Comments

@kix
Copy link
Contributor

commented Feb 21, 2019

Symfony version(s) affected: 4.2.*

Description
Server does not start in a new Symfony project.

How to reproduce

  1. $ php -vPHP 7.3.1 (cli) (built: Jan 10 2019 13:15:37) ( NTS )
  2. $ composer create-project symfony/website-skeleton server-poc
  3. $ cd server-poc && bin/console server:start yields:
bin/console server:start -vvv
10:55:07 DEBUG     [php] Warning: fsockopen(): unable to connect to 127.0.0.1:8001 (Connection refused)
[
  "exception" => Symfony\Component\Debug\Exception\SilencedErrorContext {
    +count: 1
    -severity: E_WARNING
    trace: {
      ./vendor/symfony/web-server-bundle/WebServerConfig.php:139 { …}
      ./vendor/symfony/web-server-bundle/WebServerConfig.php:54 { …}
    }
  }
]

...and no server is running on port 8001. bin/console server:run works, though

@ismail1432

This comment has been minimized.

Copy link
Contributor

commented Feb 22, 2019

It works with php 7.2.1 did you try with an upper PHP version ?

@kix

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

@ismail1432, PHP version affected is 7.3.1

@kix

This comment has been minimized.

Copy link
Contributor Author

commented Mar 6, 2019

I'm using macOS Mojave with Homebrew-installed PHP 7.3.1, and that is the real cause of the problem.

After an investigation, I came to a conclusion this is related to the segfaults reported here: bobthecow/psysh#540 (comment)
Here's an issue in Homebrew-core: Homebrew/homebrew-core#35491

A temporary workaround would be setting pcre.jit=0 in php.ini

@xabbuh

This comment has been minimized.

Copy link
Member

commented Mar 6, 2019

Does it mean this has to be fixed on the PHP side? Can the issue be closed then?

@kix

This comment has been minimized.

Copy link
Contributor Author

commented Mar 6, 2019

I guess so. It's not like we could skip PCRE at all, as Psysh maintainers have done.

@itsjavi

This comment has been minimized.

Copy link

commented Jul 10, 2019

@kix disabling pcre JIT made the trick. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.