date:20051005


Paddy Sreenivasan wrote:


Use ipcrm -m  to remove them and try amflush again.


It worked! Thanks for your help. :-)

Shang-Lin


It appears taper is not cleaning up properly. tape_writer_side should call
detach_buffers() in case 'Q' to explicitly detach the shared memory (might
be required for Solaris)

Paddy


On 10/5/05, *Shang-Lin Chen* <[EMAIL PROTECTED] 
> wrote:


On Wed, 2005-10-05 at 16:39 -0700, Paddy Sreenivasan wrote:
> Maybe some other processes is using more shared memory or shared
> memory segments.
> Check output of ipcs (ipcs equivalent in Solaris)
>
This is the output I'm getting from ipcs -m:
IPC status from  as of Wed Oct  5 17:25:34 PDT 2005
T ID  KEYMODEOWNERGROUP
Shared Memory:
m  0   0x5674 --rw-r--r-- root root
m  1   0  --rw---   amanda   amanda
m   2702   0  --rw-rw-rw-   webmgrstaff
m   1203   0  --rw---   amanda   amanda
m104   0  --rw---   amanda   amanda
m  5   0  --rw---   amanda   amanda
m106   0  --rw---   amanda   amanda
m207   0  --rw---   amanda   amanda
m  8   0  --rw---   amanda   amanda
m109   0  --rw---   amanda   amanda
m210   0  --rw---   amanda   amanda
m511   0  --rw---   amanda   amanda
m312   0  --rw---   amanda   amanda
m   1213   0  --rw---   amanda   amanda
m   1014   0  --rw---   amanda   amanda
m115   0  --rw---   amanda   amanda
m716   0  --rw---   amanda   amanda
m 17   0  --rw---   amanda   amanda
m118   0  --rw---   amanda   amanda
m319   0  --rw---   amanda   amanda
m620   0  --rw---   amanda   amanda
m221   0  --rw---   amanda   amanda
m622   0  --rw---   amanda   amanda
m523   0  --rw---   amanda   amanda
m224   0  --rw---   amanda   amanda
m125   0  --rw---   amanda   amanda
m126   0  --rw---   amanda   amanda
m227   0  --rw---   amanda   amanda
m128   0  --rw---   amanda   amanda
m   1029   0  --rw---   amanda   amanda
m   2330   0  --rw---   amanda   amanda
m231   0  --rw---   amanda   amanda
m   1532   0  --rw---   amanda   amanda
m 33   0  --rw---   amanda   amanda
m   2034   0  --rw---   amanda   amanda
m235   0  --rw---   amanda   amanda
m436   0  --rw---   amanda   amanda
m   1037   0  --rw---   amanda   amanda
m638   0  --rw---   amanda   amanda
m539   0  --rw---   amanda   amanda
m140   0  --rw---   amanda   amanda
m141   0  --rw---   amanda   amanda
m   1542   0  --rw---   amanda   amanda
m643   0  --rw---   amanda   amanda
m144   0  --rw---   amanda   amanda
m345   0  --rw---   amanda   amanda
m   1346   0  --rw---   amanda   amanda
m   1447   0  --rw---   amanda   amanda
m848   0  --rw---   amanda   amanda
m   1849   0  --rw---   amanda   amanda
m 50   0  --rw---   amanda   amanda
m151   0  --rw---   amanda   amanda
m152   0  --rw---   amanda   amanda
m153   0  --rw---   amanda   amanda
m154   0  --rw---   amanda   amanda
m155   0  --rw---   amanda   amanda
m556   0  --rw---   amanda   amanda
m257   0  --rw---   amanda   amanda
m258   0  --rw---   amanda   amanda
m659   0  --rw---   amanda   amanda
m   1160   0  --rw---   amanda   amanda
m261   0  --rw---   amanda   amanda
m262   0  --rw---   amanda   amanda
m363   0  --rw---   amanda   amanda
m 64   0  --rw---   amanda   amanda
m265   0  --rw---   amanda   amanda
m 66   0  --rw---   amanda   amanda
m267   0  --rw---   amanda   amanda
m468   0  --rw---   amanda   amanda
m769   0  --rw---   amanda

Re: File owner changed upon recovery

2005-10-05 Thread Matt Hyclak

On Thu, Oct 06, 2005 at 11:02:38AM +0900, David Leangen enlightened us:
> Hello!
> 
> I noticed a strange thing...
> 
> I am using gnu-tar. When I recover files, the owner of certain files is 
> changed. Of course, this is not good...
> 
> Any ideas why this happens?
> 

You are going to have to be *way* more specific than that to get an answer.

Are you restoring the file on the same system it was dumped from? Are you
waiting until the restore process is complete before coming to this
conclusion? 

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263

File owner changed upon recovery

2005-10-05 Thread David Leangen



Hello!

I noticed a strange thing...

I am using gnu-tar. When I recover files, the owner of certain files is 
changed. Of course, this is not good...


Any ideas why this happens?


Thanks!

Re: no space left on device during amflush

2005-10-05 Thread Paddy Sreenivasan

Use ipcrm -m  to remove them and try amflush again. 

It appears taper is not cleaning up properly. tape_writer_side should call
detach_buffers() in case 'Q' to explicitly detach the shared memory (might
be required for Solaris)

