From owner-freebsd-questions@FreeBSD.ORG Fri Dec 17 13:48:38 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 331F7106566B for ; Fri, 17 Dec 2010 13:48:38 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id B21448FC17 for ; Fri, 17 Dec 2010 13:48:37 +0000 (UTC) Received: by wyf19 with SMTP id 19so612193wyf.13 for ; Fri, 17 Dec 2010 05:48:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=p5LqYHs3Xrww1b3JKe+bzirtQuOCcmvtkIpGlRMLZYg=; b=Rb+9omrnM0Sj3rrO52LrUMu53xyVfT++NKItHvAO7GK+AR6DrA1vQiEFRFGZ1OA9iR a0pstJHtmgzGQdTZDU5Y0DdXfIG7wWplp/76pqsBTxopDBMdbhWda8pxLyu+Lrg2n0lj q5n0Ys2NEE2KkQC16ICSadIxWa7IX8Jp4dODU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=M3FbgNzYkTvnegbUyH/gVwslisT/LgFH/xhadkhXS2hY/SPdsIlP7gw2wdONnZMWKe Ff9GyjMO/vKMJ9svpn7Xhmg18YLR8SoTzCbUFeCLG8O6np6jt6hG0ZUR7esoay3Cdal9 YpBzjPfm9Ei4PEEfZtO7V5nXEN3vuTHhD9lbE= MIME-Version: 1.0 Received: by 10.216.188.141 with SMTP id a13mr1118921wen.59.1292593716665; Fri, 17 Dec 2010 05:48:36 -0800 (PST) Received: by 10.216.72.198 with HTTP; Fri, 17 Dec 2010 05:48:36 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Dec 2010 13:48:36 +0000 Message-ID: From: krad To: =?UTF-8?Q?Matej_=C5=A0erc?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.2-RELEASE amd64 hangs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 13:48:38 -0000 On 17 December 2010 13:47, krad wrote: > > > On 16 December 2010 17:42, Matej =C5=A0erc wrote: > >> Hi, >> >> I am experiencing a strange issue that has never occurred to me in all t= he >> years of using different versions of FreeBSD. >> >> One of our servers, which was running without any issues until yesterday= , >> stopped responding for two times now - yesterday and today. About three >> days >> ago another process of pulling out SNMP data from devices was added, but= I >> was looking the system load and the system was working normally and also >> processes were cmpleting successfully within the timeframe of 5 minutes >> (much faster, they completed in about 2 minutes). I also want to mention >> that those SNMP pulling processes were already working about a month or = so >> on the same server (no hardware was changed in the meantime) and I am >> pretty >> sure that it should work normally as it did. >> >> My main problem is, that there is abcolutely nothing in log files - no >> errors, no warnings, nothing. No strange messages, every process just >> stops >> logging at one time and then continues after the reboot. Another >> interesting >> issue is that both hangs occured at approximately the same time, but the= re >> was nobody in the server room and also no one was logged into the server >> at >> that time except me. About 10 minutes before hang I was investigating >> processes and everything was very normal - no large CPU eating or memory >> eating processes. This might be interesting, even after every process >> stops >> responding, I was still able to ping the network interfaces and receive >> ICMP >> replies back. >> >> Of course my idea about it is that it must be connected to some hardware >> problems - my suggestion was to make some memory tests. But I would like >> to >> hear some your oppinions about the entire situation. Could some power >> supply >> issues be doing it? The server is about a year old and has, as I already >> mentioned, worked like a charm until now. How come there is no kernel >> panic >> since no daemon seems to be working? Why is network interface still up a= nd >> working? >> >> I was unable to go to the co-location facility so I can't say what was o= n >> the screen at both times, but I suppose there was nothing else than >> messages >> I can read from log files. >> >> I know that 7.2 is pretty old version, but it was working until now on t= he >> same hardware and we had no reason to change that. Now the system is aft= er >> reboot again running smoothly and without any issues at all. >> >> Thank you very much for any information regarding the issue. >> >> BR, Matej >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscribe@freebsd.org" >> > > I'm not a huge fan of letting snmp spawn heavy weight scripts and process= es > as it is to easy for a remote machine to effectively dos the machine. I > realise you are fairly sure the scripts arent an issue, but try croning t= hem > every 5 minutes, and writing the results to a file. SNMP can then simply > retrieve the results from the file. This safeguard to to a certain extent= , > in that it stops many processes being spawned. All you have to watch afte= r > that is the job run time > > > Also lets stops resources being tied up on the monitoring machine, as it doent have to hang around for x minutes for the results for its query