Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Mar 2007 10:53:08 GMT
From:      Heiko Weber<heiko@wecos.de>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   i386/110214: FreeBSD 6.2 freezes on SSH activitiy caused by nagios
Message-ID:  <200703121053.l2CAr8bs008801@www.freebsd.org>
Resent-Message-ID: <200703121100.l2CB0CIl063825@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         110214
>Category:       i386
>Synopsis:       FreeBSD 6.2 freezes on SSH activitiy caused by nagios
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 12 11:00:11 GMT 2007
>Closed-Date:
>Last-Modified:
>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:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200703121053.l2CAr8bs008801>