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.

urgent! cpanel/httpd down...corruption

Discussion in 'General Discussion' started by NoAgendas, Sep 4, 2006.

  1. NoAgendas

    NoAgendas Guest

    root@server [/tmp]# yum update glibc
    Setting up Update Process
    Setting up repositories
    Reading repository metadata in from local files
    Excluding Packages in global exclude list
    Finished
    Could not find update match for glibc
    No Packages marked for Update/Obsoletion

    root@server [/tmp]# rpm -Uvh http://mirror.centos.org/centos-4/4....-2.25.i386.rpm
    Retrieving http://mirror.centos.org/centos-4/4....-2.25.i386.rpm
    Preparing... ########################################### [100%]
    package glibc-2.3.4-2.25 is already installed


    I had upgraded cpanel to EDGE to attempt to fix a php upgrade problem (as suggested by many on cpanel forums, but failed). I had downgraded back to RELEASE and attempted to reocmpile apache again back to the working php 4.4.2, got this:


    pwd: cannot get current directory: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    sh: line 0: cd: lxdialog: No such file or directory
    sh: /callbacklog: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    sh: line 0: cd: lxdialog: No such file or directory
    sh: /callbacklog: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    sh: lxmenu: No such file or directory
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    sh: lxmenu: No such file or directory
     
  2. NoAgendas

    NoAgendas Guest

    I had to do a #8 default on /scripts/easyapache

    Now no accounts are listed in whm > list accounts but the accounts ALL show (I memorize some hosted domains on this server) cpnael's default green page!

    What is the fix for this?

    I did updateuserdomains, fixeverything, created a new test account (this was noted as a fix for missing accounts in list).
    Nothing worked.

    I manualy reversed (restored) httpd.conf and now I cannot update apache via whm, only via easyapache. WHM shows page not found
    when attempting to update. upcp --force a few times on release does nothing to fix it
     
    #2 NoAgendas, Sep 4, 2006
    Last edited by a moderator: Sep 4, 2006
  3. hikaro

    hikaro Well-Known Member

    Joined:
    Nov 22, 2005
    Messages:
    99
    Likes Received:
    0
    Trophy Points:
    16
    same problem here, when i try to restart cpanel it comes

    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
     
  4. Solokron

    Solokron Well-Known Member

    Joined:
    Aug 8, 2003
    Messages:
    849
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Seattle
    cPanel Access Level:
    DataCenter Provider
    Same issue here.
     
  5. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    This is the tattle tale line in what you quoted ....

    Anytime you use EasyApache to recompile apache, all of the apache folders are
    actually deleted and re-created again.

    If you are sitting in those folders or the modules or conf areas, then everything
    will seem to disapear around you and you will get the error messages that
    were displayed.

    Basically, you need to recompile Apache from outside the Apache folder paths
    when you do that and if you have any shell sitting in Apache folders after the
    re-compile, you need to change to some other folder path like "/home" or
    something and then come back to the folder again and then you will be
    able to see things again.

    That will deal with the errors you are describing. Now beyond that, whatever is
    bringing down Apache is probably something else.

    If all else fails, you can try re-compiling Apache with the "Last Resort" default config
    which is recommended anyway if you are switching back and forth from 1.3x and 2.x
    or vice versa since the httpd.conf really needs to be rebuilt from scratch for those.
     
Loading...

Share This Page