Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

SOLVED tailwatchd.service: Supervising process 11108 which is not our child

Discussion in 'General Discussion' started by Spirogg, Feb 21, 2018.

Tags:
  1. Spirogg

    Spirogg Member

    Joined:
    Feb 21, 2018
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    chicago
    cPanel Access Level:
    Root Administrator
    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

    Code:
    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
     
  2. Spirogg

    Spirogg Member

    Joined:
    Feb 21, 2018
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    chicago
    cPanel Access Level:
    Root Administrator
    here is my system info just incase you need it :)

    Code:
    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
     
  3. Spirogg

    Spirogg Member

    Joined:
    Feb 21, 2018
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    chicago
    cPanel Access Level:
    Root Administrator
    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

    Code:
    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:~#
     
  4. Spirogg

    Spirogg Member

    Joined:
    Feb 21, 2018
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    chicago
    cPanel Access Level:
    Root Administrator


    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 tailwatch
     
    #4 Spirogg, Feb 23, 2018
    Last edited by a moderator: Feb 24, 2018
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    43,215
    Likes Received:
    1,759
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The following output is normal and isn't an indication of any problems on the server:

    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.
     
  6. Spirogg

    Spirogg Member

    Joined:
    Feb 21, 2018
    Messages:
    23
    Likes Received:
    3
    Trophy Points:
    3
    Location:
    chicago
    cPanel Access Level:
    Root Administrator
    thanks Mark as Solved
     
    cPanelMichael likes this.
Loading...

Share This Page