Re: selfcheck reply timed out
Maybe there are some "zombie" amanda processes hanging in the background. Try looking at "ps" to see if any processes need to be killed. Look at the files in /tmp/amanda on the server and the clients to see if there are any clues. Try rebooting and see if the problem still persists. On Wed, 2004-03-24 at 13:09, Pablo Quinta Vidal wrote: > I´ve NIS running without errors and now the message is "selfcheck request > timed out" > I had this problem earlier and when I solve this then came "selfcheck reply > timed out" and now again > the old problem. > I checked the help ind docs/FAQ but it doesn´t work. > Help please and sorry if I´m tedious!! > Thanks -- Jonathan Dill <[EMAIL PROTECTED]>
Re: selfcheck reply timed out
> >Doubtful. Do any files appear in /tmp/amanda? Specifically > >/tmp/amanda/amandad*debug would be helpful. What OS are you using? Have > >you setup (x)inetd appropriately? > > I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright but > in a file in /tmp/amanda > appears this: > > amandad: time 0.011: sending ack: > > amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172 > > > amandad: error [getpwuid(-1) fails] > amandad: time 0.025: error [getpwuid(-1) fails] > amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004 > > > Remembet I have the NIS stopped. Then you need to either fix NIS or define the amanda user locally on the server. I´ve NIS running without errors and now the message is "selfcheck request timed out" I had this problem earlier and when I solve this then came "selfcheck reply timed out" and now again the old problem. I checked the help ind docs/FAQ but it doesn´t work. Help please and sorry if I´m tedious!! Thanks _ Dale rienda suelta a tu tiempo libre. Encuentra mil ideas para exprimir tu ocio con MSN Entretenimiento. http://entretenimiento.msn.es/
Re: selfcheck reply timed out
On Wed, 2004-03-24 at 11:30, Joshua Baker-LePain wrote: > > Remembet I have the NIS stopped. > > Then you need to either fix NIS or define the amanda user locally on the > server. My experience has been that on linux, NIS (via ypbind) is unreliable and tends to crash, so I always put the amanda user in the local passwd file to make sure that backups don't fail even if ypbind craps out. I think part of my problem has been that I'm using SGI IRIX as NIS servers, and Linux as NIS clients, and something between them is not 100% compatible. If you really want to rely on NIS, I would suggest setting up some kind of a "watchdog" to restart ypbind if it fails. In fact, I think I am going to look into that option right now, it would fix some of the problems/complaints that I have had, like occasional problems with people not being able to login. -- Jonathan Dill <[EMAIL PROTECTED]>
Re: selfcheck reply timed out
Doubtful. Do any files appear in /tmp/amanda? Specifically /tmp/amanda/amandad*debug would be helpful. What OS are you using? Have you setup (x)inetd appropriately? I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright but in a file in /tmp/amanda appears this: amandad: time 0.011: sending ack: amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172 amandad: error [getpwuid(-1) fails] amandad: time 0.025: error [getpwuid(-1) fails] amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004 Remembet I have the NIS stopped. _ ¿Todavía no conoces el nuevo MSN Messenger? Descárgatelo gratis aquí. http://messenger.microsoft.com/es
Re: selfcheck reply timed out
On Wed, 24 Mar 2004 at 5:26pm, Pablo Quinta Vidal wrote > >Doubtful. Do any files appear in /tmp/amanda? Specifically > >/tmp/amanda/amandad*debug would be helpful. What OS are you using? Have > >you setup (x)inetd appropriately? > > I´m running AMANDA in Debian with kernel 2.4.20. The inetd is allright but > in a file in /tmp/amanda > appears this: > > amandad: time 0.011: sending ack: > > amanda 2.4 ACK HANDLE 000-403B0508 SEQ 1078488172 > > > amandad: error [getpwuid(-1) fails] > amandad: time 0.025: error [getpwuid(-1) fails] > amandad: pid 2179 finish time Thu Mar 4 12:50:02 2004 > > > Remembet I have the NIS stopped. Then you need to either fix NIS or define the amanda user locally on the server. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: selfcheck reply timed out
On Wed, 24 Mar 2004 at 4:40pm, Pablo Quinta Vidal wrote > I have my amanda configureted as Diaria and when it check the clients hosts > its tell me: > > > WARNING: medulio: selfcheck reply timed out. > > > medulio is the server and the only client. > I have the NIS deactivated because doesn´t works well. Should it be the > error?? Doubtful. Do any files appear in /tmp/amanda? Specifically /tmp/amanda/amandad*debug would be helpful. What OS are you using? Have you setup (x)inetd appropriately? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
selfcheck reply timed out
Hi list!!! I have my amanda configureted as Diaria and when it check the clients hosts its tell me: WARNING: medulio: selfcheck reply timed out. medulio is the server and the only client. I have the NIS deactivated because doesn´t works well. Should it be the error?? Thanks _ Reparaciones, servicios a domicilio, empresas, profesionales... Todo en la guía telefónica de QDQ. http://qdq.msn.es/msn.cfm
Re: selfcheck reply timed out issue
Tom Brown wrote: ... WARNING: : selfcheck reply timed out ... i have managed to fix this - seems the OS partition on the client was at 100% and so this was causing the check to fail. Maybe the error could have been a bit more descriptive! But probably because the OS partition was full, the OS itself had trouble starting up the client-part for amanda selfcheck, and so amanda hadn't even the chance to give some more informative messages. The server never got a reply back. The selfcheck on the client does already check if there is some minimal space available on e.g. the filesytem that hold /etc (when it has to rewrite amandates), and warns you with nice messages. -- 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: selfcheck reply timed out issue
> Hi, > > One of my systems that backs up 4 clients last night failed on 1 of the > clients. The other 3 were ok. I have gone through and checked everything, > restarted xinetd on the client, but still the same error. > > Has anyone seen > > WARNING: xxxx: selfcheck reply timed out > > This is on amanda-2.4.4 on both the client and the server. This is odd as > neither machine has changed in any way nor have they been rebooted. They are > on the same network so no firewall is in the way and i have disabled the > built in firewall on the client, redhat 7.3, as i though that might cause it > but no better. i have managed to fix this - seems the OS partition on the client was at 100% and so this was causing the check to fail. Maybe the error could have been a bit more descriptive! thanks Tom
selfcheck reply timed out issue
Hi, One of my systems that backs up 4 clients last night failed on 1 of the clients. The other 3 were ok. I have gone through and checked everything, restarted xinetd on the client, but still the same error. Has anyone seen WARNING: : selfcheck reply timed out This is on amanda-2.4.4 on both the client and the server. This is odd as neither machine has changed in any way nor have they been rebooted. They are on the same network so no firewall is in the way and i have disabled the built in firewall on the client, redhat 7.3, as i though that might cause it but no better. thanks Tom
