Re: Amanda and localhost definition?
On Thu, Apr 13, 2006 at 11:18:10AM +0200, Paul Bijnens wrote: > On 2006-04-12 18:06, stan wrote: > >[EMAIL PROTECTED]:~$ ping amanda > >PING amanda.meadwestvaco.com (170.85.113.24) 56(84) bytes of data. > >64 bytes from amanda.meadwestvaco.com (170.85.113.24): icmp_seq=1 ttl=63 > >time=0.650 ms > > So you are pinging a computer with IP-adress 170.85.113.24. This is ebarisng :- But in the name of full disclosure, taht is indeed the probelm. My only excuse is that all of my machines (except for a couple0 are on the 113 network. o what was hapeining here was that the /etc/hosts files and DNS disagreed on teh IP address of this machine. Interesting failure mode for that. Thanks to you and everyone else for the patioent help!, and again I apologize!! -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wednesday 12 April 2006 20:58, stan wrote: [...] >> Now obviously some of the above will need massaging in your favorite >> editor, so check the accuracy of every line above to make sure its >> right for *your* system. > >I know this thread has been draging on for days, so here is my > configure script, which was posted earlier in this thread BTW. Unforch, you put your config under the sig seperator, which means it won't echo when I do a reply, so cut & paste to the rescue. #!/bin/sh ./configure \ --with-config=DailyDump \ --prefix=/opt/amanda \ --with-index-server=amanda.meadwestvaco.com \ --with-user=amanda \ --with-group=operator \ --with-tape-server=amanda.meadwestvaco.com \ --with-debugging \ --with-tape-device=/dev/nst0 \ --sbindir=/opt/amanda/sbin \ --libexecdir=/opt/amanda/libexec \ --libdir=/opt/amanda/lib \ --with-configdir=/opt/amanda/etc \ --with-gnutar-listdir=/opt/amanda/var/gnutar-lists \ --mandir=/opt/amanda/man \ --without-rundump Where is the location of your tar, and what is this last --without_rundump, I'm not familiar with that? I did change to FQDN's from short host name. -- 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: Amanda and localhost definition?
On 2006-04-12 18:06, stan wrote: [EMAIL PROTECTED]:~$ ping amanda PING amanda.meadwestvaco.com (170.85.113.24) 56(84) bytes of data. 64 bytes from amanda.meadwestvaco.com (170.85.113.24): icmp_seq=1 ttl=63 time=0.650 ms So you are pinging a computer with IP-adress 170.85.113.24. [EMAIL PROTECTED]:~$ nslookup amanda Server: 1xx.xx.113.8 Address:1xx.xx.113.8#53 Name: amanda.meadwestvaco.com Address: 1xx.xx.109.24 But (apart from the x's) the nameserver says the IP-number ends in 109.24 instead of 113.24. Or was that a mistake when adding the x's to obfuscate the number? So, yes there is a computer named amanda, and everything seems OK, to me from that standpoint. I'm not convinced yet... In the debug dir /tmp/amanda, there should be file "selfcheck.datatime.debug". Does that file contain indeed the error messages? Unfortuntaely there does not seem to e such a file, which is also starnge. Indeed. That's why I asked it. The client executes these commands, and it logs the same error in those files. Another argument that host "amanda" is still pointing to some other host too. When you do "ssh amanda" from your server, do you get to the localhost? Or do you get to another machine? -- 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: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 07:17:49PM -0400, Gene Heskett wrote: > On Wednesday 12 April 2006 12:10, stan wrote: > >On Wed, Apr 12, 2006 at 09:53:37AM -0400, Jon LaBadie wrote: > >> On Wed, Apr 12, 2006 at 08:42:44AM -0400, stan wrote: > >> > On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > >> > > On 2006-04-12 12:27, stan wrote: > >> > > >Again, I've never done that in the past. I've just made ceratin > >> > > > that the amanda user exists, > >> > > >and done the build/make install as root. Permissions have > >> > > > alwasy been fine. > >> > > > > >> > > >Having sad that, I'll rebuild the whole thing today using > >> > > > FQDB's, and building as amanda, then > >> > > >installing as root. > >> > > > >> > > It is not important as who you build -- root is no problem (but > >> > > security minded sysadmins avoid doing things as root unless > >> > > needed). But the "make install" should be done as root. > >> > > > >> > > Then subsequently, you should not RUN the program as root > >> > > (except amrecover, which should be run as root), because when > >> > > running the first time, Amanda creates some files. When doing > >> > > that as root - even only once - those files are owned by root > >> > > instead of the amanda user and you run into trouble next time. > >> > > >> > Right, we are good on that. > >> > > >> > > >BTW, speaking of rebuilding amanda, it would be nice if there > >> > > > were a "make no-overwrite > >> > > >confgis" option. > >> > > > >> > > "make install" does not install, nor overwrite any config file. > >> > > No need to disable that non-existing feature. > >> > > >> > I just foudn that out, to my pleasent suprise. > >> > > >> > In any case, I rebuilt uinsg FQDN's, and I still have these > >> > problems, An amcheck reports: > >> > >> Did your rebuild also involve rerunning "configure"? > > > >Yes, esentialy "make distclean ; ./run_configure ; make ; su - make > > install > > Stan, see the script below. You don't just "./configure" amanda, it > needs some arguments such as these in my script. > > #!/bin/sh > # since I'm always forgetting to su amanda... > if [ `whoami` != 'amanda' ]; then > echo > echo " Warning " > echo "Amanda needs to be configured and built by the user amanda," > echo "but must be installed by user root." > echo > exit 1 > fi > make clean > rm -f config.status config.cache > ./configure --with-user=amanda \ > --with-group=disk \ > --with-owner=amanda \ > --with-gnu-ld \ > --prefix=/usr/local \ > --with-tapedev="FILE:/amandatapes" \ > --with-debugging=/tmp/amanda-dbg/ \ > --with-tape-server=coyote \ > --with-amandahosts \ > --with-configdir=/usr/local/etc/amanda \ > --with-config=Daily \ > --with-gnutar=/usr/local/bin/tar > > make > = > Now obviously some of the above will need massaging in your favorite > editor, so check the accuracy of every line above to make sure its > right for *your* system. > I know this thread has been draging on for days, so here is my configure script, which was posted earlier in this thread BTW. -- I know this thread has been draging on for days, so here is my configure script, which was posted earlier in this thread BTW. #!/bin/sh ./configure \ --with-config=DailyDump \ --prefix=/opt/amanda \ --with-index-server=amanda.meadwestvaco.com \ --with-user=amanda \ --with-group=operator \ --with-tape-server=amanda.meadwestvaco.com \ --with-debugging \ --with-tape-device=/dev/nst0 \ --sbindir=/opt/amanda/sbin \ --libexecdir=/opt/amanda/libexec \ --libdir=/opt/amanda/lib \ --with-configdir=/opt/amanda/etc \ --with-gnutar-listdir=/opt/amanda/var/gnutar-lists \ --mandir=/opt/amanda/man \ --without-rundump I did change to FQDN's from short host name. U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wednesday 12 April 2006 12:10, stan wrote: >On Wed, Apr 12, 2006 at 09:53:37AM -0400, Jon LaBadie wrote: >> On Wed, Apr 12, 2006 at 08:42:44AM -0400, stan wrote: >> > On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: >> > > On 2006-04-12 12:27, stan wrote: >> > > >Again, I've never done that in the past. I've just made ceratin >> > > > that the amanda user exists, >> > > >and done the build/make install as root. Permissions have >> > > > alwasy been fine. >> > > > >> > > >Having sad that, I'll rebuild the whole thing today using >> > > > FQDB's, and building as amanda, then >> > > >installing as root. >> > > >> > > It is not important as who you build -- root is no problem (but >> > > security minded sysadmins avoid doing things as root unless >> > > needed). But the "make install" should be done as root. >> > > >> > > Then subsequently, you should not RUN the program as root >> > > (except amrecover, which should be run as root), because when >> > > running the first time, Amanda creates some files. When doing >> > > that as root - even only once - those files are owned by root >> > > instead of the amanda user and you run into trouble next time. >> > >> > Right, we are good on that. >> > >> > > >BTW, speaking of rebuilding amanda, it would be nice if there >> > > > were a "make no-overwrite >> > > >confgis" option. >> > > >> > > "make install" does not install, nor overwrite any config file. >> > > No need to disable that non-existing feature. >> > >> > I just foudn that out, to my pleasent suprise. >> > >> > In any case, I rebuilt uinsg FQDN's, and I still have these >> > problems, An amcheck reports: >> >> Did your rebuild also involve rerunning "configure"? > >Yes, esentialy "make distclean ; ./run_configure ; make ; su - make > install Stan, see the script below. You don't just "./configure" amanda, it needs some arguments such as these in my script. #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo " Warning " echo "Amanda needs to be configured and built by the user amanda," echo "but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev="FILE:/amandatapes" \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/usr/local/bin/tar make = Now obviously some of the above will need massaging in your favorite editor, so check the accuracy of every line above to make sure its right for *your* system. -- 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: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 09:53:37AM -0400, Jon LaBadie wrote: > On Wed, Apr 12, 2006 at 08:42:44AM -0400, stan wrote: > > On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > > > On 2006-04-12 12:27, stan wrote: > > > >Again, I've never done that in the past. I've just made ceratin that the > > > >amanda user exists, > > > >and done the build/make install as root. Permissions have alwasy been > > > >fine. > > > > > > > >Having sad that, I'll rebuild the whole thing today using FQDB's, and > > > >building as amanda, then > > > >installing as root. > > > > > > It is not important as who you build -- root is no problem (but > > > security minded sysadmins avoid doing things as root unless needed). > > > But the "make install" should be done as root. > > > > > > Then subsequently, you should not RUN the program as root (except > > > amrecover, which should be run as root), because when running the first > > > time, Amanda creates some files. When doing that as root - even only > > > once - those files are owned by root instead of the amanda user > > > and you run into trouble next time. > > > > Right, we are good on that. > > > > > > > > > > >BTW, speaking of rebuilding amanda, it would be nice if there were a > > > >"make > > > >no-overwrite > > > >confgis" option. > > > > > > "make install" does not install, nor overwrite any config file. > > > No need to disable that non-existing feature. > > > > > I just foudn that out, to my pleasent suprise. > > > > In any case, I rebuilt uinsg FQDN's, and I still have these problems, > > An amcheck reports: > > > > > Did your rebuild also involve rerunning "configure"? Yes, esentialy "make distclean ; ./run_configure ; make ; su - make install > -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 03:05:55PM +0200, Paul Bijnens wrote: > On 2006-04-12 14:46, stan wrote: > > > >Remember this all started when I changed /etc/hosts to fix sendmail. > > > > Actually you should have fixed sendmail instead of unfixing /etc/hosts :-) > > /etc/hosts: > 127.0.0.1 saturn.example.com saturn localhost.localdomain localhost [EMAIL PROTECTED]:/tmp/amanda$ cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 170.85.113.24 amanda.meadwestvaco.com amanda > > Next what is the output of "hostname"? [EMAIL PROTECTED]:/tmp/amanda$ hostname amanda > That should be the fqdn. > You may set the hostname if needed (and then find out how your > startup script configure that hostname and change that source of all > evil. (RH stores it in /etc/sysconfig/network). OK, I'll fix that. It's in /etc/hostname on Debian derived distros. I'll report back after I try that. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 09:32:50AM -0400, Gene Heskett wrote: > On Wednesday 12 April 2006 08:42, stan wrote: > >On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > >> On 2006-04-12 12:27, stan wrote: > >> >Again, I've never done that in the past. I've just made ceratin > >> > that the amanda user exists, > >> >and done the build/make install as root. Permissions have alwasy > >> > been fine. > >> > > >> >Having sad that, I'll rebuild the whole thing today using FQDB's, > >> > and building as amanda, then > >> >installing as root. > >> > >> It is not important as who you build -- root is no problem (but > >> security minded sysadmins avoid doing things as root unless needed). > >> But the "make install" should be done as root. > >> > >> Then subsequently, you should not RUN the program as root (except > >> amrecover, which should be run as root), because when running the > >> first time, Amanda creates some files. When doing that as root - > >> even only once - those files are owned by root instead of the amanda > >> user and you run into trouble next time. > > > >Right, we are good on that. > > > >> >BTW, speaking of rebuilding amanda, it would be nice if there were > >> > a "make no-overwrite > >> >confgis" option. > >> > >> "make install" does not install, nor overwrite any config file. > >> No need to disable that non-existing feature. > > > >I just foudn that out, to my pleasent suprise. > > > >In any case, I rebuilt uinsg FQDN's, and I still have these problems, > >An amcheck reports: > > > >Amanda Backup Client Hosts Check > > > >ERROR: amanda: [Can't open exclude file > >'/opt/amanda/lib/gnutar_exclude_list': No such file or directory] > >ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file > > or directory] > >ERROR: amanda: [could not access /data_backups (/data_backups): No > > such file or directory] > >Client check: 44 hosts checked in 9.986 seconds, 3 problems found > > > >(brought to you by Amanda 2.5.0) > > These look like legit errors. Do these locations and file exist? yes, see below. > > >but: > > > >[EMAIL PROTECTED]:~$ ls -l /opt/amanda/lib/gnutar_exclude_list > >-rw-r--r-- 1 amanda root 0 Mar 31 21:18 > > /opt/amanda/lib/gnutar_exclude_list > > Wrong ownership maybe? I use amanda:disk for such things here. > -rw-r--r-- 1 amanda disk27 Jun 2 2005 excludes > > >[EMAIL PROTECTED]:~$ ls -ld /dumpdisk > >drwxr-xr-x 3 amanda operator 27 Apr 11 12:27 /dumpdisk > drwxr-xr-x 2 amanda disk 4096 Apr 12 02:56 /dumps > > >[EMAIL PROTECTED]:~$ ls -ld /data_backups > >drwxrwxrwx 9 root root 232 Apr 12 02:01 /data_backups > drwxr-xr-x 4 amanda disk 4096 Dec 6 2004 /amandatapes > and every subdir and file in this tree is owned by amanda:disk > > I'd be more interested in an ls -lR on the above dir. But that will be > bulky. oHere's the first part of it: If you _really_ want it, I'll send it off list: [EMAIL PROTECTED]:/tmp/amanda$ ls -lR /data_backups | head /data_backups: total 2 drwxr-xr-x 29 stan root 856 Apr 8 21:36 elog_backups drwxr-xr-x 3 oracle sys 72 Apr 12 02:01 oracle_backups drwxrwxr-x 3 oracle sys 72 Apr 11 07:47 oracle_backups.previous drwxr-xr-x 26 amanda root 736 Mar 28 22:14 stan drwxrwxrwx 24 root root 680 Apr 11 19:37 tmp /data_backups/elog_backups: total 86 -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 03:18:07PM +0200, Paul Bijnens wrote: > On 2006-04-12 14:42, stan wrote: > > > >In any case, I rebuilt uinsg FQDN's, and I still have these problems, > >An amcheck reports: > > > >Amanda Backup Client Hosts Check > > > >ERROR: amanda: [Can't open exclude file > >'/opt/amanda/lib/gnutar_exclude_list': No such file or directory] > >ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file or > >directory] > >ERROR: amanda: [could not access /data_backups (/data_backups): No such > >file or directory] > >Client check: 44 hosts checked in 9.986 seconds, 3 problems found > > > >(brought to you by Amanda 2.5.0) > > So there is a computer named "amanda". Is it the correct one? > Is "ping amanda" pinging the good one? There is no other computer > named "amanda"? [EMAIL PROTECTED]:~$ ping amanda PING amanda.meadwestvaco.com (170.85.113.24) 56(84) bytes of data. 64 bytes from amanda.meadwestvaco.com (170.85.113.24): icmp_seq=1 ttl=63 time=0.650 ms [EMAIL PROTECTED]:~$ nslookup amanda Server: 1xx.xx.113.8 Address:1xx.xx.113.8#53 Name: amanda.meadwestvaco.com Address: 1xx.xx.109.24 So, yes there is a computer named amanda, and everything seems OK, to me from that standpoint. > I assume that is the server itself, ok? Correct. > Are ALL the DLE's on that server wrong? (I presume you have the root > fs also in the diskist, but that seems to be fine.) No,/ works fine (strange). Also when I do a reun, nothing goes to tape, which I suspect is related. > > In the debug dir /tmp/amanda, there should be file > "selfcheck.datatime.debug". > Does that file contain indeed the error messages? > Unfortuntaely there does not seem to e such a file, which is also starnge. > > > >but: > > > >[EMAIL PROTECTED]:~$ ls -l /opt/amanda/lib/gnutar_exclude_list > >-rw-r--r-- 1 amanda root 0 Mar 31 21:18 > >/opt/amanda/lib/gnutar_exclude_list > > > >[EMAIL PROTECTED]:~$ ls -ld /dumpdisk > >drwxr-xr-x 3 amanda operator 27 Apr 11 12:27 /dumpdisk > > > >[EMAIL PROTECTED]:~$ ls -ld /data_backups > >drwxrwxrwx 9 root root 232 Apr 12 02:01 /data_backups > > > >It helps in diagnosing this problem to remeber that this part was working > >_before_ I messed with /etc/hosts on the Amada machine. > > > >I'm totaly confused at this point in time, what should I do to further > >diagnose this problem? > > Would you believe I'm confused too? Yes :-) -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 08:42:44AM -0400, stan wrote: > On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > > On 2006-04-12 12:27, stan wrote: > > >Again, I've never done that in the past. I've just made ceratin that the > > >amanda user exists, > > >and done the build/make install as root. Permissions have alwasy been fine. > > > > > >Having sad that, I'll rebuild the whole thing today using FQDB's, and > > >building as amanda, then > > >installing as root. > > > > It is not important as who you build -- root is no problem (but > > security minded sysadmins avoid doing things as root unless needed). > > But the "make install" should be done as root. > > > > Then subsequently, you should not RUN the program as root (except > > amrecover, which should be run as root), because when running the first > > time, Amanda creates some files. When doing that as root - even only > > once - those files are owned by root instead of the amanda user > > and you run into trouble next time. > > Right, we are good on that. > > > > > > > >BTW, speaking of rebuilding amanda, it would be nice if there were a "make > > >no-overwrite > > >confgis" option. > > > > "make install" does not install, nor overwrite any config file. > > No need to disable that non-existing feature. > > > I just foudn that out, to my pleasent suprise. > > In any case, I rebuilt uinsg FQDN's, and I still have these problems, > An amcheck reports: > Did your rebuild also involve rerunning "configure"? If so, before doing the configure, did you run "make distclean"? The configure program retains some info from run to run so it doesn't have to redetermine some parameters. The "distclean" target gets rid of all cached information. There is another target that does it also, but I forget which. It definitely is not "clean". -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda and localhost definition?
On Wednesday 12 April 2006 08:46, stan wrote: >On Wed, Apr 12, 2006 at 08:31:35AM -0400, Gene Heskett wrote: >> On Wednesday 12 April 2006 06:27, stan wrote: >> >On Wed, Apr 12, 2006 at 12:40:32AM -0400, Gene Heskett wrote: >> >> On Tuesday 11 April 2006 18:04, stan wrote: >> >> >On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: >> >> >> On Tuesday 11 April 2006 13:23, stan wrote: >> >> >> >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: >> >> >> >> On Tuesday 11 April 2006 11:59, stan wrote: >> >> >> >> >I'm setting up a new Ubuntu box as my next generation >> >> >> >> > Amanda server. Somehow the /etc/hosts file for this >> >> >> >> > machine was created looking like this: >> >> >> >> >> >> FQDN's or addresses, but see below. >> >> I'm reminded of the lines displayed rather prominantly on the cover >> of the manual of what was pretty close to the first *decent* >> consumer audio tape recorder marketed in the middle 1950's here in >> the states, the Bell RT-7, where it said: >> >>PLEASE try our way first! > >I _think_ at this point in time, I'm doing it precisely the way you > are suggesting (see previous post to this thread), but I till have > issues with _some- of the DLE's, and the exclude file on the Amanda > host _inly_. Very puzzling. > >Remember this all started when I changed /etc/hosts to fix sendmail. and I'm now leaning toward there being a problem between naming the machine amanda, and having a user named amanda. But I can't speak to the interactions that might bring about, never having tried that here. Perhaps someone else can adress that subject? -- 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: Amanda and localhost definition?
On Wednesday 12 April 2006 08:42, stan wrote: >On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: >> On 2006-04-12 12:27, stan wrote: >> >Again, I've never done that in the past. I've just made ceratin >> > that the amanda user exists, >> >and done the build/make install as root. Permissions have alwasy >> > been fine. >> > >> >Having sad that, I'll rebuild the whole thing today using FQDB's, >> > and building as amanda, then >> >installing as root. >> >> It is not important as who you build -- root is no problem (but >> security minded sysadmins avoid doing things as root unless needed). >> But the "make install" should be done as root. >> >> Then subsequently, you should not RUN the program as root (except >> amrecover, which should be run as root), because when running the >> first time, Amanda creates some files. When doing that as root - >> even only once - those files are owned by root instead of the amanda >> user and you run into trouble next time. > >Right, we are good on that. > >> >BTW, speaking of rebuilding amanda, it would be nice if there were >> > a "make no-overwrite >> >confgis" option. >> >> "make install" does not install, nor overwrite any config file. >> No need to disable that non-existing feature. > >I just foudn that out, to my pleasent suprise. > >In any case, I rebuilt uinsg FQDN's, and I still have these problems, >An amcheck reports: > >Amanda Backup Client Hosts Check > >ERROR: amanda: [Can't open exclude file >'/opt/amanda/lib/gnutar_exclude_list': No such file or directory] >ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file > or directory] >ERROR: amanda: [could not access /data_backups (/data_backups): No > such file or directory] >Client check: 44 hosts checked in 9.986 seconds, 3 problems found > >(brought to you by Amanda 2.5.0) These look like legit errors. Do these locations and file exist? >but: > >[EMAIL PROTECTED]:~$ ls -l /opt/amanda/lib/gnutar_exclude_list >-rw-r--r-- 1 amanda root 0 Mar 31 21:18 > /opt/amanda/lib/gnutar_exclude_list Wrong ownership maybe? I use amanda:disk for such things here. -rw-r--r-- 1 amanda disk27 Jun 2 2005 excludes >[EMAIL PROTECTED]:~$ ls -ld /dumpdisk >drwxr-xr-x 3 amanda operator 27 Apr 11 12:27 /dumpdisk drwxr-xr-x 2 amanda disk 4096 Apr 12 02:56 /dumps >[EMAIL PROTECTED]:~$ ls -ld /data_backups >drwxrwxrwx 9 root root 232 Apr 12 02:01 /data_backups drwxr-xr-x 4 amanda disk 4096 Dec 6 2004 /amandatapes and every subdir and file in this tree is owned by amanda:disk I'd be more interested in an ls -lR on the above dir. But that will be bulky. >It helps in diagnosing this problem to remeber that this part was > working _before_ I messed with /etc/hosts on the Amada machine. > >I'm totaly confused at this point in time, what should I do to further >diagnose this problem? > >Oh, and thnks for all the help! NP, If I can help. -- 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: Amanda and localhost definition?
On 2006-04-12 14:42, stan wrote: In any case, I rebuilt uinsg FQDN's, and I still have these problems, An amcheck reports: Amanda Backup Client Hosts Check ERROR: amanda: [Can't open exclude file '/opt/amanda/lib/gnutar_exclude_list': No such file or directory] ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file or directory] ERROR: amanda: [could not access /data_backups (/data_backups): No such file or directory] Client check: 44 hosts checked in 9.986 seconds, 3 problems found (brought to you by Amanda 2.5.0) So there is a computer named "amanda". Is it the correct one? Is "ping amanda" pinging the good one? There is no other computer named "amanda"? I assume that is the server itself, ok? Are ALL the DLE's on that server wrong? (I presume you have the root fs also in the diskist, but that seems to be fine.) In the debug dir /tmp/amanda, there should be file "selfcheck.datatime.debug". Does that file contain indeed the error messages? but: [EMAIL PROTECTED]:~$ ls -l /opt/amanda/lib/gnutar_exclude_list -rw-r--r-- 1 amanda root 0 Mar 31 21:18 /opt/amanda/lib/gnutar_exclude_list [EMAIL PROTECTED]:~$ ls -ld /dumpdisk drwxr-xr-x 3 amanda operator 27 Apr 11 12:27 /dumpdisk [EMAIL PROTECTED]:~$ ls -ld /data_backups drwxrwxrwx 9 root root 232 Apr 12 02:01 /data_backups It helps in diagnosing this problem to remeber that this part was working _before_ I messed with /etc/hosts on the Amada machine. I'm totaly confused at this point in time, what should I do to further diagnose this problem? Would you believe I'm confused too? -- 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: Amanda and localhost definition?
On 2006-04-12 14:46, stan wrote: Remember this all started when I changed /etc/hosts to fix sendmail. Actually you should have fixed sendmail instead of unfixing /etc/hosts :-) /etc/hosts: 127.0.0.1 saturn.example.com saturn localhost.localdomain localhost Next what is the output of "hostname"? That should be the fqdn. You may set the hostname if needed (and then find out how your startup script configure that hostname and change that source of all evil. (RH stores it in /etc/sysconfig/network). -- 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: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 08:31:35AM -0400, Gene Heskett wrote: > On Wednesday 12 April 2006 06:27, stan wrote: > >On Wed, Apr 12, 2006 at 12:40:32AM -0400, Gene Heskett wrote: > >> On Tuesday 11 April 2006 18:04, stan wrote: > >> >On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: > >> >> On Tuesday 11 April 2006 13:23, stan wrote: > >> >> >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: > >> >> >> On Tuesday 11 April 2006 11:59, stan wrote: > >> >> >> >I'm setting up a new Ubuntu box as my next generation Amanda > >> >> >> > server. Somehow the /etc/hosts file for this machine was > >> >> >> > created looking like this: > >> >> > >> >> FQDN's or addresses, but see below. > >> >> > > I'm reminded of the lines displayed rather prominantly on the cover of > the manual of what was pretty close to the first *decent* consumer > audio tape recorder marketed in the middle 1950's here in the states, > the Bell RT-7, where it said: > >PLEASE try our way first! > I _think_ at this point in time, I'm doing it precisely the way you are suggesting (see previous post to this thread), but I till have issues with _some- of the DLE's, and the exclude file on the Amanda host _inly_. Very puzzling. Remember this all started when I changed /etc/hosts to fix sendmail. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > On 2006-04-12 12:27, stan wrote: > >Again, I've never done that in the past. I've just made ceratin that the > >amanda user exists, > >and done the build/make install as root. Permissions have alwasy been fine. > > > >Having sad that, I'll rebuild the whole thing today using FQDB's, and > >building as amanda, then > >installing as root. > > It is not important as who you build -- root is no problem (but > security minded sysadmins avoid doing things as root unless needed). > But the "make install" should be done as root. > > Then subsequently, you should not RUN the program as root (except > amrecover, which should be run as root), because when running the first > time, Amanda creates some files. When doing that as root - even only > once - those files are owned by root instead of the amanda user > and you run into trouble next time. Right, we are good on that. > > > > >BTW, speaking of rebuilding amanda, it would be nice if there were a "make > >no-overwrite > >confgis" option. > > "make install" does not install, nor overwrite any config file. > No need to disable that non-existing feature. > I just foudn that out, to my pleasent suprise. In any case, I rebuilt uinsg FQDN's, and I still have these problems, An amcheck reports: Amanda Backup Client Hosts Check ERROR: amanda: [Can't open exclude file '/opt/amanda/lib/gnutar_exclude_list': No such file or directory] ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file or directory] ERROR: amanda: [could not access /data_backups (/data_backups): No such file or directory] Client check: 44 hosts checked in 9.986 seconds, 3 problems found (brought to you by Amanda 2.5.0) but: [EMAIL PROTECTED]:~$ ls -l /opt/amanda/lib/gnutar_exclude_list -rw-r--r-- 1 amanda root 0 Mar 31 21:18 /opt/amanda/lib/gnutar_exclude_list [EMAIL PROTECTED]:~$ ls -ld /dumpdisk drwxr-xr-x 3 amanda operator 27 Apr 11 12:27 /dumpdisk [EMAIL PROTECTED]:~$ ls -ld /data_backups drwxrwxrwx 9 root root 232 Apr 12 02:01 /data_backups It helps in diagnosing this problem to remeber that this part was working _before_ I messed with /etc/hosts on the Amada machine. I'm totaly confused at this point in time, what should I do to further diagnose this problem? Oh, and thnks for all the help! -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Wednesday 12 April 2006 06:27, stan wrote: >On Wed, Apr 12, 2006 at 12:40:32AM -0400, Gene Heskett wrote: >> On Tuesday 11 April 2006 18:04, stan wrote: >> >On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: >> >> On Tuesday 11 April 2006 13:23, stan wrote: >> >> >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: >> >> >> On Tuesday 11 April 2006 11:59, stan wrote: >> >> >> >I'm setting up a new Ubuntu box as my next generation Amanda >> >> >> > server. Somehow the /etc/hosts file for this machine was >> >> >> > created looking like this: >> >> >> >> FQDN's or addresses, but see below. >> >> >> >> >BTW, hostname returns "amanda", not the FQDN. I geuss I could >> >> > change /etc/hostname to the FQDN if needed. >> >> >> >> Yes, 'hostname' should return the FQDN. Here I don't use a dns >> >> server for local stuff, just the /etc/hosts files on all >> >> machines. And each FQDN also has a one word alias that works just >> >> fine for such things as disklist entries. It also works for that >> >> script of mine, but I cleaned that up for public comsumption as >> >> its not always going to work for everyone if they're using a dns >> >> & no hosts file. >> >> >> >> FWIW my tar isn't that one either, I'm using a locally built >> >> 1.15-1 installed in /usr/local/bin, with that line suitably >> >> modifed. >> > >> >OK, I corected my /etc/hosts file as shown above. Now, when I run a >> > dump it seems to go OK (went to hloding disk, but when it finishes >> > I expect to find a tape name problem. >> > >> >However, on the Amanda server itself / was backed up, but to other >> > partions in the disklist failed to estimate. and amcheck claims it >> > can't read the gnutar exclude file. Permissions on all of these >> > seem OK, and were working before I messed with /etchosts, the >> > first time. >> > >> >Sugestions? >> >> You did build amanda as a unpriviledged (uid>500) user, and then >> become root to install her, followed by a run of ldconfig, also as >> root? This sound like a permissions problem, and not doing the >> above is probably 90% of the permissions problems genesis moment. >> This unpriviledged user, and I use amanda for that, also needs to be >> a member of the group 'disk' or possibly 'backup' in order to >> function nominally. > >Again, I've never done that in the past. I've just made ceratin that > the amanda user exists, and done the build/make install as root. > Permissions have alwasy been fine. They should not have been, ever, when doing it that way. >Having sad that, I'll rebuild the whole thing today using FQDB's, and > building as amanda, then installing as root. > >BTW, speaking of rebuilding amanda, it would be nice if there were a > "make no-overwrite confgis" option. It doesn't ever overwrite your existing amanda.conf, nor any other file in your /config/ directory. Now if you are refering to the arguments passed to the ./configure program, thats another story, best carved into a script you execute to do the ./configure and make steps. I use one here, it hasn't changed in over a year now, and I posted it here just in the past week in case someone needed a template to use as an example. Because configuration arguments CAN be forgotten, and WILL be forgotten, the script method is a serious butt saver and I wouldn't consider doing without it. >I'll bet you lunch this does not fix my problem though. But it's worth > a try. I'm reminded of the lines displayed rather prominantly on the cover of the manual of what was pretty close to the first *decent* consumer audio tape recorder marketed in the middle 1950's here in the states, the Bell RT-7, where it said: PLEASE try our way first! :-) -- 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: Amanda and localhost definition?
On 2006-04-12 12:27, stan wrote: Again, I've never done that in the past. I've just made ceratin that the amanda user exists, and done the build/make install as root. Permissions have alwasy been fine. Having sad that, I'll rebuild the whole thing today using FQDB's, and building as amanda, then installing as root. It is not important as who you build -- root is no problem (but security minded sysadmins avoid doing things as root unless needed). But the "make install" should be done as root. Then subsequently, you should not RUN the program as root (except amrecover, which should be run as root), because when running the first time, Amanda creates some files. When doing that as root - even only once - those files are owned by root instead of the amanda user and you run into trouble next time. BTW, speaking of rebuilding amanda, it would be nice if there were a "make no-overwrite confgis" option. "make install" does not install, nor overwrite any config file. No need to disable that non-existing feature. I'll bet you lunch this does not fix my problem though. But it's worth a try. -- 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: Amanda and localhost definition?
On Wed, Apr 12, 2006 at 12:40:32AM -0400, Gene Heskett wrote: > On Tuesday 11 April 2006 18:04, stan wrote: > >On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: > >> On Tuesday 11 April 2006 13:23, stan wrote: > >> >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: > >> >> On Tuesday 11 April 2006 11:59, stan wrote: > >> >> >I'm setting up a new Ubuntu box as my next generation Amanda > >> >> > server. Somehow the /etc/hosts file for this machine was > >> >> > created looking like this: > >> > >> FQDN's or addresses, but see below. > >> > >> >BTW, hostname returns "amanda", not the FQDN. I geuss I could > >> > change /etc/hostname to the FQDN if needed. > >> > >> Yes, 'hostname' should return the FQDN. Here I don't use a dns > >> server for local stuff, just the /etc/hosts files on all machines. > >> And each FQDN also has a one word alias that works just fine for > >> such things as disklist entries. It also works for that script of > >> mine, but I cleaned that up for public comsumption as its not always > >> going to work for everyone if they're using a dns & no hosts file. > >> > >> FWIW my tar isn't that one either, I'm using a locally built 1.15-1 > >> installed in /usr/local/bin, with that line suitably modifed. > > > >OK, I corected my /etc/hosts file as shown above. Now, when I run a > > dump it seems to go OK (went to hloding disk, but when it finishes I > > expect to find a tape name problem. > > > >However, on the Amanda server itself / was backed up, but to other > > partions in the disklist failed to estimate. and amcheck claims it > > can't read the gnutar exclude file. Permissions on all of these seem > > OK, and were working before I messed with /etchosts, the first time. > > > >Sugestions? > > You did build amanda as a unpriviledged (uid>500) user, and then become > root to install her, followed by a run of ldconfig, also as root? This > sound like a permissions problem, and not doing the above is probably > 90% of the permissions problems genesis moment. This unpriviledged > user, and I use amanda for that, also needs to be a member of the group > 'disk' or possibly 'backup' in order to function nominally. > Again, I've never done that in the past. I've just made ceratin that the amanda user exists, and done the build/make install as root. Permissions have alwasy been fine. Having sad that, I'll rebuild the whole thing today using FQDB's, and building as amanda, then installing as root. BTW, speaking of rebuilding amanda, it would be nice if there were a "make no-overwrite confgis" option. I'll bet you lunch this does not fix my problem though. But it's worth a try. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Tuesday 11 April 2006 18:04, stan wrote: >On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: >> On Tuesday 11 April 2006 13:23, stan wrote: >> >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: >> >> On Tuesday 11 April 2006 11:59, stan wrote: >> >> >I'm setting up a new Ubuntu box as my next generation Amanda >> >> > server. Somehow the /etc/hosts file for this machine was >> >> > created looking like this: >> >> FQDN's or addresses, but see below. >> >> >BTW, hostname returns "amanda", not the FQDN. I geuss I could >> > change /etc/hostname to the FQDN if needed. >> >> Yes, 'hostname' should return the FQDN. Here I don't use a dns >> server for local stuff, just the /etc/hosts files on all machines. >> And each FQDN also has a one word alias that works just fine for >> such things as disklist entries. It also works for that script of >> mine, but I cleaned that up for public comsumption as its not always >> going to work for everyone if they're using a dns & no hosts file. >> >> FWIW my tar isn't that one either, I'm using a locally built 1.15-1 >> installed in /usr/local/bin, with that line suitably modifed. > >OK, I corected my /etc/hosts file as shown above. Now, when I run a > dump it seems to go OK (went to hloding disk, but when it finishes I > expect to find a tape name problem. > >However, on the Amanda server itself / was backed up, but to other > partions in the disklist failed to estimate. and amcheck claims it > can't read the gnutar exclude file. Permissions on all of these seem > OK, and were working before I messed with /etchosts, the first time. > >Sugestions? You did build amanda as a unpriviledged (uid>500) user, and then become root to install her, followed by a run of ldconfig, also as root? This sound like a permissions problem, and not doing the above is probably 90% of the permissions problems genesis moment. This unpriviledged user, and I use amanda for that, also needs to be a member of the group 'disk' or possibly 'backup' in order to function nominally. -- 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: Amanda and localhost definition?
On Tue, Apr 11, 2006 at 04:46:38PM -0400, Gene Heskett wrote: > On Tuesday 11 April 2006 13:23, stan wrote: > >On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote: > >> On Tuesday 11 April 2006 11:59, stan wrote: > >> >I'm setting up a new Ubuntu box as my next generation Amanda > >> > server. Somehow the /etc/hosts file for this machine was created > >> > looking like this: > >> > > > FQDN's or addresses, but see below. > > >BTW, hostname returns "amanda", not the FQDN. I geuss I could change > >/etc/hostname to the FQDN if needed. > > Yes, 'hostname' should return the FQDN. Here I don't use a dns server > for local stuff, just the /etc/hosts files on all machines. And each > FQDN also has a one word alias that works just fine for such things as > disklist entries. It also works for that script of mine, but I cleaned > that up for public comsumption as its not always going to work for > everyone if they're using a dns & no hosts file. > > FWIW my tar isn't that one either, I'm using a locally built 1.15-1 > installed in /usr/local/bin, with that line suitably modifed. > OK, I corected my /etc/hosts file as shown above. Now, when I run a dump it seems to go OK (went to hloding disk, but when it finishes I expect to find a tape name problem. However, on the Amanda server itself / was backed up, but to other partions in the disklist failed to estimate. and amcheck claims it can't read the gnutar exclude file. Permissions on all of these seem OK, and were working before I messed with /etchosts, the first time. Sugestions? -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Amanda and localhost definition?
On Tuesday 11 April 2006 13:40, Anne Wilson wrote: >On Tuesday 11 April 2006 18:23, stan wrote: >> OK, so this should work, right? >> >> 127.0.0.1 localhost.localdomain localhost >> 1XX.XX.113.24 amanda.meadwestvaco.com amanda > >Isn't it generally considered bad practice to have a hostname and > username identical? I suppose some would call that a security risk, but he has other, greater problems that once he knows howto fix, will make this an easily done fix. The fact that we're discussing it will also help. >Anne -- 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: Amanda and localhost definition?
On Tuesday 11 April 2006 13:23, stan wrote:
>On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote:
>> On Tuesday 11 April 2006 11:59, stan wrote:
>> >I'm setting up a new Ubuntu box as my next generation Amanda
>> > server. Somehow the /etc/hosts file for this machine was created
>> > looking like this:
>> >
>> >170.85.113.24 localhost.localdomain localhost
>> >
>> >At least _I think_ this was what was there. I did not keep a copy,
>> > as I thought I new how to set up a hosts file. Little did I know
>> > :-(
>>
>> 8:{
>>
>> >I really did not pick up on this for quite some time, Finally i
>> > tracing down why email from this machine would not work I noticed
>> > this. So I changed it to:
>> >
>> >127.0.0.1 localhost
>>
>> address full_name alias
>> wrong, s/b 127.0.0.1 localhost.localdomain localhost
>>
>> >170.85.113.24 amanda amanda.meadwestvaco.com
>>
>> wrong, the alias goes after the full domain name string
>> Also, the 'amanda' needs to be the machines real domain name,
>> matching what you get when you run hostname from the cli. Also,
>> when posting addresses that do not resolve from the outside, but are
>> exposed, always obfuscate the numerical address for security
>> reasons.
>
>OK, so this should work, right?
>
>127.0.0.1 localhost.localdomain localhost
>1XX.XX.113.24 amanda.meadwestvaco.com amanda
>
>> Here is the script I've been using for that for some years now:
>> =cut below & paste to your script===
>> #!/bin/sh
>> # since I'm always forgetting to su amanda...
>> if [ `whoami` != 'amanda' ]; then
>> echo
>> echo " Warning "
>> echo "Amanda needs to be configured and built by the user amanda,"
>> echo "but must be installed by user root."
>> echo
>> exit 1
>> fi
>> make clean
>> rm -f config.status config.cache
>> ./configure --with-user=amanda \
>> --with-group=disk \
>> --with-owner=amanda \
>> --with-gnu-ld \
>> --prefix=/usr/local \
>> --with-tapedev="FILE:/amandatapes" \
>> --with-debugging=/tmp/amanda-dbg/ \
>> --with-tape-server=coyote.coyote.den \
>> --with-amandahosts \
>> --with-configdir=/usr/local/etc/amanda \
>> --with-config=Daily \
>> --with-gnutar=/usr/bin/tar
>>
>> make
>> paste cut to your script=
>
>Hmm, here's my build script.
>
>#!/bin/sh
>./configure --with-config=DailyDump \
>--prefix=/opt/amanda --with-index-server=amanda --with-user=amanda \
>--with-group=operator --with-tape-server=amanda --with-debugging \
>--with-tape-device=/dev/nst0 --sbindir=/opt/amanda/sbin \
>--libexecdir=/opt/amanda/libexec --libdir=/opt/amanda/lib \
>--with-configdir=/opt/amanda/etc \
>--with-gnutar-listdir=/opt/amanda/var/gnutar-lists \
>--mandir=/opt/amanda/man --without-rundump \
>
>Ar you saying that I need to ake teh tape-server and index-server
> arguments FQDN's? I'm wiling to try that, but i'm certain that I've
> used teh short name for my build scripts in the past.
FQDN's or addresses, but see below.
>BTW, hostname returns "amanda", not the FQDN. I geuss I could change
>/etc/hostname to the FQDN if needed.
Yes, 'hostname' should return the FQDN. Here I don't use a dns server
for local stuff, just the /etc/hosts files on all machines. And each
FQDN also has a one word alias that works just fine for such things as
disklist entries. It also works for that script of mine, but I cleaned
that up for public comsumption as its not always going to work for
everyone if they're using a dns & no hosts file.
FWIW my tar isn't that one either, I'm using a locally built 1.15-1
installed in /usr/local/bin, with that line suitably modifed.
--
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: Amanda and localhost definition?
NISplus disallows it, credentials collision, I'm unaware of another other restrictions. On Tue, Apr 11, 2006 at 06:40:19PM +0100, Anne Wilson wrote: > On Tuesday 11 April 2006 18:23, stan wrote: > > > > OK, so this should work, right? > > > > 127.0.0.1 localhost.localdomain localhost > > 1XX.XX.113.24 amanda.meadwestvaco.com amanda > > > Isn't it generally considered bad practice to have a hostname and username > identical? > > Anne --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Amanda and localhost definition?
On Tuesday 11 April 2006 18:23, stan wrote: > > OK, so this should work, right? > > 127.0.0.1 localhost.localdomain localhost > 1XX.XX.113.24 amanda.meadwestvaco.com amanda > Isn't it generally considered bad practice to have a hostname and username identical? Anne pgpQ0dJyUfhoe.pgp Description: PGP signature
Re: Amanda and localhost definition?
On Tue, Apr 11, 2006 at 12:34:17PM -0400, Gene Heskett wrote:
> On Tuesday 11 April 2006 11:59, stan wrote:
> >I'm setting up a new Ubuntu box as my next generation Amanda server.
> >Somehow the /etc/hosts file for this machine was created looking like
> > this:
> >
> >170.85.113.24 localhost.localdomain localhost
> >
> >At least _I think_ this was what was there. I did not keep a copy, as
> > I thought I new how to set up a hosts file. Little did I know :-(
>
> 8:{
>
> >I really did not pick up on this for quite some time, Finally i
> > tracing down why email from this machine would not work I noticed
> > this. So I changed it to:
> >
> >127.0.0.1 localhost
>
> address full_name alias
> wrong, s/b 127.0.0.1 localhost.localdomain localhost
>
> >170.85.113.24 amanda amanda.meadwestvaco.com
>
> wrong, the alias goes after the full domain name string
> Also, the 'amanda' needs to be the machines real domain name, matching
> what you get when you run hostname from the cli. Also, when posting
> addresses that do not resolve from the outside, but are exposed, always
> obfuscate the numerical address for security reasons.
OK, so this should work, right?
127.0.0.1 localhost.localdomain localhost
1XX.XX.113.24 amanda.meadwestvaco.com amanda
>
>
> Here is the script I've been using for that for some years now:
> =cut below & paste to your script===
> #!/bin/sh
> # since I'm always forgetting to su amanda...
> if [ `whoami` != 'amanda' ]; then
> echo
> echo " Warning "
> echo "Amanda needs to be configured and built by the user amanda,"
> echo "but must be installed by user root."
> echo
> exit 1
> fi
> make clean
> rm -f config.status config.cache
> ./configure --with-user=amanda \
> --with-group=disk \
> --with-owner=amanda \
> --with-gnu-ld \
> --prefix=/usr/local \
> --with-tapedev="FILE:/amandatapes" \
> --with-debugging=/tmp/amanda-dbg/ \
> --with-tape-server=coyote.coyote.den \
> --with-amandahosts \
> --with-configdir=/usr/local/etc/amanda \
> --with-config=Daily \
> --with-gnutar=/usr/bin/tar
>
> make
> paste cut to your script=
Hmm, here's my build script.
#!/bin/sh
./configure --with-config=DailyDump \
--prefix=/opt/amanda --with-index-server=amanda --with-user=amanda \
--with-group=operator --with-tape-server=amanda --with-debugging \
--with-tape-device=/dev/nst0 --sbindir=/opt/amanda/sbin \
--libexecdir=/opt/amanda/libexec --libdir=/opt/amanda/lib \
--with-configdir=/opt/amanda/etc \
--with-gnutar-listdir=/opt/amanda/var/gnutar-lists \
--mandir=/opt/amanda/man --without-rundump \
Ar you saying that I need to ake teh tape-server and index-server arguments
FQDN's? I'm wiling to try that, but i'm certain that I've used teh short
name for my build scripts in the past.
BTW, hostname returns "amanda", not the FQDN. I geuss I could change
/etc/hostname to the FQDN if needed.
Re: Amanda and localhost definition?
On Tuesday 11 April 2006 11:59, stan wrote:
>I'm setting up a new Ubuntu box as my next generation Amanda server.
>Somehow the /etc/hosts file for this machine was created looking like
> this:
>
>170.85.113.24 localhost.localdomain localhost
>
>At least _I think_ this was what was there. I did not keep a copy, as
> I thought I new how to set up a hosts file. Little did I know :-(
8:{
>I really did not pick up on this for quite some time, Finally i
> tracing down why email from this machine would not work I noticed
> this. So I changed it to:
>
>127.0.0.1 localhost
address full_name alias
wrong, s/b 127.0.0.1 localhost.localdomain localhost
>170.85.113.24 amanda amanda.meadwestvaco.com
wrong, the alias goes after the full domain name string
Also, the 'amanda' needs to be the machines real domain name, matching
what you get when you run hostname from the cli. Also, when posting
addresses that do not resolve from the outside, but are exposed, always
obfuscate the numerical address for security reasons.
>But now I seem to have confused Amanda, for instance if I run amcheck,
> I get:
>
>Amanda Backup Client Hosts Check
>
>ERROR: amanda: [Can't open exclude file
>'/opt/amanda/lib/gnutar_exclude_list': No such file or directory]
>ERROR: amanda: [could not access /dumpdisk (/dumpdisk): No such file
> or directory]
>ERROR: amanda: [could not access /data_backups (/data_backups): No
> such file or directory]
>
>These are local disk on the Amanda machine (whose name is amanda
> logically enough).
>
>Looking at the backups of the previous machine (which ran an earlier
> version of Amanda), ( it was a Debian machine BTW). I find that the
> hosts file on it looked like this:
>
>127.0.0.1 localhost
>170.85.109.24 debian debian.meadwestvaco.com
>
>Yes, same IP address, and a different name. I changed that in the DNS
> for clarity.
>
>I guess I really don't know what I am doing here :-(
>
>Can anyone show me the error of my ways?
You'll need to reconfigure and rebuild amanda as either the address, or
the FQDN of the server needs to be hard-coded into it as you pass it
the ./configure [argument list]
If you use the FQDN of the server, then it must be resolvable either by
local dns, or /etc/hosts files. The below config would be just as
valid if a set the tape-server set to a 192.168.xxx.xxx address.
Here is the script I've been using for that for some years now:
=cut below & paste to your script===
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo " Warning "
echo "Amanda needs to be configured and built by the user amanda,"
echo "but must be installed by user root."
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local \
--with-tapedev="FILE:/amandatapes" \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote.coyote.den \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--with-config=Daily \
--with-gnutar=/usr/bin/tar
make
paste cut to your script=
And modify to suit. tape-dev and tape-server in particular
All of the above info is hard-coded into amanda as its being built.
--
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.