Paddy
On 10/5/05, Shang-Lin Chen <[EMAIL PROTECTED]> wrote:
On Wed, 2005-10-05 at 16:39 -0700, Paddy Sreenivasan wrote:> Maybe some other processes is using more shared memory or shared> memory segments.> Check output of ipcs (ipcs equivalent in Solaris)>
This is the output I'm getting from ipcs -m:IPC status from  as of Wed Oct  5 17:25:34 PDT 2005T
ID  KEYMODEOWNERGROUPShared Memory:m  0  
0x5674 --rw-r--r--
root rootm  1  
0  --rw---  
amanda   amandam  
2702  
0  --rw-rw-rw-  
webmgrstaffm  
1203  
0  --rw---  
amanda   amandam104  
0  --rw---  
amanda   amandam  5  
0  --rw---  
amanda   amandam106  
0  --rw---  
amanda   amandam207  
0  --rw---  
amanda   amandam  8  
0  --rw---  
amanda   amandam109  
0  --rw---  
amanda   amandam210  
0  --rw---  
amanda   amandam511  
0  --rw---  
amanda   amandam312  
0  --rw---  
amanda   amandam  
1213  
0  --rw---  
amanda   amandam  
1014  
0  --rw---  
amanda   amandam115  
0  --rw---  
amanda   amandam716  
0  --rw---  
amanda   amandam
17  
0  --rw---  
amanda   amandam118  
0  --rw---  
amanda   amandam319  
0  --rw---  
amanda   amandam620  
0  --rw---  
amanda   amandam221  
0  --rw---  
amanda   amandam622  
0  --rw---  
amanda   amandam523  
0  --rw---  
amanda   amandam224  
0  --rw---  
amanda   amandam125  
0  --rw---  
amanda   amandam126  
0  --rw---  
amanda   amandam227  
0  --rw---  
amanda   amandam128  
0  --rw---  
amanda   amandam  
1029  
0  --rw---  
amanda   amandam  
2330  
0  --rw---  
amanda   amandam231  
0  --rw---  
amanda   amandam  
1532  
0  --rw---  
amanda   amandam
33  
0  --rw---  
amanda   amandam  
2034  
0  --rw---  
amanda   amandam235  
0  --rw---  
amanda   amandam436  
0  --rw---  
amanda   amandam  
1037  
0  --rw---  
amanda   amandam638  
0  --rw---  
amanda   amandam539  
0  --rw---  
amanda   amandam140  
0  --rw---  
amanda   amandam141  
0  --rw---  
amanda   amandam  
1542  
0  --rw---  
amanda   amandam643  
0  --rw---  
amanda   amandam144  
0  --rw---  
amanda   amandam345  
0  --rw---  
amanda   amandam  
1346  
0  --rw---  
amanda   amandam  
1447  
0  --rw---  
amanda   amandam848  
0  --rw---  
amanda   amandam  
1849  
0  --rw---  
amanda   amandam
50  
0  --rw---  
amanda   amandam151  
0  --rw---  
amanda   amandam152  
0  --rw---  
amanda   amandam153  
0  --rw---  
amanda   amandam154  
0  --rw---  
amanda   amandam155  
0  --rw---  
amanda   amandam556  
0  --rw---  
amanda   amandam257  
0  --rw---  
amanda   amandam258  
0  --rw---  
amanda   amandam659  
0  --rw---  
amanda   amandam  
1160  
0  --rw---  
amanda   amandam261  
0  --rw---  
amanda   amandam262  
0  --rw---  
amanda   amandam363  
0  --rw---  
amanda   amandam
64  
0  --rw---  
amanda   amandam265  
0  --rw---  
amanda   amandam
66  
0  --rw---  
amanda   amandam267  
0  --rw---  
amanda   amandam468  
0  --rw---  
amanda   amandam769  
0  --rw---  
amanda   amandam170  
0  --rw---  
amanda   amandam171  
0  --rw---  
amanda   amandam172  
0  --rw---  
amanda   amandam973  
0  --rw---  
amanda   amandam  
1074  
0  --rw---  
amanda   amandam  
1275  
0  --rw---  
amanda   amandam  
4176  
0  --rw---  
amanda   amandam577  
0  --rw---  
amanda   amandam878  
0  --rw---  
amanda   amandam

Re: no space left on device during amflush

On Wed, 2005-10-05 at 16:39 -0700, Paddy Sreenivasan wrote:
> Maybe some other processes is using more shared memory or shared
> memory segments.
> Check output of ipcs (ipcs equivalent in Solaris)
> 
This is the output I'm getting from ipcs -m:
IPC status from  as of Wed Oct  5 17:25:34 PDT 2005
T ID  KEYMODEOWNERGROUP
Shared Memory:
m  0   0x5674 --rw-r--r-- root root
m  1   0  --rw---   amanda   amanda
m   2702   0  --rw-rw-rw-   webmgrstaff
m   1203   0  --rw---   amanda   amanda
m104   0  --rw---   amanda   amanda
m  5   0  --rw---   amanda   amanda
m106   0  --rw---   amanda   amanda
m207   0  --rw---   amanda   amanda
m  8   0  --rw---   amanda   amanda
m109   0  --rw---   amanda   amanda
m210   0  --rw---   amanda   amanda
m511   0  --rw---   amanda   amanda
m312   0  --rw---   amanda   amanda
m   1213   0  --rw---   amanda   amanda
m   1014   0  --rw---   amanda   amanda
m115   0  --rw---   amanda   amanda
m716   0  --rw---   amanda   amanda
m 17   0  --rw---   amanda   amanda
m118   0  --rw---   amanda   amanda
m319   0  --rw---   amanda   amanda
m620   0  --rw---   amanda   amanda
m221   0  --rw---   amanda   amanda
m622   0  --rw---   amanda   amanda
m523   0  --rw---   amanda   amanda
m224   0  --rw---   amanda   amanda
m125   0  --rw---   amanda   amanda
m126   0  --rw---   amanda   amanda
m227   0  --rw---   amanda   amanda
m128   0  --rw---   amanda   amanda
m   1029   0  --rw---   amanda   amanda
m   2330   0  --rw---   amanda   amanda
m231   0  --rw---   amanda   amanda
m   1532   0  --rw---   amanda   amanda
m 33   0  --rw---   amanda   amanda
m   2034   0  --rw---   amanda   amanda
m235   0  --rw---   amanda   amanda
m436   0  --rw---   amanda   amanda
m   1037   0  --rw---   amanda   amanda
m638   0  --rw---   amanda   amanda
m539   0  --rw---   amanda   amanda
m140   0  --rw---   amanda   amanda
m141   0  --rw---   amanda   amanda
m   1542   0  --rw---   amanda   amanda
m643   0  --rw---   amanda   amanda
m144   0  --rw---   amanda   amanda
m345   0  --rw---   amanda   amanda
m   1346   0  --rw---   amanda   amanda
m   1447   0  --rw---   amanda   amanda
m848   0  --rw---   amanda   amanda
m   1849   0  --rw---   amanda   amanda
m 50   0  --rw---   amanda   amanda
m151   0  --rw---   amanda   amanda
m152   0  --rw---   amanda   amanda
m153   0  --rw---   amanda   amanda
m154   0  --rw---   amanda   amanda
m155   0  --rw---   amanda   amanda
m556   0  --rw---   amanda   amanda
m257   0  --rw---   amanda   amanda
m258   0  --rw---   amanda   amanda
m659   0  --rw---   amanda   amanda
m   1160   0  --rw---   amanda   amanda
m261   0  --rw---   amanda   amanda
m262   0  --rw---   amanda   amanda
m363   0  --rw---   amanda   amanda
m 64   0  --rw---   amanda   amanda
m265   0  --rw---   amanda   amanda
m 66   0  --rw---   amanda   amanda
m267   0  --rw---   amanda   amanda
m468   0  --rw---   amanda   amanda
m769   0  --rw---   amanda   amanda
m170   0  --rw---   amanda   amanda
m171   0  --rw---   amanda   amanda
m172   0  --rw---   amanda   amanda
m973   0  --rw---   amanda   amanda
m   1074   0  --rw---   amanda   amanda
m   1275   0  --rw---   amanda   amanda
m   4176   0  --rw---   amanda   amanda
m577   0  --rw---   amanda   amanda
m878   0  --rw---   amanda   amanda
m479   0  --rw---   amanda   amanda
m 80   0  --rw---   amanda   amanda
m381   0  --rw---   amanda   amanda
m382   0  --rw---

