-40.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2024-07-22 17:19, Robert Heller wrote:
At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo wrote:
Never used S3 but dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices
nature-we-calculated-does-not-match-the-s
> > > > > > > >
> > > > > > > > The problem might be the pathname going to Amazon is bad
> > > > > > > > (leading . or leading
> > > > > > > > /), but *I* am not using either, s
7:10:23 +0200 Exuvo wrote:
Never used S3 but dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices S3 Device
No, that does not work. Get a config file syntax error... The docs are
somewhat wrong.
Anton "exuvo" Ols
; . or leading
> > > > > > > /), but *I* am not using either, so I guess Amanda is messing up
> > > > > > > the
> > > > > > > "signature" somehow. So this might be a bug? This used to work
> > > &
; > > > > > /), but *I* am not using either, so I guess Amanda is messing up the
> > > > > > "signature" somehow. So this might be a bug? This used to work
> > > > > > with Amanda
> > > > > > 3.3, so it might be some
the "tapedev" is indicated by the
> > > > > tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> > > > > line: it is a changer on an Amazon s3 device with with a Bucket of
> > > > > sharky5-backups, with slots slot-00 through slot-
the
> > > > tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> > > > line: it is a changer on an Amazon s3 device with with a Bucket of
> > > > sharky5-backups, with slots slot-00 through slot-40.
> > > >
> > > >> Ant
I had no trouble setting up S3 with Amanda 3.3.3 under CentOS 7.
By things don't seem to be working with Amanda 3.5.1 under Debian 12...
At Tue, 23 Jul 2024 17:31:41 +0200 li...@xunil.at wrote:
>
> Am 22.07.24 um 19:49 schrieb Robert Heller:
> > I opened an issue: https://github.com/zmanda/aman
Am 22.07.24 um 19:49 schrieb Robert Heller:
I opened an issue: https://github.com/zmanda/amanda/issues/259
I uploaded the *working* configs for Amanda 3.3.3 under CentOS 7. The 3.3.3
configuation is not liked by Amanda 3.5.1 under Debian 12 (not supprising). I
*think* I updated the configs for
bug? This used to work with
> >>>>> Amanda
> >>>>> 3.3, so it might be something broke in 3.4 or 3.5.
> >>>>>
> >>>>> (I've also opened an issue on github.)
> >>>>>
> >>>>> And I thin
40.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2024-07-22 17:19, Robert Heller wrote:
At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo wrote:
Never used S3 but dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices
quot; is indicated by the
> > > > tpchanger "chg-multi:s3:sharky5-backups/slot-{00..40}"
> > > > line: it is a changer on an Amazon s3 device with with a Bucket of
> > > > sharky5-backups, with slots slot-00 through slot-40.
> > > >
&
t is a changer on an Amazon s3 device with with a Bucket of
> > > sharky5-backups, with slots slot-00 through slot-40.
> > >
> > >> Anton "exuvo" Olsson
> > >> ex...@exuvo.se
> > >>
> > >> On 2024-07-22 17:19, Rob
lot-00 through slot-40.
> >
> >> Anton "exuvo" Olsson
> >> ex...@exuvo.se
> >>
> >> On 2024-07-22 17:19, Robert Heller wrote:
> >>> At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo wrote:
> >>>
> >>>> Never used
.se
On 2024-07-22 17:19, Robert Heller wrote:
At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo wrote:
Never used S3 but dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices S3 Device
No, that does not work. Get a config fil
ut dont you need to use a "tapdev" line and device
> >> properties on that instead of on the changer?
> >> See man amanda-devices S3 Device
> > No, that does not work. Get a config file syntax error... The docs are
> > somewhat wrong.
> >
> >>
t dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices S3 Device
No, that does not work. Get a config file syntax error... The docs are
somewhat wrong.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2024-07
At Mon, 22 Jul 2024 17:10:23 +0200 Exuvo wrote:
>
> Never used S3 but dont you need to use a "tapdev" line and device properties
> on that instead of on the changer?
> See man amanda-devices S3 Device
No, that does not work. Get a config file syntax error... The do
Never used S3 but dont you need to use a "tapdev" line and device properties on
that instead of on the changer?
See man amanda-devices S3 Device
Anton "exuvo" Olsson
ex...@exuvo.se
On 2024-07-22 14:24, Robert Heller wrote:
backup@sharky5:~$ amcheck sharky5
Amanda Tape Server Host Check
backup@sharky5:~$ amcheck sharky5
Amanda Tape Server Host Check
-
NOTE: tapelist file does not exists
it will be created on the next run
NOTE: Holding disk '/var/lib/amanda/holdings/sharky5': 38816 MB disk space
available, using 12000 MB as requested
slot 1: Whi
o out to gallifrey, then jpt.
When the request to gallifrey times out, planner sees 255 status from SSH
and aborts with the EOF error. Doesn't even wait around for the timeout on
jpt.
If I go back and look at some old logs, I can see planner continue past
the `EOF on read' error
nsive, and I can see their responses arrive. There are two hosts
powered down, gallifrey and jpt. The requests go out to gallifrey, then
jpt. When the request to gallifrey times out, planner sees 255 status
from SSH and aborts with the EOF error. Doesn't even wait around for the
timeout on jpt
Hi Lou,
I'm using the same version as you, although in Fedora 37
amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some
machines that are down and the rest of the backups were made.
In my case I have this
planner: ERROR Request to MACHINE failed: Connection refu
3.5.3, the behaviour has changed. If a host doesn't
respond to the planner size request, the planner aborts the entire
backup with the error
planner: ERROR Request to gallifrey.ivriel failed:
EOF on read from gallifrey.ivriel
I've confirmed that my configuration is generally correct --- a
So, I did some more digging, the problem came because a bad log file
that contains the line:
DONE taper WARNING driver Taper protocol error
This line caused Perl module Catalog.pm to die at line 764 because $str
is empty and Perl cannot apply a regex replace on an empty string.
After I removed
Hi,
Lately, when trying to do an amrecover I get the following error message:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
I could not see anything in amandad.*.debug
In amidxtaed.*.debug I found a number of lines saying:
Warning: no log
lem>
ambind is not included in client packages for 3.5.1, therefore the
client will error trying to launch amrecover – is this across the board
for all distros/packages?
The solution as above is then to install the amanda-server package.
(doesn’t seem to be the case for Zmanda community
3NB
-Original Message-
From: owner-amanda-us...@amanda.org On Behalf
Of Charles Curley
Sent: 23 December 2021 16:35
To: amanda-users
Subject: Re: amanda client packaging and ambind (amrecover error on client)
External email to Cardiff University - Take care when replying/opening
On Thu, 23 Dec 2021 09:07:42 -0700
Charles Curley wrote:
> No.
>
> root@hawk:~# apt-file search ambind | grep /ambind$
> amanda-common: /usr/lib/amanda/ambind
> root@hawk:~#
I should have specified: This is on Debian 11 (Bullseye). It was also
the case on Debian 10 (Buster) and likely earlier.
On Thu, 23 Dec 2021 09:01:24 +
David Simpson wrote:
> ambind is not included in client packages for 3.5.1, therefore the
> client will error trying to launch amrecover - is this across the
> board for all distros/packages?
No.
root@hawk:~# apt-file search ambind | grep /ambin
Hit this exact problem in Almalinux 8.5 with a couple of test machines (rpm
from default repo/appstream):
https://utcc.utoronto.ca/~cks/space/blog/linux/Ubuntu1804AmandaProblem
ambind is not included in client packages for 3.5.1, therefore the client will
error trying to launch amrecover - is
d the amanda.conf back to using oldest. An amcheck daily told
> me there were no acceptable volumes found! So I switched back to
Hmmm... Well, clearly the exact failure mode different between the two
servers :(.
(You did previously see the "terminated with signal 11" error message o
From the other server:
amandabackup@eclogite:~/daily$ cat
/usr/local/var/amanda/chg-robot-dev-tape-by-id-scsi-1BDT-FlexStor-II-00MX64100589-LL0
$STATE = {
'drive_lru' => [
'0',
'1'
On Wed, Oct 14, 2020 at 12:20:33 -0400, Chris Hoogendyk wrote:
> Both lexical.pm and ScanInventory.pm restored to original. New fix
> only patch applied to ScanInventory.pm. amanda.conf restored to use
> oldest.
>
>amanda@marlin:~/daily$ amcheck daily
>
>Amanda Tape Server Host Check
Both lexical.pm and ScanInventory.pm restored to original. New fix only patch applied to
ScanInventory.pm. amanda.conf restored to use oldest.
amanda@marlin:~/daily$ amcheck daily
Amanda Tape Server Host Check
-
NOTE: Holding disk '/amanda3':
On Tue, Oct 13, 2020 at 21:02:34 -0400, Chris Hoogendyk wrote:
> Patched.
>
>amanda@marlin:~/daily$ amcheck -s -otaperscan=taper_lexical daily
>
>Amanda Tape Server Host Check
>-
>NOTE: Holding disk '/amanda3': 449998848 KB disk space availa
Patched.
amanda@marlin:~/daily$ amcheck -s -otaperscan=taper_lexical daily
Amanda Tape Server Host Check
-
NOTE: Holding disk '/amanda3': 449998848 KB disk space available, using
345141248 KB
NOTE: Holding disk '/amanda4': 3026923520 KB
On Tue, Oct 13, 2020 at 15:08:43 -0400, Chris Hoogendyk wrote:
>
> End of /tmp/amanda/server/daily/amcheck-device.20201013150303.debug
[...]
>Tue Oct 13 15:03:04.326400287 2020: pid 10777: thd-0x2688800:
> amcheck-device: warning: Use of
>uninitialized value $label in concatenation (.) or
a4': 3026923520 KB disk space available, using
2922065920 KB
NOTE: Holding disk '/amanda5': 104857600 KB disk space available, using
0 KB
ERROR: amcheck-device terminated with signal 11
Server check took 1.883 seconds
(brought to you by Amanda 3.5.1)
a
On Mon, Oct 12, 2020 at 22:22:45 -0400, Chris Hoogendyk wrote:
>Mon Oct 12 22:16:21.857347044 2020: pid 23996: thd-0x25c0800:
> amcheck-device: slot: 9 label:
>Bio-Research-011ds:
>Mon Oct 12 22:16:21.857380544 2020: pid 23996: thd-0x25c0800:
> amcheck-device: slot: 10 label:
>B
amanda@marlin:~/daily$ amtape -otaperscan=taper_oldest daily inventory
slot 14: label Bio-Research-013 barcode 13L7 [retention-tapes]
slot 15: label Bio-Research-003 barcode 03L7 [retention-tapes]
slot 16: label Bio-Research-004 barcode 04L7 (in drive 1)
[rete
lding disk '/amanda4': 416890880 KB disk space available, using
312033280 KB
NOTE: Holding disk '/amanda5': 104857600 KB disk space available, using
0 KB
ERROR: amcheck-device terminated with signal 11
Server check took 7.302 seconds
(brought to you by A
On Mon, Oct 12, 2020 at 14:53:03 -0400, Chris Hoogendyk wrote:
> There should be no difference in the tapes. I did them all by just
> doing an `amtape daily slot nn` followed by an `amlabel daily
> Bio-Research-nnn`. The first 20 or so were all done in sequence in
> one session, and that would incl
On Mon, Oct 12, 2020 at 15:27:44 -0400, Chris Hoogendyk wrote:
>amcheck-device: Not a SCALAR reference at
>/usr/local/share/perl/5.22.1/Amanda/Taper/Scan/lexical.pm line 102.
Ah, drat, this was a typo in my patch. Please edit line 102 of that
file and remove the doubled "$" charac
On Mon, Oct 12, 2020 at 18:19:21 +, Debra S Baddorf wrote:
> Is it worth trying to just remove the ???state??? file (rename it to
> .save for instance)
> and letting amanda recreate it?
Hmmm, that's an intersting idea... though it seems (from reading the man
pages) that it might be possil
Patch applied. Then . . .
amanda@marlin:~/daily$ amcheck -s -otaperscan=taper_lexical daily
Amanda Tape Server Host Check
-
WARNING: holding disk '/amanda3': only 104849408 KB free, using nothing
WARNING: Not enough free space specifie
There should be no difference in the tapes. I did them all by just doing an `amtape daily slot nn`
followed by an `amlabel daily Bio-Research-nnn`. The first 20 or so were all done in sequence in one
session, and that would include the four you mention. I didn't even retype the commands. I used t
Is it worth trying to just remove the “state” file (rename it to
.save for instance)
and letting amanda recreate it?
When my label reader glitches and reads the label differently than it read it
last time I used this tape,
I just remove my state file and it proceeds to recreate the whole fil
On Sun, Oct 11, 2020 at 23:32:08 -0400, Chris Hoogendyk wrote:
> Text file.
>
> attached.
Excellent, perfect.
If you are able to run the patched version of lexical.pm that should
give more explicit info, but meanwhile just looking through the
statefile: one thing that jumps out at me is that fou
Thank you!
I'll have to get to that tomorrow.
On 10/11/20 7:04 PM, Nathan Stratton Treadway wrote:
On Sun, Oct 11, 2020 at 14:48:13 -0400, Chris Hoogendyk wrote:
In any case, I currently have both systems flushing to tape using
the traditional taper scan. That may work for now, but it would b
This segment?
define changer NEO200x48 {
tpchanger
"chg-robot:/dev/tape/by-id/scsi-1BDT_FlexStor_II_00MX64200626_LL0" # your
changer
device file (T48)
property "tape-device" "0=tape:/dev/nst1" # your tape drive device
file
property append "tape-device" "1=tape:/de
On Sun, Oct 11, 2020 at 14:48:13 -0400, Chris Hoogendyk wrote:
> In any case, I currently have both systems flushing to tape using
> the traditional taper scan. That may work for now, but it would be
> good to track this down. It's also puzzling that it just turned up
R.e. tracking this down: my t
On Sun, Oct 11, 2020 at 15:51:34 -0400, Nathan Stratton Treadway wrote:
> My theory is that the driver for the changer keeps the inventory written
> in a file somewhere specific to the changer, but since I don't have a
Okay, looking back through the log file you posted a couple days ago,
it looks
On Sun, Oct 11, 2020 at 14:48:13 -0400, Chris Hoogendyk wrote:
> I'm not sure what I should be looking for.
>
> I don't see anything in amanda's home directory that seems likely,
> nor in /tmp/amanda, and there is no /etc/amanda/. The tape library
> has a web interface that I use to interact with
I'm not sure what I should be looking for.
I don't see anything in amanda's home directory that seems likely, nor in /tmp/amanda, and there is
no /etc/amanda/. The tape library has a web interface that I use to interact with it. Amanda is
configured to use mtx. I can also use mtx by hand to che
On Sun, Oct 11, 2020 at 12:24:45 -0400, Chris Hoogendyk wrote:
> /tmp/amanda/server/daily/amcheck-device.20201011120931.debug (lexical)
> Sun Oct 11 12:09:31.912816794 2020: pid 22002: thd-0xe8e600: amcheck-device:
> NEO200x48: updating state
> Sun Oct 11 12:09:31.922463203 2020: pid 22002: thd-0
: amcheck-device: NEO200x48: loading
label 'Bio-Research-002'
Sun Oct 11 12:10:16.361442086 2020: pid 22053: thd-0x8d3600: amcheck-device: new
Amanda::Changer::Error: type='failed', reason='notfound', message='label 'Bio-Research-002' not
recognize
/amanda4': only 104853504 KB free, using nothing
WARNING: Not enough free space specified in amanda.conf
NOTE: Holding disk '/amanda5': 613318656 KB disk space available, using
508461056 KB
ERROR: amcheck-device terminated with signal 11
Server check took
; fails just as before. The amanda.conf uses taper_oldest.
Okay, this lends support to the theory that the crash is actually
happening in "scan" operation, rather than in some later part of the
amcheck-driver/taper process.
(Were there any error/warning messages written to the amcheck
Wow!
amanda@marlin:~/daily$ amcheck -s -otaperscan=taper_traditional daily
Amanda Tape Server Host Check
-
NOTE: Holding disk '/amanda3': 913514496 KB disk space available, using
808656896 KB
NOTE: Holding disk '/amanda4': 158228480 KB disk space availa
On Sat, Oct 10, 2020 at 19:20:25 -0400, Chris Hoogendyk wrote:
> The taper log from last night looks exactly like the amcheck log,
> showing the same inventory followed by the updating state and the
> same three repetitions of the warning at line 102.
So you are saying that the taper log from last
at 17:11:16 -0400, Chris Hoogendyk wrote:
Also
8 lines like this in the kern.log:
Oct 9 21:05:58 eclogite kernel: [650814.343315] amcheck-device[5089]:
segfault at 0 ip
7f94159617c6 sp 7fff61039da8 error 4 in
libc-2.23.so[7f94158d6000+1c]
Well, that doesn't really tell us
On Sat, Oct 10, 2020 at 17:11:16 -0400, Chris Hoogendyk wrote:
> Also
>
> 8 lines like this in the kern.log:
>
>Oct 9 21:05:58 eclogite kernel: [650814.343315] amcheck-device[5089]:
> segfault at 0 ip
>7f94159617c6 sp 00007fff61039da8 error 4 in
> libc-2.2
ck in the original magazines, and sending the
new ones out to Iron Mountain. So, part of the point of saying all that is that I have done this
magazine swap previously. Once. Now, this evening, on both servers, I'm getting this error (ERROR:
amcheck-device terminated with signal 11). When
Also
8 lines like this in the kern.log:
Oct 9 21:05:58 eclogite kernel: [650814.343315] amcheck-device[5089]:
segfault at 0 ip
7f94159617c6 sp 7fff61039da8 error 4 in
libc-2.23.so[7f94158d6000+1c]
On 10/10/20 12:29 AM, Nathan Stratton Treadway wrote:
On Fri, Oct 09, 2020
Sorry for the delay in responding.
amanda@marlin:~/daily$ cat -n
/usr/local/share/perl/5.22.1/Amanda/Taper/Scan/oldest.pm | grep "^
*102" -C3
99 $sl->{'state'} == Amanda::Changer::SLOT_UNKNOWN) {
100 push @unknown, $sl;
101 } elsif ($sl->{
On Sat, Oct 10, 2020 at 00:29:04 -0400, Nathan Stratton Treadway wrote:
> Can you post the output of
>
> $ sed -n '99,$p;105q'
> /usr/local/share/perl/5.22.1/Amanda/Taper/Scan/oldest.pm
> ?
>
> (In other words, what's line 102 in that file on your system, with a
> few lines of context?)
(Hmm
On Fri, Oct 09, 2020 at 22:22:47 -0400, Chris Hoogendyk wrote:
> both servers, I'm getting this error (ERROR: amcheck-device
> terminated with signal 11). When I ran the amcheck before swapping
amcheck-device is a Perl program, so it's a little bit impressive to be
triggeri
ntain. So, part of the point of saying all that is that I have done this
magazine swap previously. Once. Now, this evening, on both servers, I'm getting this error (ERROR:
amcheck-device terminated with signal 11). When I ran the amcheck before swapping magazines, it
worked. I then did an `am
Am 20.07.20 um 10:18 schrieb Markus Storm:
> FWIW, I've created a bash installation procedure to get simplified user
> input to create an Amanda vtape based config.
> We bundle Amanda as the backup tool in openHABian, a software appliance
> for the openHAB home automation system.
> https://github.c
FWIW, I've created a bash installation procedure to get simplified user
input to create an Amanda vtape based config.
We bundle Amanda as the backup tool in openHABian, a software appliance
for the openHAB home automation system.
https://github.com/openhab/openhabian/blob/master/functions/backup.b
Am 13.07.20 um 16:53 schrieb Ansgar Esztermann-Kirchner:
> On Mon, Jul 13, 2020 at 02:58:55PM +0200, Stefan G. Weichinger wrote:
>>
>> off-topic, but recommended: better avoid using "localhost" as hostname
>> in your DLEs ...
>
> OK, I'll look into it.
>
>>
>> From your mail it's not clear if you
Am 13.07.20 um 18:30 schrieb Charles Curley:
> On Mon, 13 Jul 2020 16:53:51 +0200
> Ansgar Esztermann-Kirchner wrote:
>
>>> From your mail it's not clear if you successfully labelled and
>>> created your virtual tapes.
>>>
>>> Seems not: "tapelist file does not exists"
>>
>> Oh dear. I thought
On Mon, 13 Jul 2020 16:53:51 +0200
Ansgar Esztermann-Kirchner wrote:
> > From your mail it's not clear if you successfully labelled and
> > created your virtual tapes.
> >
> > Seems not: "tapelist file does not exists"
>
> Oh dear. I thought I had created (though not labelled) them; but it
>
On Mon, Jul 13, 2020 at 02:58:55PM +0200, Stefan G. Weichinger wrote:
>
> off-topic, but recommended: better avoid using "localhost" as hostname
> in your DLEs ...
OK, I'll look into it.
>
> From your mail it's not clear if you successfully labelled and created
> your virtual tapes.
>
> Seems
Am 13.07.20 um 14:58 schrieb Stefan G. Weichinger:
> Am 13.07.20 um 13:25 schrieb Ansgar Esztermann-Kirchner:
>> Hello List,
>>
>> I'm trying to use amanda with vtapes, but so far have been unable to.
>> The way I read amcheck output, amanda tries to use slot 0 and slot
>> (empty string) instead of
Am 13.07.20 um 13:25 schrieb Ansgar Esztermann-Kirchner:
> Hello List,
>
> I'm trying to use amanda with vtapes, but so far have been unable to.
> The way I read amcheck output, amanda tries to use slot 0 and slot
> (empty string) instead of starting at slot one.
> Is that true? If so, what would
ng': 4886528 KB disk space available,
using 51200 KB as requested
slot 0:Slot 0 not found
slot ?:Slot not found
ERROR: Slot not found
NOTE: host info dir '/var/lib/amanda/state/curinfo/localhost' does not exist
It will be created on the next run
NOTE: index dir '/var/li
ecover without that specified, I keep getting
amrecover> extract
Extracting files using tape drive tape:/dev/nst0 on host marlin.
The following tapes are needed: Bio-Research-027
Extracting files using tape drive tape:/dev/nst0 on host marlin.
Load tape Bio-Research-027 now
>>
>> Extracting files using tape drive tape:/dev/nst0 on host marlin.
>> The following tapes are needed: Bio-Research-027
>>
>> Extracting files using tape drive tape:/dev/nst0 on host marlin.
>> Load tape Bio-Research-027 now
>> Continue [?/Y/n/s/d
ng tape drive tape:/dev/nst0 on host marlin.
> The following tapes are needed: Bio-Research-027
>
> Extracting files using tape drive tape:/dev/nst0 on host marlin.
> Load tape Bio-Research-027 now
> Continue [?/Y/n/s/d]? y
> Error reading Amanda header: block size too smal
eded: Bio-Research-027
Extracting files using tape drive tape:/dev/nst0 on host marlin.
Load tape Bio-Research-027 now
Continue [?/Y/n/s/d]? y
Error reading Amanda header: block size too small
Load tape Bio-Research-027 now
Continue [?/Y/n/d]?
I'm not sure where to go with
> Since two days ago I have this error, everytime I try to run
> > amstatus
> >
> > amstatus: bad status on taper SHM-WRITE (taper): 16 at
> > /usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line
> > 9210.
> >
> > I can see that t
Am 02.08.19 um 10:56 schrieb Nuno Dias:
> Hi,
>
> Since two days ago I have this error, everytime I try to run amstatus
>
> amstatus: bad status on taper SHM-WRITE (taper): 16 at
> /usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line
> 9210.
>
&
Hi,
Since two days ago I have this error, everytime I try to run amstatus
amstatus: bad status on taper SHM-WRITE (taper): 16 at
/usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line
9210.
I can see that the amdump is still running, the taper process also
running, and I
Am 18.07.19 um 13:49 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
>> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>>
Add the same pattern near line 757:
return if $line =~ /^Unable to initialize
t; >> ||Amanda Backup Client Hosts Check||
> >> ||----||
> >> ||ERROR: pomerium.romanus.ca: selfcheck request failed: tcpm_recv_token:
> >> invalid size||
> >> ||Client check: 1 host checked in 5.814 seconds. 1 problem found.||
&
On 2019-07-18 10:49 p.m., Nathan Stratton Treadway wrote:
> On Thu, Jul 18, 2019 at 21:51:56 -0400, Winston Sorfleet wrote:
>> |backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
>> ||Amanda Backup Client Hosts Check||
>> ||----
On Thu, Jul 18, 2019 at 21:51:56 -0400, Winston Sorfleet wrote:
> |backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
> ||Amanda Backup Client Hosts Check||
> ||----||
> ||ERROR: pomerium.romanus.ca: selfcheck request failed: tcp
Greetings all
|backup@flamen:/etc/amanda/vtl$ amcheck -c vtl --client-verbose pomerium||
||Amanda Backup Client Hosts Check||
||||
||ERROR: pomerium.romanus.ca: selfcheck request failed: tcpm_recv_token:
invalid size||
||Client check: 1 host checked in 5.814
Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>
>>> Add the same pattern near line 757:
>>> return if $line =~ /^Unable to initialize messaging context/;
>> Tks! Applied. Hope it gets included
Am 18.07.19 um 10:44 schrieb Diego Zuccato:
> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>
>> Add the same pattern near line 757:
>> return if $line =~ /^Unable to initialize messaging context/;
> Tks! Applied. Hope it gets included in next update!
>
https://github.com/zmanda/amanda/pul
Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Tks! Applied. Hope it gets included in next update!
--
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di Bo
Am 17.07.19 um 19:04 schrieb Jean-Louis Martineau:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Oh, Jean-Louis, nice to read you!
thanks for the missing line, yes, now my first test dump is free of that
error.
Do we have a PR som
-client: HOST localhost ERROR: //192.168.0.250/ftp:
Application 'amsamba': exited with status 1
Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I n
Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figured out the correct patch ;-)
>>> Pls show your change, I want to give it another try.
>> Here it is.
>> -8<--
>> # diff -u amsa
Am 16.07.19 um 09:14 schrieb Diego Zuccato:
> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>
>> I never figured out the correct patch ;-)
>> Pls show your change, I want to give it another try.
> Here it is.
> -8<--
> # diff -u amsamba.ori amsamba
> --- amsamba.ori 2019-07-16 09:09:28
plugin "amsamba"
> property "AMANDAPASS" "/etc/amanda/daily/pass"
> }
> }
> (note the commented lines), I get a different error:
> FAILURE DUMP SUMMARY:
> localhost //192.168.48.41/port lev 0 FAILED [data timeout]
> localhost //1
Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
> I never figured out the correct patch ;-)
> Pls show your change, I want to give it another try.
Here it is.
-8<--
# diff -u amsamba.ori amsamba
--- amsamba.ori 2019-07-16 09:09:28.430585521 +0200
+++ amsamba 2019-07-10 11:02:13.352987193 +
Am 10.07.19 um 14:17 schrieb Diego Zuccato:
> Too bad the patch given here:
> http://www.backupcentral.com/forum/14/292396/smbclient_usage_fails_with__unable_to_initialize_messaging_context_
> is not in packaged version (3.5.1) yet.
>
> Adding the two lines, in my case, fixes the amcheck issue.
1 - 100 of 2274 matches
Mail list logo
