The timeout issues have been resolved (tcpd related issue), but I have no reason to believe that the dumper died errors have gone away.
svr-new is the server and client, phoenix-new is a client only. On Wednesday, November 21, 2001, at 10:11 PM, Joshua Baker-LePain wrote: > On Wed, 21 Nov 2001 at 11:40am, Sam Johnston wrote > >> FAILURE AND STRANGE DUMP SUMMARY: >> phoenix-ne /var/qmail lev 0 FAILED [Request to phoenix-new timed >> out.] >> phoenix-ne /var lev 0 FAILED [Request to phoenix-new timed out.] >> phoenix-ne /export/software lev 0 FAILED [Request to phoenix-new >> timed >> out.] >> phoenix-ne /export/public lev 0 FAILED [Request to phoenix-new timed >> out.] >> phoenix-ne /home lev 0 FAILED [Request to phoenix-new timed out.] >> phoenix-ne / lev 0 FAILED [Request to phoenix-new timed out.] >> svr-new /home lev 0 FAILED [dumper2 died] >> svr-new //office-new/backup$ lev 1 FAILED [dumper3 died] >> svr-new /export/a lev 1 FAILED [dump to tape failed] >> <snip> >> NOTES: >> planner: Full dump of svr-new:/home promoted from 3 days ahead. >> driver: dumper0 pid 5949 is messed up, ignoring it. >> driver: dumper0 died while dumping svr-new:/home lev 0. >> driver: dumper1 pid 5950 is messed up, ignoring it. >> driver: dumper1 died while dumping svr-new://office-new/backup$ lev >> 1. >> driver: dumper2 pid 5951 is messed up, ignoring it. >> driver: dumper3 pid 5952 is messed up, ignoring it. >> driver: no idle dumpers for svr-new:/export/a. >> taper: tape NEWC0007 kb 53984 fm 3 [OK] > > So it was working before, but not now? Does amcheck still say > everything > is OK? Requests timing out (phoenix-new) should definitely show up in > amcheck. I'm not sure what could be causing the dumpers to die... > > Which is the amanda server, and which is only a client? > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
