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.

i cant login to my whm

Discussion in 'General Discussion' started by aryapsh, Jan 12, 2010.

  1. aryapsh

    aryapsh Well-Known Member

    Joined:
    Apr 17, 2007
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    6
    hi
    when i want to restart my cpanel service i have the next problem
    and i cant login to my whm


    root@phoenix [/etc/csf]# service cpanel restart
    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
    Stopping tailwatchd: /usr/local/cpanel/libexec/tailwatchd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/libexec/tailwatchd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel', '/usr/local/cpanel/Cpanel/CPAN/overload/__Time'; }'
    [FAILED]
    Stopping cPanel services: /usr/local/cpanel/etc/init/stopcpsrvd: line 7: syntax error near unexpected token `{'
    /usr/local/cpanel/etc/init/stopcpsrvd: line 7: `if ( -e '/var/run/cpsrvd.pid' ) {'
    [FAILED]
    Stopping cPanel dav services: /usr/local/cpanel/etc/init/stopcpdavd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/stopcpdavd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Stopping cPanel queue services: /usr/local/cpanel/etc/init/stopqueueprocd: line 3: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/stopqueueprocd: line 3: `BEGIN { unshift @INC, '/usr/local/cpanel'; };'
    [FAILED]
    Stopping cPanel brute force detector services: /usr/local/cpanel/etc/init/stopcphulkd: line 7: syntax error near unexpected token `{'
    /usr/local/cpanel/etc/init/stopcphulkd: line 7: `if ( -e '/var/run/cphulkd_processor.pid' ) {'
    [FAILED]
    Stopping pop3 services: /usr/local/cpanel/etc/init/stopcppop: line 2: syntax error near unexpected token `"/usr/local/cpanel/etc/init/safekill","cppop"'
    /usr/local/cpanel/etc/init/stopcppop: line 2: `system("/usr/local/cpanel/etc/init/safekill","cppop");'
    [FAILED]
    Stopping cPanel log services: [FAILED]
    Stopping cPanel Chat services: [FAILED]
    Stopping Melange Chat services: [FAILED]
    Stopping InterChange services: [FAILED]
    Stopping cPanel ssl services: /usr/local/cpanel/etc/init/stopstunnel: line 8: my: command not found
    /usr/local/cpanel/etc/init/stopstunnel: line 9: syntax error near unexpected token `{'
    /usr/local/cpanel/etc/init/stopstunnel: line 9: `if ( -e $pid_file ) {'
    [FAILED]
    Stopping mailman services: /usr/local/cpanel/etc/init/stopmailman: line 2: syntax error near unexpected token `{'
    /usr/local/cpanel/etc/init/stopmailman: line 2: `if ( -e '/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl' ) {'
    [FAILED]
    Starting cPanel services: /usr/local/cpanel/etc/init/startcpsrvd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startcpsrvd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Starting cPanel brute force detector services: /usr/local/cpanel/etc/init/startcphulkd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startcphulkd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Starting cPanel dav services: /usr/local/cpanel/etc/init/startcpdavd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startcpdavd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Starting pop3 services: /usr/local/cpanel/etc/init/startcppop: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startcppop: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Starting cPanel Chat services:
    Starting Melange Chat services:
    Starting cPanel ssl services: /usr/local/cpanel/etc/init/startstunnel: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startstunnel: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel'; }'
    [FAILED]
    Starting cPanel Queue services: /usr/local/cpanel/etc/init/startqueueprocd: line 9: syntax error near unexpected token `}'
    /usr/local/cpanel/etc/init/startqueueprocd: line 9: `BEGIN { unshift @INC, '/usr/local/cpanel'; };'
    [FAILED]
    Starting tailwatchd: /usr/local/cpanel/libexec/tailwatchd: line 7: syntax error near unexpected token `}'
    /usr/local/cpanel/libexec/tailwatchd: line 7: `BEGIN { unshift @INC, '/usr/local/cpanel', '/usr/local/cpanel/Cpanel/CPAN/overload/__Time'; }'
    [FAILED]
    Starting cPanel Log services: /usr/local/cpanel/cpanellogd: line 7: BEGIN: command not found
    /usr/local/cpanel/cpanellogd: line 8: unshift: command not found
    /usr/local/cpanel/cpanellogd: line 9: syntax error near unexpected token `}'
    /usr/local/cpanel/cpanellogd: line 9: `}'
    [FAILED]
    Starting mailman services: /usr/local/cpanel/etc/init/startmailman: line 3: BEGIN: command not found
    /usr/local/cpanel/etc/init/startmailman: line 5: syntax error near unexpected token `('
    /usr/local/cpanel/etc/init/startmailman: line 5: `use Cpanel::Env ();'
    [FAILED]
     
  2. vanessa

    vanessa Well-Known Member
    PartnerNOC

    Joined:
    Sep 26, 2006
    Messages:
    817
    Likes Received:
    22
    Trophy Points:
    18
    Location:
    Virginia Beach, VA
    cPanel Access Level:
    DataCenter Provider
    The folder you are running the command from probably does not exist, which is prompting the extraneous errors.

    If you can't log into WHM, have your hold check your reseller permissions and your password.
     
  3. 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:
    An alternative to using "service" is to specify the full path, such as one of the following (both execute the same script as "/etc/init.d" is a symlink to "/etc/rc.d/init.d"):
    Code:
    # /etc/rc.d/init.d/cpanel restart
    # /etc/init.d/cpanel restart
    Does the same output occur when using the following command?
    Code:
    # /usr/local/cpanel/startup
    As Vanessa suggested, your upstream hosting vendor can assist with checking permissions. If the current working directory is indeed non-existent it will help to type "cd" or "cd /" to return to a directory that should exist (e.g., "/root/" or "/") before performing administrative tasks.

    To obtain more information about login failures or other relevant detail I recommend checking log files in the following directory path:
    Code:
    /usr/local/cpanel/logs/
    Here is a command that may be used to monitor log files in the above directory; this should be followed by attempting to access and log-in to WHM so as to reproduce relevant log entries:
    Code:
    # tail -fvn0 /usr/local/cpanel/logs/*log
     
Loading...

Share This Page