Re: Problem with amlabel
Carl Holzhauer schrieb: I'm sure I just have something written incorrectly, but here's the error I'm getting -bash-3.00$ amlabel dailyset dailyset0 slot 0 changer: got exit: 1 str: could not read result from "/usr/local/libexec/chg-scsi-solaris.conf" amlabel: could not load slot "0": could not read result from "/usr/local/libexec/chg-scsi-solaris.conf" amlabel: could not load slot "0": could not read result from "/usr/local/libexec/chg-scsi-solaris.conf" amlabel: pid 1812 finish time Wed Apr 26 16:27:24 2006 -bash-3.00$ Output of that file: -bash-3.00$ cat "/usr/local/libexec/chg-scsi-solaris.conf" number_configs 1 eject 0 # Tapedrives need an eject command sleep 15 # Seconds to wait until the tape gets ready cleanmax10 # How many times could a cleaning tape get used changerdev /dev/0bn # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/rmt/0bn# the device that is used for the tapedrive 0 (BSD type, no rewind, no compression) startuse0 # The slots associated with the drive 0 enduse 17 # statfile/usr/local/etc/amanda/dailyset/tape0-slot # The file where the actual slot is stored cleancart 18 # the slot where the cleaningcartridge for drive 0 is located cleanfile /usr/local/etc/amanda/dailyset/tape0-clean # The file where the cleanings are recorded usagecount /usr/local/etc/amanda/dailyset/totaltime tapestatus /usr/local/etc/amanda/dailyset/tape0-status #labelfile /usr/local/etc/amanda/dailyset/labelfile # Use this if you have an barcode reader -bash-3.00$ Amanada user has read/write access to /usr/local/libexec and to the chg-scsi-solaris.conf file. can anyone point me in the right direction? Thanks __ Message transport security by GatewayDefender.com 4:29:05 PM ET - 4/26/2006 Hi there, i use chg-scsi since a few years on diffrent linux-servers and have found it has a problem with the comments in chg-scsi.conf. Try to remove all comments from that file an retry it, perhaps it fixes all your problems. Christoph
No progress
At this point, I think a remote help would be the last solution. So it's necessary I communicate privately, naturally from my Linux machine, with some experienced of you. In fact I should indicate my IP address and username & password. I'm not worried for this remote access, but I can't see any other way of solving this case. That's not because I'm lazy, otherwise I wouldn't have worked in front of computers! So, my e-mail address which works in sending and receiving mails from the Linux machine is: [EMAIL PROTECTED] Someone who will be available during this days (here in Italy it is, now, eight o'clock, so six hours later than in the USA, and my work finishes at 17 o'clock in Italy so at 11 in the USA) can write messages to that address and, hopefully, give me the last support. See you soon Stefano I have also a Messenger contact,
Re: Upgraded to 2.5.0, seeing FATAL syncpipe_get: r: unexpected EOF
I'm seeing this as well. I'm not familiar with the internals of amanda and have been doing some hacking If I try and run taper interactively.. and give a START-TAPER command: $ /usr/lib/amanda/taper DailySet1 ... debug buffer stuff ommitted ... taper> START-TAPER 20060425 changer: opening pipe to: /usr/libexec/chg-zd-mtx -info changer: got exit: 0 str: 1 1 1 changer_query: changer return was 1 1 changer_query: searchable = 0 changer_find: looking for Daily102 changer is searchable = 0 changer: opening pipe to: /usr/libexec/chg-zd-mtx -slot current changer: got exit: 0 str: 1 /dev/nst0 $ ( goes straight to command prompt ) If I comment out tpcchanger in amanda.conf, it works! (I get a TAPER-OK message). If I delete the /etc/amanda/Daily/chg-zd-mtx* status files, I can go back to the changer again TAPER still doesn't write to tape though... (no error, IIRC) For now, I'm going back to 2.4 so I can flush the holding files to tape, then I'll reload 2.5 and start trying to troubleshoot again.. Robert
FreeBSD, PIX, timeout strangeness.
Hi,I'm doing a nightly dump of a number of hosts on my network through a PIX firewall. Each morning i find the same hosts fail with the common "estimate timeout issue" which usually indicates a firewall problem. If i immediately run a dump of one of the failed hosts by itself it works fine ! Its only when i run a bunch together ! Could it be the PIX is not managing to keep state on all the traffic ? I'm backing up FreeBSD hosts.. The interesting point is the FreeBSD6 servers never fail ! Here are some interesting differences in sysctl values..FreeBSD4net.inet.ip.portrange.first: 1024net.inet.ip.portrange.last: 5000FreeBSD6net.inet.ip.portrange.first: 49152net.inet.ip.portrange.last : 65535I have tried adjusting the values but it doesn't seem to make any difference.. It possibly has absolutely nothing to do with it.. Some thoughts on this problem would be appreciated..Matt.
Re: Problem with amlabel
On Wed, Apr 26, 2006 at 04:28:33PM -0400, Carl Holzhauer wrote: > I'm sure I just have something written incorrectly, but here's the error > I'm getting > > -bash-3.00$ amlabel dailyset dailyset0 slot 0 > changer: got exit: 1 str: could not read result from > "/usr/local/libexec/chg-scsi-solaris.conf" > amlabel: could not load slot "0": could not read result from > "/usr/local/libexec/chg-scsi-solaris.conf" > amlabel: could not load slot "0": could not read result from > "/usr/local/libexec/chg-scsi-solaris.conf" > amlabel: pid 1812 finish time Wed Apr 26 16:27:24 2006 > -bash-3.00$ > > Output of that file: > > -bash-3.00$ cat "/usr/local/libexec/chg-scsi-solaris.conf" > number_configs 1 > eject 0 # Tapedrives need an eject command > sleep 15 # Seconds to wait until the tape gets ready > cleanmax10 # How many times could a cleaning tape get used > changerdev /dev/0bn Haven't used chg-scsi. But, I doubt the above device is correct. First, it is not in rmt. Second, is your changer device really the same as your drive device? Often they are different lun's or scsi id's. Either would result in a different rmt device number. However to see lun's > 0 you probably will have to edit /kernel/drv/st.conf (scsi tape)then do a reconfigure reboot. Another possibility is to look at sgen.conf (scsi generic?general?) in the same directory. If it recognizes your changer mechanism you may have have a device /dev/changer and/or /dev/scsi/changer/# > # > # Next comes the data for drive 0 > # > config 0 > drivenum0 > dev /dev/rmt/0bn# the device that is used for the > tapedrive 0 (BSD type, no rewind, no compression) Certain about that "no compression"? The zero tape device (without an added l,m,h,c,u) is the default of one of the others (l,m,...). It could be any or them, compression or not. > startuse0 # The slots associated with the drive 0 > enduse 17 # > statfile/usr/local/etc/amanda/dailyset/tape0-slot # The file > where the actual slot is stored > cleancart 18 # the slot where the cleaningcartridge for drive > 0 is located > cleanfile /usr/local/etc/amanda/dailyset/tape0-clean # The file > where the cleanings are recorded > usagecount /usr/local/etc/amanda/dailyset/totaltime > tapestatus /usr/local/etc/amanda/dailyset/tape0-status > #labelfile /usr/local/etc/amanda/dailyset/labelfile # Use this if > you have an barcode reader > -bash-3.00$ > > Amanada user has read/write access to /usr/local/libexec and to the > chg-scsi-solaris.conf file. > > can anyone point me in the right direction? > > Thanks > > > > __ > Message transport security by GatewayDefender.com > 4:29:05 PM ET - 4/26/2006 >>> End of included message <<< -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amcheck: selfcheck request failed
On Thursday 27 April 2006 01:08, you wrote: > On Thursday 27 April 2006 00:44, you wrote: > > Silver Salonen wrote: > > > > >Hi again. > > > > > >In server's disklist I have: > > >silver.kodu /var/logcomp-user-tar > > > > > >When I do "amcheck daily" on server, I get this error: > > >WARNING: silver.kodu: selfcheck request failed: timeout waiting for ACK > > > on amcheck. > > > > > >wiki.zmanda.org says that it's a DNS problem - my client can't find an IP > of > > >the server's name. Both server and client are in the same subnet and use > the > > >same nameserver that definitely knows about both of their names - nslookup > > >proves that ;) > > > > > >On server: > > >$ hostname > > >silver-fedora.kodu > > > > > >On client: > > >$ nslookup fedora-silver.kodu > > >Name: silver-fedora.kodu > > >Address: 192.168.1.68 > > > > > >$ nslookup 192.168.1.68 > > >68.1.168.192.in-addr.arpa name = silver-fedora.kodu. > > > > > >What else could be wrong? > > > > > >Thanks, > > >Silver > > > > > > > > And also please send the latest amandad.debug and selfcheck.debug files > > from the /tmp/amanda on the client > > Um, I use Amanda 2.4.5p1 on FreeBSD-6.0 as a client and I can't find either > amandad.debug or selfcheck.debug :( > So I'm wondering where does Amanda keep its log. > > But whow, I find a typo in my client's inetd.conf :$ > > Um, sorry for bothering with such a thing.. > > Thanks anyway, > Silver Oh, darn! As the inetd entry was invalid, the amandad had never run. After correcting the mistake and running amcheck again, /tmp/amanda with its debuggings nicely exist. Stupid me. Silver
Re: Amcheck: selfcheck request failed
On Thursday 27 April 2006 00:44, you wrote: > Silver Salonen wrote: > > >Hi again. > > > >In server's disklist I have: > >silver.kodu /var/logcomp-user-tar > > > >When I do "amcheck daily" on server, I get this error: > >WARNING: silver.kodu: selfcheck request failed: timeout waiting for ACK > > on amcheck. > > > >wiki.zmanda.org says that it's a DNS problem - my client can't find an IP of > >the server's name. Both server and client are in the same subnet and use the > >same nameserver that definitely knows about both of their names - nslookup > >proves that ;) > > > >On server: > >$ hostname > >silver-fedora.kodu > > > >On client: > >$ nslookup fedora-silver.kodu > >Name: silver-fedora.kodu > >Address: 192.168.1.68 > > > >$ nslookup 192.168.1.68 > >68.1.168.192.in-addr.arpa name = silver-fedora.kodu. > > > >What else could be wrong? > > > >Thanks, > >Silver > > > > > And also please send the latest amandad.debug and selfcheck.debug files > from the /tmp/amanda on the client Um, I use Amanda 2.4.5p1 on FreeBSD-6.0 as a client and I can't find either amandad.debug or selfcheck.debug :( So I'm wondering where does Amanda keep its log. But whow, I find a typo in my client's inetd.conf :$ Um, sorry for bothering with such a thing.. Thanks anyway, Silver
Re: Amcheck: selfcheck request failed
Silver Salonen wrote: Hi again. In server's disklist I have: silver.kodu /var/logcomp-user-tar When I do "amcheck daily" on server, I get this error: WARNING: silver.kodu: selfcheck request failed: timeout waiting for ACK on amcheck. wiki.zmanda.org says that it's a DNS problem - my client can't find an IP of the server's name. Both server and client are in the same subnet and use the same nameserver that definitely knows about both of their names - nslookup proves that ;) On server: $ hostname silver-fedora.kodu On client: $ nslookup fedora-silver.kodu Name: silver-fedora.kodu Address: 192.168.1.68 $ nslookup 192.168.1.68 68.1.168.192.in-addr.arpa name = silver-fedora.kodu. What else could be wrong? Thanks, Silver And also please send the latest amandad.debug and selfcheck.debug files from the /tmp/amanda on the client
Re: Amcheck: selfcheck request failed
Silver Salonen wrote: Hi again. In server's disklist I have: silver.kodu /var/logcomp-user-tar When I do "amcheck daily" on server, I get this error: WARNING: silver.kodu: selfcheck request failed: timeout waiting for ACK on amcheck. wiki.zmanda.org says that it's a DNS problem - my client can't find an IP of the server's name. Both server and client are in the same subnet and use the same nameserver that definitely knows about both of their names - nslookup proves that ;) On server: $ hostname silver-fedora.kodu On client: $ nslookup fedora-silver.kodu Name: silver-fedora.kodu Address: 192.168.1.68 $ nslookup 192.168.1.68 68.1.168.192.in-addr.arpa name = silver-fedora.kodu. What else could be wrong? Thanks, Silver can you please send the last amcheck.debug file from /tmp/amanda directory
Amcheck: selfcheck request failed
Hi again. In server's disklist I have: silver.kodu /var/logcomp-user-tar When I do "amcheck daily" on server, I get this error: WARNING: silver.kodu: selfcheck request failed: timeout waiting for ACK on amcheck. wiki.zmanda.org says that it's a DNS problem - my client can't find an IP of the server's name. Both server and client are in the same subnet and use the same nameserver that definitely knows about both of their names - nslookup proves that ;) On server: $ hostname silver-fedora.kodu On client: $ nslookup fedora-silver.kodu Name: silver-fedora.kodu Address: 192.168.1.68 $ nslookup 192.168.1.68 68.1.168.192.in-addr.arpa name = silver-fedora.kodu. What else could be wrong? Thanks, Silver
Problem with amlabel
I'm sure I just have something written incorrectly, but here's the error I'm getting -bash-3.00$ amlabel dailyset dailyset0 slot 0changer: got exit: 1 str: could not read result from "/usr/local/libexec/chg-scsi-solaris.conf"amlabel: could not load slot "0": could not read result from "/usr/local/libexec/chg-scsi-solaris.conf"amlabel: could not load slot "0": could not read result from "/usr/local/libexec/chg-scsi-solaris.conf"amlabel: pid 1812 finish time Wed Apr 26 16:27:24 2006-bash-3.00$ Output of that file: -bash-3.00$ cat "/usr/local/libexec/chg-scsi-solaris.conf"number_configs 1eject 0 # Tapedrives need an eject commandsleep 15 # Seconds to wait until the tape gets readycleanmax 10 # How many times could a cleaning tape get usedchangerdev /dev/0bn## Next comes the data for drive 0#config 0drivenum 0dev /dev/rmt/0bn # the device that is used for the tapedrive 0 (BSD type, no rewind, no compression)startuse 0 # The slots associated with the drive 0enduse 17 # statfile /usr/local/etc/amanda/dailyset/tape0-slot # The file where the actual slot is storedcleancart 18 # the slot where the cleaningcartridge for drive 0 is locatedcleanfile /usr/local/etc/amanda/dailyset/tape0-clean # The file where the cleanings are recordedusagecount /usr/local/etc/amanda/dailyset/totaltimetapestatus /usr/local/etc/amanda/dailyset/tape0-status#labelfile /usr/local/etc/amanda/dailyset/labelfile # Use this if you have an barcode reader-bash-3.00$ Amanada user has read/write access to /usr/local/libexec and to the chg-scsi-solaris.conf file. can anyone point me in the right direction? Thanks Message transport security by GatewayDefender4:29:05 PM ET - 4/26/2006
Re: tape split question
On Wed, Apr 26, 2006 at 02:51:22PM -0400, McGraw, Robert P. wrote: > > > _ > Robert P. McGraw, Jr. > Manager, Computer System EMAIL: [EMAIL PROTECTED] > Purdue University ROOM: MATH-807 > Department of MathematicsPHONE: (765) 494-6055 > 150 N. University Street FAX: (419) 821-0540 > West Lafayette, IN 47907-2067 > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > On Behalf Of Jon LaBadie > > Sent: Wednesday, April 26, 2006 11:25 AM > > To: amanda-users@amanda.org > > Subject: Re: tape split question > > > > > > On Wed, Apr 26, 2006 at 10:30:42AM -0400, McGraw, Robert P. wrote: > > > > Was that a configure error not able to detect your mmap function? > > Or if you really don't have mmap, what system/OS is this? > > fssnap sounds like Solaris which certainly has mmap. > [McGraw, Robert P.] > For now I have increased my holding disk size to be greater than the largest > file system. > > I am not sure if mmap is in Solaris 10 but I would think so. I can do a man > mmap and I get the man page. > > I just ran configure.sh and let if find what is needed. > > The doc says > --with-mmapforce use of mmap instead of shared memory suppory > > I guess I could run configure with --with-mmap and see what happens. > I had to do that type of thing for several items on Solaris 8 x86, less so for Solaris 9. Locking mechanisms were the main unfound feature for me. Solaris had them "all" but none were found. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: tape split question
_
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: [EMAIL PROTECTED]
Purdue University ROOM: MATH-807
Department of MathematicsPHONE: (765) 494-6055
150 N. University Street FAX: (419) 821-0540
West Lafayette, IN 47907-2067
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Jon LaBadie
> Sent: Wednesday, April 26, 2006 11:25 AM
> To: amanda-users@amanda.org
> Subject: Re: tape split question
>
>
> On Wed, Apr 26, 2006 at 10:30:42AM -0400, McGraw, Robert P. wrote:
> > I am running Amanda 2.5.0 on a Solaris 10 host. This is the first time I
> > have tried the tape_splitsize to backup a large filesystem.
> >
> > My dump type looks a follows:
> > define dumptype users-tar-span {
> > global
> > comment "backup of users using tar with spanning"
> > program "GNUTAR"
> > tape_splitsize 30 Gb
> > maxdumps 10
> > exclude list "/pkgs/amanda/etc/amanda/exclude/user_exclude"
> > }
> >
> > In /var/amanda/archive/amdump I have
> >
> > taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6064,
> > splitting chunk that started at 62085120kb after 10208kb (next chunk
> will
> > start at 62095328kb)
> > taper: reader-side: got label archive:68 filenum 6066
> > taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6065,
> > splitting chunk that started at 62095360kb after 10208kb (next chunk
> will
> > start at 62105568kb)
> > taper: reader-side: got label archive:68 filenum 6067
> >
> > I killed the backup and the email output from the run showed the
> following:
> >
> > taper: tape archive:67 kb 172276416 fm 18 writing file: short
> write
> > taper: retrying zada:/export/data.0 on new tape due to: [writing file:
> > short write]
> > taper: mmap not available: using fallback split size of 10240kb to
> buffer
> > zorn:/export/fssnap/users.0 in-memory
> > taper: tape archive:68 kb 173468288 fm 7872 [OK]
> > taper: Received signal 15
> >
> > The filesystem that I am trying to backup with the tape split is 300GB.
> > After 12 hours the 300GB file system had only written about 60GB. I
> assume
> > the problem is the "mmap not available" and the split size of 10GB
> >
>
> Was that a configure error not able to detect your mmap function?
> Or if you really don't have mmap, what system/OS is this?
> fssnap sounds like Solaris which certainly has mmap.
[McGraw, Robert P.]
For now I have increased my holding disk size to be greater than the largest
file system.
I am not sure if mmap is in Solaris 10 but I would think so. I can do a man
mmap and I get the man page.
I just ran configure.sh and let if find what is needed.
The doc says
--with-mmapforce use of mmap instead of shared memory suppory
I guess I could run configure with --with-mmap and see what happens.
>
>
> > QUESTIONS:
> >
> > 1) The above log seems to show that the tape_splitsize is 10G and not
> the
> > 30G that I indicated in the tape_splitsize. Is this correct? Other than
> the
> > tape_splitsize what other parameter do I need.
>
> If I read that correctly, the "fallback" splitsize was 10MB, M, not G.
[McGraw, Robert P.]
I saw that after I sent the email.
>
> >
> > 2) My backup was running slow and and noticed that
> zorn./export/fssnap/users
> > was not in the HOLDING DISK so it must be reading the backup directly
> from
> > the disk. My holding disk is 200GB and the filesize that I am backing up
> is
> > 300GB. Do I need to have my HOLDING DISK size as large as the file
> system
> > that I am backing up when using the tape_splitsize?
>
> If the dumpsize is larger than available holding disk,
> the dump goes directly to tape.
>
> Sounds like a number of things might be contributing to bad performance.
[McGraw, Robert P.]
Thanks for your reply.
Reply
>
> --
> Jon H. LaBadie [EMAIL PROTECTED]
> JG Computing
> 4455 Province Line Road(609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
smime.p7s
Description: S/MIME cryptographic signature
Re: new linux client install
Paul Bijnens schrieb: > I think I see the light... :-) > The /tmp/amanda directory is owned by the wrong user! or is not writable by the amanda-user, yes ... I saw that light also ;-) Let's see if it gets through now ... Stefan
Re: new linux client install
On 2006-04-26 17:58, John Clement wrote: OK, I've re-added orinoco amandabackup orinoco.deanst.rroom.net amandabackup to the .amandahosts file, I'm sorry to tell you the bad news that this is again WRONG. on orinoco (the server) it runs as 'amanda', on the client it runs as 'amandabackup'. The error message that you get is: ... access as localuser not allowed from [EMAIL PROTECTED] : ... The LOCALUSER = amandabackup the REMOTEUSER on the AMANDASERVER is [EMAIL PROTECTED] The LOCALUSER must be able to read the file .amandahosts and in that file it finds the name of the AMANDASERVER, and the user on that server that is allowed to give orders here: amandaserver.example.com amandauserontheserver In your case: orinoco amanda. See also: http://wiki.zmanda.com/index.php/Amcheck:_access_as_localuser_not_allowed_from_remoteuser%40remotehost btw: your problem with permission of /tmp/amanda is described as one of the cause here: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out (i.e. exactly the error message you got) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: new linux client install
On 2006-04-26 17:23, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. The FILE does not need to be executable. The DIRECTORIES must be executable. You're making things so confusing... ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. I think I see the light... :-) The /tmp/amanda directory is owned by the wrong user! So do you mean that you have both a user "amanda" AND a user "amandabackup"? 1. When you put user "amanda" in the xinetd conf file, you do get a debug file, and you get the errormessage: "access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied". I can understand the "Permission denied" error here: the file is owned by user "amandabackup", and user "amanda" does not have access to the file. I do not understand why the programs says it runs as user "amandabackup" while you clearly state that you run it as "amanda". 2. When you put user "amandabackup" in xinetd conf file, you do NOT get a debug file at all. That means that xinetd didn't even got the program to START (any error in /var/log/messages?) but also that the debug file could not be created. Amandad tries to create the debug file the directory /tmp/amanda, but that was created on the first run with the wrong owner: amanda instead of amandabackup. ERASE the directory /tmp/amanda, and then try to run again with user "amandabackup" in the xinetd conf file. And let us know the complete error message. (Do not forget to signal xinetd if you made changes to the config file.) -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. Checking one of the debug files it was compiled with amandabackup as the user. So you put "amanda" in there, and you got a debug file. What errors did you find in that file? ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied You have to have orinoco amandabackup in your .amandahosts, btw (apart from the perms-problem). The server is orinoco? And there Amanda runs as amandabackup? And tries to contact the client on murray which runs as amandabackup as well?? OK, I've re-added orinoco amandabackup orinoco.deanst.rroom.net amandabackup to the .amandahosts file, on orinoco (the server) it runs as 'amanda', on the client it runs as 'amandabackup'. When putting "amandabackup" in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that "amandabackup" is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. grep amanda /etc/passwd Different group-memberships of amanda and amandabackup? Stefan amanda and amandabackup are both members of the disk group. Cheers
Re: tape split question
On Wednesday 26 April 2006 11:31, McGraw, Robert P. wrote: > For now I do have a holding disk space greater than 300GB that I can use. > If I set the size greater then 300GB this it should use this space rather > then shared memory? I think you are confusing mmap'd memory and shared memory. Shared memory is used by taper for something unrelated. There are three modes that Amanda can use when splitting dumps to tape: 1) Holding-disk mode. The entire dump is written to holding disk, then one chunk at a time is written to tape. 2) Split-diskbuffer mode. If your system supports MMAP, and you have configured a split_diskbuffer, and the image can't be done in holding-disk mode (too big, dumptype does not permit it, etc.), then the holding disk is used to buffer one chunk at a time: The chunk is written to the holding disk, then flushed to tape, then the next chunk starts, etc. 3) Memory-buffer mode. If there is a problem with split-diskbuffer mode, then Amanda will use the fallback_splitsize, and buffer the dump in-memory, one chunk at a time. You were using mode 3 in the example you sent us, because the holding disk was not big enough, and your system does not support mmap. > > When dumping directly to disk, and mmap is not available, then we use the > > fallback_splitsize (default 10M) instead of the tape_splitsize -- this is > > because the buffering is done in memory. If you have the memory, feel > > free to > > set a larger fallback_splitsize -- it will improve performance a lot. > > What does having mmap available do for me? At present, it is required for chunk-at-a-time buffering of data on the holding disk. But that mode is not preferred, because of performance. > Would this all be a non issue if I keep my holding disk size greater than > my largest filesystem? Correct. Cheers, --Ian -- Forums for Amanda discussion: http://forums.zmanda.com/
Re: new linux client install
John Clement schrieb: > Paul Bijnens wrote: >> On 2006-04-26 15:59, John Clement wrote: >>> Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: >>> /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. >>> Just made that change. >> >> Do you mean that one of the directories were not executable before, >> but now is? > Just the file wasn't executable, I didn't think it had to be, but I've > made it so now. >> > Oh yea, restarting xinetd, probably a good idea! Output from > amcheck now: > > WARNING: murray.deanst.rroom.net: selfcheck request timed out. > Host down? > Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? >>> Since changing the user in xinetd to 'amandabackup' there haven't >>> been any debug files. I checked by putting 'amanda' back in there and >>> restarting xinetd and I did get another debug file, complaining that >>> access as amandabackup is not allowed from [EMAIL PROTECTED] >> >> The user that you put in there must exist in the system (password, >> NIS,...). And the name of that user should be the one that the program >> has compiled in. You find those defaults in the debug >> file, which seems to mysteriously disappear... >> You cannot make something up. > Checking one of the debug files it was compiled with amandabackup as the > user. >> >> So you put "amanda" in there, and you got a debug file. >> What errors did you find in that file? > ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot > open /var/lib/amanda/.amand > ahosts: Permission denied You have to have orinoco amandabackup in your .amandahosts, btw (apart from the perms-problem). The server is orinoco? And there Amanda runs as amandabackup? And tries to contact the client on murray which runs as amandabackup as well?? >> When putting "amandabackup" in the xinetd.conf file, you claim there >> are no debug files and you get a selfcheck timeout. Right? >> That means to me that "amandabackup" is not a valid user or is not >> correctly defined (for xinetd). >> >> I strongly suspect a problem with that user? Do you have a uid-clash >> (two users with different name, but same uid-number)? >> Is there a local and a NIS-user that are different? >> > Having run several times with amanda and amandabackup as the user in > xinetd, its definately not making any debug files in /tmp/amanda when > xinetd's user is set to amandabackup, I've double checked that > amandabackup is a valid user, and that there's no uid clash either. grep amanda /etc/passwd Different group-memberships of amanda and amandabackup? Stefan
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: OK guys, 'amanad' was my typo copying the message into the email, here's .amandahosts Expected this, yes ... orinoco.deanst.rroom.netamanda orinoco amanda and amcheck WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Does not sound like a wrong .amandahosts ... More details (maybe you posted them earlier ..? ): What is your Amanda-server's fqdn? What's the fqdn of the client? server: orinoco.deanst.rroom.net client: murray.deanst.rroom.net and digging on both servers confirms they know who they are and who each other are. I didn't install the server or most of the clients here, I only added a client to this particular host yesterday using an RPM, as far as I remember it didn't ask me to configure what user it runs under. Can you point me in the right direction to configuring it to run as 'amanda' which appears to be how its set on the server... Run "amadmin version" and look for something like : CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=disk' [...] This way you find out the user and the group it was compiled with/for. server: user: amanda group: disk however I can't find amadmin on the client, at all (find / -name amadmin -print), although one of the debug files shows the following: user: amandabackup group: disk Thanks, john Stefan
Re: tape split question
On Wed, Apr 26, 2006 at 10:30:42AM -0400, McGraw, Robert P. wrote:
> I am running Amanda 2.5.0 on a Solaris 10 host. This is the first time I
> have tried the tape_splitsize to backup a large filesystem.
>
> My dump type looks a follows:
> define dumptype users-tar-span {
> global
> comment "backup of users using tar with spanning"
> program "GNUTAR"
> tape_splitsize 30 Gb
> maxdumps 10
> exclude list "/pkgs/amanda/etc/amanda/exclude/user_exclude"
> }
>
> In /var/amanda/archive/amdump I have
>
> taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6064,
> splitting chunk that started at 62085120kb after 10208kb (next chunk will
> start at 62095328kb)
> taper: reader-side: got label archive:68 filenum 6066
> taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6065,
> splitting chunk that started at 62095360kb after 10208kb (next chunk will
> start at 62105568kb)
> taper: reader-side: got label archive:68 filenum 6067
>
> I killed the backup and the email output from the run showed the following:
>
> taper: tape archive:67 kb 172276416 fm 18 writing file: short write
> taper: retrying zada:/export/data.0 on new tape due to: [writing file:
> short write]
> taper: mmap not available: using fallback split size of 10240kb to buffer
> zorn:/export/fssnap/users.0 in-memory
> taper: tape archive:68 kb 173468288 fm 7872 [OK]
> taper: Received signal 15
>
> The filesystem that I am trying to backup with the tape split is 300GB.
> After 12 hours the 300GB file system had only written about 60GB. I assume
> the problem is the "mmap not available" and the split size of 10GB
>
Was that a configure error not able to detect your mmap function?
Or if you really don't have mmap, what system/OS is this?
fssnap sounds like Solaris which certainly has mmap.
> QUESTIONS:
>
> 1) The above log seems to show that the tape_splitsize is 10G and not the
> 30G that I indicated in the tape_splitsize. Is this correct? Other than the
> tape_splitsize what other parameter do I need.
If I read that correctly, the "fallback" splitsize was 10MB, M, not G.
>
> 2) My backup was running slow and and noticed that zorn./export/fssnap/users
> was not in the HOLDING DISK so it must be reading the backup directly from
> the disk. My holding disk is 200GB and the filesize that I am backing up is
> 300GB. Do I need to have my HOLDING DISK size as large as the file system
> that I am backing up when using the tape_splitsize?
If the dumpsize is larger than available holding disk,
the dump goes directly to tape.
Sounds like a number of things might be contributing to bad performance.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Just the file wasn't executable, I didn't think it had to be, but I've made it so now. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. Checking one of the debug files it was compiled with amandabackup as the user. So you put "amanda" in there, and you got a debug file. What errors did you find in that file? ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amand ahosts: Permission denied When putting "amandabackup" in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that "amandabackup" is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? Having run several times with amanda and amandabackup as the user in xinetd, its definately not making any debug files in /tmp/amanda when xinetd's user is set to amandabackup, I've double checked that amandabackup is a valid user, and that there's no uid clash either. Thanks
Re: new linux client install
John Clement schrieb: > OK guys, 'amanad' was my typo copying the message into the email, here's > .amandahosts Expected this, yes ... > orinoco.deanst.rroom.netamanda > orinoco amanda > > and amcheck > > WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Does not sound like a wrong .amandahosts ... More details (maybe you posted them earlier ..? ): What is your Amanda-server's fqdn? What's the fqdn of the client? > I didn't install the server or most of the clients here, I only added a > client to this particular host yesterday using an RPM, as far as I > remember it didn't ask me to configure what user it runs under. Can you > point me in the right direction to configuring it to run as 'amanda' > which appears to be how its set on the server... Run "amadmin version" and look for something like : CONFIGURE_COMMAND="'./configure' '--with-user=amanda' '--with-group=disk' [...] This way you find out the user and the group it was compiled with/for. Stefan
Re: tape split question
On Wednesday 26 April 2006 10:30, McGraw, Robert P. wrote: > 1) The above log seems to show that the tape_splitsize is 10G and not the > 30G that I indicated in the tape_splitsize. Is this correct? Other than the > tape_splitsize what other parameter do I need. No, the tape_splitsize used was only 10M, not even 10G. Read on. > 2) My backup was running slow and and noticed that > zorn./export/fssnap/users was not in the HOLDING DISK so it must be reading > the backup directly from the disk. My holding disk is 200GB and the > filesize that I am backing up is 300GB. Do I need to have my HOLDING DISK > size as large as the file system that I am backing up when using the > tape_splitsize? Yes, the spanning and splitting functionality still does not allow you to interleave dumps from different disks. So, if you do not have a big enough holding disk, dumps will still be done directly to tape -- which can be very slow. When dumping directly to disk, and mmap is not available, then we use the fallback_splitsize (default 10M) instead of the tape_splitsize -- this is because the buffering is done in memory. If you have the memory, feel free to set a larger fallback_splitsize -- it will improve performance a lot. Another option is to break the disk into smaller chunks that will fit on the holding disk. See here: http://wiki.zmanda.com/index.php/Manually_splitting_large_disks Cheers, --Ian -- Forums for Amanda discussion: http://forums.zmanda.com/
Re: 2.5.0 config file errors on FC5
On Wed, Apr 26, 2006 at 05:11:00PM +0300, Silver Salonen wrote: > > On Wednesday 26 April 2006 16:52, you wrote: > > On 2006-04-26 15:40, Silver Salonen wrote: > > > Hi. > > > > > > As I'm in kind of hurry (I'm writing a bachelor's thesis about backups > > > and ... > > > > > > > > I've configured everything exactly as written on the quick start page, > > > but > > > >... "exactly"... :-) > > > > > > > when I try to label a virtual tape (being actually a folder on hard > drive), I > > > get several errors about my amanda.conf. > > > > > > I execute: > > > # su - amandabackup > > > $ cd /backup/amanda-vtapes/ > > > $ ammt -t file:/backup/amanda-vtapes/tape rewind > > > $ amlabel daily Test-01 > > > > > > And get: > > > > > > "/etc/amanda/daily/amanda.conf", line 164: holding disk parameter expected > > > "/etc/amanda/daily/amanda.conf", line 164: end of line expected > > > > > > > > I think there's no point to copy-paste all the problematic lines, but I'd > do > > > it about some of the first. Lines from 164 to 168 are: > > > > > > infofile "/var/lib/amanda/daily/curinfo"# database > > > logdir "/var/lib/amanda/daily"# log directory > > > indexdir "/var/lib/amanda/daily/index" # index directory > > > tapelist "/var/lib/amanda/daily/tapelist" # list of used tapes > > > > How about the lines just before? > > There is probably a "holdingdisk" section, > > and you forgot to close the brace? > > > > Oh, damn. Now I'm embarrased.. that was it.. I just didn't uncomment the last > brace. > Golden Rule of debugging, when you get a message about a bug on line 68, look first at line 67 ;) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: new linux client install
Stefan G. Weichinger wrote: John Clement schrieb: Paul Bijnens wrote: Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] amanad? Third variation now ... check for typos in there. If ok, show us .amandahosts AND Output of amcheck again. -- Decide for one user, amanda OR amandabackup. What user did you configure/compile Amanda with? Make sure that user exists on that system, add it to the disk-group. Stefan OK guys, 'amanad' was my typo copying the message into the email, here's .amandahosts orinoco.deanst.rroom.netamanda orinoco amanda and amcheck WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? I didn't install the server or most of the clients here, I only added a client to this particular host yesterday using an RPM, as far as I remember it didn't ask me to configure what user it runs under. Can you point me in the right direction to configuring it to run as 'amanda' which appears to be how its set on the server... Thanks again, John
tape split question
I am running Amanda 2.5.0 on a Solaris 10 host. This is the first time I
have tried the tape_splitsize to backup a large filesystem.
My dump type looks a follows:
define dumptype users-tar-span {
global
comment "backup of users using tar with spanning"
program "GNUTAR"
tape_splitsize 30 Gb
maxdumps 10
exclude list "/pkgs/amanda/etc/amanda/exclude/user_exclude"
}
In /var/amanda/archive/amdump I have
taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6064,
splitting chunk that started at 62085120kb after 10208kb (next chunk will
start at 62095328kb)
taper: reader-side: got label archive:68 filenum 6066
taper: r: end zorn./export/fssnap/users.20060425201728.0 part 6065,
splitting chunk that started at 62095360kb after 10208kb (next chunk will
start at 62105568kb)
taper: reader-side: got label archive:68 filenum 6067
I killed the backup and the email output from the run showed the following:
taper: tape archive:67 kb 172276416 fm 18 writing file: short write
taper: retrying zada:/export/data.0 on new tape due to: [writing file:
short write]
taper: mmap not available: using fallback split size of 10240kb to buffer
zorn:/export/fssnap/users.0 in-memory
taper: tape archive:68 kb 173468288 fm 7872 [OK]
taper: Received signal 15
The filesystem that I am trying to backup with the tape split is 300GB.
After 12 hours the 300GB file system had only written about 60GB. I assume
the problem is the "mmap not available" and the split size of 10GB
QUESTIONS:
1) The above log seems to show that the tape_splitsize is 10G and not the
30G that I indicated in the tape_splitsize. Is this correct? Other than the
tape_splitsize what other parameter do I need.
2) My backup was running slow and and noticed that zorn./export/fssnap/users
was not in the HOLDING DISK so it must be reading the backup directly from
the disk. My holding disk is 200GB and the filesize that I am backing up is
300GB. Do I need to have my HOLDING DISK size as large as the file system
that I am backing up when using the tape_splitsize?
Thanks
_
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: [EMAIL PROTECTED]
Purdue University ROOM: MATH-807
Department of MathematicsPHONE: (765) 494-6055
150 N. University Street FAX: (419) 821-0540
West Lafayette, IN 47907-2067
smime.p7s
Description: S/MIME cryptographic signature
Re: permission problem with amrecover
On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote: >Hi list, > >Thanks to your help, I've successful launched amcheck and amdump :-) >I've tried amrecover to check recovery too but some new problems > occured. > >After playing with access not allowed error, I'm still stuck on the >following one: > >backup:/# amrecover DailySet > >AMRECOVER Version 2.5.0. Contacting server on backup ... > >220 backup AMANDA index server (2.5.0) ready. > >200 Access OK > >Setting restore date to today (2006-04-26) > >200 Working date set to 2006-04-26. > >501 Could not read config file /etc/amanda/DailySet/amanda.conf! > > >I've checked amindexd logs: > >backup:/var/log/amanda# vi amindexd.20060426132954.debug > >amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26 >13:23:57 2006 > >amindexd: version 2.5.0 > >amindexd: < 220 backup AMANDA index server (2.5.0) ready. > >amindexd: > SECURITY USER root > >bsd security: remote host backup.gpsa.fr user root local user backup > >amindexd: < 200 Access OK > >amindexd: > FEATURES feff9ffe07 > >amindexd: < 200 FEATURES feff9ffe07 > >amindexd: > DATE 2006-04-26 > >amindexd: < 200 Working date set to 2006-04-26. > >amindexd: > SCNF DailySet > >could not open conf file "/etc/amanda/DailySet/amanda.conf": > Permission denied > >amindexd: < 501 Could not read config file > /etc/amanda/DailySet/amanda.conf! > > > >My permissions for /etc/amanda/DailySet/amanda.conf: > >backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf >-rwxrwx--- 1 root amanda 4451 2006-04-25 16:19 >/etc/amanda/DailySet/amanda.conf > >I don't understand why it complain about that... You've apparently edited the amanda.conf as root (never do that, always become amanda to do that) and the perms are now fubar. It should look something like this: -rw-r--r-- 1 amanda disk 22049 Apr 16 08:59 /usr/local/etc/amanda/Daily/amanda.conf The user amanda should be a member of the group disk or backup. AFAIK, there is no group 'amanda', at least not here. Is this a new install? >Any help would be appreciate > > >Thomas -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: new linux client install
On 2006-04-26 15:59, John Clement wrote: Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Do you mean that one of the directories were not executable before, but now is? Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] The user that you put in there must exist in the system (password, NIS,...). And the name of that user should be the one that the program has compiled in. You find those defaults in the debug file, which seems to mysteriously disappear... You cannot make something up. So you put "amanda" in there, and you got a debug file. What errors did you find in that file? When putting "amandabackup" in the xinetd.conf file, you claim there are no debug files and you get a selfcheck timeout. Right? That means to me that "amandabackup" is not a valid user or is not correctly defined (for xinetd). I strongly suspect a problem with that user? Do you have a uid-clash (two users with different name, but same uid-number)? Is there a local and a NIS-user that are different? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: new linux client install
John Clement schrieb: > Paul Bijnens wrote: >> Is there a debugfile created (/tmp/amanda/amandad.*.debug)? >> What is in it? >> > Since changing the user in xinetd to 'amandabackup' there haven't been > any debug files. I checked by putting 'amanda' back in there and > restarting xinetd and I did get another debug file, complaining that > access as amandabackup is not allowed from [EMAIL PROTECTED] amanad? Third variation now ... check for typos in there. If ok, show us .amandahosts AND Output of amcheck again. -- Decide for one user, amanda OR amandabackup. What user did you configure/compile Amanda with? Make sure that user exists on that system, add it to the disk-group. Stefan
Re: 2.5.0 config file errors on FC5
Oh, damn. Now I'm embarrased.. that was it.. I just didn't uncomment the last brace. Thanks, Silver On Wednesday 26 April 2006 16:52, you wrote: > On 2006-04-26 15:40, Silver Salonen wrote: > > Hi. > > > > As I'm in kind of hurry (I'm writing a bachelor's thesis about backups and a > > small part of it is about Amanda and the deadline is at the beginning of the > > next week), I installed Amanda 2.5.0 RPM for FC4 on FC5. > > > > I've looked Amanda's official documentation's page about a dozen times, but it > > looks somewhat obfuscating, so now I tried to start with Amanda according to > > Zmanda's quick start guide (http://wiki.zmanda.com/index.php/Quick_start). > > BTW, could anybody suggest a nice documentation where it would be possible to > > get a nice and quick overview about Amanda's structure (the main process, > > dealing with backup-media, etc. - some chema maybe)? The main documentation > > is really scary - it has specific information and how-to's about different > > parts, but the overall picture.. :( > > > http://wiki.zmanda.com/index.php/Amanda_chapter > > > > > > I've configured everything exactly as written on the quick start page, but > >... "exactly"... :-) > > > > when I try to label a virtual tape (being actually a folder on hard drive), I > > get several errors about my amanda.conf. > > > > I execute: > > # su - amandabackup > > $ cd /backup/amanda-vtapes/ > > $ ammt -t file:/backup/amanda-vtapes/tape rewind > > $ amlabel daily Test-01 > > > > And get: > > > > "/etc/amanda/daily/amanda.conf", line 164: holding disk parameter expected > > "/etc/amanda/daily/amanda.conf", line 164: end of line expected > > > > > I think there's no point to copy-paste all the problematic lines, but I'd do > > it about some of the first. Lines from 164 to 168 are: > > > > infofile "/var/lib/amanda/daily/curinfo"# database DIRECTORY > > logdir "/var/lib/amanda/daily"# log directory > > indexdir "/var/lib/amanda/daily/index" # index directory > > tapelist "/var/lib/amanda/daily/tapelist" # list of used tapes > > How about the lines just before? > There is probably a "holdingdisk" section, > and you forgot to close the brace? > > > > > > # tapelist is stored, by default, in the directory that contains amanda.conf > > > > I've googled about this error, but everything I've found is some of Amanda's > > source-code. > > > > Is the FC4 version really so incompatible with FC5 or what could be the > > problem? > > Too much in a hurry and overlooking the obvious errors? > > > -- > Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * > * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** > >
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] jc
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Just made that change. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? Since changing the user in xinetd to 'amandabackup' there haven't been any debug files. I checked by putting 'amanda' back in there and restarting xinetd and I did get another debug file, complaining that access as amandabackup is not allowed from [EMAIL PROTECTED] jc
Re: 2.5.0 config file errors on FC5
On 2006-04-26 15:40, Silver Salonen wrote: Hi. As I'm in kind of hurry (I'm writing a bachelor's thesis about backups and a small part of it is about Amanda and the deadline is at the beginning of the next week), I installed Amanda 2.5.0 RPM for FC4 on FC5. I've looked Amanda's official documentation's page about a dozen times, but it looks somewhat obfuscating, so now I tried to start with Amanda according to Zmanda's quick start guide (http://wiki.zmanda.com/index.php/Quick_start). BTW, could anybody suggest a nice documentation where it would be possible to get a nice and quick overview about Amanda's structure (the main process, dealing with backup-media, etc. - some chema maybe)? The main documentation is really scary - it has specific information and how-to's about different parts, but the overall picture.. :( http://wiki.zmanda.com/index.php/Amanda_chapter I've configured everything exactly as written on the quick start page, but ... "exactly"... :-) when I try to label a virtual tape (being actually a folder on hard drive), I get several errors about my amanda.conf. I execute: # su - amandabackup $ cd /backup/amanda-vtapes/ $ ammt -t file:/backup/amanda-vtapes/tape rewind $ amlabel daily Test-01 And get: "/etc/amanda/daily/amanda.conf", line 164: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 164: end of line expected I think there's no point to copy-paste all the problematic lines, but I'd do it about some of the first. Lines from 164 to 168 are: infofile "/var/lib/amanda/daily/curinfo"# database DIRECTORY logdir "/var/lib/amanda/daily"# log directory indexdir "/var/lib/amanda/daily/index" # index directory tapelist "/var/lib/amanda/daily/tapelist" # list of used tapes How about the lines just before? There is probably a "holdingdisk" section, and you forgot to close the brace? # tapelist is stored, by default, in the directory that contains amanda.conf I've googled about this error, but everything I've found is some of Amanda's source-code. Is the FC4 version really so incompatible with FC5 or what could be the problem? Too much in a hurry and overlooking the obvious errors? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
2.5.0 config file errors on FC5
Hi. As I'm in kind of hurry (I'm writing a bachelor's thesis about backups and a small part of it is about Amanda and the deadline is at the beginning of the next week), I installed Amanda 2.5.0 RPM for FC4 on FC5. I've looked Amanda's official documentation's page about a dozen times, but it looks somewhat obfuscating, so now I tried to start with Amanda according to Zmanda's quick start guide (http://wiki.zmanda.com/index.php/Quick_start). BTW, could anybody suggest a nice documentation where it would be possible to get a nice and quick overview about Amanda's structure (the main process, dealing with backup-media, etc. - some chema maybe)? The main documentation is really scary - it has specific information and how-to's about different parts, but the overall picture.. :( I've configured everything exactly as written on the quick start page, but when I try to label a virtual tape (being actually a folder on hard drive), I get several errors about my amanda.conf. I execute: # su - amandabackup $ cd /backup/amanda-vtapes/ $ ammt -t file:/backup/amanda-vtapes/tape rewind $ amlabel daily Test-01 And get: "/etc/amanda/daily/amanda.conf", line 164: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 164: end of line expected "/etc/amanda/daily/amanda.conf", line 166: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 166: end of line expected "/etc/amanda/daily/amanda.conf", line 168: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 168: end of line expected "/etc/amanda/daily/amanda.conf", line 170: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 170: end of line expected "/etc/amanda/daily/amanda.conf", line 213: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 213: end of line expected "/etc/amanda/daily/amanda.conf", line 214: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 214: end of line expected "/etc/amanda/daily/amanda.conf", line 217: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 217: end of line expected "/etc/amanda/daily/amanda.conf", line 218: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 219: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 219: end of line expected "/etc/amanda/daily/amanda.conf", line 220: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 221: holding disk parameter expected "/etc/amanda/daily/amanda.conf", line 221: end of line expected "/etc/amanda/daily/amanda.conf", line 222: holding disk parameter expected amlabel: errors processing config file "/etc/amanda/daily/amanda.conf" I think there's no point to copy-paste all the problematic lines, but I'd do it about some of the first. Lines from 164 to 168 are: infofile "/var/lib/amanda/daily/curinfo"# database DIRECTORY logdir "/var/lib/amanda/daily"# log directory indexdir "/var/lib/amanda/daily/index" # index directory tapelist "/var/lib/amanda/daily/tapelist" # list of used tapes # tapelist is stored, by default, in the directory that contains amanda.conf I've googled about this error, but everything I've found is some of Amanda's source-code. Is the FC4 version really so incompatible with FC5 or what could be the problem? Thanks in advance, Silver
permission problem with amrecover
Hi list, Thanks to your help, I've successful launched amcheck and amdump :-) I've tried amrecover to check recovery too but some new problems occured. After playing with access not allowed error, I'm still stuck on the following one: backup:/# amrecover DailySet AMRECOVER Version 2.5.0. Contacting server on backup ... 220 backup AMANDA index server (2.5.0) ready. 200 Access OK Setting restore date to today (2006-04-26) 200 Working date set to 2006-04-26. 501 Could not read config file /etc/amanda/DailySet/amanda.conf! I've checked amindexd logs: backup:/var/log/amanda# vi amindexd.20060426132954.debug amindexd: debug 1 pid 12531 ruid 34 euid 34: start at Wed Apr 26 13:23:57 2006 amindexd: version 2.5.0 amindexd: < 220 backup AMANDA index server (2.5.0) ready. amindexd: > SECURITY USER root bsd security: remote host backup.gpsa.fr user root local user backup amindexd: < 200 Access OK amindexd: > FEATURES feff9ffe07 amindexd: < 200 FEATURES feff9ffe07 amindexd: > DATE 2006-04-26 amindexd: < 200 Working date set to 2006-04-26. amindexd: > SCNF DailySet could not open conf file "/etc/amanda/DailySet/amanda.conf": Permission denied amindexd: < 501 Could not read config file /etc/amanda/DailySet/amanda.conf! My permissions for /etc/amanda/DailySet/amanda.conf: backup:/var/log/amanda# ls -al /etc/amanda/DailySet/amanda.conf -rwxrwx--- 1 root amanda 4451 2006-04-25 16:19 /etc/amanda/DailySet/amanda.conf I don't understand why it complain about that... Any help would be appreciate Thomas
Re: new linux client install
On 2006-04-26 12:03, John Clement wrote: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts /, /var, /lib, /var/lib/amanda are all readable. To be complete, they should also be executable. Oh yea, restarting xinetd, probably a good idea! Output from amcheck now: WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down? Now it looks like xinetd had some problem with it. Is there something listening on port 10080/udp? Is there a debugfile created (/tmp/amanda/amandad.*.debug)? What is in it? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Estimate timeout from localhost / driver: WARNING: got empty schedule from planner
Joshua Baker-LePain wrote: > On Tue, 25 Apr 2006 at 9:22am, Thomas Grieder wrote > >> Since a few days I get this two error messages: >> >> Estimate timeout from localhost >> driver: WARNING: got empty schedule from planner > > 1) Using localhost in the disklist is generally frowned upon. It's not a >unique name, and will likely come back to bite you someday. > > 2) Look in /tmp/amanda at the *debug files -- most likely sendize*debug >and/or amandad*debug will have more info as to what's going wrong. > Thanks, backup is working well now. Thomas
Re: new linux client install
Paul Bijnens wrote: On 2006-04-26 11:17, John Clement wrote: ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied Any more suggestions? - thanks What about leaving the Amanda set up alone for while, and just trying just this: # su amandabackup -c "cat /var/lib/amanda/.amandahosts" Does that work, or do you get "Permission denied"? Hey Paul, sorry I didn't think to include the result of doing this earlier: [EMAIL PROTECTED] amanda]# su amandabackup -c "cat /var/lib/amanda/.amandahosts" orinoco.deanst.rroom.netamanda orinoco amanda [EMAIL PROTECTED] amanda]# thanks
Re: new linux client install
On 2006-04-26 11:17, John Clement wrote: ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied Any more suggestions? - thanks What about leaving the Amanda set up alone for while, and just trying just this: # su amandabackup -c "cat /var/lib/amanda/.amandahosts" Does that work, or do you get "Permission denied"? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: new linux client install
Stefan G. Weichinger wrote:
John Clement schrieb:
OK, the story continues, thanks to all those who've contributed so
far!! Here's how things are now after all your comments. The client is
a new install of 2.5, server is 2.4.4p3
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
/, /var, /lib, /var/lib/amanda are all readable.
xinetd.d/amanda:
=
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
disable = no
only_from = 10.10.1.8 192.168.0.1
}
=
but still I get this from amcheck:
ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
Any more suggestions? - thanks
Was xinetd restarted after editing that file?
What if you remove the "only_from"-line for a test (and restart xinetd)?
Here it looks like
# ls -la ~amanda/.amandahosts
-rw--- 1 amanda root 190 Jun 27 2005 /var/lib/amanda/.amandahosts
Stefan
Oh yea, restarting xinetd, probably a good idea! Output from amcheck now:
WARNING: murray.deanst.rroom.net: selfcheck request timed out. Host down?
Re: new linux client install
John Clement schrieb:
> OK, the story continues, thanks to all those who've contributed so
> far!! Here's how things are now after all your comments. The client is
> a new install of 2.5, server is 2.4.4p3
>
> -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
>
> /, /var, /lib, /var/lib/amanda are all readable.
>
> xinetd.d/amanda:
>
> =
> service amanda
> {
>socket_type = dgram
>protocol= udp
>wait= yes
>user= amandabackup
>group = disk
>groups = yes
>server = /usr/lib/amanda/amandad
>disable = no
>only_from = 10.10.1.8 192.168.0.1
> }
> =
>
> but still I get this from amcheck:
>
> ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
> from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
> Permission denied
>
> Any more suggestions? - thanks
Was xinetd restarted after editing that file?
What if you remove the "only_from"-line for a test (and restart xinetd)?
Here it looks like
# ls -la ~amanda/.amandahosts
-rw--- 1 amanda root 190 Jun 27 2005 /var/lib/amanda/.amandahosts
Stefan
Re: new linux client install
Paul Bijnens wrote:
On 2006-04-26 10:12, John Clement wrote:
Pavel Pragin wrote:
John Clement wrote:
Having read through some of the documentation it seemed a fairly
straight forward thing to install an Amanda client. However, I
used an rpm for it, having been forced to upgrade my tar software
too but it appears to be running as amandabackup and in
/var/lib... So I'm now getting the following:
amandad: time 0.002: accept error: access as amandabackup not
allowed from [EMAIL PROTECTED]: cannot open
/var/lib/amanda/.amandahosts: Permission denied
amandad: time 0.002: sending NAK pkt:
<
ERROR access as amandabackup not allowed from [EMAIL PROTECTED]:
cannot open /var/lib/amanda/.amandahosts: Permission denied
>
at the bottom of my amcheck. I've confirmed that the file is owned
and chmoded correctly:
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
If I change the ownership or permissions it complains, so I think
they are correct. In the .amandahosts file I have
server.domain.tld amanda
server amanda
server.domain.tld amandabackup #added incase it made a difference
server amandabackup #added incase it made a difference
So can anyone make any suggestions?
Thanks
make sure that /var/lib/amanda/.amandahosts is owned by amanda and
the group is set to disk "chown amanda:disk
/var/lib/amanda/.amandahosts"
Sorry, yes, it was infact owned by amanda:disk, the line I posted was
from one of the 'lets just change something and hope it works'
attempts I was having...
...
It should be owned by the user the runs the amanda software.
It seems that is "amandabackup" in your setup.
Anatomy of the errormsg:
access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
"amandabackup" is the local user
"[EMAIL PROTECTED]" is the [EMAIL PROTECTED] that tries to connect.
And the errormsg is that the local user "amandabackup" has no
permission to read/access the file .amandahosts .
So try:
# su amandabackup -c "cat /var/lib/amanda/.amandahosts"
and fix those permissions.
OK, the story continues, thanks to all those who've contributed so
far!! Here's how things are now after all your comments. The client is
a new install of 2.5, server is 2.4.4p3
-rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts
/, /var, /lib, /var/lib/amanda are all readable.
xinetd.d/amanda:
=
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
disable = no
only_from = 10.10.1.8 192.168.0.1
}
=
but still I get this from amcheck:
ERROR: NAK murray.deanst.rroom.net: access as amandabackup not allowed
from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts:
Permission denied
Any more suggestions? - thanks
Re: new linux client install
On 2006-04-26 10:12, John Clement wrote: Pavel Pragin wrote: John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: < ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied > at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? Thanks make sure that /var/lib/amanda/.amandahosts is owned by amanda and the group is set to disk "chown amanda:disk /var/lib/amanda/.amandahosts" Sorry, yes, it was infact owned by amanda:disk, the line I posted was from one of the 'lets just change something and hope it works' attempts I was having... ... It should be owned by the user the runs the amanda software. It seems that is "amandabackup" in your setup. Anatomy of the errormsg: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied "amandabackup" is the local user "[EMAIL PROTECTED]" is the [EMAIL PROTECTED] that tries to connect. And the errormsg is that the local user "amandabackup" has no permission to read/access the file .amandahosts . So try: # su amandabackup -c "cat /var/lib/amanda/.amandahosts" and fix those permissions. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: new linux client install
Pavel Pragin wrote: John Clement wrote: Having read through some of the documentation it seemed a fairly straight forward thing to install an Amanda client. However, I used an rpm for it, having been forced to upgrade my tar software too but it appears to be running as amandabackup and in /var/lib... So I'm now getting the following: amandad: time 0.002: accept error: access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied amandad: time 0.002: sending NAK pkt: < ERROR access as amandabackup not allowed from [EMAIL PROTECTED]: cannot open /var/lib/amanda/.amandahosts: Permission denied > at the bottom of my amcheck. I've confirmed that the file is owned and chmoded correctly: -rw--- 1 amandabackup disk 109 Apr 25 14:23 .amandahosts If I change the ownership or permissions it complains, so I think they are correct. In the .amandahosts file I have server.domain.tld amanda server amanda server.domain.tld amandabackup #added incase it made a difference server amandabackup #added incase it made a difference So can anyone make any suggestions? Thanks make sure that /var/lib/amanda/.amandahosts is owned by amanda and the group is set to disk "chown amanda:disk /var/lib/amanda/.amandahosts" Sorry, yes, it was infact owned by amanda:disk, the line I posted was from one of the 'lets just change something and hope it works' attempts I was having...
