Re: DLE entries containing # (hash mark) break the communication

2017-06-26 Thread Jon LaBadie
On Mon, Jun 26, 2017 at 05:15:34PM +0200, Heiko Schlittermann wrote: > Jon LaBadie (Mo 26 Jun 2017 16:40:34 CEST): > … > > > ERROR [FORMAT ERROR IN REQUEST PACKET Error on line 1 char 2216: \ > > > Element 'property' was closed, but the currently open element is > > > 'value'] > > > > > > >

Re: DLE entries containing # (hash mark) break the communication

2017-06-26 Thread Heiko Schlittermann
Jon LaBadie (Mo 26 Jun 2017 16:40:34 CEST): … > > ERROR [FORMAT ERROR IN REQUEST PACKET Error on line 1 char 2216: \ > > Element 'property' was closed, but the currently open element is > > 'value'] > > > > > > If I replace the "#" by "?" it works find. The behaviour is reproducable > > if

Re: DLE entries containing # (hash mark) break the communication

2017-06-26 Thread Jon LaBadie
On Mon, Jun 26, 2017 at 01:42:55PM +0200, Heiko Schlittermann wrote: > Hello, > > Amanda-Server is3.3.6 (package by Debian 8 (jessie)) > Amanda-Client is3.3.9 (package by Debian 9 (stretch)) > > My server side configuration contains: > > define application tar { > plugin "amgtar"

DLE entries containing # (hash mark) break the communication

2017-06-26 Thread Heiko Schlittermann
Hello, Amanda-Server is3.3.6 (package by Debian 8 (jessie)) Amanda-Client is3.3.9 (package by Debian 9 (stretch)) My server side configuration contains: define application tar { plugin "amgtar" # grep -E (posix extended regular expressions) … property append "NORMAL"

RESULTS MISSING on all DLE when only one estimate fails?

2017-06-26 Thread Matthias Teege
Hallo! I've installed Amanda 3.3.3 on a Centos server. Sometimes backups are failing with "RESULTS MISSING" and "driver: WARNING: got empty schedule from planner". I think this is mostly because of estimate timeouts. I see "planner: ERROR Some estimate timeout on a.example.com, using server estima