Re: Solaris 8 and L200
Hi, first: please keep this task on the list, it gives other people the posibility to jump in and correct me if i tell you something wrong I guess this is a scsi-tapechanger, correct? then you have a few possibilities to get the robot moving: chg-scsi, mtx, and possibly more, i don't know all the free available tools to make tape robots move, espacialy for solaris as i am using linux on all my servers and i opperate my tapechanger all with chg-scsi. so now we are at the point where one of the solaris-people here on the list should jump in to help you further, but the need a little more info on your problem likthe exact type of your changer, which version of amanda you use, if you compiled it your self etc. Christoph Glenn Zenker schrieb: Thanks, that is a big help! I'll switch to another script and see what happens. Do you know if Amanda can move the robot?? Currently, the only software we have works through a webpage. Thanks, Glenn Christoph Scheeder wrote: Hi, You have configured amanda to use chg-multi as changer script. i don't think this is what you want. chg-multi is used with multiple tapedrives to form a virtual tape-robot. use one of the other chg-scripts, depending on which software you use to move your robot. Christoph Glenn Zenker schrieb: I have amanda installed when I run the following command as the user amanda /usr/local/sbin/amverify DailySet1 0 I get this: Tapes: Errors found: amtape: could not load slot 1: chg-multi: slot is empty amverify DailySet1 Thu Mar 4 13:18:52 EST 2004 Loading 1 slot... ** Error loading slot 1 amtape: could not load slot 1: chg-multi: slot is empty If anyone can lend a hand with how they configured their L200, that would be greatly appreciated.
Re: Resend: ? path of config file for amrecover
Hi, i'll bet you have at least 2 versions of amrecover lying around on your system, and the first one it finds in the path is the old one... if you change the install-path you'll be responsible for deleting the old installation, make install can't do that for you Christoph Allen Liu --- work schrieb: - Original Message - From: Paul Bijnens [EMAIL PROTECTED] To: Allen Liu --- work [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, March 05, 2004 12:06 PM Subject: Re: Resend: ? path of config file for amrecover Allen Liu --- work wrote: Just resend since I haven't heard anything back on it. I installed amanda in my Solaris box with configuration 'snd' like : /myapp/am1/etc/amanda/snd But when I run amrecover , it tried to to search config file from my old installation path /myapp/am/etc/amanda ( see below), it ceitainly failed. I wonder why it tried that way ? and how to make it search my new installation location ? If you change the install path, you'll have to recompile. Yes, I re-did everything : configure/make/make install. But it still behaves like this. I will try to delete everything and reinstall it. I just wonder why. -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Strange DNS lookup problems ... I think ...
Resolving IP address to a hostname (reverse lookup) is the part that looks broken, check the reverse domain in the DNS i.e. host 172.24.16.86 or nslookup 172.24.16.86 The error says *hostname* lookup failed, not address lookup failed. Someone else reported a similar problem a few days ago, and he reported that there was a typo in the reverse domain file of the DNS, and that fixing that fixed the problem. I wonder though, Why does amanda need to do a reverse lookup? You give amanda a hostname in the DLE, and it looks up the IP address, which should be adequate for amanda to do what it needs to do. But then it tries to do a reverse lookup for the hostname based on the IP address, and gives up if that fails. It would be nice if the reverse lookup could be avoided. In principle, yes, the reverse table in your DNS should be correct, but failing backup seems like an expensive DNS diagnostic. planner: ERROR intrap: [addr 172.24.16.86: hostname lookup failed] --jonathan
