HI
I should have taken a look at the logs before asking the question, it appears
that even though it was a standard install, in the /var/log/messages file the
server reported that "Can't exec "/sbin/e-smith/backup":"
on closer inspection the backup program didnt have execute permissions.
Im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
Looking 'quickly' through the source, I don't see anything obvious
that would be incompatible with V 6, yet I did not look at length at
the scripts. I would ask the same question on the Forum list.
Later, I will look closer... Remember the
John Bennett wrote:
Why must we continue with the smart ass responses? All the guy wants is
some help. So, maybe you should tell him that the list is for dev
questions, and to use the forums at contribs.org. Just a thought,
people appreciate kindness.
David,
Sorry if my reply bothered you, it wa
Why must we continue with the smart ass responses? All the guy wants is
some help. So, maybe you should tell him that the list is for dev
questions, and to use the forums at contribs.org. Just a thought,
people appreciate kindness.
David,
I would suggest to you that you do get the 6.0 final co
I know his Backup2ws is not updated for SME 6.0 final and he is away for
holidays until Jan 2,04 so he cannot confirm the other question.
Hsing-Foo Wang <[EMAIL PROTECTED]> said:
> Hi David,
>
> > I have just done an install of an Mitel Networks server 6.0beta3 box with an
> > Adaptec 29160/P SC
Hi David,
I have just done an install of an Mitel Networks server 6.0beta3 box with an
Adaptec 29160/P SCSI Controller card and a Segate STD2401LW DDS-4 20/40Gb Tape
Backup Unit
I guess you should _not_ use any beta's anymore since there is a 6.0 Final.
Next to that, I don't know if Darrell 'de
On Sun, 25 Feb 2001, Darrell May wrote:
> /sbin/e-smith/expand-template /sbin/e-smith/backup
> - or-
> /sbin/e-smith/signal-event console-save
>
> Check the /sbin/e-smith/backup again. Also note the rights
> on the file as I've noticed that sometimes the execute right
> gets dropped. Possible
>
> What is in /var/log/messages?
Mesages is quite large. Anything specific you are looking for???
> What does
>
> mt -f /dev/nst0 status
>
> say?
>
> I'm lookong for details of block size.
[root@Server1 log]# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partiti
On Fri, 16 Feb 2001, Orville Carter wrote:
>
> Here is is!
>
> [root@Server1 /root]# dd if=/dev/random of=/dev/st0 bs=1024
> dd: writing `/dev/st0': Input/output error
> 0+2 records in
> 0+1 records out
> [root@Server1 /root]#
> [root@Server1 /root]# dd if=/dev/st0 of=/dev/null bs=1024
> 0+1 rec
On Fri, 16 Feb 2001, Darrell May wrote:
> If you have not tested your hardware previously, try a taper
> backup to confirm whether it is a hardware or software fault.
> Execute this command to test a taper backup:
>
> /usr/sbin/taper -T scsi
An even simpler test is probably a good idea. The le
I agree with Darrel on this one, your backup is NOT fine, the broken pipe
will have caused the backup to stop there. I get the same thing on the
first backup that I try to do, if I then turn around and run "bash
/sbin/e-smith/backup" again, I get a good backup. I have verified both the
bad sta
>
> Orville, I don't think your backup is fine :( To confirm and
> check what actually got backed up follow this How-TO:
>
> [How to list and view the contents of a tape]
>
> First create a working directory /root/flexbackup with
> the following command:
>
> mkdir /root/flexbackup
>
> To list and
Charlie Brady wrote:
> Sent: Friday, February 16, 2001 9:50 AM
> To: Darrell May
> Cc: 'Orville Carter'; e-smith-Dev
> Subject: RE: [e-smith-devinfo] Tape Backup
> An even simpler test is probably a good idea. The less layers
> of software
> the better, if
o: Orville Carter
> Cc: [EMAIL PROTECTED]
> Subject: Re: [e-smith-devinfo] Tape Backup
>
>
> I agree with Darrel on this one, your backup is NOT fine, the
> broken pipe
> will have caused the backup to stop there. I get the same
> thing on the
> first backup that
Orville Carter wrote:
> This a clip from e-smith 4.1rc3 tape backup notification
> (Cron Daemon). This
> line appears for both
> servers. The tape drives are SCSI. The backup appears to be
> fine. I was just
>
Orville, I don't think your backup is fine :( To confirm and
check what actually go
- Original Message -
>
> On Fri, 16 Feb 2001, Darrell May wrote:
>
> > Charlie Brady wrote:
> > >
> > > mt -f /dev/st0 rewind
> > > dd if=/dev/random of=/dev/st0 bs=1024k
> > > dd of=/dev/st0 of=/dev/null bs=1024k
> > >
> > > If you get an I/O error at anything other then end of tap
After using Taper utilities the backup looks good.
Taper too several hours working on the tape - but it was worth it.
This is the auto backup using the e-smith console settings. Autobackup time:
4:00 am.
I guess we should prepare all tapes with Taper before usingperhaps?
Thanks for the in
On Fri, 16 Feb 2001, Orville Carter wrote:
> My question is on the two lines below. Is this something to be concerned
> about?
>
> DUMP: Broken Pipe
> DUMP: The ENTIRE dump is aborted.
The two lines before the ones you quoted are relevant:
buffer (writer): write of data failed: Input/output er
On Fri, 16 Feb 2001, Darrell May wrote:
> Charlie Brady wrote:
> >
> > mt -f /dev/st0 rewind
> > dd if=/dev/random of=/dev/st0 bs=1024k
> > dd of=/dev/st0 of=/dev/null bs=1024k
> >
> > If you get an I/O error at anything other then end of tape
> > during either
> > dd operation, you have a pr
On Sat, 21 Apr 2001, Lionel Lauer wrote:
> On Fri, 20 Apr 2001 21:06:08 -0400 (EDT), Charlie Brady
> <[EMAIL PROTECTED]> wrote:
>
> >On Sat, 21 Apr 2001, Lionel Lauer wrote:
> >
> >> > buffer: cannot open output file: Read-only file system
> >> > filename: /dev/nst0
> >
> >You are sure that the
Update:
I've just tried SSHing into the server with the problem, & running the
backup manually (/sbin/e-smith/backup) & it worked!
Now I'm really confused. I'll see if tonights cron job works okay, & if
so, I'll start looking for hardware problems.
--
W
. | ,. w , "Some people
On Sat, 21 Apr 2001, Lionel Lauer wrote:
> >All SMP kernels have had trouble with ppp. You have upgraded to the latest
> >ppp RPM?
>
> The system is a dual-CPU motherboard with only one CPU, so I tweaked
> lilo to only boot from the uniprocesser kernel.
Why? The SMP kernel runs fine with one pr
On Sat, 21 Apr 2001, Lionel Lauer wrote:
> > buffer: cannot open output file: Read-only file system
> > filename: /dev/nst0
You are sure that the tape is not write-protected?
Charlie Brady [EMAIL PROTECTED]
http://www.e-smith.org (development) http://www.e-smith.co
On Fri, 20 Apr 2001 22:56:37 -0400 (EDT), Charlie Brady
<[EMAIL PROTECTED]> wrote:
>
>On Sat, 21 Apr 2001, Lionel Lauer wrote:
>
>> >All SMP kernels have had trouble with ppp. You have upgraded to the latest
>> >ppp RPM?
>>
>> The system is a dual-CPU motherboard with only one CPU, so I tweaked
>
On Fri, 20 Apr 2001 21:28:24 -0400 (EDT), Charlie Brady
<[EMAIL PROTECTED]> wrote:
>> Absolutely - that was the first thing I checked. I also tried erasing a
>> tape to ensure that there was no garbage on it that might be confusing
>> the issue. Also, a 'tar -cvf /dev/nst0 /etc', followed by a 't
On Fri, 20 Apr 2001 21:06:08 -0400 (EDT), Charlie Brady
<[EMAIL PROTECTED]> wrote:
>
>On Sat, 21 Apr 2001, Lionel Lauer wrote:
>
>> > buffer: cannot open output file: Read-only file system
>> > filename: /dev/nst0
>
>You are sure that the tape is not write-protected?
Absolutely - that was the fi
Gerald, have a look at your /sbin/e-smith/backup and compare
it to the one shown below. It looks like you have not installed
the latest e-smith-backup-1.2.0-11.noarch.rpm from e-smith.
Go get this update and install it:
rpm -Uvh e-smith-backup-1.2.0-11.noarch.rpm
Then do either a:
/sbin/e-smit
27 matches
Mail list logo
