[Solved] Still Showing Ubuntu 18

Discussion in 'General' started by ahrasis, Mar 12, 2021.

  1. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    My Server OS is Ubuntu 20.04.2 and ISPConfig is 3.2.3
    Code:
    [email protected]:~# lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description:    Ubuntu 20.04.2 LTS
    Release:        20.04
    Codename:       focal
    
    The OS is wrongly displayed as Ubuntu 18.04 in Monitor > Overview:
    Screenshot 2021-03-12 070020.png

    Could it be Ubuntu upgrade bug or ISPConfig doesn't properly detect this?
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    How long has this server been on Ubuntu 20.04? It might need some time to detect this.
     
  3. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    I upgraded in October 2020 when Ubuntu 20.04.1 was released. Can you suggest any way that I could find fault on my server with regard to this?
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    What is the output of
    Code:
    cat /etc/os-release
    ?
     
  5. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    And what is the output of
    Code:
    php /usr/local/ispconfig/server/cron_debug.php --cronjob=100-monitor_os_version.inc.php
    ?

    Is it changed after running this?
     
  6. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Code:
    [email protected]:~# cat /etc/os-release
    NAME="Ubuntu"
    VERSION="20.04.2 LTS (Focal Fossa)"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu 20.04.2 LTS"
    VERSION_ID="20.04"
    HOME_URL="https://www.ubuntu.com/"
    SUPPORT_URL="https://help.ubuntu.com/"
    BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
    PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
    VERSION_CODENAME=focal
    UBUNTU_CODENAME=focal
    
    Nope. Not changed after running php command as instructed, but to note, I have a bunch of these errors in ispconfig cron.log:
    Code:
    Cannot declare class cronjob_monitor_kernel_version, because the name is already in use in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_kernel_version.php on line 31
     
  7. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Weird... what is the output of
    Code:
    grep -R "cronjob_monitor_kernel_version" /usr/local/ispconfig
     
  8. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Sorry. Meeting with friends. To update, monitor page is now fixed but cron.log still reporting the same error again and again. Below is the latest line appearing like after every 2-3 minutes.
    Code:
    Sat 13 Mar 2021 08:24:01 PM +08 PHP Fatal error:  Cannot declare class cronjob_monitor_kernel_version, because the name is already in use in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_kernel_version.php on line 31
    Sat 13 Mar 2021 08:24:01 PM +08 finished server.php.
    
    Here are the outputs:
    Code:
    [email protected]:~# grep -R "cronjob_monitor_kernel_version" /usr/local/ispconfig
    /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_kernel_version.inc.php:class cronjob_monitor_kernel_version extends cronjob {
    /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_kernel_version.php:class cronjob_monitor_kernel_version extends cronjob {
    grep: /usr/local/ispconfig/server/conf-custom/conf-custom: No such file or directory
    
     
  9. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    This file should not exist:
    /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_kernel_version.php

    (note the missing .inc)

    I see you added the file to the stable branch 2 years ago, perhaps you accidentally created it without .inc aswell?
     
  10. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    Ok. That's the fault. Thank you for finding it.

    I think I could have created a copy for testing some improvements in ISPConfig monitoring system but failed to clean up properly. Didn't check the cron.log before as everything was working fine.
     

Share This Page