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.

users canot change pass (spawn /usr/bin/passwd)

Discussion in 'General Discussion' started by icehosting, Nov 11, 2003.

  1. icehosting

    icehosting Well-Known Member

    Joined:
    Dec 22, 2002
    Messages:
    60
    Likes Received:
    0
    Trophy Points:
    6
    Hi,
    i have this problem:
    if a user try to change the password of the cpanel account receive this answer:
    "spawn /usr/bin/passwd"
    and the password is not changed.
    I have contact cpanel support team before some days but until now canot fix my box.
    It is there any solution for this cpanel bug?

    cPanel.net Support Ticket Number: 28984
     
  2. icehosting

    icehosting Well-Known Member

    Joined:
    Dec 22, 2002
    Messages:
    60
    Likes Received:
    0
    Trophy Points:
    6
    seems that cpanel support canot make this fix!
    This is very bad for my servers.
    CPANEL have lot of bugs, so support it is very importand.
    Any other tech know any fix?

    cPanel.net Support Ticket Number: 28984
     
  3. B12Org

    B12Org Well-Known Member

    Joined:
    Jul 15, 2003
    Messages:
    692
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Seattle Washington
    cPanel Access Level:
    Root Administrator
    I had this problem last week, and so then I changed the root password, and it changed every users password to the root password. So, now I have to change every users password to what they would like it to be, and with 200 users, thats a lot of work. Thankfully, i only get about 5-10 per week though, as most people just dont know or care, or think that they forgot their passwords. It could also be related to a mysql or bind problem that was going arround after the last update. Try going to the latest stable version, or edge version, depending on which one you currently use, to force an update regardless, and then go back to the stable and update again.
     
Loading...

Share This Page