Closed haidarvm closed 3 years ago
Start webman with daemon mode the command is php start.php start -d
, -d
is the key. nohup is not necessary.
Start webman with daemon mode the command is
php start.php start -d
,-d
is the key. nohup is not necessary.
i did use php start.php restart -d
#!/bin/bash
php start.php restart -d
is it same for daemon ? because i always update the apps with git pull and need to restart so prefer run restart.sh
is it same for daemon ?
Yes.
How do you know that webman is stopped? Use a command like ps aux
?
How do you know that webman is stopped? Use a command like
ps aux
?
I'm using nginx proxy so it's just said 504 Bad Gateway
Please use command ps auxf
to see if the webman process exist when got 504 Bad Gateway
.
If the webman process exist then run command php start.php status
and show the output.
Please upload vendor/workerman/workerman.log
.
ok, i'll wait next time maybe tomorrow it's gonna stop again. Usually I did before using ps aux | grep webman
is gone
[client@haidarvm ~]$ ps aux | grep webman
client 7405 0.0 0.0 221900 1056 pts/0 S+ 09:56 0:00 grep --color=auto webman
[client@haidarvm ~]$ cd roemahmedia/public_html/
[client@haidarvm public_html]$ ls
app config logs public runtime stop.sh
composer.json db nohup.out README.md start.php support
composer.lock LICENSE process restart.sh start.sh vendor
[client@haidarvm public_html]$ php start.php status
Workerman[start.php] status
Workerman[start.php] not run
[client@haidarvm public_html]$ cd /home/client/kitabemas/
[client@haidarvm kitabemas]$ php start.php status
Workerman[start.php] status
Workerman[start.php] not run
Why the webman die both on same server ? please My client complain about it
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 ....
.
Run command php start.php status
and show the output.
Upload your vendor/workerman/workerman.log
here.
Check system log (something like /var/log/kern.log
/var/log/messages
) to see if there are any error logs.
Run command dmesg
to see if there are any error logs.
Run command
top
and show the top 5 lines line which something liketop - 11:03:53 up 441 days, 13:20, 1 user, load average: 0.00, 0.05, 0.06 ....
. Run commandphp start.php status
and show the output. Upload yourvendor/workerman/workerman.log
here. Check system log (something like/var/log/kern.log
/var/log/messages
) to see if there are any error logs. Run commanddmesg
to see if there are any error logs.
Ok later i'll do again when webman stop again
You can do that now.
.
Ok I'll do it now
Workerman[start.php] status
----------------------------------------------GLOBAL STATUS----------------------------------------------------
Workerman version:4.0.16 PHP version:7.4.13
start time:2020-12-03 10:59:08 run 3 days 10 hours
load average: 0.09, 0, 0 event-loop:\Workerman\Events\Select
2 workers 3 processes
worker_name exit_status exit_count
webman 0 0
monitor 0 0
----------------------------------------------PROCESS STATUS---------------------------------------------------
pid memory listening worker_name connections send_fail timers total_request qps status
7492 6M http://roemahmedia.com:8181 webman 1 2 0 484 0 [idle]
7493 6M http://roemahmedia.com:8181 webman 1 0 0 512 0 [idle]
7494 2M none monitor 0 0 0 0 0 [idle]
----------------------------------------------PROCESS STATUS---------------------------------------------------
Summary 14M - - 2 2 0 996 0 [Summary]
vendor/workerman/workerman.log
2020-11-18 09:14:34 pid:36658 Workerman[start.php] stopping ...
2020-11-18 09:14:34 pid:36658 Workerman[start.php] has been stopped
2020-11-18 09:14:34 pid:36864 Workerman[start.php] stop success
2020-11-24 07:41:23 pid:36867 Workerman[start.php] stopping ...
2020-11-24 07:41:23 pid:36867 Workerman[start.php] stopping ...
2020-11-24 07:41:23 pid:36867 Workerman[start.php] has been stopped
2020-11-24 10:43:08 pid:6384 Workerman[start.php] restart
2020-11-24 10:43:08 pid:6384 Workerman[start.php] is stopping ...
2020-11-24 10:43:08 pid:6384 Workerman[start.php] stop success
2020-11-25 07:24:33 pid:6387 Workerman[start.php] stopping ...
2020-11-25 07:24:33 pid:6387 Workerman[start.php] stopping ...
2020-11-25 07:24:33 pid:6387 Workerman[start.php] has been stopped
2020-11-25 08:27:55 pid:3068 Workerman[start.php] restart
2020-11-25 08:27:55 pid:3068 Workerman[start.php] is stopping ...
2020-11-25 08:27:55 pid:3068 Workerman[start.php] stop success
2020-11-25 08:31:00 pid:3225 Workerman[start.php] restart
2020-11-25 08:31:00 pid:3225 Workerman[start.php] is stopping ...
2020-11-25 08:31:00 pid:3071 Workerman[start.php] stopping ...
2020-11-25 08:31:00 pid:3071 Workerman[start.php] has been stopped
2020-11-25 08:31:00 pid:3225 Workerman[start.php] stop success
2020-11-30 03:52:40 pid:212295 Workerman[start.php] restart
2020-11-30 03:52:40 pid:212295 Workerman[start.php] is stopping ...
2020-11-30 03:52:40 pid:3228 Workerman[start.php] stopping ...
2020-11-30 03:52:40 pid:3228 Workerman[start.php] has been stopped
2020-11-30 03:52:40 pid:212295 Workerman[start.php] stop success
2020-12-03 07:38:53 pid:212298 Workerman[start.php] stopping ...
2020-12-03 07:38:53 pid:212298 Workerman[start.php] stopping ...
2020-12-03 07:38:53 pid:212298 Workerman[start.php] has been stopped
2020-12-03 10:57:07 pid:7429 Workerman[start.php] status
2020-12-03 10:57:07 pid:7429 Workerman[start.php] not run
2020-12-03 10:59:08 pid:7488 Workerman[start.php] start in DAEMON mode
2020-12-06 21:55:42 pid:156878 Workerman[start.php] status
/var/log/messages
Dec 6 20:56:01 haidarvm systemd[1]: Stopped User Manager for UID 0.
Dec 6 20:56:01 haidarvm systemd[1]: user-runtime-dir@0.service: Unit not needed anymore. Stopping.
Dec 6 20:56:01 haidarvm systemd[1]: Removed slice User Slice of UID 0.
Dec 6 20:56:01 haidarvm systemd[1]: Stopping /run/user/0 mount wrapper...
Dec 6 20:56:01 haidarvm systemd[1]: Stopped /run/user/0 mount wrapper.
Dec 6 20:56:04 haidarvm dbus-daemon[568]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.47' (uid=0 pid=525 comm="/usr/sbin/sedispatch " label="system_u:system_r:auditd_t:s0") (using servicehelper)
Dec 6 20:56:04 haidarvm dbus-daemon[156911]: [system] Failed to reset fd limit before activating service: org.freedesktop.DBus.Error.AccessDenied: Failed to restore old fd limit: Operation not permitted
Dec 6 20:56:05 haidarvm dbus-daemon[568]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Dec 6 20:56:07 haidarvm setroubleshoot[156911]: SELinux is preventing local from create access on the file 1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 6964ab20-39bf-4633-8a7c-48879842665f
Dec 6 20:56:07 haidarvm platform-python[156911]: SELinux is preventing local from create access on the file 1607262961.P156909.haidarvm.com.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that local should be allowed create access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:56:07 haidarvm setroubleshoot[156911]: SELinux is preventing local from create access on the file 1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 6964ab20-39bf-4633-8a7c-48879842665f
Dec 6 20:56:07 haidarvm platform-python[156911]: SELinux is preventing local from create access on the file 1607262961.P156909.haidarvm.com.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that local should be allowed create access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:56:08 haidarvm setroubleshoot[156911]: SELinux is preventing local from getattr access on the file /root/Maildir/tmp/1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 2909b8f7-ed67-4275-8527-a530194a489d
Dec 6 20:56:08 haidarvm platform-python[156911]: SELinux is preventing local from getattr access on the file /root/Maildir/tmp/1607262961.P156909.haidarvm.com.#012#012***** Plugin restorecon (99.5 confidence) suggests ************************#012#012If you want to fix the label. #012/root/Maildir/tmp/1607262961.P156909.haidarvm.com default label should be mail_home_rw_t.#012Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.#012Do#012# /sbin/restorecon -v /root/Maildir/tmp/1607262961.P156909.haidarvm.com#012#012***** Plugin catchall (1.49 confidence) suggests **************************#012#012If you believe that local should be allowed getattr access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:56:09 haidarvm setroubleshoot[156911]: SELinux is preventing local from read access on the file 1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 9b96b297-0b8b-49fe-ae47-6d7a0bd51f01
Dec 6 20:56:09 haidarvm platform-python[156911]: SELinux is preventing local from read access on the file 1607262961.P156909.haidarvm.com.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that local should be allowed read access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:56:10 haidarvm setroubleshoot[156911]: SELinux is preventing local from read access on the file 1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 9b96b297-0b8b-49fe-ae47-6d7a0bd51f01
Dec 6 20:56:10 haidarvm platform-python[156911]: SELinux is preventing local from read access on the file 1607262961.P156909.haidarvm.com.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that local should be allowed read access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:56:10 haidarvm setroubleshoot[156911]: SELinux is preventing local from unlink access on the file 1607262961.P156909.haidarvm.com. For complete SELinux messages run: sealert -l 15b98714-be03-48ab-ab62-fb7101f8b77e
Dec 6 20:56:10 haidarvm platform-python[156911]: SELinux is preventing local from unlink access on the file 1607262961.P156909.haidarvm.com.#012#012***** Plugin catchall (100. confidence) suggests **************************#012#012If you believe that local should be allowed unlink access on the 1607262961.P156909.haidarvm.com file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'local' --raw | audit2allow -M my-local#012# semodule -X 300 -i my-local.pp#012
Dec 6 20:57:49 haidarvm systemd-logind[653]: Session 2594 logged out. Waiting for processes to exit.
Dec 6 20:57:49 haidarvm systemd-logind[653]: Removed session 2594.
Dec 6 20:58:15 haidarvm systemd[1]: Created slice User Slice of UID 1000.
Dec 6 20:58:15 haidarvm systemd[1]: Started /run/user/1000 mount wrapper.
Dec 6 20:58:15 haidarvm systemd[1]: Starting User Manager for UID 1000...
Dec 6 20:58:15 haidarvm systemd[1]: Started Session 2597 of user haidarvm.
Dec 6 20:58:15 haidarvm systemd-logind[653]: New session 2597 of user haidarvm.
Dec 6 20:58:15 haidarvm systemd[156993]: Reached target Paths.
Dec 6 20:58:15 haidarvm systemd[156993]: Started Mark boot as successful after the user session has run 2 minutes.
Dec 6 20:58:15 haidarvm systemd[156993]: Reached target Timers.
Dec 6 20:58:15 haidarvm systemd[156993]: Starting D-Bus User Message Bus Socket.
Dec 6 20:58:15 haidarvm systemd[156993]: Listening on D-Bus User Message Bus Socket.
Dec 6 20:58:15 haidarvm systemd[156993]: Reached target Sockets.
Dec 6 20:58:15 haidarvm systemd[156993]: Reached target Basic System.
Dec 6 20:58:15 haidarvm systemd[156993]: Reached target Default.
Dec 6 20:58:15 haidarvm systemd[156993]: Startup finished in 26ms.
Dec 6 20:58:15 haidarvm systemd[1]: Started User Manager for UID 1000.
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 ....
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 top
command
Just run command top
.
NO, now its die again, please check what happen
8359 nginx 20 0 846980 118024 96660 S 2,0 5,8 0:09.54 php-fpm
8271 nginx 20 0 843328 130108 112596 S 1,7 6,4 0:13.37 php-fpm
7893 nginx 20 0 843260 114968 97520 S 1,0 5,7 0:19.39 php-fpm
846 mysql 20 0 4420136 684480 11124 S 0,7 33,7 6:45.97 mysqld
1387 nginx 20 0 179992 26196 18016 S 0,7 1,3 0:44.32 nginx
8362 nginx 20 0 839000 109344 96020 S 0,3 5,4 0:09.25 php-fpm
1 root 20 0 180032 13816 8836 S 0,0 0,7 0:02.79 systemd
2 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_par_gp
Run command top
and show all the output.
Upload your vendor/workerman/workerman.log here.
Check system log (something like /var/log/kern.log
/var/log/messages
) to see if there are any error logs.
Run command dmesg
to see if there are any error logs.
Run command php -v
and show the output.
php -v
[root@haidarvm ~]# php -v
PHP 7.4.13 (cli) (built: Nov 24 2020 10:03:34) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.13, Copyright (c), by Zend Technologies
top - 11:36:31 up 5:05, 1 user, load average: 0,03, 0,14, 0,33
Tasks: 145 total, 2 running, 143 sleeping, 0 stopped, 0 zombie
%Cpu(s): 3,7 us, 0,7 sy, 0,0 ni, 95,3 id, 0,3 wa, 0,0 hi, 0,0 si, 0,0 st
MiB Mem : 1986,2 total, 120,3 free, 1124,1 used, 741,7 buff/cache
MiB Swap: 0,0 total, 0,0 free, 0,0 used. 535,9 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8990 nginx 20 0 840664 90560 75732 S 1,7 4,5 0:00.58 php-fpm
8358 nginx 20 0 843096 93680 76356 S 0,7 4,6 0:10.51 php-fpm
8450 nginx 20 0 843096 128320 111060 S 0,7 6,3 0:06.48 php-fpm
846 mysql 20 0 4420136 684552 11196 S 0,3 33,7 6:53.47 mysqld
1 root 20 0 180032 13816 8836 S 0,0 0,7 0:02.84 systemd
2 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:0H-kblockd
8 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 mm_percpu_wq
9 root 20 0 0 0 0 S 0,0 0,0 0:00.27 ksoftirqd/0
10 root 20 0 0 0 0 I 0,0 0,0 0:01.05 rcu_sched
11 root rt 0 0 0 0 S 0,0 0,0 0:00.01 migration/0
13 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0
15 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kdevtmpfs
16 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 netns
17 root 20 0 0 0 0 S 0,0 0,0 0:00.00 rcu_tasks_rude_
18 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kauditd
19 root 20 0 0 0 0 S 0,0 0,0 0:00.00 khungtaskd
20 root 20 0 0 0 0 S 0,0 0,0 0:00.00 oom_reaper
21 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 writeback
22 root 20 0 0 0 0 S 0,0 0,0 0:00.21 kcompactd0
23 root 25 5 0 0 0 S 0,0 0,0 0:00.00 ksmd
24 root 39 19 0 0 0 S 0,0 0,0 0:00.12 khugepaged
34 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 cryptd
77 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kintegrityd
78 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kblockd
79 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 blkcg_punt_bio
80 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 tpm_dev_wq
81 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 md
82 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 edac-poller
83 root -51 0 0 0 0 S 0,0 0,0 0:00.00 watchdogd
96 root 20 0 0 0 0 S 0,0 0,0 0:00.29 kswapd0
98 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kthrotld
99 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 acpi_thermal_pm
100 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kmpath_rdacd
It looks like your system has been rebooted so webman process died.
Damn, you correct, so i have to run it on startup ?
Yes.
Yes.
how to run it on startup on centos / rhel ?
Add start command to /etc/rc.local
.
For example.
/usr/bin/env php /your/path/of/webman/start.php start -d
exit 0
Add start command to
/etc/rc.local
. For example./usr/bin/env php /your/path/of/webman/start.php start -d exit 0
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