-
Notifications
You must be signed in to change notification settings - Fork 210
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
After one month I put webman application on production server, its suddently stop #83
Comments
Start webman with daemon mode the command is |
i did use php start.php restart -d
is it same for daemon ? |
Yes. |
How do you know that webman is stopped? Use a command like |
I'm using nginx proxy so it's just said 504 Bad Gateway |
Please use command |
ok, i'll wait next time maybe tomorrow it's gonna stop again. Usually I did before using |
Why the webman die both on same server ? |
Run command |
Ok later i'll do again when webman stop again |
You can do that now. |
Ok I'll do it now |
vendor/workerman/workerman.log
/var/log/messages
|
Please run command top and show the top 5 lines line which something like top - 11:03:53 up 441 days, 13:20, 1 user, load average: 0.00, 0.05, 0.06 .... |
Could you give the correct |
Just run command ```top``` .
|
NO, now its die again, please check what happen
|
Run command |
php -v
|
It looks like your system has been rebooted so webman process died. |
Damn, you correct, so i have to run it on startup ? |
Yes. |
how to run it on startup on centos / rhel ? |
Add start command to
|
Ok Done, thanks alot |
I got many times, webman service stop for unknown reason and here's the last log
and here's what happen if user_id session empty / reset. I still can't find the issue why session user_id is gone
I did use webman with nohup, it should be always start, but why it's stop many times, sometime in 3 days or less the webman service is stop
The text was updated successfully, but these errors were encountered: