Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ
On Mon, 18 Sep 2017 10:10:02 -0400 Jean-Louis Martineau wrote: > It is a compatibility issue between amrecover 3.3 and a 3.4 server. > The restore is successful, It is the error message that is bogus. > > Try the attached compat-crc.diff patch. > Patching only the perl/Amanda/Restore.pm should fix the problem. That appears to work. I didn't see a Restore.pm on the client, now running 3.3. So I applied it on the server (3.4) (on amd64), and restored the same DLE. No error messages, and diffing the restore against a known good instance of the same data showed no errors. I also did a restore on the client, with just the server patched. That also ran without any error messages and a successful diff. Thanks! -- The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. -- U.S. Const. Amendment IV Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
The debug files are in the debug directory: amgetconf build.amanda_dbgdir Jean-Louis On 23/09/17 07:31 AM, Matthias Teege wrote: > On Fri, Sep 22, 2017 at 01:16:27PM -0400, Jean-Louis Martineau wrote: > > Hi, > > I have again looked more closely. Perhaps the (recv error) problem is > an update of the Centos amanda packages. On tuesday we updated the > server and there was an update from amanda.*3.3.3-17.el7 to > 3.3.3-18.el7. > >> Can you try the attached patch? > I've compiled 3.3.3 with your patch and run a dump with: > > su amandabackup -c '/opt/amanda/3.3.3/sbin/amdump --no-taper daily nfs > /home/./c' > > It works without problems. > >> After the run, can you grep for'first read return EAGAIN' and'second >> read return EAGAIN' in the dumper debug files? > I'm surprised, there is no dumper debug file. In my amanda.conf I have: > > logdir "/var/log/amanda/daily" > debug-planner 3 > debug-dumper 3 > > but ... > > # find /var/log/amanda -name '*dump*23*' > /var/log/amanda/daily/amdump.20170923125853 > /var/log/amanda/daily/amdump.20170923123220 > /var/log/amanda/daily/amdump.20170923123412 > /var/log/amanda/server/daily/amdump.20170923005801.debug > > Is this because of "--no-taper"? > > Thanks again! > Matthias > This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver this message to anyone. Instead, destroy it and notify me by reply e-mail
Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
On Fri, Sep 22, 2017 at 01:16:27PM -0400, Jean-Louis Martineau wrote: Hi, I have again looked more closely. Perhaps the (recv error) problem is an update of the Centos amanda packages. On tuesday we updated the server and there was an update from amanda.*3.3.3-17.el7 to 3.3.3-18.el7. > Can you try the attached patch? I've compiled 3.3.3 with your patch and run a dump with: su amandabackup -c '/opt/amanda/3.3.3/sbin/amdump --no-taper daily nfs /home/./c' It works without problems. > After the run, can you grep for'first read return EAGAIN' and'second > read return EAGAIN' in the dumper debug files? I'm surprised, there is no dumper debug file. In my amanda.conf I have: logdir "/var/log/amanda/daily" debug-planner 3 debug-dumper 3 but ... # find /var/log/amanda -name '*dump*23*' /var/log/amanda/daily/amdump.20170923125853 /var/log/amanda/daily/amdump.20170923123220 /var/log/amanda/daily/amdump.20170923123412 /var/log/amanda/server/daily/amdump.20170923005801.debug Is this because of "--no-taper"? Thanks again! Matthias
