Closed graywh closed 10 years ago
I never noticed that. I guess there was a crash.
It it ever happens again, please tail Prax' log, which should be at ~/.prax/_logs/prax.log
There's nothing in the log to say what happened.
I see this consistently. Once I touch /tmp/restart.txt
, all the racker processes for that app go away, and never come back regardless of how many times I curl <app>.dev
. The only thing that fixes it is restarting the prax server completely. The prax logs and corresponding Rails logs have no output either. It's as though prax doesn't see the request at all. So basically prax restart
doesn't work for me at all. This is on a Debian Wheezy system with Rails apps.
@ysbaddaden Any tips on where to start looking to debug?
What about the "unstable" branch?
I should change the name, it's no more unstable than master and has more features. I should make it the current master.
Ah, I was hoping I could avoid using that branch, as I need subdomain symlink support and per #54 looks like unstable doesn't have that yet?
FYI I no longer have the restart problem on the unstable branch
I think it's time for unstable to become the master branch, and for the master branch to become legacy.
Has anyone else seen prax suddenly stop responding? At least once, it happened after touching
tmp/restart.txt
to restart an application. After stopping and starting prax, it worked normally.