Skip to main content

CPANEL-35110 - /proc/stat format changed when using upcp

Comments

7 comments

  • cPRex Jurassic Moderator
    Update - this is scheduled to be fixed in version 98. I'm not entirely sure when that will be released, but it will be later on this year.
    0
  • azadhussnain
    Hello, facing similar error: [root@gravity ~]# /scripts/upcp Stale PID file '/var/run/upcp.pid' (pid=30129) Cpanel::Exception::IO::FileReadError/(XID mmmbwu) The system failed to read from the file "/proc/30167/stat" because of an error: No such file or directory at /usr/local/cpanel/Cpanel/LoadFile.pm line 195. Cpanel::LoadFile::_load_r(CODE(0xbae1d8), "/proc/30167/stat") called at /usr/local/cpanel/Cpanel/LoadFile.pm line 92 Cpanel::LoadFile::load_if_exists("/proc/30167/stat") called at /usr/local/cpanel/Cpanel/UPID.pm line 133 Cpanel::UPID::_get_pid_start_delta(30167) called at /usr/local/cpanel/Cpanel/UPID.pm line 80 Cpanel::UPID::get(30167) called at /scripts/upcp line 851 scripts::upcp::_determine_logfile_path_if_running(30167) called at /scripts/upcp line 223 scripts::upcp::upcp() called at /scripts/upcp line 77 [root@gravity ~]# Cpanel::Exception::IO::FileReadError/(XID gexdwn) The system failed to read from the file "/proc/30167/stat" because of an error: No such file or directory at /usr/local/cpanel/Cpanel/LoadFile.pm line 195. Cpanel::LoadFile::_load_r(CODE(0xbae1d8), "/proc/30167/stat") called at /usr/local/cpanel/Cpanel/LoadFile.pm line 92 Cpanel::LoadFile::load_if_exists("/proc/30167/stat") called at /usr/local/cpanel/Cpanel/UPID.pm line 133 Cpanel::UPID::_get_pid_start_delta(30167) called at /usr/local/cpanel/Cpanel/UPID.pm line 80 Cpanel::UPID::get(30167) called at /scripts/upcp line 851 scripts::upcp::_determine_logfile_path_if_running(30167) called at /scripts/upcp line 247 scripts::upcp::upcp() called at /scripts/upcp line 77
    0
  • cPRex Jurassic Moderator
    @azadhussnain - were you able to try that workaround to see if that resolved the issue?
    0
  • azadhussnain
    I have tried. It does not fix.
    0
  • azadhussnain
    The error was sudden. We ran /scripts/upcp --force a day ago, and then we didn't checked it. Today when we opened ssh and ran /scripts/upcp --force again, we saw this error. Tried the fix but no change in output, getting same error.
    0
  • cPRex Jurassic Moderator
    Do you see any similar errors in /var/log/messages? I don't think this is quite the same issue as the OP, so let's check that other log file to see if there are any I/O errors listed there.
    0

Please sign in to leave a comment.