Re: no space left on device during amflush

2005-10-05 Thread Paddy Sreenivasan

Maybe some other processes is using more shared memory or shared memory segments.
Check output of ipcs (ipcs equivalent in Solaris)

PaddyOn 10/5/05, Shang-Lin Chen <[EMAIL PROTECTED]> wrote:
The Amanda server is running Solaris, so it doesn't have /proc. But Ichecked /etc/system and found this:set shmsys:shminfo_shmmax=268435456set shmsys:shminfo_shmmin=1set shmsys:shminfo_shmmni=100set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=70set semsys:seminfo_semmni=100set semsys:seminfo_semmsl=70set semsys:seminfo_semopm=100set semsys:seminfo_semvmx=32767forceload: sys/shmsysIf these settings worked before, how come amflush is failing now?
Thanks,Shang-LinOn Wed, 2005-10-05 at 14:54 -0700, Paddy Sreenivasan wrote:> Can you check the number of shared memory segments and shared memory> allocated in the system? You may have to adjust the values of
> shmall and shmmni (cat /proc/sys/kernel/shmmni)>> Paddy>> On 10/5/05, Shang-Lin Chen <[EMAIL PROTECTED]> wrote:> I added
> tapebufs 50> to amanda.conf after the labelstr line, and this is the output> I'm> getting now:>>> FAILURE AND STRANGE DUMP SUMMARY:
>   taper: FATAL shmget: (1638600 tapebufs) No space left on> device>   amflush: ERROR Cannot flush without tape.  Try again.>> Shang-Lin>> On Wed, 2005-10-05 at 17:02 -0400, Scott R. Burns wrote:
> > Try> >> > tapebufs 50> >> > In your amanda.conf file> >> > Scott...> >
> > Scott R. Burns> > NETCON Technologies Incorporated> > Suite 135 - 4474 Blakie Road> > London, Ontario, Canada> > N6L 1G7> > Voice: +1.519.652.0401
> > Fax: +1.519.652.9275> > Web: www.netcontech.com> >> > -Original Message-> > From: Shang-Lin Chen [mailto:
[EMAIL PROTECTED]]> > Sent: Wednesday, October 05, 2005 4:21 PM> > To: Paul Bijnens> > Subject: Re: no space left on device during amflush
> >> >> > > Shang-Lin Chen wrote:>
> > >   taper: FATAL shmget: (655440 tapebufs) No
space left> on device> > >> > > The default value for tapebufs is 20 (buffers of 32K bytes> each).> > > You probably got some weird value in 
amanda.conf for that> parameter.> > >> > > The above value results if over 20 GByte of RAM.> > >> > My amanda.conf file doesn't set anything for tapebufs, and
> I've never> > had this problem before. How do I change the tapebufs> setting?> >> > Thanks,> > Shang-Lin> > >
> >>>

Re: no space left on device during amflush

The Amanda server is running Solaris, so it doesn't have /proc. But I
checked /etc/system and found this:
set shmsys:shminfo_shmmax=268435456
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=70
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=70
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
forceload: sys/shmsys

If these settings worked before, how come amflush is failing now?

Thanks,
Shang-Lin

