be labeled
Amreport picks up all the lines and the final mail can become quite
large (send-amreport-on all).
Here is a relevant excerpt from the logfile. Let me now if you need any
debug logs. A simplified amanda.conf is attached.
PART taper "ST:ptxhamdaily" "POOL:ptxhamdaily&qu
7 10:21 AM, Luc Lalonde wrote:
Hey folks,
This is a weird error mesage:
amreport: ERROR error: the mailer '/bin/Mail': No such file or directory
Why the capital 'M'? It should be '/bin/mail':
[root@backupserver ~]# ls -la /bin/mail
lrwxrwxrwx 1 root root 5 Nov
Hey folks,
This is a weird error mesage:
amreport: ERROR error: the mailer '/bin/Mail': No such file or directory
Why the capital 'M'? It should be '/bin/mail':
[root@backupserver ~]# ls -la /bin/mail
lrwxrwxrwx 1 root root 5 Nov 8 07:24 /bin/mail -> m
On Tue, Apr 26, 2016 at 12:48 PM, Chris Nighswonger <
cnighswon...@foundations.edu> wrote:
> So the Quantum tech had me run a device health test on the drive using
> their xTalk utility. The drive failed with some sort of comm error similar
> to what Amanda was seeing. So he then had me clean the
On Tue, Apr 19, 2016 at 11:35 AM, Alan Hodgson
wrote:
> On Tuesday, April 19, 2016 09:57:32 AM Chris Nighswonger wrote:
> > I attempted Alan's suggestion and dd'd to the tape. /dev/md0 is > 130G
> and
> > dd borked almost immediately:
> >
> > root@scriptor:/home/manager dd if=/dev/md0 of=/dev/st0
On Tuesday, April 19, 2016 09:57:32 AM Chris Nighswonger wrote:
> I attempted Alan's suggestion and dd'd to the tape. /dev/md0 is > 130G and
> dd borked almost immediately:
>
> root@scriptor:/home/manager dd if=/dev/md0 of=/dev/st0
> dd: writing to ‘/dev/st0’: Input/output error
> 3+0 records in
>
I attempted Alan's suggestion and dd'd to the tape. /dev/md0 is > 130G and
dd borked almost immediately:
root@scriptor:/home/manager dd if=/dev/md0 of=/dev/st0
dd: writing to ‘/dev/st0’: Input/output error
3+0 records in
2+0 records out
1024 bytes (1.0 kB) copied, 15.2882 s, 0.1 kB/s
Funny thing
Well, perhaps it is a bad device. A run of amflush CONFIG resulted in
another failure:
Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper:
Quantum-Superloader3-LTO-V4: updating state
Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper:
Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
On Fri, Apr 15, 2016 at 11:17 AM, Alan Hodgson
wrote:
> On Friday, April 15, 2016 09:31:26 AM you wrote:
> > I'm trying to figure out how a LTO4 tape was filled up by 32k of data
> > or am I missing something here?
> >
>
> Any time I've started getting premature end-of-tape it has been becaus
On Fri, Apr 15, 2016 at 11:24 AM, Jean-Louis Martineau <
jmartin...@carbonite.com> wrote:
> On 15/04/16 11:15 AM, Chris Nighswonger wrote:
>
>> warning: Got EIO
>>
> What can amanda do when it get an EIO?
> Check system log for error.
> Amanda require a non-rewing device, you must use /dev/nst0 in
On Friday, April 15, 2016 09:31:26 AM you wrote:
> I'm trying to figure out how a LTO4 tape was filled up by 32k of data
> or am I missing something here?
>
Any time I've started getting premature end-of-tape it has been because the
drive is malfunctioning. Try a few times with just dd on a
On Fri, Apr 15, 2016 at 10:21 AM, Jean-Louis Martineau <
jmartin...@carbonite.com> wrote:
> Which version of amanda are you using?
>
3.3.3 (on Ubuntu 14.04.4 LTS)
> Any other error message in the report?
>
none
What is the setting of max-dle-by-volume?
>
>
amgetconf CONFIG max-dle-by-volum
Strange goings on here. amreport says:
---
These dumps were to tape campus-NGH873L4.
Not using all tapes because 1 tapes filled; runtapes=1 does not allow
additional tapes.
There are 112130560k of dumps left in the holding disk.
They will be flushed on the next run
Hi,
ok, amreport now works if I use it at commandline, but amdump didnt found the
tapes tonight. In the taper debug log I found:
/Thu Jul 4 22:00:28 2013: thd-0x2406c00: taper: Slot {372,372} with label do
not
match labelstr/
/Thu Jul 4 22:00:28 2013: thd-0x2406c00: taper: warning: Use of
On 07/05/2013 04:21 AM, Dennis Benndorf wrote:
It seems to me that it broke tonight, but amstatus shows me that some
dles were flushed. Attached the taper debug file.
Some dles where flushed. Amanda wrote to a tape and failed to unload it.
It looks like your library is slower than the defa
On 07/04/2013 08:16 AM, Dennis Benndorf wrote:
Hi,
amreport seems to have a problem with my labelstring while amcheck
does not:
amanda@dl380-54:~$ amreport mirror
Hostname: dl380-54
Org : Tagesbackup
Config : mirror
Date : July 3, 2013
These dumps were to tapes {D00224,D00224}, {D00231
Hi,
amreport seems to have a problem with my labelstring while amcheck does not:
/amanda@dl380-54:~$ amreport mirror/
/Hostname: dl380-54/
/Org : Tagesbackup/
/Config : mirror/
/Date: July 3, 2013/
/These dumps were to tapes {D00224,D00224}, {D00231,D00231},
{D00249,D00249}./
/There
On 10/19/2012 01:12 PM, Jean-Francois Malouin wrote:
* Jean-Louis Martineau [20121019 12:39]:
Jean-Francois,
I already committed many fixes that should improve it a lot.
There are still some case where it will report too much time
(waiting for the driver or operating the changers), they are on
t; >jf
> >
> >* Jean-Francois Malouin [20121005
> >15:11]:
> >>Hi,
> >>
> >>Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that
> >>I reported back in summer 2010 when I upgraded to 3.1.1: amreport
> >>taper stats
.
Jean-Louis
On 10/18/2012 05:54 PM, Jean-Francois Malouin wrote:
No takers on this one?
jf
* Jean-Francois Malouin [20121005
15:11]:
Hi,
Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that
I reported back in summer 2010 when I upgraded to 3.1.1: amreport
taper stats are not
No takers on this one?
jf
* Jean-Francois Malouin [20121005
15:11]:
> Hi,
>
> Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that
> I reported back in summer 2010 when I upgraded to 3.1.1: amreport
> taper stats are not indicative of the real tape performance
Hi,
Just upgraded to 3.3.2 from 3.3.0 and I noticed the same problem that
I reported back in summer 2010 when I upgraded to 3.1.1: amreport
taper stats are not indicative of the real tape performance when
flushing parameters are in effect.
3.3.0 didn't have this problem btw.
I'm
Running Ubuntu server 10.10 and Amanda 3.1.0
Can anyone comment on what I am seeing in /var/log/messages...?
Mar 2 10:51:03 rmt170 kernel: [440414.140671] amreport[9516]: segfault at 0 ip b7705755 sp bf857cf8 error 4 in
libc-2.12.1.so[b7691000+157000]
Greetings;
I just went back over the printouts and nothing is correct for a 3744 run,
but the svn 3740 printouts are fine.
However, backing up to 3.2.1-svn3740 does not fix an amreport return, so
I'd have to presume that the amdump.1 logfile its working from is also
borked.
--
Cheers,
On Mon, Oct 4, 2010 at 1:59 AM, Gunnarsson, Gunnar
wrote:
> Yes I hope so. What version should I go for ?
This - or rather a version improved by Jean-Louis' suggestion to print
the more precise "flush successfully retried" - will be in the next
3.2.0 beta, which we're considering releasing midwee
Incidentally, I can't help but notice that you're backing up disks
named /var/amanda/amandatapes/ems/slotNN. Will amvault be able to
help you out? If so, could you find some time to test it before I set
sail in a week and a half?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Yes I hope so. What version should I go for ?
Thanks Gunnar Gunnarsson
>Incidentally, I can't help but notice that you're backing up disks named
>/var/amanda/amandatapes/ems/slotNN. >>Will amvault be able to help you out?
>If so, could you find some time to test it before I set sail in a week
On Sun, Oct 3, 2010 at 1:46 PM, Gunnarsson, Gunnar
wrote:
> Yes this is much better - log is attached.
Fixed up in
http://github.com/djmitche/amanda/commit/z12092.patch
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Sun, Oct 3, 2010 at 10:26 AM, Gunnarsson, Gunnar <
gunnar.gunnars...@svk.se> wrote:
> It is reported as failed see below and those parts are added twice -
> filesystem 66 parts 68.
> In earlier version it is reported correctly.
>
Perhaps this is a change in behavior, but I think that this vers
It is reported as failed see below and those parts are added twice - filesystem
66 parts 68.
In earlier version it is reported correctly.
These dumps were to tapes HANSA-ARKIVE-9, HANSA-ARKIVE-10, HANSA-ARKIVE-11.
The next 4 tapes Amanda expects to use are: HANSA-ARKIVE-12, HANSA-ARKIVE-13,
HAN
On Sun, Oct 3, 2010 at 7:22 AM, Gunnarsson, Gunnar
wrote:
> I upgraded Amanda version from 2.6.1 to 3.1.2 and amreport reports:
...
> But they are written on the next tape, I'm not using tape spanning.
OK .. so what's the problem?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Hi,
I upgraded Amanda version from 2.6.1 to 3.1.2 and amreport reports:
FAILURE DUMP SUMMARY:
hansabck /var/amanda/amandatapes/ems1/slot13 lev 0 partial taper: No space
left on device
hansabck /var/amanda/amandatapes/ems1/slot65 lev 0 partial taper: No space
left on device
But they are
On Mon, Sep 20, 2010 at 6:56 PM, Jon LaBadie wrote:
> Looks better to my eye. Any one else?
With Jean-Louis' review, committed in r3428. Thanks!
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Mon, Sep 20, 2010 at 04:22:34PM -0500, Dustin J. Mitchell wrote:
> On Thu, Sep 16, 2010 at 4:52 PM, Dustin J. Mitchell wrote:
> > Are you working on this? ??Perhaps someone else on the list can jump in?
>
> Hmm, well, I just took care of this:
>
> http://github.com/djmitche/amanda/commit/z1
On Thu, Sep 16, 2010 at 4:52 PM, Dustin J. Mitchell wrote:
> Are you working on this? Perhaps someone else on the list can jump in?
Hmm, well, I just took care of this:
http://github.com/djmitche/amanda/commit/z11908.patch
Total Full Incr. Level:#
On Thu, Sep 9, 2010 at 11:05 PM, Dustin J. Mitchell wrote:
> I don't mean to put you on the spot - like I said, I can take care of
> this if you'd prefer.
Are you working on this? Perhaps someone else on the list can jump in?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Thu, Sep 9, 2010 at 10:26 PM, Jon LaBadie wrote:
> First, what I call a DLE is refered to as Filesystem some places and
> disk others.
>
> Second I don't like the repeating extra column headings printed 3
> times after the Incr. column. The headings should be moved to the
> top and the unneces
prefer, to let me know what's bugging you. Bonus points for
> also supplying a patch, but that's not at all required!
>
> Note that I do reserve the right to say, "actually, that's
> complicated" (and explain why).
Ok, here is an easy one for you; or some
Hi,
ok thats my fault, amreport moans, but it sinks in the strange messages (think
it has to be a failure)
/-- /backups/mysqlbackups lev 1 STRANGE
? Script 'mysqlbackup.sh' command 'PRE-DLE-BACKUP': sendbackup: error [exec
/usr/lib/amanda/application/mysqlbackup
a "0 MB dump
size" in amreport.
This is my config:
define script-tool mysql-backup {
comment "Mysql-Dump"
plugin "mysqlbackup.sh"
execute_on pre-dle-backup,post-dle-backup
execute_where client # or client
}
define dumptype mysql-tar {
global
progr
On Wed, Oct 21, 2009 at 4:07 PM, Stefan G. Weichinger wrote:
> As Dustin asks for post-processing ...
>
> One thing that I would like to see would be some kind of meta-tool:
>
> I monitor some dozens of amanda-installations which are hard to track,
> as data volumes change and everything is in mov
provides. We recognize that we'll
never have a report format that suits everyone's needs (the current
amreport is the best we've got), so this XML output is intended to
enable per-site customized post-processing by your own tools.
In particular, it sounds like you're interested
Paul Mantz schrieb:
> I'd be glad to explain. I'm working on a general update and rewrite
> of amreport in Perl.
Big welcome to that ...
> One of the components of this rewrite is xml
> output for better monitoring by other programs.
>
> I've been working
I'm curious whether anyone is post-processing either trace logs or
amreport output to generate statistics, and if so, if this XML report
gives you the information you need.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
I'm working on a general update and rewrite
of amreport in Perl. One of the components of this rewrite is xml
output for better monitoring by other programs.
I've been working on an abstraction of the logfile data that amreport
reads, and it's available in the repository already
Paul Mantz schrieb:
> hello everyone,
>
> I've prepared a few examples of amreport xml output, filtered through
> xmllint for readability's sake. These were prepared using the test
> cases found in installcheck/Amanda_Report.pl . I'd like to know what
> you thi
hello everyone,
I've prepared a few examples of amreport xml output, filtered through
xmllint for readability's sake. These were prepared using the test
cases found in installcheck/Amanda_Report.pl . I'd like to know what
you think; what you like, what should be changed, etc. o
On Thu, Nov 06, 2008 at 03:08:21PM -0500, Jean-Francois Malouin wrote:
> Hello,
>
> With faster tape drives it is not uncommon to get taper transfer rates
> above 100MiBs. amreport will then fill the entry "Avg Tp Write Rate
> (k/s)" with '#.#' as reporter.
Hello,
With faster tape drives it is not uncommon to get taper transfer rates
above 100MiBs. amreport will then fill the entry "Avg Tp Write Rate
(k/s)" with '#.#' as reporter.c shows at line 821 for 2.6.0p2. My
great programming skills do not allow me to fix this si
On Sat, Oct 11, 2008 at 3:41 PM, Kirk Strauser <[EMAIL PROTECTED]> wrote:
> Dustin J. Mitchell wrote:
>
>> Does "Mail" itself work properly from the command-line?
>
> Sure. I even tested it by piping "echo foo" into the same command line that
> amre
Dustin J. Mitchell wrote:
Does "Mail" itself work properly from the command-line?
Sure. I even tested it by piping "echo foo" into the same command line
that amreport was running.
On Wed, Oct 8, 2008 at 10:27 PM, Kirk Strauser <[EMAIL PROTECTED]> wrote:
> Any idea why Mail would be hanging for amreport? This is on a busyish home
> server that delivers lots of mail daily, so I'm 99.9% sure it's not because
> of problems with the mail system.
?? I 9:14PM 0:00.03
amreport Daily
operator 13599 0.0 0.0 7048 1412 ?? I 9:14PM 0:00.00 sh
-c /usr/bin/Mail -s "Daily
operator 13600 0.0 0.0 4564 1088 ?? I 9:14PM 0:00.00
/usr/bin/Mail -s DailySet1 AM
It will stay like that until I kill the Mail proces
On Sun, Jun 29, 2008 at 7:46 PM, Jukka Salmi <[EMAIL PROTECTED]> wrote:
> The attached patch fixes the problem for me, but I doubt it's the
> correct way to do it...
Well, what works, works, I suppose, and you're welcome to add that to
pkgsrc. From my perspective, I'd prefer that you get this bui
Dustin J. Mitchell --> amanda-users (2008-06-29 14:22:16 -0400):
> I would remove the "#ifdef HAVE_ALLOCA_H" from amanda.h and just
> unconditionally include alloca.h.
Hmm, the problem was that there is no alloca.h on my systems, so this
won't work ;-)
The attached patch fixes the problem for me,
On Sun, Jun 29, 2008 at 10:40 AM, Jukka Salmi <[EMAIL PROTECTED]> wrote:
>> found in the system, create a local copy of the file. I think that
>> the compiler wasn't finding it because the amflock tests didn't
> ^^
> I assume with "it" you mean the "local copy of the f
Dustin J. Mitchell --> amanda-users (2008-06-28 13:53:43 -0400):
> Actually, it's not quite "wrong." Gnulib is a little weird. What the
> rest of that macro does is to *check* for alloca.h, and if it's not
> found in the system, create a local copy of the file. I think that
> the compiler wasn't
On Sat, Jun 28, 2008 at 1:05 PM, Jukka Salmi <[EMAIL PROTECTED]> wrote:
> I'm not familiar with the autotools and with m4, but AFAICT the source
> of this problem is in config/gnulib/alloca.m4. The resulting `configure'
> script unconditionally defines HAVE_ALLOCA_H which is obviously wrong.
Actua
Dustin J. Mitchell --> amanda-users (2008-06-27 13:56:06 -0400):
> On Thu, Jun 26, 2008 at 11:34 AM, Jukka Salmi <[EMAIL PROTECTED]> wrote:
> > This is on NetBSD/i386 where at least fcntl, flock and lockf are
> > available; config.log reveals that the record locking function tests
> > failed becaus
On Thu, Jun 26, 2008 at 11:34 AM, Jukka Salmi <[EMAIL PROTECTED]> wrote:
> This is on NetBSD/i386 where at least fcntl, flock and lockf are
> available; config.log reveals that the record locking function tests
> failed because HAVE_ALLOCA_H was defined but there's no alloca.h on
> my system.
We h
Jukka Salmi wrote:
What about using record locking on a file in the logdir (maybe on the
logfile itself)? I.e. making sure that all involved processes always
acquire an exclusive lock, then write the log and afterwards release
the lock?
Amanda already lock the 'log' file.
But why it is not w
Jean-Louis Martineau --> amanda-users (2008-06-26 10:12:11 -0400):
> Amanda lock the file while writing to it.
> What is the output of: amadmin vv version | grep LOCKING
> Which filesystem is used, is it NFS mounted?
Hmm, amadmin reveals that
LOCKING=**NONE**
on my system, which probably
Dustin J. Mitchell --> amanda-users (2008-06-26 10:11:54 -0400):
[...]
> Unfortunately, that file is basically the intermingled freeform stderr
> of just about every process spawned by amdump/amflush, so there's no
> single interface through which we can funnel all notifications. The
> long-term p
rom 2.4.4p4 to 2.5.2p1, backup
reports always contain lines like these:
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR unexpected log line: 20080625 2 [sec 45.227 kb 41655 kps
921.7]
amreport: ERROR unexpected log line: 20080625 0 [sec 35.747 kb 67281 kps
1883.0]
The log file which causes th
, note that these are the amdump logs,
which are only used by amreport and amstatus, and not the trace logs,
which form Amanda's catalog. Trace logs are only written by a single
process, so they won't see this kind of overlap. (See
http://wiki.zmanda.com/index.php/Log_Files for the types
Jukka Salmi --> amanda-users (2008-06-25 12:37:15 +0200):
> Hello,
>
> since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup
> reports always contain lines like these:
>
> FAILURE AND STRANGE DUMP SUMMARY:
> amreport: ERROR unexpected log line: 2008062
Hello,
since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup
reports always contain lines like these:
FAILURE AND STRANGE DUMP SUMMARY:
amreport: ERROR unexpected log line: 20080625 2 [sec 45.227 kb 41655 kps
921.7]
amreport: ERROR unexpected log line: 20080625 0 [sec
rding
to amdump.1 this is what happens:
amdump: end at Wed Apr 2 01:57:12 WEST 2008
Invalid or incomplete multibyte or wide character
. . . message not sent.
"/data/amanda/dead.letter" 324/19378
amreport: mail command failed: /usr/bin/Mail -s "ISR1 AMANDA MAIL
REPORT FO
Hello,
from some time now amanda has refused to send me mails. According to
amdump.1 this is what happens:
amdump: end at Wed Apr 2 01:57:12 WEST 2008
Invalid or incomplete multibyte or wide character
. . . message not sent.
"/data/amanda/dead.letter" 324/19378
amreport: mail comm
Paul Bijnens wrote:
On 2008-02-14 09:56, Theodotos Andreou wrote:
Since a month ago I have the following problem appearing:
When amdump is completed amreport takes long to complete. When it
finally finishes it won't send any mail. Running amreport manually
results in a mail with su
On 2008-02-14 09:56, Theodotos Andreou wrote:
Since a month ago I have the following problem appearing:
When amdump is completed amreport takes long to complete. When it
finally finishes it won't send any mail. Running amreport manually
results in a mail with subject:
It takes so
Since a month ago I have the following problem appearing:
When amdump is completed amreport takes long to complete. When it
finally finishes it won't send any mail. Running amreport manually
results in a mail with subject:
Org DailyJob AMANDA MAIL REPORT FOR BogusMonth 0, 0
and
Hi Tom
> Anyone have a
> suggestion on where I should look to clear this up?
Is cron running? Anything in the cron logs? What exactly is your cron
entry, and which file is it in?
--
Keith Edmunds
+-+
| Tiger Computing Ltd |
Just a quick note to say thanx for the suggestions, and that I'm working on
them.
I have a question which I think is more Linux than Amanda, but it's
affecting Amanda. On one of the servers I receive the amreport via email
just fine, but on the other I have to manually request it
Dustin J. Mitchell wrote:
On Dec 14, 2007 11:11 AM, Tom Herrera <[EMAIL PROTECTED]> wrote:
? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.mil
On Fri, Dec 14, 2007 at 08:11:14AM -0800, Tom Herrera wrote:
>
> Quick thanks to Jon, Gene, Chris, and John for assist with my amflush
> question
>
> Am now looking for folks suggestions on whay I'm seeing on my amreport.
> I've copied it below. Since I'm still
On Dec 14, 2007 11:11 AM, Tom Herrera <[EMAIL PROTECTED]> wrote:
> ? gtar: ./mnt/cdrom: Cannot savedir: Input/output error
> ? gtar: ./mnt/cdrom: Warning: Cannot savedir: Input/output error
These are a problem. You should add an exclude for /mnt to your DLE:
brain.milw / {
WHATEVER_DUMPTYPE_YO
Quick thanks to Jon, Gene, Chris, and John for assist with my amflush
question
Am now looking for folks suggestions on whay I'm seeing on my amreport.
I've copied it below. Since I'm still very new to both Linux and Amanda I'm
wondering which lines I need to be concerned ab
amdump myconfig
has been crashing during the report phase -- after the dumps are
done and okay. We are at 2.5.1p2which was thought to fix this,
but it hasn't helped.
After some local debugging, my expert source tells me
that this patch should fix the problem (it fixed ours):
T
Hi,
I just tried the amreport command and it looks like it is not
providing the proper result.
The email it generated was that the results were missing for every
client and in the summary the line I kept is was repeated for every
client too.
I checked and indeed there is no log file in the
Hi,
I noticed that when I issue the amreport command I get an error in
the report that it generates:
amreport: ERROR could not open log /usr/local/etc/amanda/test/log:
No such file or directory
that file does indeed not exist, but there are a lot of log.xx.0
files in the usr
Alan Pearson schreef:
Hi Users,
I'm looking for some enlightenment about amreport.
This is "amstatus" output ...
Below is a snippet from the last dump run, and I'm particularly confused
by the 'no-dumpers' entries.
The "no-dumpers" here means, t
Hi Users,
I'm looking for some enlightenment about amreport.
Below is a snippet from the last dump run, and I'm particularly
confused by the 'no-dumpers' entries.
I've set inparallel to 12, but I don't understand why all 12 don't
get used simultaneously or
On (05/15/06 19:29), Jon LaBadie wrote:
> I've never heard of it using sendmail by default. grep'ping the source
> found no instance of sendmail. But the configure script has lines like:
>
> for ac_prog in Mail mailx mail
>
> case $MAILER in # Let the user override the test with a path.
>
On Mon, May 15, 2006 at 06:30:24PM -0400, Josh Steadmon wrote:
> On (05/15/06 16:56), Jon LaBadie wrote:
> > I don't think sendmail supports a -s option, neither postfix's compatibility
> > version nor the real version.
>
> Interesting. Since Amanda tries to use sendmail (apparently) by
> default
On (05/15/06 16:56), Jon LaBadie wrote:
> I don't think sendmail supports a -s option, neither postfix's compatibility
> version nor the real version.
Interesting. Since Amanda tries to use sendmail (apparently) by
default, I'm surprised I wasn't able to find any other posts by people
having the
sing postfix is having the same problems I
> am. In the past, I've built Amanda with MAILER="/usr/bin/Mail", but I'd
> rather get amreport to work directly with postfix. I've now built
> Amanda without explicitly specifying the mailer, and the configure
> scr
;/usr/bin/Mail", but I'd
rather get amreport to work directly with postfix. I've now built
Amanda without explicitly specifying the mailer, and the configure
script chooses postfix's version of sendmail. However, this version of
sendmail doesn't like the -s "Subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've tested and it's ok.
Thanks for your speed help.
Paul Bijnens wrote:
| Christian Molière wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Yes, I do with this version but now I have same problem in an oth
Christian Molière wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, I do with this version but now I have same problem in an other
part of amreport file, in section DUMP SUMMARY:
I'd like to parse all sections without truncated hostname neither
truncated disk. Is it possible an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, I do with this version but now I have same problem in an other
part of amreport file, in section DUMP SUMMARY:
I'd like to parse all sections without truncated hostname neither
truncated disk. Is it possible and how could I do that ?
Christian Molière wrote:
I parsed an amreport file but I have a problem in FAILURE AND STRANGE
DUMP SUMMARY section with truncated hostname. Hostname are truncated
til 10 characters.
Is there a meaning to increase this limit when I use amreport tool
even if I have to recompile sources files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I parsed an amreport file but I have a problem in FAILURE AND STRANGE
DUMP SUMMARY section with truncated hostname. Hostname are truncated
til 10 characters.
Is there a meaning to increase this limit when I use amreport tool
even if I have
On Tue, Apr 05, 2005 at 03:17:19PM +0200, Chrisanth Lederer enlightened us:
> how can I tidy up the dump summary of the amreport emails ?
>
> The reports I get look like this:
>
> ..
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS
On Tue, 5 Apr 2005 at 3:17pm, Chrisanth Lederer wrote
> how can I tidy up the dump summary of the amreport emails ?
>
> The reports I get look like this:
>
> ..
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS
Hello list,
how can I tidy up the dump summary of the amreport emails ?
The reports I get look like this:
..
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
localhost/home/SAMBA 0
I said 16 tapes because I know it's better to have at least one more
tape (5x3+1). In this way I don't overwrite a valid copy and have valid
backups for 3 weeks.
Thanks,
ddaas
Paul Bijnens schrieb:
ddaasd wrote:
I've modified the amanda.conf in the following way for my backup
scenario (I want
Hi all,
I've modified the amanda.conf in the following way for my backup
scenario (I want to backup only weekdays, I have 16 Tapes).
###
dumpcycle 7 days
runspercycle 5 days #only weekdays. I run amdump only Mo-Fr
tapecycle 16 tapes #I have 16 tapes
runtapes 1 # one tape is used for every run
bu
On Monday 28 February 2005 09:52, ddaasd wrote:
>The idea with 3 groups sounds better.
>
>I have 2 more questions for this scenario:
>
>1. If my dumpcycle=5, runspercycle=5 then I need tapecycle to be
> minimum 6 (runspercycle+1). These are for one group (for one week
> - only weekdays). If I woul
ddaasd wrote:
The idea with 3 groups sounds better.
I have 2 more questions for this scenario:
1. If my dumpcycle=5, runspercycle=5 then I need tapecycle to be minimum
6 (runspercycle+1). These are for one group (for one week - only
weekdays). If I would have 3 groups then it seems I need 18 tap
1 - 100 of 160 matches
Mail list logo
