Results 1 to 7 of 7

Thread: Install on Ubuntu 10.10

  1. #1

    Default Install on Ubuntu 10.10

    Good afternoon. I have been working on setting up amanda on our backup server. I believe I have hit a stopping point though. When I run amcheck to make sure that amanda is working correctly this is what I get.

    amanda@db3:/etc/amanda/DailySet1$ amcheck -c DailySet1
    "/etc/amanda/DailySet1/amanda.conf", line 641: dumptype parameter expected
    "/etc/amanda/DailySet1/amanda.conf", line 641: end of line is expected
    amcheck: errors processing config file

    So I commented out the offending line of code.

    define dumptype nocomp-user-gnutar {
    program "GNUTAR"
    comment "user partitions dumped with tar and no compression"
    #options no-compress
    no-compress
    priority medium
    }

    And ran amcheck again and it just hangs.

    amanda@db3:/home/projectteam$ amcheck -c DailySet1

    Amanda Backup Client Hosts Check
    --------------------------------

    After a bit of Googling, I think that I need that dumptype in the amanda.conf file in order to copy files from windows. I have installed samba and believe it is configured correctly as well. I also added an amandapass file to the correct directory.

    Any help would be greatly appreciated.

  2. #2
    Join Date
    Oct 2005
    Posts
    1,559

    Default

    What version of amanda are you using?

    Please check contents of /var/log/amanda/ log files for more information. Look at "selfcheck*" log file.

    Paddy

  3. #3

    Default

    Thanks for the reply. I am using version 3.1.0

    I didn't see any log files under /var/log/amanda/ that started with selfcheck.

    However I did look at the two amcheck logs. With the code uncommented from my orginal post. I saw this.

    Thu Oct 21 14:12:11 2010: amcheck: pid 7868 ruid 1001 euid 1001 version 3.1.0: start at Thu Oct 21 14:12:11 2010
    Thu Oct 21 14:12:11 2010: amcheck: "/etc/amanda/DailySet1/amanda.conf", line 641: dumptype parameter expected
    Thu Oct 21 14:12:11 2010: amcheck: "/etc/amanda/DailySet1/amanda.conf", line 641: end of line is expected
    Thu Oct 21 14:12:11 2010: amcheck: pid 7868 ruid 1001 euid 1001 version 3.1.0: rename at Thu Oct 21 14:12:11 2010
    Thu Oct 21 14:12:11 2010: amcheck: critical (fatal): errors processing config file
    /usr/lib/amanda/libamanda-3.1.0.so(+0x20bcb)[0x130bcb]
    /lib/libglib-2.0.so.0(g_logv+0x1fb)[0xd5c0eb]
    /lib/libglib-2.0.so.0(g_log+0x32)[0xd5c572]
    amcheck(main+0xce2)[0x8052132]
    /lib/libc.so.6(__libc_start_main+0xe7)[0x4e5ce7]
    amcheck[0x804aa01]

    And with the code commented out (prepare for wall of text)
    Thu Oct 21 14:07:15 2010: amcheck: pid 7754 ruid 1001 euid 1001 version 3.1.0: start at Thu Oct 21 14:07:15 2010
    Thu Oct 21 14:07:15 2010: amcheck: pid 7754 ruid 1001 euid 1001 version 3.1.0: rename at Thu Oct 21 14:07:15 2010
    Thu Oct 21 14:07:15 2010: amcheck-clients: security_getdriver(name=BSD) returns 0xc31c40
    Thu Oct 21 14:07:15 2010: amcheck-clients: security_handleinit(handle=0x8add978, driver=0xc31c40 (BSD))
    Thu Oct 21 14:07:15 2010: amcheck-clients: dgram_bind: setting up a socket with family 2
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 843: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 844: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 845: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 846: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 847: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 848: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 849: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 850: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 851: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 852: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 853: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 854: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 855: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 856: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 857: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 858: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 859: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 860: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 840: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 841: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 842: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange: all ports between 840 and 860 busy
    Thu Oct 21 14:07:15 2010: amcheck-clients: dgram_bind: Could not bind to port in range: 840 - 860.
    Thu Oct 21 14:07:15 2010: amcheck-clients: dgram_bind: Retrying entire range after 10 second delay.
    Thu Oct 21 14:07:30 2010: amcheck-clients: bind_portrange2: Try port 858: Available - Permission denied
    Thu Oct 21 14:07:30 2010: amcheck-clients: bind_portrange2: Try port 859: Available - Permission denied
    Thu Oct 21 14:07:30 2010: amcheck-clients: bind_portrange2: Try port 860: Available - Permission denied
    Thu Oct 21 14:07:30 2010: amcheck-clients: bind_portrange2: Try port 840: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 841: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange2: Try port 842: Available - Permission denied
    Thu Oct 21 14:07:15 2010: amcheck-clients: bind_portrange: all ports between 840 and 860 busy
    Thu Oct 21 14:07:15 2010: amcheck-clients: dgram_bind: Could not bind to port in range: 840 - 860.
    Thu Oct 21 14:07:15 2010: amcheck-clients: dgram_bind: Retrying entire range after 10 second delay.

    I didn't bother with the rest of it since it was all the same. Looks like there is something I am missing to give permission to amanda.

  4. #4

    Default

    I didnt realize that there was a selfcheck file on the clients.

    here is one of them

    elfcheck: debug 1 pid 13571 ruid 33 euid 33: start at Thu Oct 21 16:31:29 2010
    /usr/lib64/amanda/selfcheck: version 2.4.4p3
    selfcheck: time 0.006: checking disk /etc
    selfcheck: time 0.019: device /etc
    selfcheck: time 0.019: disk "/etc" OK
    selfcheck: time 0.019: amdevice "/etc" OK
    selfcheck: time 0.019: device "/etc" OK
    selfcheck: time 0.019: checking disk /db/backup
    selfcheck: time 0.024: device /db/backup
    selfcheck: time 0.024: disk "/db/backup" OK
    selfcheck: time 0.024: amdevice "/db/backup" OK
    selfcheck: time 0.024: device "/db/backup" OK
    selfcheck: time 0.029: pid 13571 finish time Thu Oct 21 16:31:30 2010

    Is this not working because the version numbers don't match?
    If so is there anything I can follow to update this on a RedHat Enterprise 4 system?

    Sorry for the newbie questions. I am trying to feel my way through this.

  5. #5
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    amcehck must be setuid root, fix permission before using it.

    a 2.4.4p3 client should works with a new server.

    Your config file use old syntax, update your config file syntax for the server version.

  6. #6

    Default

    Setuid is root for amcheck.

    Not sure what you mean by check for old syntax.

    Troubleshooting seems to suggest that the issue is on the server's side. xinetd seems to be set correctly.

    Thanks for any help in this issue.

  7. #7

    Default

    Well I was able to figure out the issue with the servers not communicating. Amcheck has been running fine for me, but I have a different issue now.

    I have been able to run amdump but when I do the amflush report gives me this.


    Amanda Tape Server Host Check
    -----------------------------
    Holding disk /db/amanda: 112068 MB disk space available, using 111968 MB
    WARNING: skipping tape test because amdump or amflush seem to be running
    WARNING: if they are not, you must run amcleanup
    WARNING: tapecycle (10) <= runspercycle (10).
    Server check took 0.135 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 2 hosts checked in 0.389 seconds. 0 problems found.

    (brought to you by Amanda 3.1.0)

    When I run amcleanup there are no logs to cleanup

    amanda@db3:~$ amcleanup DailySet1
    amcleanup: no unprocessed logfile to clean up.

    I don't see amdump or amflush running when I use the top command.

    Always 1 step forward followed by a halt.

    [EDIT]
    I let the program run as scheduled with the tape it should have been asking for. Below is the result of the amflush command.

    Amanda Tape Server Host Check
    -----------------------------
    Holding disk /db/amanda: 122004 MB disk space available, using 121904 MB
    slot 1: volume 'DailySet1-0202' is still active and cannot be overwritten
    Taper scan algorithm did not find an acceptable volume.
    (expecting a new volume)
    ERROR: No acceptable volumes found
    WARNING: tapecycle (10) <= runspercycle (10).
    Server check took 0.460 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 2 hosts checked in 0.261 seconds. 0 problems found.

    (brought to you by Amanda 3.1.0)

    Listed below is the result of the last debug file for taper
    Thu Oct 28 01:00:02 2010: taper: pid 21712 ruid 1001 euid 1001 version 3.1.0: start at Thu Oct 28 01:00:02 2010
    Thu Oct 28 01:00:02 2010: taper: pid 21712 ruid 1001 euid 1001 version 3.1.0: rename at Thu Oct 28 01:00:02 2010
    Thu Oct 28 01:00:02 2010: taper: warning: "/dev/st0" uses deprecated device naming convention;
    using "tape:/dev/st0" instead.

    Thu Oct 28 01:00:02 2010: taper: Amanda::Taper::Scan::traditional stage 1: search for oldest reusable volume
    Thu Oct 28 01:00:02 2010: taper: Amanda::Taper::Scan::traditional no oldest reusable volume
    Thu Oct 28 01:00:02 2010: taper: Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
    Thu Oct 28 01:00:02 2010: taper: warning: "/dev/st0" uses deprecated device naming convention;
    using "tape:/dev/st0" instead.

    Thu Oct 28 01:00:02 2010: taper: Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
    Thu Oct 28 01:00:02 2010: taper: new Amanda::Changer::Error: type='failed', reason='notfound', message='all slots have been loaded'
    Thu Oct 28 01:00:02 2010: taper: Amanda::Taper::Scan::traditional result: scan failed
    Thu Oct 28 01:22:03 2010: taper: pid 21712 finish time Thu Oct 28 01:22:03 2010

    I also tried the command listed below

    amanda@db3:~$ amtape DailySet1 taper
    slot 1: volume 'DailySet1-0202' is still active and cannot be overwritten
    UNKNOWN
    ERROR: No acceptable volumes found


    Again any help with this would be much apprectiated.
    Last edited by MrRogers; October 28th, 2010 at 09:28 AM. Reason: More information (Better to add information then not have enough)

Posting Permissions

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