[Solved] Incorrect "Node not up-to-date"

Discussion in 'ISPConfig 3 Priority Support' started by remkoh, Sep 3, 2025 at 1:53 PM.

  1. remkoh

    remkoh Active Member HowtoForge Supporter

    Several nodes that were still running Ubuntu 22.04 have been upgraded to 24.04.
    All went fine and is still functioning properly except for one thing.

    ISPC panel is saying one node has updates pending but that's not true.
    I've ran "apt update && apt upgrade -y" several times and there are no updates pending.
    Yet in the panel multiple kernel updates are listed as pending.

    How to correct this incorrect info?
     
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    It takes a while, just relax and wait for a bit :) IIRC that info is fetched not that regular.
     
  3. remkoh

    remkoh Active Member HowtoForge Supporter

    I know it takes a while. But not almost 24hrs. That's why I posted now and not shortly after the upgrade.
     
  4. pyte

    pyte Well-Known Member HowtoForge Supporter

    Well you could have mentioned that fact :D

    Does "apt list --upgradable" list anything on the host in question?
     
  5. remkoh

    remkoh Active Member HowtoForge Supporter

    Nothing, as expected.
    Code:
    Listing... Done
    There is only a notification of a few Ubuntu Pro esm-apps security updates when running "apt upgrade".
    But those aren't listed in the panel.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Check the sys_cron table in the dbispconfig database on the affected nodes. Are there any records in the state running? Maybe they got interrupted during update and are hanging now.
     
  7. remkoh

    remkoh Active Member HowtoForge Supporter

    Right on the money! As always :D
    Thanks a million.
     
  8. remkoh

    remkoh Active Member HowtoForge Supporter

    Also on every node "cronjob_monitor_sys_usage" seemed to be hanging since last evening.

    In hindsight not strange at all.
    The node in question with the (no longer) incorrect update status is the master node.
    That node was upgrading around the time "cronjob_monitor_sys_usage" hanged everywhere else.
     

Share This Page