From nobody@FreeBSD.org  Mon Mar 12 10:53:09 2007
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 570E216A400
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 12 Mar 2007 10:53:09 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [69.147.83.33])
	by mx1.freebsd.org (Postfix) with ESMTP id 327CE13C44B
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 12 Mar 2007 10:53:09 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l2CAr8iA008802
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 12 Mar 2007 10:53:08 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id l2CAr8bs008801;
	Mon, 12 Mar 2007 10:53:08 GMT
	(envelope-from nobody)
Message-Id: <200703121053.l2CAr8bs008801@www.freebsd.org>
Date: Mon, 12 Mar 2007 10:53:08 GMT
From: Heiko Weber<heiko@wecos.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 6.2 freezes on SSH activitiy caused by nagios
X-Send-Pr-Version: www-3.0

>Number:         110214
>Category:       i386
>Synopsis:       [hang] FreeBSD 6.2 freezes on SSH activitiy caused by nagios
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    remko
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 12 11:00:11 GMT 2007
>Closed-Date:    Wed Jul 14 07:38:57 UTC 2010
>Last-Modified:  Wed Jul 14 07:38:57 UTC 2010
>Originator:     Heiko Weber
>Release:        FreeBSD 6.2
>Organization:
Wecos
>Environment:
FreeBSD xxx 6.2-STABLE FreeBSD 6.2-STABLE #2: Sat Feb  3 00:42:07 CET 2007     heiko@wecos.de:/usr/obj/usr/src/sys/SINIX  i386
>Description:
We have a dual xeon machine running apache webserver and mysql database.
This machine is monitored from a linux machine with nagios. Recently we
updated from FreeBSD 6.1 to 6.2. Since then we noticed some "system
freezes", the FreeBSD box is unusable for 1-2 minutes, sometimes up to
10-15 minutes.

During this freeze, even to console input there is no response. Commands
typed on console are executed later as if the freeze holds for two seconds
to continue with normal operation, and then continue to freeze.

The first time I noticed such a freeze, it went away ~5 minutes. But the
last two freeze were so heavy I rebooted after ~15 minutes the system.
After reboot the machine runs fine for about 1-2 weeks.

Two things which I notice, are new to 6.2:
1) after reboot sometimes the system show the following message in daily log:

+collecting pv entries -- suggest increasing PMAP_SHPGPERPROC

but not 5 times, as I remember I would say: 2nd day, 5th day. 10th day.

2) At the day the system freezes there are some of
Mar  9 12:04:00 www nrpe[81935]: Error: Could not complete SSL handshake. 5
Mar  9 12:04:00 www nrpe[81938]: Error: Could not complete SSL handshake. 5
Mar  9 12:05:33 www nrpe[81958]: Error: Could not complete SSL handshake. 5
Mar  9 12:05:33 www nrpe[81951]: Error: Could not complete SSL handshake. 5
Mar  9 12:05:33 www nrpe[81966]: Error: Could not complete SSL handshake. 5
Mar  9 12:05:33 www nrpe[81968]: Error: Could not complete SSL handshake. 5
Mar  9 12:06:42 www nrpe[81984]: Error: Could not complete SSL handshake. 5
Mar  9 12:06:42 www nrpe[81992]: Error: Could not complete SSL handshake. 5
Mar  9 12:06:42 www nrpe[81996]: Error: Could not complete SSL handshake. 5
Mar  9 12:06:43 www nrpe[81994]: Error: Could not complete SSL handshake. 5

but only on "freeze" days, not before - other days nagios works weel and
quickly reports any problems on the machine (if a monitored service shutdowns).

For now, I disabled nagios on the linux machine and stop monitoring - but
I am asking myself if that problem can be used to attack a freebsd machine
from the outside ?

Any hints or advice would be great.

Heiko

>How-To-Repeat:
Wait two weeks :-)
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Tue Jul 13 20:14:41 UTC 2010 
State-Changed-Why:  
Does this still occur? I monitor a few hosts as well and I do 
not see this kind of behaviour. I am getting the kernel messages 
you are talking about, but that requires tweaking on my end. It 
does not interrupt the machine's behaviour. 


Responsible-Changed-From-To: freebsd-i386->remko 
Responsible-Changed-By: remko 
Responsible-Changed-When: Tue Jul 13 20:14:41 UTC 2010 
Responsible-Changed-Why:  
Take. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=110214 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Wed Jul 14 07:38:56 UTC 2010 
State-Changed-Why:  
This was fixed by time, the submitter no longer has the setup available 
so this cannot be reproduced. Sadly, by waiting long enough we will face 
these things periodically. Thank you for your patience! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=110214 
>Unformatted:
