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.

Cpanel error?! I really need help.

Discussion in 'General Discussion' started by BlazeHost, May 15, 2012.

  1. BlazeHost

    BlazeHost Member

    Joined:
    May 4, 2012
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    My cpanel wont load and when I restart it it gives me this.
    Code:
    Stopping tailwatchd:  [2012-05-15 23:49:09 +0400] warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2214] [2012-05-15 23:49:09 +0400] [main] [STOP Ok] 2033 at /usr/local/cpanel/Cpanel/TailWatch.pm line 1015
            Cpanel::TailWatch::panic(Cpanel::TailWatch=HASH(0x9257964), 'Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory\x0A[2214] [2012-05-15 23:49:09 +0400] [main] [STOP Ok] 2033') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 318
            Cpanel::TailWatch::log(Cpanel::TailWatch=HASH(0x9257964), '[STOP Ok] 2033', 1) called at /usr/local/cpanel/Cpanel/TailWatch/Utils/Stop.pm line 40
            Cpanel::TailWatch::stop(Cpanel::TailWatch=HASH(0x9257964)) called at /usr/local/cpanel/libexec/tailwatchd line 47
    warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2214] [2012-05-15 23:49:09 +0400] [main] [STOP Ok] 2033
    Could not initiate log /usr/local/cpanel/logs/tailwatchd_log:  at /usr/local/cpanel/Cpanel/TailWatch/Utils/Stop.pm line 40.
                                                               [FAILED]
    Stopping cPanel services:  Waiting for cpsrvd to shutdown ... ...Done
    Waiting for cpsrvd-ssl to shutdown ... ...Done
    Waiting for whostmgrd to shutdown ... ...Done
                                                               [  OK  ]
    Stopping cPanel dav services:  [Tue May 15 23:49:09 2012] Current process '1984' stopped
    Waiting for cpdavd to shutdown ... ...Done
    Waiting for cpdavd-ssl to shutdown ... ...Done
                                                               [  OK  ]
    Stopping cPanel queue services:  Graceful shutdown of cPanel TaskQueue Daemon requested. complete
                                                               [  OK  ]
    Stopping cPanel brute force detector services:  Waiting for cphulkd.pl to shutdown ... ...Done
    Waiting for cPhulkd to shutdown ... ...Done
    Waiting for cphulkd to shutdown ... ...Done
                                                               [  OK  ]
    Stopping pop3 services:  Waiting for cppop to shutdown ... ...Done
    Waiting for cppop-ssl to shutdown ... ...Done
                                                               [  OK  ]
    Stopping cPanel log services:                              [  OK  ]
    Stopping cPanel Chat services:                             [FAILED]
    Stopping InterChange services:                             [FAILED]
    Stopping cPanel ssl services:                              [  OK  ]
    Stopping mailman services:  Shutting down Mailman's master qrunner
    PID unreadable in: /usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid
    [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid'
    Is qrunner even running?
    mailmanctl: no process killed
    Starting cPanel services: Waiting for cpsrvd to shutdown ... ...Done
    Waiting for cpsrvd-ssl to shutdown ... ...Done
    Waiting for whostmgrd to shutdown ... ...Done
    Starting cpsrvd.
                                                               [  OK  ]
    Starting cPanel brute force detector services:             [  OK  ]
    Starting cPanel dav services:                              [  OK  ]
    Starting pop3 services: Waiting for cppop to shutdown ... ...Done
    Waiting for cppop-ssl to shutdown ... ...Done
                                                               [  OK  ]
    Starting cPanel Chat services:
    
    Starting cPanel ssl services: Using Native SSL support (stunnel not needed)
                                                               [  OK  ]
    Starting cPanel Queue services:                            [  OK  ]
    Starting tailwatchd: [2012-05-15 23:49:29 +0400] warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:29 +0400] [Cpanel::TailWatch] [INFO] Configured to conserve memory; skipped load of Linux::Inotify2. at /usr/local/cpanel/Cpanel/TailWatch.pm line 1015
            Cpanel::TailWatch::panic(Cpanel::TailWatch=HASH(0x81969b8), 'Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory\x0A[2373] [2012-05-15 23:49:29 +0400] [Cpanel::TailWatch] [INFO] Configured to conserve memory; skipped load of Linux::Inotify2.') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 318
            Cpanel::TailWatch::log(Cpanel::TailWatch=HASH(0x81969b8), '[INFO] Configured to conserve memory; skipped load of Linux::Inotify2.') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 1026
            Cpanel::TailWatch::info(Cpanel::TailWatch=HASH(0x81969b8), 'Configured to conserve memory; skipped load of Linux::Inotify2.') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 131
            Cpanel::TailWatch::new('Cpanel::TailWatch') called at /usr/local/cpanel/libexec/tailwatch/tailwatchd line 23
    warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:29 +0400] [Cpanel::TailWatch] [INFO] Configured to conserve memory; skipped load of Linux::Inotify2.
    [2012-05-15 23:49:30 +0400] warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch::Eximstats] Loading email sending limits from 1337108400 - 1337112000 at /usr/local/cpanel/Cpanel/TailWatch.pm line 1015
            Cpanel::TailWatch::panic(Cpanel::TailWatch=HASH(0x81969b8), 'Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory\x0A[2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch::Eximstats] Loading email sending limits from 1337108400 - 1337112000') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 318
            Cpanel::TailWatch::log(Cpanel::TailWatch=HASH(0x81969b8), 'Loading email sending limits from 1337108400 - 1337112000') called at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 1162
            Cpanel::TailWatch::Eximstats::_setup_email_limits_data(Cpanel::TailWatch::Eximstats=HASH(0x8371e10)) called at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 1080
            Cpanel::TailWatch::Eximstats::_validate_email_limits_data(Cpanel::TailWatch::Eximstats=HASH(0x8371e10)) called at /usr/local/cpanel/Cpanel/TailWatch/Eximstats.pm line 110
            Cpanel::TailWatch::Eximstats::new('Cpanel::TailWatch::Eximstats', Cpanel::TailWatch=HASH(0x81969b8)) called at /usr/local/cpanel/Cpanel/TailWatch.pm line 1117
            eval {...} called at /usr/local/cpanel/Cpanel/TailWatch.pm line 1117
            Cpanel::TailWatch::_load_module(Cpanel::TailWatch=HASH(0x81969b8), 'Eximstats') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 171
            Cpanel::TailWatch::new('Cpanel::TailWatch') called at /usr/local/cpanel/libexec/tailwatch/tailwatchd line 23
    warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch::Eximstats] Loading email sending limits from 1337108400 - 1337112000
    
    !!
    ATTENTION ATTENTION ATTENTION ATTENTION
    
    Cpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.
    
    When mysql is unable to execute a query they are logged for processing later.
    
    Eventually these SQL files may be handled automatically and this message will not appear.
    
    In the meantime you can execute the queries as root with something like this:
    
      mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy
      /scripts/restartsrv_tailwatchd
      mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    Once you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    
    ATTENTION ATTENTION ATTENTION ATTENTION
    !!
    
    [2012-05-15 23:49:30 +0400] warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch]
    !!
    ATTENTION ATTENTION ATTENTION ATTENTION
    
    Cpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.
    
    When mysql is unable to execute a query they are logged for processing later.
    
    Eventually these SQL files may be handled automatically and this message will not appear.
    
    In the meantime you can execute the queries as root with something like this:
    
      mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy
      /scripts/restartsrv_tailwatchd
      mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    Once you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    
    ATTENTION ATTENTION ATTENTION ATTENTION
    !!
    
     at /usr/local/cpanel/Cpanel/TailWatch.pm line 1015
            Cpanel::TailWatch::panic(Cpanel::TailWatch=HASH(0x81969b8), 'Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory\x0A[2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch] \x0A!!\x0AATTENTION ATTENTION ATTENTION ATTENTION \x0A\x0ACpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.\x0A\x0AWhen mysql is unable to execute a query they are logged for processing later.\x0A\x0AEventually these SQL files may be handled automatically and this message will not appear.\x0A\x0AIn the meantime you can execute the queries as root with something like this:\x0A\x0A  mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A  /scripts/restartsrv_tailwatchd\x0A  mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A\x0AOnce you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A\x0A\x0AATTENTION ATTENTION ATTENTION ATTENTION \x0A!!\x0A\x0A') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 318
            Cpanel::TailWatch::log(Cpanel::TailWatch=HASH(0x81969b8), '\x0A!!\x0AATTENTION ATTENTION ATTENTION ATTENTION \x0A\x0ACpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.\x0A\x0AWhen mysql is unable to execute a query they are logged for processing later.\x0A\x0AEventually these SQL files may be handled automatically and this message will not appear.\x0A\x0AIn the meantime you can execute the queries as root with something like this:\x0A\x0A  mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A  /scripts/restartsrv_tailwatchd\x0A  mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A\x0AOnce you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A\x0A\x0AATTENTION ATTENTION ATTENTION ATTENTION \x0A!!\x0A\x0A') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 267
            Cpanel::TailWatch::alert(Cpanel::TailWatch=HASH(0x81969b8), 'Cpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.\x0A\x0AWhen mysql is unable to execute a query they are logged for processing later.\x0A\x0AEventually these SQL files may be handled automatically and this message will not appear.\x0A\x0AIn the meantime you can execute the queries as root with something like this:\x0A\x0A  mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A  /scripts/restartsrv_tailwatchd\x0A  mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A\x0AOnce you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy\x0A') called at /usr/local/cpanel/Cpanel/TailWatch.pm line 213
            Cpanel::TailWatch::new('Cpanel::TailWatch') called at /usr/local/cpanel/libexec/tailwatch/tailwatchd line 23
    warn [tailwatchd] Failed to open /usr/local/cpanel/logs/tailwatchd_log in append mode: No such file or directory
    [2373] [2012-05-15 23:49:30 +0400] [Cpanel::TailWatch]
    !!
    ATTENTION ATTENTION ATTENTION ATTENTION
    
    Cpanel::TailWatch::Eximstats appears to have unprocessed SQL in /var/cpanel/sql/eximstats.sql.
    
    When mysql is unable to execute a query they are logged for processing later.
    
    Eventually these SQL files may be handled automatically and this message will not appear.
    
    In the meantime you can execute the queries as root with something like this:
    
      mv /var/cpanel/sql/eximstats.sql /var/cpanel/sql/eximstats.sql.tmp_working_copy
      /scripts/restartsrv_tailwatchd
      mysql eximstats < /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    Once you are sure all is well you can remove /var/cpanel/sql/eximstats.sql.tmp_working_copy
    
    
    ATTENTION ATTENTION ATTENTION ATTENTION
    !!
    
    
    [Tue May 15 23:49:30 2012] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon
    Log is at /usr/local/cpanel/logs/tailwatchd_log
                                                               [  OK  ]
    Starting cPanel Log services: ==> cPanel Log Daemon version 25.0
                                                               [  OK  ]
    Starting mailman services:                                 [  OK  ]
    root@nl [~]# Could not open stats_log (/usr/local/cpanel/logs/stats_log) for writing! at /usr/local/cpanel/libexec/cpanellogd line 65.
    
    
    
     
  2. BlazeHost

    BlazeHost Member

    Joined:
    May 4, 2012
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    It now gives me this error on cpanel
    Internal Server Error

    Can't use an undefined value as filehandle reference at /usr/local/cpanel/Cpanel/LegacyLogin.pm line 148.

    at /usr/local/cpanel/Cpanel/LegacyLogin.pm line 148
    Cpanel::LegacyLogin::login('IO::Socket::SSL=GLOB(0x94fa4dc)', 'cpanel', 'goto_uri', '/', 'dest_uri', '/', 'user', undef, ...) called at cpsrvd-ssl line 8127
    main::process_legacy_login('login', 'IO::Socket::SSL=GLOB(0x94fa4dc)', 'cpanel', 'goto_uri', '/', 'dest_uri', '/', 'user', ...) called at cpsrvd-ssl line 2640
    main::badpass() called at cpsrvd-ssl line 4721
    main::handle_auth() called at cpsrvd-ssl line 993
    main::handle_one_connection() called at cpsrvd-ssl line 863
     
  3. ChrisRHS

    ChrisRHS Well-Known Member

    Joined:
    Jul 12, 2006
    Messages:
    292
    Likes Received:
    5
    Trophy Points:
    18
    Hello there,

    Have you tried to force an update?

    Code:
    /scripts/upcp --force
    
    Chris
     
  4. BlazeHost

    BlazeHost Member

    Joined:
    May 4, 2012
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Yes thanks so much man!
     
  5. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Also, if you see an error about /usr/local/cpanel/logs/tailwatchd_log not existing, please check if the file exists for anyone else who ever sees such an error:

    Code:
    ls -lah /usr/local/cpanel/logs/
    I've seen people move /usr/local/cpanel to another partition and symlink it back to /usr/local/cpanel, which can then cause major errors to occur.
     
  6. pjssms

    pjssms Member

    Joined:
    Mar 24, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    I am having the same issue and the /scripts/upcp --force is not working.


    => Log opened from /scripts/upcp at Wed Jun 20 19:56:45 2012
    [20120620.195645] Detected cron=0 (Terminal detected)
    [20120620.195645] mtime on upcp is 1338866195 (Tue Jun 5 04:16:35 2012)
    => Log closed Wed Jun 20 19:56:45 2012
    [20120620.195645] E Running `/usr/local/cpanel/scripts/updatenow --upcp --log=/var/cpanel/updatelogs/update.1340218605.log --force` failed, exited with code 512

    What else can i try ?

    Thank you,

    Paulo Santos
     
  7. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Is /usr/local/cpanel moved elsewhere and symlinked? Otherwise, two errors were mentioned in this thread in two different posts, which error are you specifically receiving?
     
Loading...

Share This Page