Why Satellite services remain stopped after a failed offline backup?
Issue
-
After a failed offline backup, Satellite services are not restarted and Satellite is unavailable:
# satellite-maintain backup offline /backup [...] \-------------------------------------------------------------------------------- Backup mongo offline: - Collecting Mongo data [FAIL] Failed executing tar --selinux --create --file=/backup/satellite-backup-2021-03-10-11-17-59/mongo_data.tar --exclude=mongod.lock --listed-incremental=/backup/satellite-backup-2021-03-10-11-17-59/.mongo.snar --transform 's,^,var/lib/mongodb/,S' -S *, exit status 2: tar: /backup/satellite-backup-2021-03-10-11-17-59/mongo_data.tar: Cannot write: No space left on device tar: Error is not recoverable: exiting now \-------------------------------------------------------------------------------- Scenario [Backup] failed. The following steps ended up in failing state: [backup-offline-mongo] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="backup-offline-mongo" The runner is already in quit state# satellite-maintain service status | egrep displaying\|Active / displaying rh-mongodb34-mongod Active: inactive (dead) since Wed 2021-03-10 11:19:20 GMT; 3min 0s ago / displaying postgresql Active: inactive (dead) since Wed 2021-03-10 11:19:13 GMT; 3min 7s ago / displaying qdrouterd Active: inactive (dead) since Wed 2021-03-10 11:19:13 GMT; 3min 7s ago / displaying qpidd Active: inactive (dead) since Wed 2021-03-10 11:19:13 GMT; 3min 7s ago / displaying rh-redis5-redis Active: inactive (dead) since Wed 2021-03-10 11:19:13 GMT; 3min 8s ago / displaying squid Active: inactive (dead) since Wed 2021-03-10 11:19:12 GMT; 3min 8s ago / displaying pulp_celerybeat Active: inactive (dead) since Wed 2021-03-10 11:19:12 GMT; 3min 8s ago / displaying pulp_resource_manager Active: inactive (dead) since Wed 2021-03-10 11:19:11 GMT; 3min 9s ago / displaying pulp_streamer Active: inactive (dead) since Wed 2021-03-10 11:19:07 GMT; 3min 13s ago / displaying pulp_workers Active: inactive (dead) since Wed 2021-03-10 11:19:07 GMT; 3min 13s ago / displaying smart_proxy_dynflow_core Active: inactive (dead) since Wed 2021-03-10 11:19:02 GMT; 3min 18s ago / displaying tomcat Active: inactive (dead) since Wed 2021-03-10 11:19:02 GMT; 3min 18s ago / displaying dynflow-sidekiq@orchestrator Active: inactive (dead) since Wed 2021-03-10 11:19:01 GMT; 3min 19s ago / displaying foreman Active: inactive (dead) since Wed 2021-03-10 11:19:00 GMT; 3min 20s ago / displaying httpd Active: inactive (dead) since Wed 2021-03-10 11:18:59 GMT; 3min 21s ago / displaying puppetserver Active: inactive (dead) since Wed 2021-03-10 11:18:54 GMT; 3min 26s ago / displaying dynflow-sidekiq@worker Active: inactive (dead) since Wed 2021-03-10 11:18:53 GMT; 3min 27s ago / displaying dynflow-sidekiq@worker-hosts-queue Active: inactive (dead) since Wed 2021-03-10 11:18:50 GMT; 3min 30s ago / displaying foreman-proxy Active: inactive (dead) since Wed 2021-03-10 11:18:48 GMT; 3min 32s ago -
Why Satellite services are not restarted after a failed offline backup?
Environment
- Red Hat Satellite 6.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.