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.

queueprocd on server.xxxxxxxxxx.net failed

Discussion in 'General Discussion' started by jonyzinho, May 30, 2009.

  1. jonyzinho

    jonyzinho Active Member

    Joined:
    Apr 2, 2005
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    6
    Hi,

    I have one problem of one server.

    I have many mail report.

    This is the body of mail report:

    ================================================

    queueprocd failed @ Sat May 30 17:22:27 2009. A restart was attempted automagically.
    Service Check Method: [check command]

    ================================================

    and in the Service Status of WHM the queueprocd is "failed".

    You may help me please ?

    How I make the service "queueprocd" UP ?

    Regards,

    Jony
     
  2. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,460
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Please open a support ticket for this issue. Thank you.
     
  3. anand

    anand Well-Known Member

    Joined:
    Nov 11, 2002
    Messages:
    1,435
    Likes Received:
    1
    Trophy Points:
    38
    Location:
    India
    cPanel Access Level:
    DataCenter Provider
    What's the solution for this issue ? I just started to see this on a box. Have 300+ mails with the same message in it.

    Code:
    queueprocd failed @ Tue Oct 27 18:51:48 2009. A restart was attempted automagically.
    Service Check Method:  [check command] 
    
     
  4. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    What is the full cPanel version number of the affected system?

    It may be that the system was upgraded to version 11.25 (e.g., on EDGE), then later downgraded to version 11.24 (e.g., on RELEASE or STABLE at the time of writing).

    cPanel version 11.25 adds an entry for queueprocd in the chkservd monitoring configuration found here:
    Code:
    /etc/chkserv.d/chkservd.conf
    /etc/chkserv.d/queueprocd
    If you would like assistance with determining the specific cause and appropriate corrective measures, please consider submitting a ticket where we can investigate with more precision.
     
  5. anand

    anand Well-Known Member

    Joined:
    Nov 11, 2002
    Messages:
    1,435
    Likes Received:
    1
    Trophy Points:
    38
    Location:
    India
    cPanel Access Level:
    DataCenter Provider
    Hi Donald,

    The version of cpanel is cPanel 11.24.5-R38506 - WHM 11.24.2 - X 3.9. Don't recall updating it to CURRENT and then downgrading.

    Anyways i did find the queueprocd inside the /etc/chkserv.d directory and have removed the same.

    I will update incase i face the problem again. Thanks for the help.
     
  6. gearheadhost

    gearheadhost Member

    Joined:
    Jun 14, 2009
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Thanks cPanelDon,

    Had this exact issue but funny thing is it only came to light as I rebooted into the new CentOS Kernel.

    Weird.

    Now all is beautiful and working.
     
  7. Epademic

    Epademic Active Member

    Joined:
    Nov 21, 2003
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    6
    Whats the best way to solve this? Its only just started happening to one of my boxes running 11.25.0-C40255.

    Many thanks,

    James
     
  8. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    The information I posted earlier in the thread was for a very specific symptom when downgrading from 11.25 to 11.24; if the system is still on the CURRENT build tree I believe the symptom, while similar, may stem from a different cause.

    If you have a system that is currently at cPanel version 11.25 (EDGE or CURRENT) where there is difficulty with "queueprocd" please consider submitting a support request as it may be a different issue and it will help to ensure an accurate diagnosis by having the system inspected directly and checking the circumstances involved; when available, please PM me the ticket ID number so I may follow-up internally.
     
  9. Epademic

    Epademic Active Member

    Joined:
    Nov 21, 2003
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    6
    cPanel fixed this for me. The issue was

    They corrected the corrupted entry and everything is now working fine.
     
  10. Fernis

    Fernis Well-Known Member

    Joined:
    Oct 28, 2006
    Messages:
    192
    Likes Received:
    1
    Trophy Points:
    18
    Do you know what the corrupted entry was are what exactly was changed to correct the issue?
     
  11. Wajdan

    Wajdan Member

    Joined:
    Sep 11, 2009
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    I got the same problem but looks like i have resolved it :)
     
  12. Epademic

    Epademic Active Member

    Joined:
    Nov 21, 2003
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    6
    Hi Fernis, sorry no i don't know the exact details of what was changed.
     
  13. sharmaine001

    sharmaine001 Well-Known Member

    Joined:
    Jun 23, 2006
    Messages:
    143
    Likes Received:
    0
    Trophy Points:
    16
    I started to get this issue after I install SSL to whm/webmail/cpanel (service configuration)

    Can you please tell us the solution instead of putting a support ticket?
     
  14. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    There is no single solution that applies to all possible situations; however, if you do submit a support request and PM me the ticket ID number, then I can assist with confirming the unique resolution, and you may also post to share with others how the specific issue was resolved.

    As a starting point to help determine where the issue may be at, please check the cPanel log files in the following directory path:
    Code:
    /usr/local/cpanel/logs/
    To monitor the cPanel error log while at the same time attempting to reproduce the issue please use the following command via root SSH access:
    Code:
    # tail -fvn0 /usr/local/cpanel/logs/error_log
    If the issue reoccurs with log detail it will help to provide that information so the issue can be more accurately evaluated.

    Please confirm your full cPanel version number; this will help to narrow-down what factors are involved:
    Code:
    # grep '' /usr/local/cpanel/version
     
    #14 cPanelDon, Dec 2, 2009
    Last edited: Dec 2, 2009
  15. serversurgeon

    serversurgeon Registered

    Joined:
    Dec 18, 2009
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Or you can try to run as root:

    /scripts/checkperlmodules
    and
    /scripts/upcp

    restart cpanel. It may help.
     
  16. sharmaine001

    sharmaine001 Well-Known Member

    Joined:
    Jun 23, 2006
    Messages:
    143
    Likes Received:
    0
    Trophy Points:
    16
    I already had cpanel checked it and they confirmed its a bug in the current build of cPanel
     
  17. megalai

    megalai Registered

    Joined:
    Mar 22, 2005
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Fixed it by running /scripts/restartsrv_queueprocd in one of our servers. Hope this helps someone.




    Thx,
    Megalai
     
  18. PCZero

    PCZero Well-Known Member

    Joined:
    Dec 13, 2003
    Messages:
    526
    Likes Received:
    34
    Trophy Points:
    28
    Location:
    Earth
    I am getting email flooded with the errors about queueprocd as well...

    /scripts/restartsrv_queueprocd failed @ Mon Dec 28 22:43:58 2009. A restart was attempted automagically.


    Just ran the script mentioned above. Will advise of any changes.
     
  19. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    If the issue persists please submit a support request so that we can examine the system and investigate the circumstances involved. If needed, the link in my forums signature may be used to initiate a ticket submission; when available, please PM me the new ticket ID number so I may follow-up internally.
     
  20. PCZero

    PCZero Well-Known Member

    Joined:
    Dec 13, 2003
    Messages:
    526
    Likes Received:
    34
    Trophy Points:
    28
    Location:
    Earth
    Will do Don. I think it has been resolved. Here is a run down of what went on.

    Historically, the server in question was set to manual updates to release version.

    recently ran an updates to cPanel 11.25.0-R42399 - WHM 11.25.0 - X 3.9 and soon after started getting a handful of warning messages at various places in WHM and cPanel.

    Changed my update preference to manual stable and ran the update again. This took me back to a previous version. When it completed I had major issues with CPHulk locking me out of WHM and cPanel.

    Once I got back into the server, I went back to the release version and ran the update again. This time it appears that the update processed differently and I no longer got the warnings.

    I think the issue discussed in this thread started after the change to stable and was resolved when I went back to the more up to date release. So far no additional messages about the process. I'll post again in 24 hours or so to provide additional feedback.
     
Loading...

Share This Page