Moderator

 • 

2.9K Posts

December 16th, 2025 14:38

Hi, it may related with repo metadata and catalog schema structure changes. I think to reduce stale metadata remove unused repos periodically. 

Moderator

 • 

4.7K Posts

December 12th, 2025 19:32

Hello,

 

The fact that Refresh_11/29/2025 SUCCESS and Refresh_12/06/2025 FAILURE indicates:

DRM was functioning correctly before.

The failure is not due to installation corruption but likely due to catalog data or repository state changes between those dates not a systemic failure.

 

The NullPointerException (getAllComponents() is null) means the comparison report object is empty during refresh.

This usually happens when:

The catalog downloaded on 12/06 was incomplete or corrupted.

The repository being refreshed has no valid components to compare (e.g., empty or misconfigured repository).

Permissions or storage path issues prevented DRM from writing catalog data.

 

Recommended troubleshooting steps

From User Guide below: Page 19–20 (Configure Catalog Settings) and Page 25–26 (Refresh Repository):

  1. Validate Catalog Source
  2. Check Repository Content
    • If the repository is empty or contains unsupported systems, refresh will fail.
    • Use CLI to list repositories:
      drm --list=rep
      drm --details -
      (Page 52–53)
  3. Delete and Re-add Catalog
    drm --delete --catalog=<catalog_id>
    drm --update --catalog=all
    (Page 52–53)
  4. Permissions
    • Confirm drmuser has full access to /opt/dell/dellrepositorymanager/ and /var/dell/drm/log. (Page 63–64)
  5. Logs
    • Check /var/dell/drm/log/drmservice-0.log for catalog download errors. (Page 26, Page 64)
  6. Repair DRM if needed ./Change Dell Repository Manager Installation (Page 43)

 

 

Dell Repository Manager version 3.4.9 User’s Guide

https://dl.dell.com/content/manual44163007-dell-repository-manager-version-3-4-9-user-s-guide.pdf?language=en-us

1 Rookie

 • 

9 Posts

December 16th, 2025 12:51

Hello,

Thanks for your quick reply. Wev'e tried every step from the troubleshooting guide but nothing worked. Out of spite i've made a new repo, again, and this time the refresh/export worked.

It happend a lot, is there any guidelines about why we have to create a new repo everytime to fix the failed refresh ?

Regards

1 Rookie

 • 

9 Posts

December 16th, 2025 14:57

Alright, i've removed every other unused repo. Thanks for your help

No Events found!

Top