mon-devel Mailing List for mon (Page 2)
Brought to you by:
trockij
Menu
▾
▴
mon-devel — Discussions related to mon development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(27) |
Mar
|
Apr
(9) |
May
(11) |
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(15) |
| 2006 |
Jan
|
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(14) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(4) |
Dec
(8) |
| 2008 |
Jan
(6) |
Feb
(4) |
Mar
(7) |
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2010 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(7) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
(3) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Alex H. <ah...@bm...> - 2011-10-06 10:56:58
|
Jim Trocki uttered: > On Tue, 4 Oct 2011, Alex Hooper wrote: > >> Hello, >> >> I see from the archives that this list is pretty quiet but I post this >> in case >> it reaches someone with experience of this problem or some insight. >> I've been >> using mon for over ten years now, I think, and have always found it to >> be highly >> reliable and adaptable. I've recently migrated our mon installation to >> a new >> server and done a little tidying up. Doing so has brought to light an >> oddity >> that I cannot explain: >> >> I have a watch which checks the http service for one host. The http >> service on >> that host is down (it's a load-balancer node which has been removed >> from the >> pool and therefore always returns false when checked via the monitor >> below). >> However, the service periodically sends me an upalert. I've turned on >> debugging >> on the http_tppnp.monitor and this consistently shows the service >> failing -- it >> NEVER shows the monitor passing. >> >> Does anyone have any ideas as to what might be going on, or how I >> might better >> track it down? > > which version of mon? > > you can run "mon -d" to turn on debug logging, and it will show the exit > status of every monitor, so that may provide some hints if you'd like > to track the up/down state from the viewpoint of the server. > Interesting results. Normally, the monitor fails and the debug output contains (we are interested in learning-06): watching file handle 7 for learning-06/http select returned 0 file handles 3165 watching file handle 8 for bestpractice-04/http select returned 0 file handles 3166 watching file handle 9 for learning-03/http select returned 2 file handles [http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy 45 bytes 0.193042 s String 'alteon_healthcheck_ok' is missing ] from FileHandle=GLOB(0x1bde0c8) EOF on FileHandle=GLOB(0x1bde0c8) EOF on FileHandle=GLOB(0x1bddd68) PID 6169 (besthealth-05/http) exited with [0] process_event type=m group=besthealth-05 service=http exitval=0 output=[] PID 6173 (learning-06/http) exited with [1] process_event type=m group=learning-06 service=http exitval=1 output=[http://lea rning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy 45 bytes 0.193042 s String 'alteon_healthcheck_ok' is missing ] do_alert flags=1 But sometimes watching file handle 7 for learning-06/http select returned 0 file handles 3299 watching file handle 8 for besthealth-03/http select returned 1 file handles EOF on FileHandle=GLOB(0x1bc1c90) PID 6569 (ics/http) exited with [0] process_event type=m group=ics service=http exitval=0 output=[] 3300 select returned 1 file handles [http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy 45 bytes 0.211609 s String 'alteon_healthcheck_ok' is missing ] from FileHandle=GLOB(0x1bc1ca8) EOF on FileHandle=GLOB(0x1bc1ca8) PID 6587 (learning-06/http) exited with [0] process_event type=m group=learning-06 service=http exitval=0 output=[http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy http://learning-06.ntt.bmjgroup.com/alteonhealthcheck/alteonhealthcheck@noproxy 45 bytes 0.211609 s String 'alteon_healthcheck_ok' is missing ] do_alert flags=2 3301 Which shows mon reporting that the monitor exited with a return code of 0. But the monitor script has output summary information which it only does when reporting failure and, indeed, the printing of summary info by the script is invariably followed by an 'exit 1' statement. So... interesting but not as yet enlightening. Alex. _______________________________________________________________________ The BMJ Group is one of the world's most trusted providers of medical information for doctors, researchers, health care workers and patients group.bmj.com. This email and any attachments are confidential. If you have received this email in error, please delete it and kindly notify us. If the email contains personal views then the BMJ Group accepts no responsibility for these statements. The recipient should check this email and attachments for viruses because the BMJ Group accepts no liability for any damage caused by viruses. Emails sent or received by the BMJ Group may be monitored for size, traffic, distribution and content. BMJ Publishing Group Limited trading as BMJ Group. A private limited company, registered in England and Wales under registration number 03102371. Registered office: BMA House, Tavistock Square, London WC1H 9JR, UK. _______________________________________________________________________ |
|
From: Alex H. <ah...@bm...> - 2011-10-06 07:58:28
|
Jim Trocki uttered: > On Tue, 4 Oct 2011, Alex Hooper wrote: > >> Hello, >> >> I see from the archives that this list is pretty quiet but I post this >> in case >> it reaches someone with experience of this problem or some insight. >> I've been >> using mon for over ten years now, I think, and have always found it to >> be highly >> reliable and adaptable. I've recently migrated our mon installation to >> a new >> server and done a little tidying up. Doing so has brought to light an >> oddity >> that I cannot explain: >> >> I have a watch which checks the http service for one host. The http >> service on >> that host is down (it's a load-balancer node which has been removed >> from the >> pool and therefore always returns false when checked via the monitor >> below). >> However, the service periodically sends me an upalert. I've turned on >> debugging >> on the http_tppnp.monitor and this consistently shows the service >> failing -- it >> NEVER shows the monitor passing. >> >> Does anyone have any ideas as to what might be going on, or how I >> might better >> track it down? > > which version of mon? > $ mon -v $Id: mon,v 1.22.2.2 2007/06/06 11:46:19 trockij Exp $ $Name: mon-1-2-0-release $ > you can run "mon -d" to turn on debug logging, and it will show the exit > status of every monitor, so that may provide some hints if you'd like > to track the up/down state from the viewpoint of the server. > Ah, good plan. I'll give that a go. Thanks, Alex. > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ -- Alex Hooper Operations Team Leader, BMJ Group, BMA House, London WC1H 9JR Tel: +44 (0) 20 7383 6049 http://group.bmj.com/ _______________________________________________________________________ The BMJ Group is one of the world's most trusted providers of medical information for doctors, researchers, health care workers and patients group.bmj.com. This email and any attachments are confidential. If you have received this email in error, please delete it and kindly notify us. If the email contains personal views then the BMJ Group accepts no responsibility for these statements. The recipient should check this email and attachments for viruses because the BMJ Group accepts no liability for any damage caused by viruses. Emails sent or received by the BMJ Group may be monitored for size, traffic, distribution and content. BMJ Publishing Group Limited trading as BMJ Group. A private limited company, registered in England and Wales under registration number 03102371. Registered office: BMA House, Tavistock Square, London WC1H 9JR, UK. _______________________________________________________________________ |
|
From: Jim T. <tr...@gm...> - 2011-10-05 17:32:44
|
On Tue, 4 Oct 2011, Alex Hooper wrote: > Hello, > > I see from the archives that this list is pretty quiet but I post this in case > it reaches someone with experience of this problem or some insight. I've been > using mon for over ten years now, I think, and have always found it to be highly > reliable and adaptable. I've recently migrated our mon installation to a new > server and done a little tidying up. Doing so has brought to light an oddity > that I cannot explain: > > I have a watch which checks the http service for one host. The http service on > that host is down (it's a load-balancer node which has been removed from the > pool and therefore always returns false when checked via the monitor below). > However, the service periodically sends me an upalert. I've turned on debugging > on the http_tppnp.monitor and this consistently shows the service failing -- it > NEVER shows the monitor passing. > > Does anyone have any ideas as to what might be going on, or how I might better > track it down? which version of mon? you can run "mon -d" to turn on debug logging, and it will show the exit status of every monitor, so that may provide some hints if you'd like to track the up/down state from the viewpoint of the server. |
|
From: Alex H. <ah...@bm...> - 2011-10-04 07:02:01
|
Hello,
I see from the archives that this list is pretty quiet but I post this in case
it reaches someone with experience of this problem or some insight. I've been
using mon for over ten years now, I think, and have always found it to be highly
reliable and adaptable. I've recently migrated our mon installation to a new
server and done a little tidying up. Doing so has brought to light an oddity
that I cannot explain:
I have a watch which checks the http service for one host. The http service on
that host is down (it's a load-balancer node which has been removed from the
pool and therefore always returns false when checked via the monitor below).
However, the service periodically sends me an upalert. I've turned on debugging
on the http_tppnp.monitor and this consistently shows the service failing -- it
NEVER shows the monitor passing.
Does anyone have any ideas as to what might be going on, or how I might better
track it down?
Cheers,
Alex.
watch besthealth-01
service http
interval 2m
randskew 12s
depend 00_gateway:ping
monitor http_tppnp.monitor --okstring 'alteon_healthcheck_ok' -l
/var/log/mon/client_sites
period wd {Mon-Sun}
alertevery 12h
alertafter 2
upalertafter 5m
alert irc.alert -c alerts -S irc.internal.bmjgroup.com -U
monaltert@bream -n alertbot -j
upalert irc.alert -c alerts -S irc.internal.bmjgroup.com -U
monaltert@bream -n alertbot -j
period ESCALATE: wd {Mon-Sun}
alertevery 12h
alertafter 15m
upalertafter 5m
alert mail.alert ah...@bm... bmj...@li...
upalert mail.alert -u ah...@bm... bmj...@li...
--
Alex Hooper
Operations Team Leader, BMJ Group, BMA House, London WC1H 9JR
Tel: +44 (0) 20 7383 6049
http://group.bmj.com/
_______________________________________________________________________
The BMJ Group is one of the world's most trusted providers of medical information for doctors, researchers, health care workers and patients group.bmj.com. This email and any attachments are confidential. If you have received this email in error, please delete it and kindly notify us. If the email contains personal views then the BMJ Group accepts no responsibility for these statements. The recipient should check this email and attachments for viruses because the BMJ Group accepts no liability for any damage caused by viruses. Emails sent or received by the BMJ Group may be monitored for size, traffic, distribution and content. BMJ Publishing Group Limited trading as BMJ Group. A private limited company, registered in England and Wales under registration number 03102371. Registered office: BMA House, Tavistock Square, London WC1H 9JR, UK.
_______________________________________________________________________
|
|
From: Nathan G. <na...@cm...> - 2010-01-23 00:50:06
|
* Nathan Gibbs wrote: > While working on something that uses Mon::Client, I ran into the > following situation. > > I just sent a mod of the list_opstatus sub in Mon::Client to Jim, that should close this issue. -- Sincerely, Nathan Gibbs Systems Administrator Christ Media http://www.cmpublishers.com |
|
From: Nathan G. <na...@cm...> - 2010-01-23 00:50:03
|
* Nathan Gibbs wrote: > While working on something that uses Mon::Client, I ran into the > following situation. > > I just sent a mod of the list_opstatus sub in Mon::Client to Jim, that should close this issue. -- Sincerely, Nathan Gibbs Systems Administrator Christ Media http://www.cmpublishers.com |
|
From: Nathan G. <na...@cm...> - 2010-01-20 05:24:03
|
While working on something that uses Mon::Client, I ran into the
following situation.
I changed a call to list_opstatus from
list_opstatus{};
to
list_opstatus([$args]);
This doesn't work if $args eq "";
$args is passed to a sub, and could be anything.
in the contest of this call it would be either "" or something like
"servers,ftp" or "servers"
I put a check for the null in my code like this.
if ( $arg ne "" ) {
%rethash = $c->list_opstatus( [$arg] );
}else{
%rethash = $c->list_opstatus();
}
However I will have to do so everywhere I use list_opstatus,
list_successes or list_failures.
Personally, no big deal, however it would simplify things if
list_opstatus([""]);
were treated as a
list_opstatus();
internally by Mon::Client.
Thoughts?
|
|
From: Nathan G. <na...@cm...> - 2010-01-15 03:15:58
|
* Jim Trocki wrote:
> On Thu, 14 Jan 2010, Nathan Gibbs wrote:
>
>> I posted this on the main mon list last week, but haven't heard one way
>> or the other.
>> Am I seeing a bug, feature, or an issue with my own installation.
>>
>>
SNIP
>
> that could be due to $sref->{"_depend_status"} not being defined at the
> time of the query, probably because there is no "depend" definition
> in the configuration. could you check that?
>
>
Yes, depends are defined for the services I was looking at.
We have a "dep_behavior = hm" line in our mon.cf.
If I comment it out depstatus works.
If I set it to m it works.
After Reading the manuals, it seems impossible to get mon to return a
depstatus in this mode. The interface doesn't appear to return enough
info at Group:Service:Host resolution.
I think this should be a bug, but am clueless about how to fix it.
:-(
--
Sincerely,
Nathan Gibbs
Systems Administrator
Christ Media
http://www.cmpublishers.com
|
|
From: Augie S. <aug...@gm...> - 2010-01-15 00:02:26
|
I favored the following for our deployment; mon alerts if the monitor
is not defined or if it can't be found.
What are peoples thoughts about including this into the trunk, and
back-porting into the stable branch?
--Augie
--- /usr/sbin/mon.old 2010-01-14 15:39:33.000000000 -0800
+++ /usr/sbin/mon 2010-01-14 15:39:43.000000000 -0800
@@ -3498,7 +3498,6 @@
if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
syslog ('err', "no monitor found while trying to run [$monitor]");
- return undef;
} else {
$monitor = $MONITORHASH{$monitor};
}
@@ -3610,7 +3609,8 @@
if (!exec @args)
{
syslog ('err', "could not exec '@args': $!");
- exit (1);
+ print ("run_monitor: could not exec '@args': $!\n");
+ exit (1);
}
}
On Thu, Jan 14, 2010 at 12:15 AM, <den...@or...> wrote:
> With 'exit(1)' your mon process will not send alert either as he will just stop running.
> In fact it will be worth as 'mon' will just stop monitoring anything, even groups with still valid monitor.
>
> My idea is that if the monitor can't be run it should be seen and reported as a failure of the service not a failure of the whole 'mon' process.
>
> Maybe, the simpler way to do this is just not to return at all and let the exec fail in the forked process.
> By the way, when a monitor can't be run we could add a summary line before exiting the forked process, that way, the problem could be seen in the mon.cgi interface instead of having to look in the syslog files.
>
> Below a possible patch (NOT TESTED ! no test environment available to me righ now):
>
> --- mon-1.2.0/mon 2009-12-16 13:46:33.808765600 +0000
> +++ mon-1.2.0-missingmonitor/mon 2010-01-14 08:11:39.641127600 +0000
> @@ -3498,9 +3498,11 @@
>
> ($monitor, $monitorargs) = ($sref->{"monitor"} =~ /^(\S+)(\s+(.*))?$/);
>
> - if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
> + if (!defined $MONITORHASH{$monitor}) {
> syslog ('err', "no monitor found while trying to run [$monitor]");
> - return undef;
> + # Hopefully the following path does not exists and
> + # an error will be raised when trying to exec this
> + $monitor = "/no/monitor/defined/in/configuration/file";
> } else {
> $monitor = $MONITORHASH{$monitor};
> }
> @@ -3611,6 +3613,7 @@
>
> if (!exec @args)
> {
> + printf("run_monitor: could not exec '@args': $!\n");
> syslog ('err', "could not exec '@args': $!");
> exit (1);
> }
>
>
> Denis Choulette
>
> den...@or...
>
>
> Orange Business Services
> CS&O / ITSO / MA&SM / E1RSD / SQOCM
>
> BP 91235 Rue de la Touche Lambert
> Bâtiment 7
> F35512 Cesson Sévigné Cedex France
>
> Phone: +33 (0) 2 23 28 41 09
> Fax: +33 (0) 2 23 28 45 83
> http://www.equant.com
>
>
> -----Original Message-----
> From: Augie Schwer [mailto:aug...@gm...]
> Sent: 14 January 2010 02:12
> To: mon...@li...
> Subject: [Mon-devel] no monitor found while trying to run.
>
> Shouldn't "no monitor found while trying to run" be a critical event?
> If someone removes fping.monitor on accident, your whole network could be dead and you would never know except for all the syslog messages.
> In the best case it would be a typo when you were setting something up, and you'd still want to know you screwed up sooner than later right?
>
> if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
> syslog ('err', "no monitor found while trying to run [$monitor]");
> return undef;
>
> I haven't tried it yet -- I think instead of returning an 'undef'
> 'run_monitor' should "exit(1)" in this case; what do you folks think?
>
>
> --
> Augie Schwer - Augie@Schwer.us - http://schwer.us
> Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> Mon-devel mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/mon-devel
>
> *********************************
> This message and any attachments (the "message") are confidential and intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered, changed or falsified.
> If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
> ********************************
>
>
--
Augie Schwer - Augie@Schwer.us - http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
|
|
From: Jim T. <tr...@gm...> - 2010-01-14 19:53:54
|
On Thu, 14 Jan 2010, Nathan Gibbs wrote:
> I posted this on the main mon list last week, but haven't heard one way
> or the other.
> Am I seeing a bug, feature, or an issue with my own installation.
>
>
>> It appears that mon fails to return depstatus when queried with
>> list_successes
>> list_failures
>> or
>> list_opstatus
>
>> Noticed this in the cgi.
>> Verified it with moncmd.
>
>> Always returns depstatus=
that could be due to $sref->{"_depend_status"} not being defined at the
time of the query, probably because there is no "depend" definition
in the configuration. could you check that?
|
|
From: Jim T. <tr...@gm...> - 2010-01-14 14:47:19
|
On Thu, 14 Jan 2010, den...@or... wrote:
> My idea is that if the monitor can't be run it should be seen and
> reported as a failure of the service not a failure of the whole 'mon'
> process.
how about having a special "watch" definition for severe system errors
which may require their own alerts? you could define something like
this:
watch system-events
service failed-monitors
blah blah blah
service failed-alerts
blah blah blah
service default-failure
blah blah blah
there could be a new opstatus value for a regular service which fails
executing the monitor to reflect that, rather than making it look like
the service itself is failing, which in that event would actually be
indeterminate. it could be called $STAT_EXECFAIL or maybe something
more generic.
also, there could be an "internal" kind of alert, maybe called "log"
which would write out a message to a log or to syslog or whatever without
having to fork off an external program. one would have the option of
using that, so the behavior would be similar to what it is now, or
you could have it call a real alert to get the operator's attention.
|
|
From: Nathan G. <na...@cm...> - 2010-01-14 14:17:23
|
I posted this on the main mon list last week, but haven't heard one way or the other. Am I seeing a bug, feature, or an issue with my own installation. > It appears that mon fails to return depstatus when queried with > list_successes > list_failures > or > list_opstatus > Noticed this in the cgi. > Verified it with moncmd. > Always returns depstatus= -- Sincerely, Nathan Gibbs Systems Administrator Christ Media http://www.cmpublishers.com |
|
From: <den...@or...> - 2010-01-14 08:42:40
|
Sorry, I find a problem with the patch I just sent. It should be a 'print' not a 'printf' in exec test, so that we can display monitor and argument with % in the string without trying to format them. (Arguments with % occurs frequently with URL encoded requests where %2F, for example, is very common.) Here is the fixed patch: <<< Patch removed. >>> Denis Choulette den...@or... Orange Business Services CS&O / ITSO / MA&SM / E1RSD / SQOCM BP 91235 Rue de la Touche Lambert Bâtiment 7 F35512 Cesson Sévigné Cedex France Phone: +33 (0) 2 23 28 41 09 Fax: +33 (0) 2 23 28 45 83 http://www.equant.com -----Original Message----- From: den...@or... [mailto:den...@or...] Sent: 14 January 2010 09:15 To: Augie Schwer; mon...@li... Subject: Re: [Mon-devel] no monitor found while trying to run. With 'exit(1)' your mon process will not send alert either as he will just stop running. In fact it will be worth as 'mon' will just stop monitoring anything, even groups with still valid monitor. My idea is that if the monitor can't be run it should be seen and reported as a failure of the service not a failure of the whole 'mon' process. Maybe, the simpler way to do this is just not to return at all and let the exec fail in the forked process. By the way, when a monitor can't be run we could add a summary line before exiting the forked process, that way, the problem could be seen in the mon.cgi interface instead of having to look in the syslog files. Below a possible patch (NOT TESTED ! no test environment available to me righ now): --- mon-1.2.0/mon 2009-12-16 13:46:33.808765600 +0000 +++ mon-1.2.0-missingmonitor/mon 2010-01-14 08:11:39.641127600 +0000 @@ -3498,9 +3498,11 @@ ($monitor, $monitorargs) = ($sref->{"monitor"} =~ /^(\S+)(\s+(.*))?$/); - if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) { + if (!defined $MONITORHASH{$monitor}) { syslog ('err', "no monitor found while trying to run [$monitor]"); - return undef; + # Hopefully the following path does not exists and + # an error will be raised when trying to exec this + $monitor = "/no/monitor/defined/in/configuration/file"; } else { $monitor = $MONITORHASH{$monitor}; } @@ -3611,6 +3613,7 @@ if (!exec @args) { + printf("run_monitor: could not exec '@args': $!\n"); syslog ('err', "could not exec '@args': $!"); exit (1); } Denis Choulette den...@or... Orange Business Services CS&O / ITSO / MA&SM / E1RSD / SQOCM BP 91235 Rue de la Touche Lambert Bâtiment 7 F35512 Cesson Sévigné Cedex France Phone: +33 (0) 2 23 28 41 09 Fax: +33 (0) 2 23 28 45 83 http://www.equant.com -----Original Message----- From: Augie Schwer [mailto:aug...@gm...] Sent: 14 January 2010 02:12 To: mon...@li... Subject: [Mon-devel] no monitor found while trying to run. Shouldn't "no monitor found while trying to run" be a critical event? If someone removes fping.monitor on accident, your whole network could be dead and you would never know except for all the syslog messages. In the best case it would be a typo when you were setting something up, and you'd still want to know you screwed up sooner than later right? if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) { syslog ('err', "no monitor found while trying to run [$monitor]"); return undef; I haven't tried it yet -- I think instead of returning an 'undef' 'run_monitor' should "exit(1)" in this case; what do you folks think? -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Mon-devel mailing list Mon...@li... https://lists.sourceforge.net/lists/listinfo/mon-devel ********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ******************************** ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Mon-devel mailing list Mon...@li... https://lists.sourceforge.net/lists/listinfo/mon-devel ********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ******************************** |
|
From: <den...@or...> - 2010-01-14 08:15:35
|
With 'exit(1)' your mon process will not send alert either as he will just stop running.
In fact it will be worth as 'mon' will just stop monitoring anything, even groups with still valid monitor.
My idea is that if the monitor can't be run it should be seen and reported as a failure of the service not a failure of the whole 'mon' process.
Maybe, the simpler way to do this is just not to return at all and let the exec fail in the forked process.
By the way, when a monitor can't be run we could add a summary line before exiting the forked process, that way, the problem could be seen in the mon.cgi interface instead of having to look in the syslog files.
Below a possible patch (NOT TESTED ! no test environment available to me righ now):
--- mon-1.2.0/mon 2009-12-16 13:46:33.808765600 +0000
+++ mon-1.2.0-missingmonitor/mon 2010-01-14 08:11:39.641127600 +0000
@@ -3498,9 +3498,11 @@
($monitor, $monitorargs) = ($sref->{"monitor"} =~ /^(\S+)(\s+(.*))?$/);
- if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
+ if (!defined $MONITORHASH{$monitor}) {
syslog ('err', "no monitor found while trying to run [$monitor]");
- return undef;
+ # Hopefully the following path does not exists and
+ # an error will be raised when trying to exec this
+ $monitor = "/no/monitor/defined/in/configuration/file";
} else {
$monitor = $MONITORHASH{$monitor};
}
@@ -3611,6 +3613,7 @@
if (!exec @args)
{
+ printf("run_monitor: could not exec '@args': $!\n");
syslog ('err', "could not exec '@args': $!");
exit (1);
}
Denis Choulette
den...@or...
Orange Business Services
CS&O / ITSO / MA&SM / E1RSD / SQOCM
BP 91235 Rue de la Touche Lambert
Bâtiment 7
F35512 Cesson Sévigné Cedex France
Phone: +33 (0) 2 23 28 41 09
Fax: +33 (0) 2 23 28 45 83
http://www.equant.com
-----Original Message-----
From: Augie Schwer [mailto:aug...@gm...]
Sent: 14 January 2010 02:12
To: mon...@li...
Subject: [Mon-devel] no monitor found while trying to run.
Shouldn't "no monitor found while trying to run" be a critical event?
If someone removes fping.monitor on accident, your whole network could be dead and you would never know except for all the syslog messages.
In the best case it would be a typo when you were setting something up, and you'd still want to know you screwed up sooner than later right?
if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
syslog ('err', "no monitor found while trying to run [$monitor]");
return undef;
I haven't tried it yet -- I think instead of returning an 'undef'
'run_monitor' should "exit(1)" in this case; what do you folks think?
--
Augie Schwer - Augie@Schwer.us - http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Mon-devel mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/mon-devel
*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
|
|
From: Augie S. <aug...@gm...> - 2010-01-14 01:11:40
|
Shouldn't "no monitor found while trying to run" be a critical event?
If someone removes fping.monitor on accident, your whole network could
be dead and you would never know except for all the syslog messages.
In the best case it would be a typo when you were setting something
up, and you'd still want to know you screwed up sooner than later
right?
if (!defined $MONITORHASH{$monitor} || ! -f $MONITORHASH{$monitor}) {
syslog ('err', "no monitor found while trying to run [$monitor]");
return undef;
I haven't tried it yet -- I think instead of returning an 'undef'
'run_monitor' should "exit(1)" in this case; what do you folks think?
--
Augie Schwer - Augie@Schwer.us - http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
|
|
From: Nathan G. <na...@cm...> - 2009-12-30 15:14:55
|
* den...@or... wrote: > Hi all, > > I used mon for 5 years now. > > I fixed a bug after the 'exec' call in 'call_alert' function. I hope this is the good place to send the patch. > > The problem occured on a Solaris server with a high CPU and memory load. > Sometime, when an alert script was to be run, the 'mon' process was able to 'fork' but not to 'exec'. > In mon-1.2.0, when the exec of 'call_alert' fail in the forked 'mon' process, the function 'call_alert' just 'return', and from function to function, the execution goes back up to the main loop. At which time we have 2 "clone" 'mon' processes (the original one and the forked one) running all the tests twice. > > As this happened on a server with high CPU and memory load, running all tests twice, did not improve the situation and the "cloning" occured more and more frequently until we had so many mon processes that the system was not able to respond anymore. > > This whole problem occured several times before we could be sure of the root cause. I've seen this happen also, but didn't know the cause. Thanks for finding and fixing it. -- Sincerely, Nathan Gibbs Systems Administrator Christ Media http://www.cmpublishers.com |
|
From: Jim T. <tr...@gm...> - 2009-12-29 18:56:32
|
On Mon, 28 Dec 2009, den...@or... wrote: > I fixed a bug after the 'exec' call in 'call_alert' function. I hope this is the good place to send the patch. yes it is, thank you. i've applied it and checked it into cvs under mon-1-2-branch. |
|
From: Augie S. <aug...@gm...> - 2009-01-19 18:54:43
|
This isn't code I wrote, but it is code we use in production that I thought might help others using Mon. By the way, does anyone have any tricks they use for verifying certificates being used for Secure FTP? --Augie On Mon, Jan 19, 2009 at 10:42 AM, Augie Schwer <as...@us...> wrote: > Update of /cvsroot/mon/mon-contrib/monitors/ssl > In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv17672/ssl > > Added Files: > ssl-cert-check > Log Message: > Adding ssl/ssl-cert-check to the contrib. tree. > > --- NEW FILE: ssl-cert-check --- > #!/bin/bash > # > # Program: SSL Certificate Check <ssl-cert-check> > # > # Source code home: http://prefetch.net/code/ssl-cert-check > # > # Author: Matty < matty91 at gmail dot com > > # > # Current Version: 3.14 > # > # Revision History: > # > # Version 3.14 > # - Fixed the Common Name parser to handle DN's where the CN is not the last item > # eg. EmailAddr -- Jason Brothers > # - Added the ability to grab the serial number -- Jason Brothers > # - Added the "-b" option to print results without a header -- Jason Brothers > # - Added the "-v" option for certificate validation -- Jason Brothers > # > # Version 3.13 > # - Updated the subject line to include the hostname as well as > # the common name embedded in the X509 certificate (if it's > # available) -- idea proposed by Mike Burns > # > # Version 3.12 > # - Updated the license to allow redistribution and modification > # > # Version 3.11 > # - Added ability to comment out lines in files passed > # to the "-f" option -- Brett Stauner > # - Fixed comment next to file processing logic > # > # Version 3.10 > # - Fixed POP3 port -- Simon Matter > # > # Version 3.9 > # - Switched binary location logic to use which utility > # > # Version 3.8 > # - Fixed display on 80 column displays > # - Cleaned up the formatting > # > # Version 3.7 > # - Fixed bug in NAGIOS tests -- Ben Allen > # > # Version 3.6 > # - Added support for certificates stored in PKCS#12 databases -- Ken Gallo > # - Cleaned up comments > # - Adjusted variables to be more consistent > # > # Version 3.5 > # - Added support for NAGIOS -- Quanah Gibson-Mount > # - Added additional checks for mail -- Quanah Gibson-Mount > # - Convert tabs to spaces -- Quanah Gibson-Mount > # - Cleaned up usage() routine > # - Added additional checks for openssl > # > # Version 3.4 > # - Added a missing "{" to line 364 -- Ken Gallo > # - Move mktemp to the start of the main body to avoid errors > # - Adjusted default binary paths to make sure the script just works > # w/ Solaris, BSD and Linux hosts > # > # Version 3.3 > # - Added common name from X.509 certificate file to E-mail body / header -- Doug Curtis > # - Fixed several documentation errors > # - Use mktemp to create temporary files > # - Convert printf, sed and awk to variables > # - Check for printf, sed, awk and mktemp binaries > # - Add additional logic to make sure mktemp returned a valid temporary file > # > # Version 3.2 > # - Added option to list certificates in the file passed to "-f". > # > # Version 3.1 > # - Added handling for starttls for smtp -- Marco Amrein > # - Added handling for starttls for pop3 (without s) -- Marco Amrein > # - Removed extra spacing at end of script > # > # Version 3.0 > # - Added "-i" option to print certificate issuer > # - Removed $0 from Subject line of outbound e-mails > # - Fixed some typographical errors > # - Removed redundant "-b" option > # > # Version 2.0 > # - Fixed an issue with e-mails formatting incorrectly > # - Added additional space to host column -- Darren-Perot Spruell > # - Replaced GNU date dependency with CHRIS F. A. JOHNSON's > # date2julian shell function. This routine can be found on > # page 170 of Chris's book "Shell Scripting Recipes: A > # Problem-Solution Approach," ISBN #1590594711. Julian function > # was created based on a post to comp.unix.shell by Tapani Tarvainen. > # - Cleaned up function descriptions > # - Removed several lines of redundant code > # - Adjusted the help message > # > # Version 1.1 > # - Added "-c" flag to report expiration status of a PEM encoded > # certificate -- Hampus Lundqvist > # - Updated the prints messages to display the reason a connection > # failed (connection refused, connection timeout, bad cert, etc) > # - Updated the GNU date checking routines > # - Added checks for each binary required > # - Added checks for connection timeouts > # - Added checks for GNU date > # - Added a "-h" option > # - Cleaned up the documentation > # > # Version 1.0 > # Initial Release > # > # Last Updated: 05-06-2008 > # > # Purpose: > # ssl-cert-check checks to see if a digital certificate in X.509 format > # has expired. ssl-cert-check can be run in interactive and batch mode, > # and provides facilities to alarm if a certificate is about to expire. > # > # License: > # Copyright (C) 2007 Ryan Matteson <matty91 at gmail dot com> > # This program is free software; you can redistribute it and/or modify > # it under the terms of the GNU General Public License as published by > # the Free Software Foundation; either version 2 of the License, or > # (at your option) any later version. > # > # This program is distributed in the hope that it will be useful, > # but WITHOUT ANY WARRANTY; without even the implied warranty of > # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > # GNU General Public License for more details. > # > # Requirements: > # Requires openssl > # > # Installation: > # Copy the shell script to a suitable location > # > # Tested platforms: > # -- Solaris 9 using /bin/bash > # -- Solaris 10 using /bin/bash > # -- OS X 10.4.2 using /bin/sh > # -- OpenBSD using /bin/sh > # -- FreeBSD using /bin/sh > # -- Redhat advanced server 3.0MU3 using /bin/sh > # > # Usage: > # Refer to the usage() sub-routine, or invoke ssl-cert-check > # with the "-h" option. > # > # Examples: > # Please refer to the following site for documentation and > # examples: > # http://prefetch.net/articles/checkcertificate.html > # > > PATH=/bin:/usr/bin:/usr/local/bin:/usr/local/ssl/bin:/usr/sfw/bin ; export PATH > > # Who to page when an expired certificate is detected (cmdline: -e) > ADMIN="root" > > # Number of days in the warning threshhold (cmdline: -x) > WARNDAYS=30 > > # If QUIET is set to TRUE, don't print anything on the console (cmdline: -q) > QUIET="FALSE" > > # Don't send E-mail by default (cmdline: -a) > ALARM="FALSE" > > # Don't run as a Nagios plugin by default (cmdline: -n) > NAGIOS="FALSE" > > # NULL out the PKCSDBPASSWD variable for later use (cmdline: -k) > PKCSDBPASSWD="" > > # Location of system binaries > AWK=$(which awk) > DATE=$(which date) > GREP=$(which grep) > OPENSSL=$(which openssl) > PRINTF=$(which printf) > SED=$(which sed) > MKTEMP=$(which mktemp) > > if [ -f /usr/bin/mailx ] > then > MAIL="/usr/bin/mailx" > else > MAIL=$(which mail) > fi > > # Return code used by nagios. Initialize to 0. > RETCODE=0 > > # Set the default umask to be somewhat restrictive > umask 077 > > ############################################################################# > # Purpose: Convert a date from MONTH-DAY-YEAR to Julian format > # Acknowledgements: Code was adapted from examples in the book > # "Shell Scripting Recipes: A Problem-Solution Approach" > # ( ISBN 1590594711 ) > # Arguments: > # $1 -> Month (e.g., 06) > # $2 -> Day (e.g., 08) > # $3 -> Year (e.g., 2006) > ############################################################################# > date2julian() { > > if [ "${1} != "" ] && [ "${2} != "" ] && [ "${3}" != "" ] > then > ## Since leap years add aday at the end of February, > ## calculations are done from 1 March 0000 (a fictional year) > d2j_tmpmonth=$((12 * ${3} + ${1} - 3)) > > ## If it is not yet March, the year is changed to the previous year > d2j_tmpyear=$(( ${d2j_tmpmonth} / 12)) > > ## The number of days from 1 March 0000 is calculated > ## and the number of days from 1 Jan. 4713BC is added > echo $(( (734 * ${d2j_tmpmonth} + 15) / 24 > - 2 * ${d2j_tmpyear} + ${d2j_tmpyear}/4 > - ${d2j_tmpyear}/100 + ${d2j_tmpyear}/400 + $2 + 1721119 )) > else > echo 0 > fi > } > > ############################################################################# > # Purpose: Convert a string month into an integer representation > # Arguments: > # $1 -> Month name (e.g., Sep) > ############################################################################# > getmonth() > { > case ${1} in > Jan) echo 1 ;; > Feb) echo 2 ;; > Mar) echo 3 ;; > Apr) echo 4 ;; > May) echo 5 ;; > Jun) echo 6 ;; > Jul) echo 7 ;; > Aug) echo 8 ;; > Sep) echo 9 ;; > Oct) echo 10 ;; > Nov) echo 11 ;; > Dec) echo 12 ;; > *) echo 0 ;; > esac > } > > ############################################################################# > # Purpose: Calculate the number of seconds between two dates > # Arguments: > # $1 -> Date #1 > # $2 -> Date #2 > ############################################################################# > date_diff() > { > if [ "${1}" != "" ] && [ "${2}" != "" ] > then > echo $((${2} - ${1})) > else > echo 0 > fi > } > > ##################################################################### > # Purpose: Print a line with the expiraton interval > # Arguments: > # $1 -> Hostname > # $2 -> TCP Port > # $3 -> Status of certification (e.g., expired or valid) > # $4 -> Date when certificate will expire > # $5 -> Days left until the certificate will expire > # $6 -> Issuer of the certificate > ##################################################################### > prints() > { > if [ "${QUIET}" != "TRUE" ] && [ "${ISSUER}" = "TRUE" ] && [ "${VALIDATION}" != "TRUE" ] > then > MIN_DATE=$(echo $4 | ${AWK} '{ print $1, $2, $4 }') > ${PRINTF} "%-35s %-17s %-8s %-11s %-4s %-30s\n" "$1:$2" "$6" "$3" "$MIN_DATE" "$5" > > elif [ "${QUIET}" != "TRUE" ] && [ "${ISSUER}" = "TRUE" ] && [ "${VALIDATION}" == "TRUE" ] > then > ${PRINTF} "%-35s %-35s %-32s %-17s\n" "$1:$2" "$7" "$8" "$6" > > elif [ "${QUIET}" != "TRUE" ] && [ "${VALIDATION}" != "TRUE" ] > then > MIN_DATE=$(echo $4 | ${AWK} '{ print $1, $2, $4 }') > ${PRINTF} "%-47s %-12s %-12s %-4s %-30s\n" "$1:$2" "$3" "$MIN_DATE" "$5" > > elif [ "${QUIET}" != "TRUE" ] && [ "${VALIDATION}" == "TRUE" ] > then > ${PRINTF} "%-35s %-35s %-32s\n" "$1:$2" "$7" "$8" > fi > } > > > #################################################### > # Purpose: Print a heading with the relevant columns > # Arguments: > # None > #################################################### > print_heading() > { > if [ "${NOHEADER}" != "TRUE" ] > then > if [ "${QUIET}" != "TRUE" ] && [ "${ISSUER}" = "TRUE" ] && [ "${NAGIOS}" != "TRUE" ] && [ "${VALIDATION}" != "TRUE" ] > then > ${PRINTF} "\n%-35s %-17s %-8s %-11s %-4s\n" "Host" "Issuer" "Status" "Expires" "Days" > echo "----------------------------------- ----------------- -------- ----------- ----" > > elif [ "${QUIET}" != "TRUE" ] && [ "${ISSUER}" = "TRUE" ] && [ "${NAGIOS}" != "TRUE" ] && [ "${VALIDATION}" == "TRUE" ] > then > ${PRINTF} "\n%-35s %-35s %-32s %-17s\n" "Host" "Common Name" "Serial #" "Issuer" > echo "----------------------------------- ----------------------------------- -------------------------------- -----------------" > > elif [ "${QUIET}" != "TRUE" ] && [ "${NAGIOS}" != "TRUE" ] && [ "${VALIDATION}" != "TRUE" ] > then > ${PRINTF} "\n%-47s %-12s %-12s %-4s\n" "Host" "Status" "Expires" "Days" > echo "----------------------------------------------- ------------ ------------ ----" > > elif [ "${QUIET}" != "TRUE" ] && [ "${NAGIOS}" != "TRUE" ] && [ "${VALIDATION}" == "TRUE" ] > then > ${PRINTF} "\n%-35s %-35s %-32s\n" "Host" "Common Name" "Serial #" > echo "----------------------------------- ----------------------------------- --------------------------------" > fi > fi > } > > > ########################################## > # Purpose: Describe how the script works > # Arguments: > # None > ########################################## > usage() > { > echo "Usage: $0 [ -e email address ] [ -x days ] [-q] [-a] [-b] [-h] [-i] [-n] [-v]" > echo " { [ -s common_name ] && [ -p port] } || { [ -f cert_file ] } || { [ -c certificate file ] }" > echo "" > echo " -a : Send a warning message through E-mail" > echo " -b : Will not print header" > echo " -c cert file : Print the expiration date for the PEM or PKCS12 formatted certificate in cert file" > echo " -e E-mail address : E-mail address to send expiration notices" > echo " -f cert file : File with a list of FQDNs and ports" > echo " -h : Print this screen" > echo " -i : Print the issuer of the certificate" > echo " -k password : PKCS12 file password" > echo " -n : Run as a Nagios plugin" > echo " -p port : Port to connect to (interactive mode)" > echo " -s commmon name : Server to connect to (interactive mode)" > echo " -q : Don't print anything on the console" > echo " -v : Only print validation data" > echo " -x days : Certificate expiration interval (eg. if cert_date < days)" > echo "" > } > > > ########################################################################## > # Purpose: Connect to a server ($1) and port ($2) to see if a certificate > # has expired > # Arguments: > # $1 -> Server name > # $2 -> TCP port to connect to > ########################################################################## > check_server_status() { > > if [ "_${2}" = "_smtp" -o "_${2}" = "_25" ] > then > TLSFLAG="-starttls smtp" > > elif [ "_${2}" = "_pop3" -o "_${2}" = "_110" ] > then > TLSFLAG="-starttls pop3" > else > TLSFLAG="" > fi > > echo "" | ${OPENSSL} s_client -connect ${1}:${2} ${TLSFLAG} 2> ${ERROR_TMP} 1> ${CERT_TMP} > > if ${GREP} -i "Connection refused" ${ERROR_TMP} > /dev/null > then > prints ${1} ${2} "Connection refused" "Unknown" > > elif ${GREP} -i "gethostbyname failure" ${ERROR_TMP} > /dev/null > then > prints ${1} ${2} "Cannot resolve domain" "Unknown" > > elif ${GREP} -i "Operation timed out" ${ERROR_TMP} > /dev/null > then > prints ${1} ${2} "Operation timed out" "Unknown" > > elif ${GREP} -i "ssl handshake failure" ${ERROR_TMP} > /dev/null > then > prints ${1} ${2} "SSL handshake failed" "Unknown" > > elif ${GREP} -i "connect: Connection timed out" ${ERROR_TMP} > /dev/null > then > prints ${1} ${2} "Connection timed out" "Unknown" > else > check_file_status ${CERT_TMP} $1 $2 > fi > } > > ##################################################### > ### Check the expiration status of a certificate file > ### Accepts three parameters: > ### $1 -> certificate file to process > ### $2 -> Server name > ### $3 -> Port number of certificate > ##################################################### > check_file_status() { > > CERTFILE=${1} > HOST=${2} > PORT=${3} > > ### Check to make sure the certificate file exists > if [ ! -r ${CERTFILE} ] > then > echo "ERROR: The file named ${CERTFILE} is unreadable or doesn't exist" > RETCODE=1 > return > fi > > ### Grab the expiration date from the X.509 certificate > if [ "${PKCSDBPASSWD}" != "" ] > then > # Extract the certificate from the PKCS#12 database, and > # send the informational message to /dev/null > ${OPENSSL} pkcs12 -nokeys -in ${CERTFILE} \ > -out ${CERT_TMP} -password pass:${PKCSDBPASSWD} 2> /dev/null > > # Extract the expiration date from the certificate > CERTDATE=$(${OPENSSL} x509 -in ${CERT_TMP} -enddate -noout | \ > ${SED} 's/notAfter\=//') > > # Extract the issuer from the certificate > CERTISSUER=$(${OPENSSL} x509 -in ${CERT_TMP} -issuer -noout | \ > ${AWK} 'BEGIN {RS="/" } $0 ~ /^O=/ \ > { print substr($0,3,17)}') > > ### Grab the common name (CN) from the X.509 certificate > COMMONNAME=$(${OPENSSL} x509 -in ${CERT_TMP} -subject -noout | \ > ${SED} -e 's/.*CN=//' | \ > ${SED} -e 's/\/.*//') > > ### Grab the serial number from the X.509 certificate > SERIAL=$(${OPENSSL} x509 -in ${CERT_TMP} -serial -noout | \ > ${SED} -e 's/serial=//') > else > # Extract the expiration date from the ceriticate > CERTDATE=$(${OPENSSL} x509 -in ${CERTFILE} -enddate -noout | \ > ${SED} 's/notAfter\=//') > > # Extract the issuer from the certificate > CERTISSUER=$(${OPENSSL} x509 -in ${CERTFILE} -issuer -noout | \ > ${AWK} 'BEGIN {RS="/" } $0 ~ /^O=/ { print substr($0,3,17)}') > > ### Grab the common name (CN) from the X.509 certificate > COMMONNAME=$(${OPENSSL} x509 -in ${CERTFILE} -subject -noout | \ > ${SED} -e 's/.*CN=//' | \ > ${SED} -e 's/\/.*//') > ### Grab the serial number from the X.509 certificate > SERIAL=$(${OPENSSL} x509 -in ${CERT_TMP} -serial -noout | \ > ${SED} -e 's/serial=//') > fi > > ### Split the result into parameters, and pass the relevant pieces to date2julian > set -- ${CERTDATE} > MONTH=$(getmonth ${1}) > > # Convert the date to seconds, and get the diff between NOW and the expiration date > CERTJULIAN=$(date2julian ${MONTH#0} ${2#0} ${4}) > CERTDIFF=$(date_diff ${NOWJULIAN} ${CERTJULIAN}) > > if [ ${CERTDIFF} -lt 0 ] > then > if [ "${ALARM}" = "TRUE" ] > then > echo "The SSL certificate for ${HOST} \"(CN: ${COMMONNAME})\" has expired!" \ > | ${MAIL} -s "Certificate for ${HOST} \"(CN: ${COMMONNAME})\" has expired!" ${ADMIN} > fi > > prints ${HOST} ${PORT} "Expired" "${CERTDATE}" "${CERTDIFF}" "${CERTISSUER}" "${COMMONNAME}" "${SERIAL}" > RETCODE=2 > > elif [ ${CERTDIFF} -lt ${WARNDAYS} ] > then > if [ "${ALARM}" = "TRUE" ] > then > echo "The SSL certificate for ${HOST} \"(CN: ${COMMONNAME})\" will expire on ${CERTDATE}" \ > | ${MAIL} -s "Certificate for ${HOST} \"(CN: ${COMMONNAME})\" will expire in ${WARNDAYS}-days or less" ${ADMIN} > fi > prints ${HOST} ${PORT} "Expiring" "${CERTDATE}" "${CERTDIFF}" "${CERTISSUER}" "${COMMONNAME}" "${SERIAL}" > RETCODE=1 > > else > prints ${HOST} ${PORT} "Valid" "${CERTDATE}" "${CERTDIFF}" "${CERTISSUER}" "${COMMONNAME}" "${SERIAL}" > RETCODE=0 > fi > } > > ################################# > ### Start of main program > ################################# > while getopts abinve:f:c:hk:p:s:qx: option > do > case "${option}" > in > a) ALARM="TRUE";; > b) NOHEADER="TRUE";; > c) CERTFILE=${OPTARG};; > e) ADMIN=${OPTARG};; > f) SERVERFILE=$OPTARG;; > h) usage > exit 1;; > i) ISSUER="TRUE";; > k) PKCSDBPASSWD=${OPTARG};; > n) NAGIOS="TRUE";; > p) PORT=$OPTARG;; > s) HOST=$OPTARG;; > q) QUIET="TRUE";; > v) VALIDATION="TRUE";; > x) WARNDAYS=$OPTARG;; > \?) usage > exit 1;; > esac > done > > ### Check to make sure a openssl utility is available > if [ ! -f ${OPENSSL} ] > then > echo "ERROR: The openssl binary does not exist in ${OPENSSL}." > echo "FIX: Please modify the \${OPENSSL} variable in the program header." > exit 1 > fi > > ### Check to make sure a date utility is available > if [ ! -f ${DATE} ] > then > echo "ERROR: The date binary does not exist in ${DATE} ." > echo "FIX: Please modify the \${DATE} variable in the program header." > exit 1 > fi > > ### Check to make sure a grep utility is available > if [ ! -f ${GREP} ] > then > echo "ERROR: The grep binary does not exist in ${GREP} ." > echo "FIX: Please modify the \${GREP} variable in the program header." > exit 1 > fi > > ### Check to make sure the mktemp and printf utilities are available > if [ ! -f ${MKTEMP} ] || [ ! -f ${PRINTF} ] > then > echo "ERROR: Unable to locate the mktemp or printf binary." > echo "FIX: Please modify the \${MKTEMP} and \${PRINTF} variables in the program header." > exit 1 > fi > > ### Check to make sure the sed and awk binaries are available > if [ ! -f ${SED} ] || [ ! -f ${AWK} ] > then > echo "ERROR: Unable to locate the sed or awk binary." > echo "FIX: Please modify the \${SED} and \${AWK} variables in the program header." > exit 1 > fi > > ### CHeck to make sure a mail client is available it automated notifcations are requested > if [ "${ALARM}" = "TRUE" ] && [ ! -f ${MAIL} ] > then > echo "ERROR: You enabled automated alerts, but the mail binary could not be found." > echo "FIX: Please modify the ${MAIL} variable in the program header." > exit 1 > fi > > # Place to stash temporary files > CERT_TMP=$($MKTEMP /var/tmp/cert.XXXXXX) > ERROR_TMP=$($MKTEMP /var/tmp/error.XXXXXX) > > ### Baseline the dates so we have something to compare to > MONTH=$(${DATE} "+%m") > DAY=$(${DATE} "+%d") > YEAR=$(${DATE} "+%Y") > NOWJULIAN=$(date2julian ${MONTH#0} ${DAY#0} ${YEAR}) > > ### Touch the files prior to using them > if [ ! -z "${CERT_TMP}" ] && [ ! -z "${ERROR_TMP}" ] > then > touch ${CERT_TMP} ${ERROR_TMP} > else > echo "ERROR: Problem creating temporary files" > echo "FIX: Check that mktemp works on your system" > exit 1 > fi > > ### If a HOST and PORT were passed on the cmdline, use those values > if [ "${HOST}" != "" ] && [ "${PORT}" != "" ] > then > print_heading > check_server_status "${HOST}" "${PORT}" > > ### If a file is passed to the "-f" option on the command line, check > ### each certificate or server / port combination in the file to see if > ### they are about to expire > elif [ -f "${SERVERFILE}" ] > then > print_heading > while read HOST PORT > do > if [ "${HOST:0:1}" = "#" ] > then > : > elif [ "$PORT" = "FILE" ] > then > check_file_status ${HOST} "FILE" "${HOST}" > else > check_server_status "${HOST}" "${PORT}" > fi > > done < ${SERVERFILE} > > ### Check to see if the certificate in CERTFILE is about to expire > elif [ "${CERTFILE}" != "" ] > then > print_heading > check_file_status ${CERTFILE} "FILE" "${CERTFILE}" > > ### There was an error, so print a detailed usage message and exit > else > usage > exit 1 > fi > > ### Remove the temporary files > rm -f ${CERT_TMP} ${ERROR_TMP} > > ### Exit with a success indicator > if [ "${NAGIOS}" = "TRUE" ]; then > exit $RETCODE > else > exit 0 > fi > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Mon-commit mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mon-commit > -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 |
|
From: Augie S. <aug...@gm...> - 2008-11-15 00:58:22
|
I added a unified RAID monitor; it does Linux software RAID, and handles hardware RAID controllers from 3ware and Areca; it should run on the box you want to monitor and you can get at via SNMP easily enough. --Augie On Fri, Nov 14, 2008 at 1:31 PM, Augie Schwer <as...@us...> wrote: > Update of /cvsroot/mon/mon/mon.d > In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv25390 > > Added Files: > raid.monitor > Log Message: > Adding raid.monitor the unified software/hardware RAID monitor. > > --- NEW FILE: raid.monitor --- > #!/usr/bin/perl > > # raid.monitor > # A unified RAID monitor to monitor both software and hardware RAID. > # Works with Linux software RAID, 3ware's tw_cli tool, and Areca's areca_cli tool. > # Augie Schwer <au...@co...> > > use strict; > use warnings; > > my $MDSTAT= '/proc/mdstat'; > my $TWCLI = `which tw_cli 2> /dev/null`; > my $ARCCLI= `which areca_cli 2> /dev/null`; > > chomp $TWCLI; > chomp $ARCCLI; > > my $mdstat = ''; > > # Check for any failed software RAID. > if ( -f $MDSTAT ) > { > $mdstat = `egrep "\[.*_.*\]" $MDSTAT`; > $mdstat = '' if $mdstat =~ 'read_ahead not set'; # Fix for Red Hat 7.3 boxes. > } > if ( $mdstat ) > { > print "Failure of one or more software RAID devices\n"; > exit 1; > } > > # Check for any 3ware RAID failures. > if ( -x $TWCLI ) > { > my %controllers = (); > # Handle multiple controllers. > my @controllers = `$TWCLI info | grep '^c' | awk {'print \$1'}`; > my (@units,@ports); > > # Iterate through controllers and find broken ports and units. > for my $controller (@controllers) > { > chomp $controller; > @{$controllers{$controller}->{'failed_units'}} = `$TWCLI info $controller | grep -v 'NOT-PRESENT' | grep '^u' | awk {'print \$3'} | grep -v 'OK' | grep -v 'VERIFYING'`; > @{$controllers{$controller}->{'failed_ports'}} = `$TWCLI info $controller | grep -v 'NOT-PRESENT' | grep '^p' | awk {'print \$2'} | grep -v 'OK' | grep -v 'VERIFYING'`; > } > > # Display failure and exit with an error if there are any failed ports or units. > for my $controller (@controllers) > { > if ( @{$controllers{$controller}->{'failed_units'}} or @{$controllers{$controller}->{'failed_ports'}} ) > { > print "Failure of one or more of the hardware RAID devices.\n"; > exit 1; > } > } > } > > # Check for any Areca RAID failures. > if ( -x $ARCCLI ) > { > my @failed_raid_sets = `$ARCCLI rsf info | grep 'Raid Set' | grep -v 'Normal'`; > # Display failure and exit with an error if there were any failed Raid Sets. > if ( @failed_raid_sets ) > { > print "Failure of one or more of the hardware RAID devices.\n"; > exit 1; > } > } > > # Otherwise everything was OK. > print "Success\n"; > exit 0; > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mon-commit mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mon-commit > -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 |
|
From: Augie S. <aug...@gm...> - 2008-10-24 22:05:55
|
Added this (ipvs.alert) to the mon-contrib alert directory and created a new "lvs" sub-directory; I also added the ipvs.monitor to the mon-contrib monitor directory and added a new "lvs" sub-directory; seemed fitting. I checked them out and they are pretty straight forward; I'm surprised there weren't any LVS monitors already checked in; I thought for sure that I had seen them some place. --Augie On Fri, Oct 24, 2008 at 2:59 PM, Augie Schwer <as...@us...> wrote: > Update of /cvsroot/mon/mon-contrib/alerts/lvs > In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv29556/alerts/lvs > > Added Files: > ipvs.alert > Log Message: > Added a lvs monitor and alert; contributed by Richard Hartmann <ric...@gm...>. > > --- NEW FILE: ipvs.alert --- > #!/usr/bin/perl > > > # ipvs.alert - Linux Virtual Server alert for mon > # Bring a realserver up or down, or remove the entire virtual server. > # > # Invocation: > # To remove a realserver from a virtual service: > # ipvs.alert -P <protocol> -V <virtual_server:port> -R <real_server:port> > # To add a realserver to an existing virtual service: > # ipvs.alert -u -P <protocol> -V <virtual_server:port> -R <real_server:port> -W <weight> -F <forwarding> > # To remove a virtual service along with any associated realservers: > # ipvs.alert -D -P <protocol> -V <virtual_server:port> > # To create a virtual service with the given realserver: > # ipvs.alert -u -B -P <protocol> -V <virtual_server:port> -S <scheduler> -R <real_server:port> -W <weight> -F <forwarding> > # > # Options: > # -P protocol (tcp|udp) > # -V virtual server > # -R realserver > # -W weight > # -F forwarding type (nat|tun|dr) > # -S scheduler (rr|wrr|lc|wlc|lblc|lblcr|dh|sh|sed|nq) > # -D delete the entire virtual server > # -B rebuild the virtual server > # > # Notes: > # - -u is added automatically when ipvs.alert is part of an > # ``upalert''. You can leave it out or append a dozen, this does not > # matter. > # - You can't build (-B) a virtual service without giving a > # realserver, but you *can* add a realserver without building a > # virtual service. > # - the comments are almost double the volume of the script itself. > # Good, bad or just plain ugly? > # - Since it uses ipvsadm, this script (and therefore Mon) must > # unfortunately run as root :( > > > use Getopt::Std; > > getopts ("uDBs:g:h:t:l:P:V:R:W:F:S:"); > > $ipvsadm = "/sbin/ipvsadm"; > $virtual_service = "$opt_V"; > $realserver = "-r $opt_R"; > $scheduler = "-s $opt_S"; > %proto = ( > "tcp" => "-t", > "udp" => "-u", > ); > %type = ( > "nat" => "-m", > "tun" => "-i", > "dr" => "-g", > ); > > if ($opt_u) { # bring up the realserver > if ($opt_B) { # build the virtual service first > system("$ipvsadm -A $proto{$opt_P} $virtual_service $scheduler"); > } > $weight = "-w $opt_W"; > system("$ipvsadm -a $proto{$opt_P} $virtual_service $realserver $weight $type{$opt_F}"); > } elsif ($opt_D) { # tear down the entire virtual server > system("$ipvsadm -D $proto{$opt_P} $virtual_service"); > } else { # delete the realserver > system("$ipvsadm -d $proto{$opt_P} $virtual_service $realserver"); > }; > > > # # ## ### ##### ######## ############# ##################### > # CHANGELOG > # Mon Jul 12 14:12:49 MYT 2004 > # Initial [messy] version > # Christopher DeMarco <cde...@md...> > # Thu Jul 15 11:02:06 MYT 2004 > # Added -D to delete the entire virtual server > # Bringing up a service also adds the virtual server > # General code overhaul > # Christopher DeMarco <cde...@md...> > # Mon Jul 26 10:09:34 MYT 2004 > # Renamed "lvs" to "ipvs" > # Christopher DeMarco <cde...@md...> > # Wed Oct 1 18:34:27 CEST 2008 > # fixed inline documentation > # fixed whitespace/tab > # Richard Hartmann <ri...@ne...> > > > # # ## ### ##### ######## ############# ##################### > # Copyright (C) 2004, Christopher DeMarco > # Copyright (C) 2008, Richard Hartmann > # > # This program is free software; you can redistribute it and/or > # modify it under the terms of the GNU General Public License as > # published by the Free Software Foundation; either version 2 of the > # License, or (at your option) any later version. > # > # This program is distributed in the hope that it will be useful, > # but WITHOUT ANY WARRANTY; without even the implied warranty of > # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > # General Public License for more details. > # > # You should have received a copy of the GNU General Public License > # along with this program; if not, write to the Free Software > # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA > # 02111-1307 USA > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mon-commit mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mon-commit > -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 |
|
From: Augie S. <aug...@gm...> - 2008-10-23 20:11:32
|
Modified dns-query.monitor to allow for multiple query names: dns-query.monitor -n google.com,yahoo.com,youtube.com ns1.sonic.net ns2.sonic.net for example. I've tested it and now have it in production monitoring and it seems to be working fine. The only caveat would be that too many query names would slow down the whole monitor. --Augie On Thu, Oct 23, 2008 at 1:05 PM, Augie Schwer <as...@us...> wrote: > Update of /cvsroot/mon/mon/mon.d > In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv4081 > > Modified Files: > dns-query.monitor > Log Message: > Accept multiple query names. > > > Index: dns-query.monitor > =================================================================== > RCS file: /cvsroot/mon/mon/mon.d/dns-query.monitor,v > retrieving revision 1.2 > retrieving revision 1.3 > diff -C2 -d -r1.2 -r1.3 > *** dns-query.monitor 7 Feb 2008 22:31:31 -0000 1.2 > --- dns-query.monitor 23 Oct 2008 20:05:42 -0000 1.3 > *************** > *** 5,9 **** > # arguments: > # -t timeout timeout (defaults to 5 seconds) > ! # -n name name to query, defaults to "mailhost" > # -T Use TCP instead of default UDP. > # > --- 5,10 ---- > # arguments: > # -t timeout timeout (defaults to 5 seconds) > ! # -n name[,name] name to query, defaults to "mailhost"; separate > ! # multiple names with a ',' (comma). > # -T Use TCP instead of default UDP. > # > *************** > *** 38,41 **** > --- 39,44 ---- > my $USETCP = $opt{'T'}; > > + my @names = split /,/,$NAME; > + > my $r = Net::DNS::Resolver->new; > > *************** > *** 61,76 **** > $r->nameservers ($server); > > ! my $p = $r->search ($NAME); > ! > ! if (!defined $p) > { > ! $bad{$server}->{"detail"} = $r->errorstring; > ! } > > ! else > ! { > ! my $n = $p->{"answer"}->[0]; > > ! $good{$server}->{"detail"} = "$n->{name} $n->{class} $n->{type} $n->{address}"; > } > } > --- 64,82 ---- > $r->nameservers ($server); > > ! foreach my $name (@names) > { > ! my $p = $r->search ($name); > > ! if (!defined $p) > ! { > ! $bad{$server}->{$name}->{"detail"} = $r->errorstring; > ! } > > ! else > ! { > ! my $n = $p->{"answer"}->[0]; > ! > ! $good{$server}->{$name}->{"detail"} = "$n->{name} $n->{class} $n->{type} $n->{address}"; > ! } > } > } > *************** > *** 89,95 **** > { > print "failures:\n"; > ! foreach my $k (keys %bad) > { > ! print " $k: $bad{$k}->{detail} ($NAME)\n"; > } > > --- 95,104 ---- > { > print "failures:\n"; > ! foreach my $server (keys %bad) > { > ! foreach my $name (keys %{ $bad{$server} }) > ! { > ! print " $server: $bad{$server}->{$name}->{detail} ($name)\n"; > ! } > } > > *************** > *** 101,107 **** > print "successes:\n"; > > ! foreach my $k (keys %good) > { > ! print " $k: successfull lookup for $good{$k}->{detail} ($NAME)\n"; > } > } > --- 110,119 ---- > print "successes:\n"; > > ! foreach my $server (keys %good) > { > ! foreach my $name (keys %{ $good{$server} }) > ! { > ! print " $server: successfull lookup for $good{$server}->{detail} ($name)\n"; > ! } > } > } > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mon-commit mailing list > Mon...@li... > https://lists.sourceforge.net/lists/listinfo/mon-commit > -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 |
|
From: 欧阳锦杰 <sd...@ld...> - 2008-07-29 15:48:37
|
<html> <head> <meta http-equiv="Content-Language" content="zh-cn"> <meta http-equiv="Content-Type" content="text/html; charset=gb2312"> <title>Home</title> </head> <body> <div align="center"> <table border="0" width="500" id="table1"> <tr> <td align="center" bgcolor="#FF0000"> <p style="line-height: 150%"><b> <font face="Verdana" color="#FFFF00" size="2"> <a target="_blank" href="http://hi.baidu.com/exporthats/blog/item/2c4d3afb00f77b8f9e5146e8.html" style="text-decoration: none"> <font color="#FFFF00">Home</font></a></font></b></td> <td align="center" bgcolor="#FF0000"> <p style="line-height: 150%"><b> <font face="Verdana" color="#FFFF00" size="2"> <a target="_blank" href="http://hi.baidu.com/exporthats/blog/item/37b611168fbdb9074a90a7f5.html" style="text-decoration: none"> <font color="#FFFF00">Lady's hats</font></a></font></b></td> <td align="center" bgcolor="#FF0000"> <p style="line-height: 150%"><b> <font face="Verdana" color="#FFFF00" size="2"> <a target="_blank" href="http://hi.baidu.com/exporthats/blog/item/5c4544fa0dd2ab62034f56f5.html" style="text-decoration: none"> <font color="#FFFF00">Men's hats</font></a></font></b></td> <td align="center" bgcolor="#FF0000"> <p style="line-height: 150%"><b> <font face="Verdana" color="#FFFF00" size="2"> <a target="_blank" href="http://hi.baidu.com/exporthats/blog/item/ab09f4f3d5519315b07ec5f6.html" style="text-decoration: none"> <font color="#FFFF00">Other hats</font></a></font></b></td> <td align="center" bgcolor="#FF0000"> <p style="line-height: 150%"><b> <font face="Verdana" color="#FFFF00" size="2"> <a target="_blank" href="http://hi.baidu.com/exporthats/blog/item/9f43c63cb28f3bc19f3d62f6.html" style="text-decoration: none"> <font color="#FFFF00">Contact us</font></a></font></b></td> </tr> <tr> <td colspan="5"><font size="2" face="Verdana">We, Guangzhou Kingdu Hats Co., Ltd., recommend Chinese hand-made hats to you. These hats are exported to the US, Japan, EU. and other parts of the world.<br> <br> Our company is located in Guangzhou, China, which is a developed city of hand-made manufacturing. We can supply low cost & high quality products due to the cheaper hand-made employees.<br> <br> If you have your own brand, logo, artwork or sample that you want to develop and import from us, please send them to us by e-mail attachment or air parcel, we'll do our best to develop the samples including designing them for you.<br> <br> And we promise you that we are the best supplier based on our long-time experience, products of high quality, competitive prices, versatile designs and on-time delivery, and with the principle of, "Customer First". <br> <br> If you wish to form a powerful, long-term business relationship, please do not hesitate to contact us. And we'll reply to your inquiry as soon as possible.<br> <br> <font color="#800080">(Please send your inquiry to the email address on our website. )</font></font><table border="0" width="100%" id="table2" cellspacing="0" cellpadding="0"> <tr> <td align="center"> <img border="0" src="http://photo14.hexun.com/p/2008/0715/224587/b_2B4B2C0ED85E013ED8D61CC852E00F8C.jpg" width="120" height="96"></td> <td align="center"> <img border="0" src="http://photo14.hexun.com/p/2008/0715/224587/b_0A5646F65A47F33B6D8850C972D450BE.jpg" width="120" height="96"></td> <td align="center"> <img border="0" src="http://photo14.hexun.com/p/2008/0715/224588/b_D215234E77328FF035CBF721D04258B5.jpg" width="120" height="96"></td> <td align="center"> <img border="0" src="http://photo14.hexun.com/p/2008/0715/224588/b_0C8C4EC69DAECAC6266EB04061265FE4.jpg" width="120" height="96"></td> </tr> </table> <p align="center" style="line-height: 150%"><b> <font face="Verdana" size="2">Guangzhou Kingdu Hats Co., Ltd.<br> Tel：+86-20-83617056 Fax：+86-20-87279459<br> Add：Room 1908, 320, shataibei Road, GuangZhou City, China 510515</font></b></p> <p align="left"><font face="Verdana" size="2">If you can not refer to the link and the photos above, pls visit this website：<font color="#000080"><b>http://hi.baidu.com/exporthats/blog/item/37b611168fbdb9074a90a7f5.html</b></font></font></td> </tr> </table> </div> <p> </p> </body> </html> |
![http://photo14.hexun.com/p/2008/0715/224587/b_2B4B2C0ED85E013ED8D61CC852E00F8C.jpg"](http://photo14.hexun.com/p/2008/0715/224587/b_2B4B2C0ED85E013ED8D61CC852E00F8C.jpg"){kind=link}
![http://photo14.hexun.com/p/2008/0715/224587/b_0A5646F65A47F33B6D8850C972D450BE.jpg"](http://photo14.hexun.com/p/2008/0715/224587/b_0A5646F65A47F33B6D8850C972D450BE.jpg"){kind=link}
![http://photo14.hexun.com/p/2008/0715/224588/b_D215234E77328FF035CBF721D04258B5.jpg"](http://photo14.hexun.com/p/2008/0715/224588/b_D215234E77328FF035CBF721D04258B5.jpg"){kind=link}
![http://photo14.hexun.com/p/2008/0715/224588/b_0C8C4EC69DAECAC6266EB04061265FE4.jpg"](http://photo14.hexun.com/p/2008/0715/224588/b_0C8C4EC69DAECAC6266EB04061265FE4.jpg"){kind=link}
|
From: Wolfram S. <li...@wo...> - 2008-06-17 10:45:53
|
* Wolfram Schlich <li...@wo...> [2008-06-07 16:26]: > * Wolfram Schlich <li...@wo...> [2008-03-12 15:04]: > > * Jim Trocki <tr...@ar...> [2007-12-03 18:56]: > > > On Fri, 30 Nov 2007, Wolfram Schlich wrote: > > >> I really don't want to bother you, but: any news on this upalertafter bug? > > >> :o) > > > > > > it'll be fixed this week. > > > > Jim, sorry for asking once again, but... when will upalertafter be fixed? > > So, will it be fixed *at all*?! Ok, to sum it up: - mon has not seen a release for 1 year - I reported the severe upalertafter bug 8 months ago - no developer response to my inquiries for 6 months Now that's just enough to finally get rid of mon. FYI, I am now unsubscribing from the mon lists. So long and thanks for all the fish. -- Regards, Wolfram Schlich <wsc...@ge...> Gentoo Linux * http://dev.gentoo.org/~wschlich/ |
|
From: Wolfram S. <li...@wo...> - 2008-06-07 14:25:51
|
* Wolfram Schlich <li...@wo...> [2008-03-12 15:04]: > * Jim Trocki <tr...@ar...> [2007-12-03 18:56]: > > On Fri, 30 Nov 2007, Wolfram Schlich wrote: > >> I really don't want to bother you, but: any news on this upalertafter bug? > >> :o) > > > > it'll be fixed this week. > > Jim, sorry for asking once again, but... when will upalertafter be fixed? So, will it be fixed *at all*?! -- Regards, Wolfram Schlich <wsc...@ge...> Gentoo Linux * http://dev.gentoo.org/~wschlich/ |
|
From: Augie S. <aug...@gm...> - 2008-03-18 23:44:45
|
On Tue, Mar 18, 2008 at 12:22 PM, Chris Hoogendyk <hoo...@bi...> wrote: > at some point I plan to implement a backup server in another department > and have the backups backup each other and the mons mon each other. Then > I could maybe have mon issue a "Good morning, Sysadmins!" with a summary > of things that have been checked and are running alright. It would come > on right before NPR's Morning Edition (in the US -- for other locations, > substitute appropriate national/regional/local morning news). If it > could query the coffee maker as well, then we'd be all set. ;-) You should definitely have a second box monitoring mon; if your main mon box dies and you don't know about it in the middle of the night, then you also won't know about all the other stuff that may have just failed too. -- Augie Schwer - Augie@Schwer.us - http://schwer.us Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072 |
3 messages has been excluded from this view by a project administrator.