From owner-freebsd-questions Mon Oct 18 8:44:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc1017255-a.srst1.fl.home.com (cc1017255-a.srst1.fl.home.com [24.3.122.197]) by hub.freebsd.org (Postfix) with ESMTP id 2786114C25 for ; Mon, 18 Oct 1999 08:44:55 -0700 (PDT) (envelope-from hg@n2wx.ampr.org) Received: from penny.n2wx.ampr.org (penny [172.16.0.5]) by cc1017255-a.srst1.fl.home.com (Postfix) with ESMTP id AD09F1E5A; Mon, 18 Oct 1999 11:44:45 -0400 (EDT) Received: by penny.n2wx.ampr.org (Postfix, from userid 1000) id 9350ACD; Mon, 18 Oct 1999 11:44:37 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14347.16485.447355.530978@penny.n2wx.ampr.org> Date: Mon, 18 Oct 1999 11:44:37 -0400 (EDT) From: Howard Goldstein To: freebsd-questions@freebsd.org, dorin@gr-303.com Subject: Re: amanda problems X-Mailer: VM 6.62 under Emacs 19.34.1 Organization: disorganization Reply-To: hgoldste@bbs.mpcs.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I am trying to get amanda running properly as a client under freebsd : 3.1-release. I am having tons and tons of problems for example, what : causes this: From what I've gathered from the mailing lists it's vm bitrot. It may be fixed in 3.3R (it wasn't fixed in a circa mid-august 3.2S). Kill and restart inetd and amandaidx should be be okay for (some indeterminate length of time). When you can sucessfully telnet to puma's port 10082 you'll be back in business. : : Oct 17 14:26:12 puma /kernel: pid 10777 (amandad), uid 2: exited on signal 11 : Oct 17 14:26:12 puma inetd[136]: /usr/local/libexec/amanda/amandad[10777]: exit status 0xb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message