tailwatchd.service: Supervising process 11108 which is not our child
Hi @cPanelMichael
still get this
Feb 21 03:02:14 server.xxxxx.com systemd[1]: tailwatchd.service: Supervising process 11108 which is not our child. We'll most likely not notice when it exits.
here is output
([tailwatch] the output of just this word was in red just FYI if that means anything) thanks for your Help Spiro
server1:~# ps aux|grep tailwatch
root 12411 0.0 0.0 62844 16096 ? S 13:00 0:00 tailwatchd
root 13053 0.0 0.0 112664 976 pts/0 R+ 13:14 0:00 grep --color=auto tailwatch ([tailwatch] the output of just this word was in red just FYI if that means anything) thanks for your Help Spiro
-
here is my system info just incase you need it :) server1:~# grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf /etc/redhat-release:CentOS Linux release 7.4.1708 (Core) /usr/local/cpanel/version:11.70.0.16 /var/cpanel/envtype:standard CPANEL=current0 -
just doing a little google research and I found this as an explanation but not sure how it is suppose to get fixed\\ systemd reads the pidfile (as the PIDFile= directive in the unit file asks it to) in order to know which process is the main process of the service. When that process dies, systemd wants to know. But since PID XXXXX is not a direct child of PID X, systemd will not receive the SIGCHLD. This is what the warning message means. I don't know why it does not write PID XXXXX in the pidfile. If it did that, systemd would be able to supervise it and the warning would go away. I also used another line of code in ssh and i get the same error here server:~# /scripts/restartsrv_queueprocd "status Waiting for "queueprocd" to restart "waiting for "queueprocd" to initialize "finished. Service Status queueprocd (queueprocd - waiting up to 120s to process a task) is running as root with PID 29912 (systemd+/proc check method). Startup Log Feb 21 19:04:38 server.xxxx.com systemd[1]: Starting cPanel Queue services... Feb 21 19:04:38 server.xxxx.com startqueueprocd[29907]: ==> cPanel TaskQueue Processing Daemon version 1.0 Feb 21 19:04:38 server.xxxxx.com systemd[1]: queueprocd.service: Supervising process 29912 which is not our child. We'll most likely not notice when it exits. Feb 21 19:04:38 server.xxxxx.com systemd[1]: Started cPanel Queue services. Startup Log Feb 21 19:04:38 server.xxxxx.com systemd[1]: Starting cPanel Queue services... Feb 21 19:04:38 server.xxxxx.com startqueueprocd[29907]: ==> cPanel TaskQueue Processing Daemon version 1.0 Feb 21 19:04:38 server.xxxxx.com systemd[1]: queueprocd.service: Supervising process 29912 which is not our child. We'll most likely not notice when it exits. Feb 21 19:04:38 server.xxxxx.com systemd[1]: Started cPanel Queue services. queueprocd restarted successfully. server:~#0 -
here is my system info just incase you need it :)
server1:~# grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf /etc/redhat-release:CentOS Linux release 7.4.1708 (Core) /usr/local/cpanel/version:11.70.0.16 /var/cpanel/envtype:standard CPANEL=current
i have updated to cloudlinux just FYI server1:~# ps aux|grep tailwatch root 5172 0.0 0.0 65516 17432 ? S 15:12 0:00 tailwatchd root 32519 0.0 0.0 114716 972 pts/0 S+ 21:22 0:00 grep --color=auto tailwatch0 -
Hello, The following output is normal and isn't an indication of any problems on the server: [QUOTE] Startup Log Feb 26 10:17:28 hostname systemd[1]: Starting cPanel Queue services... Feb 26 10:17:28 hostname startqueueprocd[6977]: ==> cPanel TaskQueue Processing Daemon version 1.0 Feb 26 10:17:28 hostname systemd[1]: queueprocd.service: Supervising process 6982 which is not our child. We'll most likely not notice when it exits. Feb 26 10:17:28 hostname systemd[1]: Started cPanel Queue services.
It's related to how systemd reads the pidfile (as referenced on the PIDFile= line of /etc/systemd/system/queueprocd.service). You can read more about how queueprocd works at: The Task Queue System - Version 70 Documentation - cPanel Documentation Thank you.0 -
thanks Mark as Solved 0
Please sign in to leave a comment.
Comments
5 comments