Date: Tue, 24 May 2005 13:26:05 -0400 From: Christopher Black <cblack@securecrossing.com> To: Bigbrother <bigbrother@bonbon.net> Cc: freebsd-questions@freebsd.org Subject: Re: RE:VM pager read error Message-ID: <1116955565.3676.3.camel@localhost> In-Reply-To: <200505241712.j4OHC4sO025518@bigb3server.ath.cx> References: <200505241712.j4OHC4sO025518@bigb3server.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-SLC9VAZprKfytr5iz5o4 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Good food for thought. I'm not using NFS, so there should be no issues related to dropped packets. Also, I've never seen the swap being touched, which makes me doubt the boxes are just running out of memory. =20 Is it possible that cheap hardware or buggy RAM could be causing this, or is it more likely a software issue? If it's software, has anyone seen similar issues with FBSD 5.4? Thanks, Chris On Tue, 2005-05-24 at 20:12 +0300, Bigbrother wrote: > > I have a distributed network of systems running FreeBSD 4.10-Release, > > and periodically, I see the following errors on the console: > > > > vm_fault: pager read error, pid 1 (init) >=20 > I have also a network with many diskless boxes of 4.11 FreeBSD and every = now > and then I see messages like this.=20 > The process that dies varies...It is not always (init)..Some times it is > (mrtg) some times (sshd) or (syslogd) and some other processes that the > boxes are running. >=20 >=20 > I have resolved this situation by running a series of crontab scripts tha= t > rlogin to every diskless box and checks/restarts every > service that is critical for that box (e.g. syslogd, cron, sshd...). >=20 > Of course if your (init )dies then you cannot do anything with it and you > should ask/phone a worker there to do a reboot on that machine. I think t= he > problem relies on poor hardware (my network has some low-end network card= s). >=20 > It would be nice if we could find any solution to this (without buying ne= w > cards). >=20 >=20 >=20 > Perhaps if we could define that some processes would never be swapped out > (like init) this problem would disappeared, but I > do not have time for such experiments. >=20 >=20 >=20 > BB >=20 >=20 > p.s. Even though people leave the office, perhaps crontab and periodic > execute some scripts...So perhaps the machines > have a high cpu load and some NFS packets are dropped resulting in the > process to die. >=20 > --- > Give a man fire, and he'll be warm for a day; set a man on fire, and he'l= l > be warm for the rest of his life=20 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" --=20 Christopher Black Chief Security Engineer Secure Crossing 22750 Woodward Suite 304 - Ferndale, MI 48220 Tel (800) 761-4299 | Direct (248) 658-6120 cblack@securecrossing.com | www.securecrossing.com --=-SLC9VAZprKfytr5iz5o4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCk2OtAPxZlIbJ6AwRAiluAJ0Tcxtd0A1BsJyMCc1j4PjjWQi1yACdFsQc 5T0BGivzI7Rb0bk/lsDHNzE= =kQPS -----END PGP SIGNATURE----- --=-SLC9VAZprKfytr5iz5o4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1116955565.3676.3.camel>