reinstalled php 8.1 but always have the red cross in phpmon

[vdvcoder]

Hello,

I reinstalled PHP (brew install PHP (8.1.4)) but in phpmon it always shows the red cross.
Any ideas, what's wrong?
If I switch to php@8.0 or php@7.4 it's all checked.

Maybe a tip: adding a tooltip to those check/crosses to see what's wrong? Now, it doesn't say much what's good or not.

[nicoverbruggen]

Hi @vdvcoder!

Have you tried using First Aid & Services > Fix My Valet? This can fix issues that pop up after upgrading. You can also try Restart All Services under First Aid & Services.

If you see a red cross, that usually means that the service is not running or has failed to start correctly. Sometimes the service will be running but the process reports itself as in an "error" state, as well. In those cases, you'll see a red cross.

If you go into the terminal and run:

sudo brew services info php --json

Which should give you some output like this:

[
  {
    "name": "php",
    "service_name": "homebrew.mxcl.php",
    "running": true,
    "loaded": true,
    "schedulable": false,
    "pid": 150,
    "exit_code": 0,
    "user": "root",
    "status": "started",
    "file": "/Library/LaunchDaemons/homebrew.mxcl.php.plist",
    "command": "/opt/homebrew/opt/php/sbin/php-fpm --nodaemonize",
    "working_dir": "/opt/homebrew/var",
    "root_dir": null,
    "log_path": null,
    "error_log_path": "/opt/homebrew/var/log/php-fpm.log",
    "interval": null,
    "cron": null
  }
]

You should see more information about the service here, probably that it has failed to run correctly (under status).

One of the things you can investigate is error_log_path, which points to a file on your filesystem which might contain more information about why the service won't start/run correctly.

What version of Valet and PHP Monitor are you running, by the way?

Hope this helps!

[vdvcoder]

Hi @nicoverbruggen,

Sorry for the late response.

Versions:
Laravel Valet 3.1.2
PHP Monitor Version 5.2.1 (757)

This is the output for: sudo brew services info php --json

 {
    "name": "php",
    "service_name": "homebrew.mxcl.php",
    "running": false,
    "loaded": true,
    "schedulable": false,
    "pid": null,
    "exit_code": 19968,
    "user": "root",
    "status": "error",
    "file": "/Library/LaunchDaemons/homebrew.mxcl.php.plist",
    "command": "/opt/homebrew/opt/php/sbin/php-fpm --nodaemonize",
    "working_dir": "/opt/homebrew/var",
    "root_dir": null,
    "log_path": null,
    "error_log_path": "/opt/homebrew/var/log/php-fpm.log",
    "interval": null,
    "cron": null
  }

And the error_log_path:

...
[31-Jul-2021 10:44:50] NOTICE: [pool valet] child 43433 started
[31-Jul-2021 10:44:50] WARNING: [pool valet] child 43432 exited on signal 9 (SIGKILL) after 0.000206 seconds from start
...

Thank you!

Kind regards.

[nicoverbruggen]

Doesn't look like the log has anything useful in it (it's from last year).

What happens if you run sudo valet services restart php? Does that fix the issue?

[nicoverbruggen]

Hey @vdvcoder and @saineshmamgain (who confirmed he was seeing this too in #149)

I'm pushing out a new bugfix build soon, please check if it fixes this issue -- it might: https://github.com/nicoverbruggen/phpmon/files/8520621/phpmon-522.zip

You probably need to switch versions but after that the problem is hopefully fixed :)

Let me know if that helped!

[vdvcoder]

Hello @nicoverbruggen ,

Thank you! It works.

[nicoverbruggen]

Great to hear!

[vdvcoder]

Hey @nicoverbruggen since the latest update I got that red cross again for php8.1 (PHP)

sudo brew services info php --json
[
  {
    "name": "php",
    "service_name": "homebrew.mxcl.php",
    "running": true,
    "loaded": true,
    "schedulable": false,
    "pid": 96942,
    "exit_code": 19968,
    "user": "root",
    "status": "started",
    "file": "/Library/LaunchDaemons/homebrew.mxcl.php.plist",
    "command": "/opt/homebrew/opt/php/sbin/php-fpm --nodaemonize",
    "working_dir": "/opt/homebrew/var",
    "root_dir": null,
    "log_path": null,
    "error_log_path": "/opt/homebrew/var/log/php-fpm.log",
    "interval": null,
    "cron": null
  }
]

And the error path keeps adding new childs ...

[31-Jul-2021 10:41:55] WARNING: [pool valet] child 19880 exited on signal 9 (SIGKILL) after 0.000172 seconds from start
[31-Jul-2021 10:41:55] NOTICE: [pool valet] child 19882 started
[31-Jul-2021 10:41:55] WARNING: [pool valet] child 19881 exited on signal 9 (SIGKILL) after 0.000217 seconds from start
[31-Jul-2021 10:41:55] NOTICE: [pool valet] child 19883 started
[31-Jul-2021 10:41:55] WARNING: [pool valet] child 19882 exited on signal 9 (SIGKILL) after 0.000176 seconds from start
[31-Jul-2021 10:41:55] NOTICE: [pool valet] child 19884 started
[31-Jul-2021 10:41:55] WARNING: [pool valet] child 19883 exited on signal 9 (SIGKILL) after 0.000186 seconds from start
[31-Jul-2021 10:41:55] NOTICE: [pool valet] child 19885 started
[31-Jul-2021 10:41:55] WARNING: [pool valet] child 19884 exited on signal 9 (SIGKILL) after 0.000181 seconds from start
[31-Jul-2021 10:41:55] NOTICE: [pool valet] child 19886 started

Thanks in advance

[nicoverbruggen]

This is related to #173, I believe...

I'll see if I can't push out another bugfix update with a fix for that soon!

For now, switching PHP versions (and back) or running Fix My Valet should fix the problem, I think? Give that a try and let me know if that worked.

[nicoverbruggen]

This should now automatically be fixed whenever you restart PHP Monitor, by the way! A fix for this landed in v5.3.2, which I've released just now. Let me know should you happen to see this issue pop up again.