Requires a reboot after most actions

[mishterk]

Howdy,

I've recently run into some issues where I now have to reboot my machine whenever I:

1. Run valet secure or valet unsecure
2. Run valet use php@xx

Whenever I do a reboot, I also need to run mysql.server start.

I recently completely reinstalled Valet using this approach – #326 (comment).

Some possibly helpful info:

To demonstrate

Here are the php, dnsmasq, and nginx processes before changing anything:

I then run valet unsecure and the same processes change to:

Checking config – looks ok...

From there I attempt to run NGINX again:

I check port 80:

This is where I'm not sure what to do next and go for the reboot after which everything works fine again.

Can anyone give me some direction on what I need to do here to get Valet running smoothly again? I'm guessing there is an issue with daemons and that's possibly related to permissions but I'm pushing the boundaries of what I'm used to here.

Thanks!
Phil

[drbyte]

The primary difference between yours and mine is that you've installed Apache, and it's sitting there running as root. And it appears to be listening on port 80.
Nginx won't be able to bind itself to listen on ports 80 or 443 if Apache is already sitting there listening for incoming traffic on those ports.

I suppose the quick test is:
sudo brew services stop httpd
And then valet restart

[mishterk]

Thanks, @drbyte.

I'm halfway there 🎉

I wasn't able to stop apache using sudo brew services stop httpd. It was listed as stopped in brew services list after running the command but was still running on port 80 – guessing it was OSX's built-in Apache that was running. sudo apachectl stop wouldn't work for me either so to stop it I had to use sudo /usr/sbin/apachectl stop:

From there, a valet restart resulted in NGINX running again:

The only thing that I still need to do after a reboot is mysql.server start. It's not a huge issue but if anyone has an idea on how I get Valet's daemon handling this again that would be rad.

[drbyte]

Valet doesn't have anything to do with MySQL. It's entirely optional and completely under your sole control.

(Given you've installed it with Homebrew), the best way to have it self-start upon reboot is to follow Homebrew's instructions (get them with brew info mysql) for telling it to start upon boot:

To have launchd start mysql now and restart at login:
  brew services start mysql
Or, if you don't want/need a background service you can just run:
  mysql.server start

If that doesn't work, then I suggest looking at your MySQL logs or your OSX Console for why it's stopping/not-starting.