Content access via SUSE Manager Proxy returns 404 error

This document (000021343) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager Proxy 4.3

Situation

While accessing content via a SUSE Manager Proxy, requests fail with a HTTP 404 error. Checking /var/log/messages on the proxy shows errors similar to:

[Mon Jan 29 21:40:35.748914 2024] [wsgi:error] [pid 50516] [client CLIENT-IP:47874] SUSE Manager 50516 2024/01/29 21:40:35 +02:00: ('Checksum check failed: CHECKSUMSTRING_IN_FILE != CHECKSUMSTRING_KNOWN_BY_SUSE_MANAGER', "fields = ['system_id', 'os_release', 'operating_system', 'architecture', 'username', 'type']", "attrs = {'username': 'admin', 'os_release': '4.1', 'operating_system': 'sles-release', 'architecture': 'x86_64-redhat-linux', 'system_id': 'ID-SYSTEM', 'type': 'REAL', 'profile_name': 'HOSTNAME', 'description': 'Initial Registration Parameters:\\\\nOS: sles-release\\\\nRelease: 12.1\\\\nCPU Arch: x86_64'}")

Resolution

/etc/sysconfig/rhn/systemid contains an unknown checksum which is used for authentication against SUSE Manager. To resolve this issue, please use the following steps:

spacewalk-proxy stop ; systemctl stop salt-minion
Edit /etc/sysconfig/rhn/systemid and change the checksum value to the value known by SUSE Manager. For example, from the error message in Situation above, change the checksum value from what CHECKSUMSTRING_IN_FILE displays to the value CHECKSUMSTRING_KNOWN_BY_SUSE_MANAGER displays.
systemctl start salt-minion ; spacewalk-proxy start

Cause

The checksum value in /etc/sysconfig/rhn/systemid changed.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.