From owner-freebsd-questions@freebsd.org Wed Feb 22 23:27:53 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64B91CE9F69 for ; Wed, 22 Feb 2017 23:27:53 +0000 (UTC) (envelope-from doug@mail.sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 535BF112E; Wed, 22 Feb 2017 23:27:52 +0000 (UTC) (envelope-from doug@mail.sermon-archive.info) Received: from [10.0.1.251] (unknown [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 089A8114C387; Wed, 22 Feb 2017 15:27:46 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Daily and Weekly Periodic Scripts From: Doug Hardie In-Reply-To: <3483b77e-0836-fdf8-fd7e-32510de3c40b@freebsd.org> Date: Wed, 22 Feb 2017 15:28:46 -0800 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0DB0B402-4F0E-444D-A050-58E87687A7D5@mail.sermon-archive.info> References: <18376E93-56AB-4D07-AC78-C66DE4ABFB11@lafn.org> <58AD5A9A.7070407@fjl.co.uk> <3483b77e-0836-fdf8-fd7e-32510de3c40b@freebsd.org> To: Matthew Seaman X-Mailer: Apple Mail (2.3259) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 23:27:53 -0000 > On 22 February 2017, at 01:53, Matthew Seaman = wrote: >=20 > On 02/22/17 09:32, Frank Leonhardt wrote: >> For what it's worth, in a similar situation I simply have a cron >> triggered script that greps certain files (or the output of certain >> utilities) and fires off an email if it finds/doesn't find certain >> things. Very simple and flexible, and it keeps nagging if I don't do >> anything about it. I keep thinking of doing something more gala, but >> over many years I've found this actually works for me. >>=20 >=20 > If anyone is looking for a project, teaching hte daily / weekly = /monthly > scripts to produce output in a machine parseable form, like JSON or = UCL > suitable for injecting into a system like logstash would be pretty = useful. >=20 > As it is, the nightly email generated by FreeBSD don't scale well = beyond > a few dozen machines. If you're dealing with an installation of that > size, you'ld be better off redirecting hte output to a log file on the > server and then setting up appropriate monitoring to tell you about = any > problems as they occur -- eg. through nagios or icinga or the like. I investigated teaching the scripts to output JSON, but that is a big = project. However, even when that is done, I still would need something = to parse it to find the problems. Thats not trivial either. I like the idea of moving those checks over to nagios which I am using = on all the machines anyway. I decided to start with the daily netstat = numbers. However, there are some things I don't understand about them = and a problem with disappearing addresses that I will send separately. = Thanks to all.=