Results 1 to 3 of 3

Thread: driver: FATAL flush line 1: syntax error

Hybrid View

  1. #1
    Join Date
    Aug 2006
    Posts
    34

    Default driver: FATAL flush line 1: syntax error

    Hi all,
    I upgraded my Amanda clients and server to 2.5.2-1.rhel4. The server and clients are running Red Hat Enterprise Linux AS release 4 (Nahant Update 5). After upgrade, nightly dumps started failing with the following message in the report:

    FAILURE AND STRANGE DUMP SUMMARY:
    cfdev.xxx / RESULTS MISSING
    cfdev.xxx /var RESULTS MISSING
    <snip>
    driver: FATAL flush line 1: syntax error (skipping != FLUSH)

    Excerpt from /tmp/amanda/server/ISDaily2.5/driver.20070521091137.debug:
    Code:
    driver: debug 1 pid 15157 ruid 502 euid 502: start at Mon May 21 09:11:37 2007
    driver: debug 1 pid 15157 ruid 502 euid 502: rename at Mon May 21 09:11:37 2007
    driver: time 0.123: flush line 1: syntax error (skipping != FLUSH)
    driver: time 0.123: pid 15157 finish time Mon May 21 09:11:37 2007
    Excerpt from ~amandabackup/ISDaily2.5/amdump.1 on the server:
    Code:
    dumper: pid 16583 executable dumper13 version 2.5.2
    driver: started dumper13 pid 16583
    driver: send-cmd time 0.127 to dumper13: START 20070521131153
    driver: flush line 1: syntax error (skipping != FLUSH)
    Any ideas?

  2. #2

    Default

    Quote Originally Posted by bethany View Post
    Hi all,
    I upgraded my Amanda clients and server to 2.5.2-1.rhel4. The server and clients are running Red Hat Enterprise Linux AS release 4 (Nahant Update 5). After upgrade, nightly dumps started failing with the following message in the report:

    driver: FATAL flush line 1: syntax error (skipping != FLUSH)

    Any ideas?
    I have had the same. I THINK (can't be absolutely sure until there is another dump to auto-flush) that this is caused by there being additional "cruft" in the amanda holding directories. My solution was to move the amanda holding area one directory lower in the file system. This may be an amanda bug, but if my workaround works I don't intend to try and fix it.

    Chris Ritson, Computing Science, Newcastle University, UK.

  3. #3
    Join Date
    Mar 2007
    Location
    Chicago, IL
    Posts
    688

    Default

    Chris -- you've hit it, exactly. It will be fixed in an upcoming release.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •