Phil Homewood wrote:
Inconclusive. The email reported an 81.5% ratio where
the printout claimed 81.7. Close, but no cigar... I
think I'll wait and see what tonight's run does...
The compression ratio on my 2.4.4p2 box printed
correctly. I think this was purely coincidental.
The 2.4.4p3 box
Paul Bijnens wrote:
Upgraded one box to 2.4.4p3. amreport still shows the
bogus labels when run against a log generated under
2.4.4p2. Tonight I'll see what it does when it creates
the log itself. :-)
Do you mean you upgraded a client? Just the amanda server is fine.
The 2.4.4p3 server is
the
bogus labels when run against a log generated under
2.4.4p2. Tonight I'll see what it does when it creates
the log itself. :-)
(Does amreport pull its stats from anywhere but the logfile?)
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61
to have started occurring sometime since
2.4.4 (not sure now whether 2.4.4p1 behaved, but I
know 2.4.4 was good.) Anyone?
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - A CyberGuard Company
is relative to the level 0 on the daily
that came before it, for instance
I posted about #2 some months ago, and suggested that I might
come up with a fix for it. Unfortunately I never did; we ended
up rearranging things rather creatively to get around the
problem here.
--
Phil Homewood, Systems
configured on the host machine - perhaps it is telling
me it is working, but I can't read what it says.
That could well be the case. :-) Though it should spend
a noticeable amount of time telling you nothing before
it emails you.
Does amadmin config info tell you anything useful?
--
Phil Homewood
Dave Ewart wrote:
[...] kernel: st0: Error with sense data: Info fld=0x8000, Deferred st09:00: sns =
f1 4
[...] kernel: ASC=15 ASCQ= 1
[...] kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns = f0 3
[...] kernel: ASC=15 ASCQ= 2
[repeated]
What looks like the problem
Autoresponder Notification Dumping Archive.
I made the same mistake.
:-/
(Seriously, though: can we shoot the people who send this
virus responder junk here? Or at least reject their mail
at amanda.org before it gets to the lists? Please?)
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
Phil Homewood wrote:
Now that you mention it, I have had this, a couple of times in the
last week. Am still trying to debug it, but:
??error [/bin/tar got signal 13, compress got signal 11]? dumper: strange [missing
size line from sendbackup]
Turns out this also appears to be bad hardware
configuration working
fine.
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
a chance of being
accepted into the amanda codebase?
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
anyone attempted anything like this before? It doesn't seem
that unusual, does it?
Finally, is there any reason *why* GNUTAR_LISTED_INCREMENTAL_DIR
isn't configurable in amanda.conf?
Any suggestions/advice/heckling appreciated...
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL
data. What's
worse -- crippling the functionality, or being inconsistent?)
Cheers...
--
Phil Homewood, Systems Janitor, http://www.SnapGear.com
[EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances
Paul Bijnens wrote:
This directive would be needed by a client, and currently a client
does not need a configuration file.
Could it not be supplied from the server to the client, as I believe
the exclude list option is?
The other reason is that no-one submitted a patch (for a seperate
14 matches
Mail list logo
