Date: Thu, 17 Oct 2002 14:28:57 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: "Alvaro Rosales R." <aran80@wintersperu.com.pe> Cc: freebsd-questions@FreeBSD.org Subject: Re: Problem With FreeBSD4.6 core dump Message-ID: <20021017112857.GE14331@hades.hell.gr> In-Reply-To: <3DAD3050.17614.3A0E89D@localhost> References: <3DAD3050.17614.3A0E89D@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-10-16 09:24, "Alvaro Rosales R." <aran80@wintersperu.com.pe> wrote: > Hi Guys I 've got an error everyday on my console at 3:01:01AM, > it shows this message: > /kernel:pid677 (dump), uid 0: exited on signal 11 (core dumped). The fact that the message shows up at 03:01:01 is probably indicative of something that runs through cron. The hour (just seconds after 03:00am) points to the daily scripts that FreeBSD runs to check things. The program that fails is called "dump". There is only one instance of a "dump" command in /etc/periodic/daily/* files: keramida@hades[14:26]/etc/periodic/daily$ grep dump * 400.status-disks: dump W || rc=3;; Can you try running the following command as root and see if it fails? # dump W > I've installed this OS in 3 different servers and i've got the same > error at the same time everyday. Hown can I eliminate this error?. By fixing the problems that dump(8) has. > I am using freebsd 4.6 release #1. Release kernels do not have #1 as their number, but #0. This is probably an indication of a kernel recompile that you did, without going through the recommended buildworld/buildkernel steps. If this is the case, you have kernel that is not in sync with your userland tools, and that could very well be the cause behind the dump(8) failures that you're seeing. Giorgos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021017112857.GE14331>