Hello,
Ran into some difficulties attempting to upgrade a e450 (2.6 2.7).
This server, unfortunately was my amanda backup server.
I am trying to restore using dd, as my preserved data (thanks sun for the
painless upgrade)is next to useless, and I'm running into some problems.
Following
OK, but I have to ask a few questions anyway to make sure something
wasn't lost in translation.
Sure
Is /tmp/amanda/amandad*debug getting updated on atsun01?
Yes, ls -lu /tmp/amanda/amandad.debug confirms this.
What happens if you run .../amandad by hand **as the Amanda user**
(the one
OK, that's all normal. But I asked what was in selfcheck*debug, not
amandad*debug.
Ugh, sorry about that.
* I ran this manually as user amanda - it does not get updated on amcheck *
selfcheck: debug 1 pid 11368 ruid 101 euid 101 start time Tue Jan 23
14:15:54 2001
./selfcheck: version
What's in the matching amandad*debug file?
It's not being updated by amcheck :(
When run manually as user amanda /usr/local/libexec/./amandad I get the
following in /tmp/amanda/amandad.debug
amandad: debug 1 pid 11289 ruid 101 euid 101 start time Tue Jan 23 13:58:41
2001
./amandad: version
I'd suggest blowing away /tmp/amanda, doing the amcheck, and then seeing
what's in there. There should be an amandad*debug and selfcheck*debug,
both recently updated (as of the time of the amcheck). Take a look at
the first few lines of each (assuming they are both there) and an "ls -l"
to
Okay,
A reboot seemed to fix things - weird.
I enabled the original amadad entry in /etc/inetd.conf and restarted.
Went ahead and ran amcheck atlab as user amanda and it is now creating
amandad.debug selfcheck.debug
in /tmp/amanda.
Ahhh.. now this is much better :)
cat
We need the stack traceback. Please do this again and enter "where"
before "quit".
Sorry bout that.
(gdb) run
Starting program: /usr/local/libexec/amandad
warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0074
Program received signal SIGSEGV, Segmentation fault.
0xff0b6e94 in
frame 4# this should put you at "main"
#4 0x11c54 in main (argc=1, argv=0xffbefc04) at amandad.c:174
174 dbprintf(("%s: %s", argv[0], *vp));
print argv[0]
$1 = 0xffbefcd0 "/usr/local/libexec/amandad"
print vp
$2 = (char **) 0x24974
print *vp
$3 = 0x2 Address 0x2
What happens if you run "amadmin xx version"?
(*insecure*)amanda@atsun01:~$ amadmin atlab version
build: VERSION="Amanda-2.4.1p1"
BUILT_DATE="Tue Jan 23 21:41:04 PST 2001"
BUILT_MACH="SunOS atsun01 5.7 Generic_106541-14 sun4u sparc
SUNW,Ultra-4"
CC="gcc"
paths:
One more test:
break main
run
print version_info[20] # just to make sure we're looking at
# the right stuff
print version_info[21]
gdb) break main
Breakpoint 1 at 0x11a78: file amandad.c, line 116.
(gdb) run
Starting program:
I don't think this would matter, but what do you get when you run
"gcc -v"? Was it built for the OS version you have (2.7, as I recall)?
atsun01:/# gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.8.1/specs
gcc version 2.8.1
I might add that this was a package,
I could be smoking something here, but I seem to recall seeing this
(*insecure*) crap on my Solaris 2.6 box here, and my amchecks failed
until I got rid of the (*insecure*) by fixing my hostname lookups
for my own host.
The (*insecure*) bit is just part of amanda's .bashrc...
if [ $SHLVL
checking disk /home: device /dev/rdsk/c0t0d0s7: Permission denied
what does ls -la on c0t0d0s7 look like?
For example:
ls -la ../../devices/pci@1f,4000/scsi@3/sd@0,0:h,raw
crw-r- 1 root sys 32, 7 Jan 22 14:15
Make sure the user amanda runs as has read permission on the raw device.
Oops... make sure the group of the user that amanda runs as has read
permission.
-Ben
On Solaris 7? IIRC, GCC 2.8.1 needed some patches to support Solaris 7.
Yes. I built the latest ( I believe ) 2.95.2 and tried compling, making and
install again (fresh build dir)
No luck. Still get amandad looping, and ending up with a segmentation fault
So my next alternative is to
What does common-src/version.c look like?
/* version.c - generated by genversion.c - DO NOT EDIT! */
char *version_info[] = {
"build: VERSION=\"Amanda-2.4.1p1\"\n",
" BUILT_DATE=\"Thu Jan 25 10:04:03 PST 2001\"\n",
" BUILT_MACH=\"SunOS atsun01 5.7 Generic_106541-14 sun4u sparc
Well...
I decided to move the sun dlt7000 over to another
e450 sun solaris 2.7 and give that a shot.
Configure, make make install.
Things are working now... very strange?!?
Anyways, I'm back up and running.
Now THIS is what I like seeing :)
(*insecure*)amanda@atsun04:/tmp/amanda$ amcheck
I am runing it on a freebsd 4.2-Release
On my openbsd box I see gmake in my ports tree here.
(bhyatt)@kawasaki:/usr/ports/devel/gmake:[115]
HTH
-Ben
Clem Kumah
[EMAIL PROTECTED]
System Administrator / Teamleader
and in your /etc aliases put this:
backup: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
and you get what you want..
at least, thats the way we do it.
Christoph
don't forget to run 'newaliases'
-Ben
Is there any easy way to force a level 0 backup of every disk in the
disklist?
man amadmin
force hostname [ disks ]
Force the disks on hostname to do a full level 0 backup
during the next Amanda run.
EXAMPLES
Request three specific file systems on machine-a get a full
Can anybody tell me what is going on?
What is this taper: FATAL shmget: Cannot allocate memory message mean?
use ipcs to list resources allocated by user 'amanda' ; ipcrm to remove.
-Ben
Please don't flame me for asking this but the NT admins onsite here
would like something simpler than the UNIX command line. Is there a Web
front available for Amanda or for amrecover in particular.
If your NT admins need a gui, I'd suggest having them look at other
solutions, i.e Veritas
Ever since I rebuilt Amanda and moved it over to another box, I have noticed
that
the email report size wise is huge (9 MB).
Didn't recall the report's to be that big on the old amanda instance I had
running.
Had an amanda alias pointing to my corp email address, but now that the
message size is
Doesn't this mean that there is something wrong with backup ?
I have 8 samba shares which get backed up - due to open files I get a lot
of errors from samba.
I added 2 samba shares to the disklist (previous instance had 6 samba shares
defined) my previous reports were never this big.
create /usr/local/src/amanda/2.4.2p1/Makefile (attached)
create /usr/local/src/amanda/2.4.2p1/config.site (attached)
create /usr/local/src/amanda/2.4.2p1/amanda-2.4.2p1.tar.gz (distribution)
cd /usr/local/src/amanda/2.4.2p1
make ! 0-make-log
Thank you very much Todd.
then you have a
configure: error: *** --with-user=USER is missing
Any corrective suggestions are welcomed.
Read the documentation that comes with source - docs/INSTALL.
Amanda needs a user defined, ie --with-user=amanda.
-Ben
Is ther any second entry to make in amanda.conf or anywhere?
Make sure gtar is in your path before running 'configure' - assuming you're
building from source.
Add gtar to your path, re-run configure, make and make install.
-Ben
amanda issueHi,
I'm installing amanda software on Sun Solaris box. I make userand as
amanda. i logged in as amanda and run
./configure --with-user=amanda --with-group=amanda . works fine after that
i logeed in as root and give a command make it gives me an error:-
../libtool: ar: not found
kindly let me know now what will i do.
I want to make this Sun box make as a Backup Server because this box contain a
Tape Drive.
Waiting for you reply
I would highly suggest you read the documentation in the DOCS directory.
Also the amanda website has a faq-o-matic page that answers some
Error: Autoconf requires GNU m4 1.1 or later
make: *** [autoconf.m4f] Error 1
You need GNU make
ftp://ftp.gnu.org/gnu/make/
-Ben
anurag
I created the user group and home dir for amanda also. Modified the
/etc/services /etc/inetd.conf , and HUP'd the inetd.
What does your inetd.conf look like? (amanda entries)
On the BSD boxes I get:
On the bsd boxes, what does /tmp/amanda/amanda/selfcheck*debug say?
Apr 11 11:18:38
Hello,
Just wanted to double check my configuration here.
What I want to do aside from my production backups is to have
a separate config for archival purposes.
I've checked the list archives and have done the following:
a)Made a separate config for archive
b)edited amanda.conf
having some problems with amcheck (amandapass and amandates)
output from amcheck
ERROR: atsun01: [cannot find password for //atdell01/d$]
ERROR: atsun01: [cannot find password for //atdell01/c$]
ERROR: atsun01: [can not read/write /etc/amandates: No such file or directory]
ERROR: atsun01:
Because these files are looked at by client programs, not by server
programs. So they must exist on clients that need them.
Ugh... that was extremely dumb of me - had that server defined in the disklist
unixhost //samba/share
Thanks,
-Ben
Alexandre Oliva Enjoy Guarana', see
Lately he's been making some interesting comments...
mach kernel is crap, dump is stupid blah blah blah
Seems to me that if he didn't create it, er steal it it's
automatically 'crap' or 'stupid'.
Maybe he's still upset at Andrew S. Tanenbaum for
giving him 2 f's on operating system design
Brian,
What does your amanda /etc/inetd.conf entries look like?
should look like...
amanda dgram udp waitamanda /usr/local/libexec/amandad
amandad
./Ben
I was getting a selfcheck error on one of my sun boxes I just built amanda
on and this is what I found in
36 matches
Mail list logo
