On Jan 7, 2008 9:03 AM, Mister Olli [EMAIL PROTECTED] wrote:
(gdb) bt
#0 0x281ece17 in shmget () from /lib/libc.so.6
#1 0x080520f4 in attach_buffers ()
#2 0x0804b872 in main ()
Eek -- this is where the taper is allocating the memory that it will
share with the tape-writer process. Have
Op ma 07jan08 om 07:45 schreef Marc Muehlfeld:
last saturday my monthly off-site backup started. But at the starttime, the
holding disk was full of scrap.
Maybe you have to be careful with scrap, especially when made by Amanda: did
you run amcleanup?
Gerrit
Dustin J. Mitchell schrieb:
Yes -- that check takes place when the driver starts up, and is not
made again.
Maybe a feature for the wishlist? E. g. amanda could have a look for free
diskspace every time when a dump of a DLE starts.
--
Marc Muehlfeld (Sysadmin)
IMGM Laboratories GmbH
Dustin J. Mitchell wrote at 09:46 -0500 on Jan 7, 2008:
On Jan 7, 2008 9:03 AM, Mister Olli [EMAIL PROTECTED] wrote:
(gdb) bt
#0 0x281ece17 in shmget () from /lib/libc.so.6
#1 0x080520f4 in attach_buffers ()
#2 0x0804b872 in main ()
Eek -- this is where the taper is
On Jan 7, 2008 10:05 AM, Marc Muehlfeld
[EMAIL PROTECTED] wrote:
Dustin J. Mitchell schrieb:
Yes -- that check takes place when the driver starts up, and is not
made again.
Maybe a feature for the wishlist? E. g. amanda could have a look for free
diskspace every time when a dump of a DLE
John E Hein wrote at 08:53 -0700 on Jan 7, 2008:
Dustin J. Mitchell wrote at 09:46 -0500 on Jan 7, 2008:
On Jan 7, 2008 9:03 AM, Mister Olli [EMAIL PROTECTED] wrote:
(gdb) bt
#0 0x281ece17 in shmget () from /lib/libc.so.6
#1 0x080520f4 in attach_buffers ()
#2
I have run some more tests and now I am getting a different error
message altogether in my logs. I am attaching the amdump log and the
script amaespipe, which is used to encrypt. The amaespipe is complaining
about improper usage.
I had to make some changes to the script because Solaris does not
I assume that the '18' in the amdump logfile is coming from this line:
seedstr=`head 18 /dev/urandom | uuencode - | head -n 2 | tail -1`
and that this is probably a result of non-portable shell (or, in this
case, 'head') syntax.
You can replace all of those 'head NN' with 'sed' invocations,
Dustin,
When I run amaespipe, by itself, I get the usage error message the first
2 times and then the third and subsequent times I get the following:
# amaespipe
bz2aespipe%10uu00MDGVU,T;M_I:)BBXZQM1Z$+MMVF5@*K3TMV@7AM-FI(ZSBQY
$:]+#8Error: gpg key file decryption failed
Paul Crittenden
Computer
On Jan 7, 2008 3:09 PM, Paul Crittenden [EMAIL PROTECTED] wrote:
Dustin,
When I run amaespipe, by itself, I get the usage error message the first
2 times and then the third and subsequent times I get the following:
# amaespipe
bz2aespipe%10uu00MDGVU,T;M_I:)BBXZQM1Z$+MMVF5@*K3TMV@7AM-FI(ZSBQY
Here it is and yes I have corrected the head and tail entries.
$ sh -x amaespipe
ENCRYPTION=AES256
HASHFUNC=SHA256
ITERCOUNTK=100
WAITSECONDS=1
AMANDA_HOME=/export/home/amanda
GPGKEY=/export/home/amanda/.gnupg/am_key.gpg
FDNUMBER=3
PATH=/usr/bin:/usr/local/bin:/sbin:/usr/sbin
+ export PATH
+ test
11 matches
Mail list logo