On Wed, 2005-10-05 at 14:54 -0700, Paddy Sreenivasan wrote:
> Can you check the number of shared memory segments and shared memory
> allocated in the system? You may have to adjust the values of
> shmall and shmmni (cat /proc/sys/kernel/shmmni)
> 
> Paddy
> 
> On 10/5/05, Shang-Lin Chen <[EMAIL PROTECTED]> wrote:
> I added
> tapebufs 50
> to amanda.conf after the labelstr line, and this is the output
> I'm
> getting now:
> 
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   taper: FATAL shmget: (1638600 tapebufs) No space left on
> device 
>   amflush: ERROR Cannot flush without tape.  Try again.
> 
> Shang-Lin
> 
> On Wed, 2005-10-05 at 17:02 -0400, Scott R. Burns wrote:
> > Try
> >
> > tapebufs 50
> >
> > In your amanda.conf file 
> >
> > Scott...
> >
> > Scott R. Burns
> > NETCON Technologies Incorporated
> > Suite 135 - 4474 Blakie Road
> > London, Ontario, Canada
> > N6L 1G7
> > Voice: +1.519.652.0401
> > Fax: +1.519.652.9275 
> > Web: www.netcontech.com
> >
> > -Original Message-
> > From: Shang-Lin Chen [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 05, 2005 4:21 PM
> > To: Paul Bijnens
> > Subject: Re: no space left on device during amflush
> >
> >
> > > Shang-Lin Chen wrote:
> > > >   taper: FATAL shmget: (655440 tapebufs) No space left
> on device 
> > >
> > > The default value for tapebufs is 20 (buffers of 32K bytes
> each).
> > > You probably got some weird value in amanda.conf for that
> parameter.
> > >
> > > The above value results if over 20 GByte of RAM. 
> > >
> > My amanda.conf file doesn't set anything for tapebufs, and
> I've never
> > had this problem before. How do I change the tapebufs
> setting?
> >
> > Thanks,
> > Shang-Lin
> > >
> >
> 
>

Re: no space left on device during amflush

2005-10-05 Thread Paddy Sreenivasan

Can you check the number of shared memory segments and shared memory

allocated in the system? You may have to adjust the values of

shmall and shmmni (cat /proc/sys/kernel/shmmni)


PaddyOn 10/5/05, Shang-Lin Chen <[EMAIL PROTECTED]> wrote:
I addedtapebufs 50to amanda.conf after the labelstr line, and this is the output I'mgetting now:FAILURE AND STRANGE DUMP SUMMARY:  taper: FATAL shmget: (1638600 tapebufs) No space left on device
  amflush: ERROR Cannot flush without tape.  Try again.Shang-LinOn Wed, 2005-10-05 at 17:02 -0400, Scott R. Burns wrote:> Try>> tapebufs 50>> In your amanda.conf file
>> Scott...>> Scott R. Burns> NETCON Technologies Incorporated> Suite 135 - 4474 Blakie Road> London, Ontario, Canada> N6L 1G7> Voice: +1.519.652.0401> Fax: +1.519.652.9275
> Web: www.netcontech.com>> -Original Message-> From: Shang-Lin Chen [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 05, 2005 4:21 PM> To: Paul Bijnens> Subject: Re: no space left on device during amflush>>> > Shang-Lin Chen wrote:> > >   taper: FATAL shmget: (655440 tapebufs) No space left on device
> >> > The default value for tapebufs is 20 (buffers of 32K bytes each).> > You probably got some weird value in amanda.conf for that parameter.> >> > The above value results if over 20 GByte of RAM.
> >> My amanda.conf file doesn't set anything for tapebufs, and I've never> had this problem before. How do I change the tapebufs setting?>> Thanks,> Shang-Lin> >
>

RE: no space left on device during amflush

I added
tapebufs 50
to amanda.conf after the labelstr line, and this is the output I'm
getting now:


FAILURE AND STRANGE DUMP SUMMARY:
  taper: FATAL shmget: (1638600 tapebufs) No space left on device
  amflush: ERROR Cannot flush without tape.  Try again.

Shang-Lin

On Wed, 2005-10-05 at 17:02 -0400, Scott R. Burns wrote:
> Try
> 
> tapebufs 50
> 
> In your amanda.conf file
> 
> Scott...
> 
> Scott R. Burns
> NETCON Technologies Incorporated
> Suite 135 - 4474 Blakie Road
> London, Ontario, Canada
> N6L 1G7
> Voice: +1.519.652.0401
> Fax: +1.519.652.9275
> Web: www.netcontech.com 
> 
> -Original Message-
> From: Shang-Lin Chen [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 05, 2005 4:21 PM
> To: Paul Bijnens
> Subject: Re: no space left on device during amflush
> 
> 
> > Shang-Lin Chen wrote:
> > >   taper: FATAL shmget: (655440 tapebufs) No space left on device
> > 
> > The default value for tapebufs is 20 (buffers of 32K bytes each).
> > You probably got some weird value in amanda.conf for that parameter.
> > 
> > The above value results if over 20 GByte of RAM.
> > 
> My amanda.conf file doesn't set anything for tapebufs, and I've never
> had this problem before. How do I change the tapebufs setting?
> 
> Thanks,
> Shang-Lin
> > 
>

[Fwd: Re: no space left on device during amflush]


--- Begin Message ---
> Shang-Lin Chen wrote:
> >   taper: FATAL shmget: (655440 tapebufs) No space left on device
> 
> The default value for tapebufs is 20 (buffers of 32K bytes each).
> You probably got some weird value in amanda.conf for that parameter.
> 
> The above value results if over 20 GByte of RAM.
> 
My amanda.conf file doesn't set anything for tapebufs, and I've never
had this problem before. How do I change the tapebufs setting?

Thanks,
Shang-Lin
> 
--- End Message ---

Re: Configuration for Windows PC client

2005-10-05 Thread Chris Jones

Paddy Sreenivasan wrote:

> Chris,
>
> Have you specified samba user and password in
> /etc/amandapass configuration file.
>
> amandapass format:
>
>  % 
>
> See http://www.amanda.org/docs/samba.html
>
> Thanks,
> Paddy
>
> On 10/1/05, *Chris Jones* <[EMAIL PROTECTED]
> > wrote:
>
> I have a Fedora Core 4 PC running Amanda server (and backing up the
> server satisfactorily) and a couple of Windows PC's (one is Win2k and
> the other a WinXP).
>
> I have setup amanda to backup the win2k pc using samba following the
> how-to, but I am getting an error when I run amcheck for this backup.
>
> The error I get is (obfuscated private data):
> Amanda Backup Client Hosts Check
> 
> ERROR: local-machine: [samba access error: //server/share: Error
> connecting to 192.168.0.2  (Permission
> denied): Connection to server
> failed: returned 1]
> Client check: 1 host checked in 0.323 seconds, 1 problem found
>
> Where is my configuration likely to be in error and how should I
> correct
> this, please?
>
> --
> It's not easy, being green.
> -- Kermit the Frog
>
>
Paddy,

Yes, I have specified the amanda user exactly as specified for each share.


-- 
mailto:[EMAIL PROTECTED]
Depart not from the path which fate has assigned you.
Q:  How do you stop an elephant from charging?
A:  Take away his credit cards.

Re: no space left on device during amflush


Shang-Lin Chen wrote:

  taper: FATAL shmget: (655440 tapebufs) No space left on device


The default value for tapebufs is 20 (buffers of 32K bytes each).
You probably got some weird value in amanda.conf for that parameter.

The above value results if over 20 GByte of RAM.


--
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: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?


shoaib r wrote:

This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT 
server (bkpclient):
 
amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct  5 
13:08:50 2005

amandad: version 2.4.5

...

amandad: time 30.005: dgram_recv: timeout after 30 seconds



Was this the debug file resulting from the "start manually and wait
30 seconds" test?  Or was it the result of amandad invoked by inetd?


--
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: no space left on device during amflush

On Wed, 2005-10-05 at 19:35 +0200, Alexander Jolk wrote:
> Shang-Lin Chen wrote:
> > FAILURE AND STRANGE DUMP SUMMARY:
> >   taper: FATAL shmget: (655440 tapebufs) No space left on device
> >   amflush: ERROR Cannot flush without tape.  Try again.
> 
> That sounds as if taper had not been able to allocate its buffers.  What 
> operating system are you on?  Did you change anything recently in your 
> amanda.conf?  If you are on linux, do you have a pseudo filesystem 
> mounted on /dev/shm?  In that case, what does `df -lh' give you?
> 

Amanda is running on a machine with SunOS, I think Solaris 8. Recently
the only change I've made to amanda.conf was to change the holding disk
to an automounted partition, but I changed it back to the original when
the automount didn't work.

Contents of my amanda.conf file:
#
# amanda.conf - Amanda configuration file.
#

includefile "/opt/amanda/config/amanda.conf-common"

org  "DailyScec1"   # your organization name for reports
mailto   "amanda"   # the mailing list for operators at your site
dumpuser "amanda"   # the user to run dumps under

inparallel   12 # maximum dumpers that will run in parallel
netusage   3000 # maximum net bandwidth for Amanda, in KB per sec

dumpcycle  10 days  # the number of days in the normal dump cycle
tapecycle 14 tapes  # the number of tapes in rotation
runspercycle 0  # the number of amdump runs in dumpcycle days

bumpsize 10 MB  # minimum savings (threshold) to bump level 1 -> 2
bumpdays 2  # minimum days at each level
bumpmult 2  # threshold = bumpsize * (level-1)**bumpmult

etimeout 300# seconds per filesystem for estimates
#etimeout -600  # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-
out.
# The default is 5 minutes per filesystem.

# Specify tape device and/or tape changer.  If you don't have a tape
# changer, and you don't want to use more than one tape per run of
# amdump, just comment out the definition of tpchanger.

# Some tape changers require tapedev to be defined; others will use
# their own tape device selection mechanism.  Some use a separate tape
# changer device (changerdev), others will simply ignore this
# parameter.  Some rely on a configuration file (changerfile) to
# obtain more information about tape devices, number of slots, etc;
# others just need to store some data in files, whose names will start
# with changerfile.  For more information about individual tape
# changers, read docs/TAPE.CHANGERS.

# At most one changerfile entry must be defined; select the most
# appropriate one for your configuration.  If you select man-changer,
# keep the first one; if you decide not to use a tape changer, you may
# comment them all out.

runtapes 2  # number of tapes to be used in a single run of amdump
tpchanger "chg-multi"   # the tape-changer glue script
#tapedev "/dev/rmt/0bn" # the no-rewind tape device to be used
changerfile "/opt/amanda/config/DailyScec1/chg-multi.conf"
#changerdev "/dev/null"

tapetype SDX-300-Compress   # what kind of tape it is (see tapetypes
below)
labelstr "^DailyScec1.[0-9][0-9]*$" # label constraint regex: all tapes
must match

# Specify holding disks.  These are used as a temporary staging area for
# dumps before they are written to tape and are recommended for most
sites.
# The advantages include: tape drive is more likely to operate in
streaming
# mode (which reduces tape and drive wear, reduces total dump time);
multiple
# dumps can be done in parallel (which can dramatically reduce total
dump time.
# The main disadvantage is that dumps on the holding disk need to be
flushed
# (with amflush) to tape after an operating system crash or a tape
failure.
# If no holding disks are specified then all dumps will be written
directly
# to tape.  If a dump is too big to fit on the holding disk than it will
be
# written directly to tape.  If more than one holding disk is specified
then
# they will all be used round-robin.

holdingdisk hd1 {
comment "/export/home1 holding disk"
comment "/home/amanda new holding disk"
# directory "/export/home1/amanda"  # where the holding disk is
directory "/backup2/amanda"  # old one is too small
#directory "/home/amanda" # auto-mounted version of /backup2/amanda 
use -500 Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
chunksize 0 # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
#   -1 dont split
#0 use INT_MAX
#other use this value (200 Mb)
}

# If amanda cannot find a tape on which to store backups, it will run
# as many backups a

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

I've checked there are definately no firewalls between. Also both servers are connected to the same switch.Alexander Jolk <[EMAIL PROTECTED]> wrote:
shoaib r wrote:> This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT > server (bkpclient):[...]> amandad: time 30.005: dgram_recv: timeout after 30 seconds> amandad: error receiving message: timeout> amandad: time 30.006: error receiving message: timeout> amandad: time 30.006: pid 7021 finish time Wed Oct 5 13:09:20 2005Please keep this thread on the list. Really.You get a timeout after 30s. That means that the first packet arrives but subsequent ones don't seem to get through. Sounds like a firewall problem to me; please double-check that none of the two machines has a local firewall configured and that there's no other firewall between them.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

Re: no space left on device during amflush

2005-10-05 Thread Alexander Jolk


Shang-Lin Chen wrote:

FAILURE AND STRANGE DUMP SUMMARY:
  taper: FATAL shmget: (655440 tapebufs) No space left on device
  amflush: ERROR Cannot flush without tape.  Try again.


That sounds as if taper had not been able to allocate its buffers.  What 
operating system are you on?  Did you change anything recently in your 
amanda.conf?  If you are on linux, do you have a pseudo filesystem 
mounted on /dev/shm?  In that case, what does `df -lh' give you?


Alex


--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Note: forwarded message attached.
		How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! 
Photos--- Begin Message ---
This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient):
 
amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct  5 13:08:50 2005amandad: version 2.4.5amandad: build: VERSION="Amanda-2.4.5"amandad:    BUILT_DATE="Wed Aug 17 17:42:57 BST 2005"amandad:    BUILT_MACH="SunOS dptsdsda02 5.9 Generic_117171-02 sun4u sparc SUNW,Sun-Fire-480R"amandad:    CC="gcc"amandad:    CONFIGURE_COMMAND="'./configure' '--prefix=/usr/local/amanda' '--with-user=amanda' '--with-group=amanda'"amandad: paths: bindir="/usr/local/amanda/bin"amandad:    sbindir="/usr/local/amanda/sbin"amandad:    libexecdir="/usr/local/amanda/libexec"amandad:    mandir="/usr/local/amanda/man"
 AMANDA_TMPDIR="/tmp/amanda"amandad:    AMANDA_DBGDIR="/tmp/amanda"amandad:    CONFIG_DIR="/usr/local/amanda/etc/amanda"amandad:    DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"amandad:    DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"amandad:    VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEFamandad:    VXDUMP=UNDEF VXRESTORE=UNDEFamandad:    SAMBA_CLIENT="/usr/local/samba/bin/smbclient"amandad:    GNUTAR="/usr/local/bin/tar" COMPRESS_PATH="/usr/bin/gzip"amandad:    UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp"amandad:   
 MAILER="/usr/bin/mailx"amandad:    listed_incr_dir="/usr/local/amanda/var/amanda/gnutar-lists"amandad: defs:  DEFAULT_SERVER="dptsdsda02" DEFAULT_CONFIG="DailySet1"amandad:    DEFAULT_TAPE_SERVER="dptsdsda02"amandad:    DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHMamandad:    LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODEamandad:    AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTSamandad:    CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIPamandad:    COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"amandad:    COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"amandad: time 30.005: dgram_recv: timeout after 30 secondsamand!
 ad: error
 receiving message: timeoutamandad: time 30.006: error receiving message: timeoutamandad: time 30.006: pid 7021 finish time Wed Oct  5 13:09:20 2005Alexander Jolk <[EMAIL PROTECTED]> wrote:
shoaib r wrote:> sorry Alexander> > My mistake. As I'm working on a gov't project, I had to change the > hostnames for aliases for the amanda mailing list. I basically vut and > paste the wrong alias.> > Here is the actual error mesage:> > $ amcheck -c daily> Amanda Backup Client Hosts Check> > WARNING: bkupclient.b.c.uk: selfcheck request timed out. Host down?> Client check: 2 hosts checked in 30.072 seconds, 1 problem found> (brought to you by Amanda 2.4.5)OK, so let's get back to the mailing list. Please do look into /tmp/amanda/ on the failing client, and send any information therein to the list.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.--- End Message ---

no space left on device during amflush

Hi,

Last night I forgot to change tapes, so all the dumps were made to the
holding disk. Normally I would change the tape in the morning and run
amflush, and everything would work fine. But this morning, when I tried
to run amflush, it failed immediately and sent me this error message:
FAILURE AND STRANGE DUMP SUMMARY:
  taper: FATAL shmget: (655440 tapebufs) No space left on device
  amflush: ERROR Cannot flush without tape.  Try again.

The correct tape is sitting in the drive, and amcheck gives the correct
output:
Amanda Tape Server Host Check
-
/backup2/amanda: 723260628 KB disk space available, using 722748628 KB.
amcheck-server: slot 1: date 20050910 label DailyScec1.016 (exact label
match)
NOTE: skipping tape-writable test.
Tape DailyScec1.016 label ok.
Server check took 33.191 seconds.

Amanda Backup Client Hosts Check

Client check: 4 hosts checked in 0.979 seconds, 0 problems found.

(brought to you by Amanda 2.4.2)


Thanks for your help!

S. Chen

Re: compiling on aix 5.3

2005-10-05 Thread Jerome Pioux

I did - I am running amanda client on AIX 5.3 (server is on Linux) but I 
built both on AIX anyhow.

I used vac.C V6.0.0.10. Below are the options I set.
I didn't see any problem

[mgd] (amanda) amanda> amadmin daily version
build: VERSION="Amanda-2.4.5"
  BUILT_DATE="Thu Sep 8 22:35:50 MST 2005"
  BUILT_MACH="AIX mgd 3 5 0031C97A4C00" CC="cc"
  CONFIGURE_COMMAND="'./configure' '--prefix=/usr/local/amanda' 
'--bindir=/usr/local/amanda/bin' '--sbindir=/usr/local/amanda/sbin' 
'--libexecdir=/usr/local/amanda/libexec' '--libdir=/usr/local/amanda/lib' 
'--mandir=/usr/local/amanda/man' '--datadir=/usr/local/amanda/share' 
'--sysconfdir=/usr/local/amanda/etc' '--localstatedir=/usr/local/amanda/var' 
'--with-configdir=/usr/local/amanda/etc' 
'--with-gnutar-listdir=/usr/local/amanda/var/gnutar-lists' 
'--with-user=amanda' '--with-group=sys' '--without-amandahosts' 
'--with-index-server=reddog' '--with-tape-server=reddog' 
'--with-tape-device=file:/saves/daily' '--disable-shared'"

paths: bindir="/usr/local/amanda/bin"
  sbindir="/usr/local/amanda/sbin"
  libexecdir="/usr/local/amanda/libexec"
  mandir="/usr/local/amanda/man" AMANDA_TMPDIR="/tmp/amanda"
  AMANDA_DBGDIR="/tmp/amanda"
  CONFIG_DIR="/usr/local/amanda/etc" DEV_PREFIX="/dev/"
  RDEV_PREFIX="/dev/r" DUMP="/usr/sbin/backup"
  RESTORE="/usr/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF
  XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
  SAMBA_CLIENT=UNDEF GNUTAR="/usr/bin/tar"
  COMPRESS_PATH="/usr/bin/gzip"
  UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lpr"
  MAILER="/usr/bin/Mail"
  listed_incr_dir="/usr/local/amanda/var/gnutar-lists"
defs:  DEFAULT_SERVER="reddog" DEFAULT_CONFIG="DailySet1"
  DEFAULT_TAPE_SERVER="reddog"
  DEFAULT_TAPE_DEVICE="file:/saves/daily" AIX_BACKUP
  AIX_TAPEIO HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID
  DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY
  CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
  COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
  COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"


- Jerome


- Original Message - 
From: "Daniel Kropveld" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, October 05, 2005 7:20 AM
Subject: compiling on aix 5.3


Is there anybody who has succesfully built Amanda on AIX 5.3?


I ended up with (among others) these errors:

configure: WARNING: *** Neither shmget() nor mmap() found!
configure: WARNING: *** This system will not support the Amanda server.


Any help is welcome,
TIA
--
Daniël Kropveld
Medial Automatisering
tel: 023 890 8688
gsm: 0644 - 112344
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-05 Thread Alexander Jolk

shoaib r wrote:

>  > + running on tapesvr +
>  > $ amcheck -c daily
>  > Amanda Backup Client Hosts Check
>  > 
>  > WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?
>  > Client check: 2 hosts checked in 30.072 seconds, 1 problem found
>  > (brought to you by Amanda 2.4.5)
>  > 

Just in case it makes any difference to what you know already, the 
backups for tapesrv are working just fine.

Then why do you get a timeout message?  Unless you mixed up both 
machines when you edited the hostnames in your example.

Please confirm the exact error message that you are getting; if you 
think you need to edit the hostnames, triple-check what you are doing; 
and please give us the debug files in /tmp/amanda/ from the machine that 
is failing.

Alex

--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Just in case it makes any difference to what you know already, the backups for tapesrv are working just fine.
 
I've checked inetd.conf, services, .amandahosts etc and their permissions and ownerships against a completey separate configuration that works. All seems to be fine:
 
--- On tapesrv ---
/etc/services:
amanda  10080/udp   # Amanda backupamandaidx   10082/tcp   # Amanda backup index
/etc/inetd.conf:
amandaidx  stream  tcp nowait  amanda  /usr/local/amanda/libexec/amindexd  \amindexdamidxtape  stream  tcp nowait  amanda  /usr/local/amanda/libexec/amidxtaped    \amidxtapedamanda  dgram   udp wait    amanda  /usr/local/amanda/libexec/amandad   \amandad
Does the interface column in disklist make any difference?
 
Have I missed anything out?
 
Appreciate you help so far.
 
ShabsAlexander Jolk <[EMAIL PROTECTED]> wrote:
shoaib r wrote:> Thanks for the responses so far folks> > Ok. I have 2 hosts tapesrv and bkpclient The error message is:> > > + running on tapesvr +> $ amcheck -c daily> Amanda Backup Client Hosts Check> > WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?> Client check: 2 hosts checked in 30.072 seconds, 1 problem found> (brought to you by Amanda 2.4.5)> Actually, it is tapesrv.bc.uk that's timing out and not bkpclient. Forget about bkpclient, it seems to work just fine; look into /tmp/amanda/ on tapesrv, that's where your problem is. And yes, even local backup (from a disk on tapesrv to a tape on tapesrv) go over a net connection, so check inetd, xinetd, services etc. *on
 tapesrv*.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

compiling on aix 5.3

2005-10-05 Thread Daniel Kropveld

Is there anybody who has succesfully built Amanda on AIX 5.3?


I ended up with (among others) these errors:

configure: WARNING: *** Neither shmget() nor mmap() found!
configure: WARNING: *** This system will not support the Amanda server.


Any help is welcome,
TIA
-- 
Daniël Kropveld
Medial Automatisering
tel: 023 890 8688
gsm: 0644 - 112344
[EMAIL PROTECTED]
[EMAIL PROTECTED]

RE: Tapelist issue only using 3 tape out of a tapecycle of 10.

2005-10-05 Thread Scott R. Burns

Could your tapecycle be smaller now than when you labelled the tapes? I am
not sure exactly the effect this would have but if it were reduced it may
ignore the other tapes 

Scott...

Scott R. Burns
NETCON Technologies Incorporated
Suite 135 - 4474 Blakie Road
London, Ontario, Canada
N6L 1G7
Voice: +1.519.652.0401
Fax: +1.519.652.9275
Web: www.netcontech.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Chuck Amadi Systems
Administrator
Sent: Wednesday, October 05, 2005 5:07 AM
To: Amanda List
Cc: Chuck
Subject: Tapelist issue only using 3 tape out of a tapecycle of 10.


Hi I have noticed that the backup schedule as changed somehow and is
only using DailySet108 to DailySet110 (3 tapes) is there away to check
and force it to use the next tape after DailySet110 which should be
DailySet101. I did relabel a faulty tape recently.

finaceserver:/etc/amanda/DailySet1 # less tapelist
20051005 DailySet109 reuse
20050930 DailySet108 reuse
20050929 DailySet107 reuse
20050922 DailySet106 reuse
20050916 DailySet105 reuse
20050915 DailySet104 reuse
20050909 DailySet103 reuse
20050908 DailySet102 reuse
20050907 DailySet101 reuse
20050906 DailySet110 reuse


I did Replace a tape DailySet107 which Amanda reports a tape to be
faulty, the label could not be read on the tape, or the data could not
be saved on the tape. It is time to replace the tape.

In order to keep the set of tapes consistant, the new tape should have
the same label as the old tape. So I used the label DailySet107.

 1. Connect on Amanda server, first as root, then change to the user
amanda, with the command su.
 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line
containing the label,(DailySet107) Usually the line is the last
one of the file.
 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the
same way. Usually the line is the one before the last.
 4. prepare a new tape and write the label on it with the command:
amlabel normal DailySet107.
 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that
the line with the label is back, but it is now at the top of the
file, and the number at the begining is 0. Just move that line
to the bottom of the file. This worked So I assumed.

Cheers

--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-05 Thread Alexander Jolk


shoaib r wrote:

Thanks for the responses so far folks
 
Ok. I have 2 hosts tapesrv and bkpclient The error message is:
 
 
+ running on tapesvr +

$ amcheck -c daily
Amanda Backup Client Hosts Check

WARNING: tapesvr.b.c.uk: selfcheck request timed out.  Host down?
Client check: 2 hosts checked in 30.072 seconds, 1 problem found
(brought to you by Amanda 2.4.5)



Actually, it is tapesrv.bc.uk that's timing out and not bkpclient. 
Forget about bkpclient, it seems to work just fine; look into 
/tmp/amanda/ on tapesrv, that's where your problem is.  And yes, even 
local backup (from a disk on tapesrv to a tape on tapesrv) go over a net 
connection, so check inetd, xinetd, services etc. *on tapesrv*.


Alex




--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 /  fax +33-1 42 68 18 29

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

Thanks for the responses so far folks
Ok. I have 2 hosts tapesrv and bkpclient The error message is:
+ running on tapesvr +
$ amcheck -c daily
Amanda Backup Client Hosts CheckWARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?Client check: 2 hosts checked in 30.072 seconds, 1 problem found
(brought to you by Amanda 2.4.5)
There is no firewall between tapesvr and bkpclient.
When I start amandad from the bkpclient as user amanda it does indeed sit there for 30secs and then terminates.
I get nothing useful or conspicuous lets say from /tmp/amanda/*.debug
My .amandahosts file goes like this on "tapesvr" :
tapesvr amandatapesvr rootbkpclient.b.c.uk amandabkpclient.b.c.uk root
I'm not sure about the commands in solaris of how to check if the connections are comming in.
Thx
Shabs
Paul Bijnens <[EMAIL PROTECTED]> wrote:
shoaib r wrote:> > I've been trying to get Amanda to be able to query the one backup client > host that I have with no luck. I've been thru all the tech pages with no > progress yet.> > Am I missing something?We miss the exact error messages. :-)> > My .amandahosts file has the FQDN and I've only got one line specified > for the client as a test in the disklist file.> > I've checked inetd.conf and /etc/services according to advice and they > seem fine:Is the amandad client started and gives an error or isn't it startedat all?What happens when you start the amandad client from a command line?It should sit there for 30 seconds and than terminate. Or do you getany error message there.Verify that the amandad program is indeed started by inetd.Any
output in /tmp/amanda/*.debug on the client?-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://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
How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo!
Photos

Re: WARNING: hostxxx: selfcheck request timed out. Host down?


shoaib r wrote:
 
I've been trying to get Amanda to be able to query the one backup client 
host that I have with no luck. I've been thru all the tech pages with no 
progress yet.
 
Am I missing something?


We miss the exact error messages.  :-)

 
My .amandahosts file has the FQDN and I've only got one line specified 
for the client as a test in the disklist file.
 
I've checked inetd.conf and /etc/services according to advice and they 
seem fine:


Is the amandad client started and gives an error or isn't it started
at all?

What happens when you start the amandad client from a command line?
It should sit there for 30 seconds and than terminate.  Or do you get
any error message there.

Verify that the amandad program is indeed started by inetd.

Any output in /tmp/amanda/*.debug on the client?



--
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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-05 Thread Matt Hyclak

On Wed, Oct 05, 2005 at 07:53:26AM -0400, Scott R. Burns enlightened us:
> Is the error report reporting the FQDN or a shorter name. Try putting the
> name it is reporting in the .amandahosts.
> 

If it was a problem with .amandahosts, it would most likely be returning a
"Permission Denied from Host" error, not a timeout.

Are there any firewalls in between or on either the client or server?

Can you watch a tcpdump of the traffic to see what is being exchanged?

-- 
Matt Hyclak
Department of Mathematics 
Department of Social Work
Ohio University
(740) 593-1263

RE: WARNING: hostxxx: selfcheck request timed out. Host down?

2005-10-05 Thread Scott R. Burns




Is the 
error report reporting the FQDN or a shorter name. Try putting the name it is 
reporting in the .amandahosts.
 
Scott...
 
Scott R. BurnsNETCON Technologies IncorporatedSuite 135 
- 4474 Blakie RoadLondon, Ontario, CanadaN6L 1G7Voice: 
+1.519.652.0401Fax: +1.519.652.9275Web: www.netcontech.com 

  -Original Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On 
  Behalf Of shoaib rSent: Wednesday, October 05, 2005 7:37 
  AMTo: amanda-users@amanda.orgSubject: WARNING: hostxxx: 
  selfcheck request timed out. Host down?
  Hi folks
   
  I've been trying to get Amanda to be able to query the one backup client 
  host that I have with no luck. I've been thru all the tech pages with no 
  progress yet.
   
  Am I missing something?
   
  My .amandahosts file has the FQDN and I've only got one line specified 
  for the client as a test in the disklist file.
   
  I've checked inetd.conf and /etc/services according to advice and they 
  seem fine:
   
  Any help would be appreciated.
   
  Thanks
   
  Shabs
  
  
  Yahoo! 
  Messenger NEW - crystal clear PC to PC calling 
  worldwide with voicemail

WARNING: hostxxx: selfcheck request timed out. Host down?

Hi folks
 
I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet.
 
Am I missing something?
 
My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file.
 
I've checked inetd.conf and /etc/services according to advice and they seem fine:
 
Any help would be appreciated.
 
Thanks
 
Shabs
		Yahoo! Messenger 
 NEW - crystal clear PC to PC 
calling worldwide with voicemail

Tapelist issue only using 3 tape out of a tapecycle of 10.

2005-10-05 Thread Chuck Amadi Systems Administrator

Hi I have noticed that the backup schedule as changed somehow and is
only using DailySet108 to DailySet110 (3 tapes) is there away to check
and force it to use the next tape after DailySet110 which should be
DailySet101. I did relabel a faulty tape recently.

finaceserver:/etc/amanda/DailySet1 # less tapelist
20051005 DailySet109 reuse
20050930 DailySet108 reuse
20050929 DailySet107 reuse
20050922 DailySet106 reuse
20050916 DailySet105 reuse
20050915 DailySet104 reuse
20050909 DailySet103 reuse
20050908 DailySet102 reuse
20050907 DailySet101 reuse
20050906 DailySet110 reuse


I did Replace a tape DailySet107 which Amanda reports a tape to be
faulty, the label could not be read on the tape, or the data could not
be saved on the tape. It is time to replace the tape.

In order to keep the set of tapes consistant, the new tape should have
the same label as the old tape. So I used the label DailySet107.

 1. Connect on Amanda server, first as root, then change to the user
amanda, with the command su.
 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line
containing the label,(DailySet107) Usually the line is the last
one of the file.  
 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the
same way. Usually the line is the one before the last.
 4. prepare a new tape and write the label on it with the command:
amlabel normal DailySet107.
 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that
the line with the label is back, but it is now at the top of the
file, and the number at the begining is 0. Just move that line
to the bottom of the file. This worked So I assumed.

Cheers

-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: What program do Amanda use to do the backup ?

2005-10-05 Thread Jordi Burguet Castell

On Wednesday 05 October 2005 09:24, Paul Bijnens wrote:
> [EMAIL PROTECTED] wrote:
> > Hi List,
> > How can you tell what program Amanda used to do the backup ?
>
> In the dumptype you specify program "gnutar" or "dump".
> That information is also written in the fileheader (first 32k bytes)
> of each backup image on tape (or on holdingdisk).
> When using dump, amanda executes the appropriate dump program
> on the client, suitable for that filesystem
> Use "amadmin version" on that client to find out what dump program it uses.

Also, if you rewind the tape or go to the position of the beginning of the 
backup, you can
  file - < /dev/nst0
repeatedly to see what is there. That and
  mt -f /dev/nst0 fsf 1
when needed to go to the next file in the tape. Of course use your tape device 
instead of /dev/nst0.

jordi

Re: What program do Amanda use to do the backup ?