-----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of m.roth@xxxxxxxxx Sent: Thursday, June 13, 2013 1:04 PM To: General Red Hat Linux discussion list Subject: RE: [rhel - user] backup error message in mail Constance Morris wrote: > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of m.roth@xxxxxxxxx >> Constance Morris wrote: >> >>> Has anyone ever received the following 2 types of backup error >>> messages in their linux mail: >> >> 1.) >> >>> tar: Error exit delayed from previous errors Backup >>> complete...taking CP out of hot backup mode at: Tue May 7 02:54:20 > >> This one reminds me of when either a) the filesystem's full, or b) >> trying to back up something that shouldn't be backed up, like /dev/<anything>... >> or maybe the tarfile it's creating, itself. You might try running it >> manually, and see what happens. > <snip> >> 2.) >> >>>From user@xxxxxxxxxxxxxxxxx Tue Apr 30 05:55:13 2013 >> Date: Tue, 30 Apr 2013 05:55:12 -0400 >>> From: user@xxxxxxxxxxxxxxxxx (Cron Daemon) >>> To: user@xxxxxxxxxxxxxxxxx >>> Subject: Cron <user@portal> /opt/luminis/bin/hotbackoff >>> X-Cron-Env: <SHELL=/bin/sh> >>> X-Cron-Env: <HOME=/home/user> >>> X-Cron-Env: <PATH=/usr/bin:/bin> >>> X-Cron-Env: <LOGNAME=user> >>> X-Cron-Env: <USER=user> >>> System hot backup state has been set to off. >> >>> I've never seen these before. Any suggestions? > >> This clearly has to do with some software that I'm not familiar with, >> or you've got a mirror site, and there's some issue with the mirror. > > On #1. Could any of those things (filesystem file, etc.) cause the > system not to boot back up when it goes down for backups? > Forgive my ignorance - is there a system-wide command for running it > manually? > I did not setup the backups and am not sure how to do that. I see a problem here: when we say "the system is down" it means it's *down*, not running. You're using to mean "some service(s) are down while we do backups". For example, you might say "the d/b system is down while we do backups"... but you can't do anything with a brick, sitting there, which is what a server is when it's down. Please explain what you mean by "not to boot back up". mark -------- Ah, so sorry. Based upon your definition - then I would say I was referring to a service normally available to clients via the web not coming back up (aka: being available to the clients via the web) after going down for the backups. The way our backup is setup I know it takes the services down - backs things up - and then starts the services up. However, I did not know if that error that seems to be happening during backups could cause the server to get hung up and not start the services back up. Am I making sense? Thanks, Constance -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
