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.

Nasty bug in killacct?

Discussion in 'General Discussion' started by morpheous, Feb 15, 2005.

  1. morpheous

    morpheous Member

    Joined:
    Dec 21, 2004
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Hey,

    When deleting an account as root, the killacct script hangs in the WHM GUI at "Terminating processes... Done", and when I do ps aux (When the server load had hit 1.32), I see:

    Code:
    root     11196  0.1  2.3 12808 11492 ?       S    22:59   0:00 /usr/local/cpanel/whostmgr/bin/whostmgr ./killacct
    root     11199  0.1  0.7  5048 3456 ?        S    22:59   0:00 /usr/bin/perl /scripts/killacct im
    root     11206  0.0  0.1  2056  956 ?        S    22:59   0:00 sh -c /scripts/grpck >/dev/null 2>/dev/null
    root     11207  0.3  0.9  6136 4504 ?        S    22:59   0:00 /usr/bin/perl /scripts/grpck
    root     11208 91.5 29.3 143120 141996 ?     R    22:59   1:42 /usr/sbin/grpck -r
    
    Is there a way to stop this? Is this a know bug? Also, when I kill the grpck -r (11208), it stops the whole /killacct process, and leaves the account half-deleted, which is not good- I now have a 10GB account on my system half-deleted, all files still intact.

    Thanks in advance,
    Morph
     
  2. dezignguy

    dezignguy Well-Known Member

    Joined:
    Sep 26, 2004
    Messages:
    534
    Likes Received:
    0
    Trophy Points:
    16
    trying searching these forums for 'grpck' or 'grpck load' and/or 'grpck suspend' as this has already been discussed quite a bit.
     
  3. jester.ro

    jester.ro Well-Known Member
    PartnerNOC

    Joined:
    Feb 6, 2004
    Messages:
    304
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Bucharest, Romania
    cPanel Access Level:
    DataCenter Provider
    yes, and especially read the posts of cpanelben, he had some options to fix this issue. I actually fixed 2 servers forcing an install of an older version of shadow-utils
     
Loading...

Share This Page