2. Troubleshooting Subscription Asset Manager
2.1. Subscription Asset Manager 1.3
2.1.1. Required Upgrades for Instance-Based Subscription Changes
2.1.2. Common Problems with Enhanced Reporting
- Q: Why are no systems displayed in the report?
- Q: I tried to create a new report, but I got the error Validation failed: A server name has not been defined in the database. The backend splice tool must execute at least one time.
- Q: Why are all systems marked as invalid?
- Q: I updated subscriptions for a system or my Satellite server in Subscription Asset Manager, but those changes are not being reflected in the report.
- Q: The link to the Satellite 5.6 UI in the report results is returning an HTTP 404 error.
- Q: I had other organizations and systems registered with my Subscription Asset Manager server, but they have disappeared from the UI. What happened?
- The information isn't being pulled from the Satellite server.
- The information is being corrupted or improperly formatted when it is sent to the Subscription Asset Manager server.
- The information is not being properly transmitted from Subscription Asset Manager into the reporting database.
- The information is not being properly stored in the database.
- The information stored in Subscription Asset Manager is outdated.
[root@sam-server ~]# service mongod status [root@sam-server ~]# telnet localhost 27017
[root@sam-server ~]# mongo checkin_service --eval "printjson(db.marketing_product_usage.count())"
[root@sam-server ~]# /usr/bin/splice-debug
splice-debug-YYYY-MM-DD-TIME. For example,
spacewalk-splice-checkinutility on the Subscription Asset Manager server pulls the data out of the Satellite server and into the Subscription Asset Manager database. Without that run, there is no Satellite information and the report cannot be set up with the required Satellite server and organizations.
[root@sam-server ~]# su - splice -s /bin/bash [splice@sam-server ~]$ spacewalk-splice-checkin
rhn-searchprocess is running on the Satellite 5.6 machine.