Xymon Mailing List Archive search

Scheduled maintenances

13 messages in this thread

list Pierre Lardinois · Mon, 31 Jul 2006 09:43:57 +0200 ·
Hello,

Are the "Scheduled actions" stored somewhere in a file or in a list on the
Hobbit server ?  Or is there an other way to list them than via the
enable/disable interface ?

Thanks.

Regards,

Pierre

Pierre Lardinois
Int. ICT Infrastructure Team
TI Automotive
 

The information contained in this transmission may contain privileged and confidential information.  It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
list Henrik Størner · Mon, 31 Jul 2006 11:11:02 +0200 ·
quoted from Pierre Lardinois
On Mon, Jul 31, 2006 at 09:43:57AM +0200, Lardinois, Pierre wrote:
Are the "Scheduled actions" stored somewhere in a file or in a list on the
Hobbit server ?  Or is there an other way to list them than via the
enable/disable interface ?
They should be listed on the enable/disable page, below the already
disabled tests.

You can also list them with 
  bb 127.0.0.1 "schedule"
It looks like

1|1155373200|172.16.10.2|disable client1,hswn,dk.* 240 \nDisabled by: henrik @ 172.16.10.100\nReason: Down for memory upgrade\n

i.e. a job number, time when the job is scheduled to run, where the job
was sent from, and the command that will be sent to Hobbit.


Henrik
list Pierre Lardinois · Mon, 31 Jul 2006 11:37:49 +0200 ·
Hello,

Thanks. I didn't know this command.  Is there somewhere a complete list of
the Hobbit protocol ? 
One question again regarding the scheduled tasks : is there a way to cancel
them without using the enable/disable interface ? 
Thank you for your support.

regards

Pierre
quoted from Henrik Størner

-----Original Message-----
From: user-ce4a2c883f75@xymon.invalid [mailto:user-ce4a2c883f75@xymon.invalid] Sent: lundi 31 juillet 2006 11:11
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Scheduled maintenances

On Mon, Jul 31, 2006 at 09:43:57AM +0200, Lardinois, Pierre wrote:
Are the "Scheduled actions" stored somewhere in a file or in a list on the Hobbit server ?  Or is there an other way to list them than via the enable/disable interface ?
They should be listed on the enable/disable page, below the already disabled
tests.

You can also list them with
  bb 127.0.0.1 "schedule"
It looks like

1|1155373200|172.16.10.2|disable client1,hswn,dk.* 240 \nDisabled by: 1|1155373200|henrik @ 172.16.10.100\nReason: Down for memory upgrade\n
quoted from Pierre Lardinois

i.e. a job number, time when the job is scheduled to run, where the job was
sent from, and the command that will be sent to Hobbit.


Henrik


The information contained in this transmission may contain privileged and confidential information.  It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
list Henrik Størner · Mon, 31 Jul 2006 12:03:56 +0200 ·
quoted from Pierre Lardinois
On Mon, Jul 31, 2006 at 11:37:49AM +0200, Lardinois, Pierre wrote:
Thanks. I didn't know this command.  Is there somewhere a complete list of
the Hobbit protocol ? 
The "bb" man page has most of them, but I noticed this one was not
described. I've added it now.
quoted from Pierre Lardinois
One question again regarding the scheduled tasks : is there a way to cancel
them without using the enable/disable interface ? 
Use the "schedule" command to grab the list of currently scheduled
tasks. In this list, the first item of each line is a job ID. Use this
number in a "schedule cancel JOBID" command; this cancels the scheduled
task.


Regards,
Henrik
list Michael Frey · Mon, 31 Jul 2006 09:24:49 -0400 ·
Henrik,

Last Sunday, July 23rd, at approximately 6:00 AM, almost all of my hosts' 
histfiles were cleared, and lost the 'color' status:

Sun Jul 23 06:06:25 2006  1153649185 888

This has caused the History page to fail.

I am running 4.2-beta-20060605.

I did try the latest version, but that did not make any difference.

All other functionality is present, the history files are just corrupt.

Nothing appears in any log file during this timeframe.

My Hobbit server is Linux, and until now I have been able to correct any 
issues that arose.

Thanks,

Michael Frey


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
list Henrik Størner · Mon, 31 Jul 2006 16:40:57 +0200 ·
Hi Michael,
quoted from Michael Frey

On Mon, Jul 31, 2006 at 09:24:49AM -0400, Michael Frey wrote:
Henrik,

Last Sunday, July 23rd, at approximately 6:00 AM, almost all of my hosts' 
histfiles were cleared, and lost the 'color' status:

Sun Jul 23 06:06:25 2006  1153649185 888

This has caused the History page to fail.
Could you send one of the corrupted files from the data/hist/ directory
to user-ce4a2c883f75@xymon.invalid ? I'd like to see just what this corruption looks
like.

Also, there's a debugging tool included in Hobbit - the lib/availability
utility which is built together with Hobbit, but not installed. Could
you try running this with

   cd hobbit-4.2-beta*/lib
   ./availability ~hobbit/data/hist/myhost.conn 0 `date +%s`


The snippet you've copied above looks like the color text is missing
altogether. That could happen if there's some way that an unknown color
text is passed to the history module ... I'll make sure it doesn't trip
up the history log reporting.


Regards,
Henrik
list Michael Frey · Mon, 31 Jul 2006 10:55:50 -0400 ·
Output Requested:

[root at nbtbigbro1 lib]# ./availability 
~hobbit/data/hist/nbtsanecc2p,nro,glic,com.conn 0 `date +%s` 
2006-07-31 10:50:24 Got entry starting 2869 lasting 1154354555
2006-07-31 10:50:24 Reporting starts with this entry: Sun Jul 23 05:38:50 
2006  1153647530 2869

2006-07-31 10:50:24 Duration for color 0: 0
2006-07-31 10:50:24 Duration for color 1: 0
2006-07-31 10:50:24 Duration for color 2: 0
2006-07-31 10:50:24 Duration for color 3: 0
2006-07-31 10:50:24 Duration for color 4: 0
2006-07-31 10:50:24 Duration for color 5: 0
2006-07-31 10:50:24 Color 0: Count=0, pct=0.00
2006-07-31 10:50:24 Color 1: Count=0, pct=0.00
2006-07-31 10:50:24 Color 2: Count=0, pct=0.00
2006-07-31 10:50:24 Color 3: Count=0, pct=0.00
2006-07-31 10:50:24 Color 4: Count=0, pct=0.00
2006-07-31 10:50:24 Color 5: Count=0, pct=0.00
2006-07-31 10:50:24 Availability: 100.00, color =0
2006-07-31 10:50:24 History file status: OK
You have new mail in /var/spool/mail/root
[root at nbtbigbro1 lib]# 

Contents of hist file:  (color status is missing)

Sun Jul 23 05:38:50 2006  1153647530 2869
Sun Jul 23 06:26:39 2006 green 1153650399 128621
Mon Jul 24 18:10:20 2006 red 1153779020 1138
Mon Jul 24 18:29:18 2006 green 1153780158 60483
Tue Jul 25 11:17:21 2006 red 1153840641 3398
Tue Jul 25 12:13:59 2006 green 1153844039 86990
Wed Jul 26 12:23:49 2006 clear 1153931029 587
Wed Jul 26 12:33:36 2006 green 1153931616 178738
Fri Jul 28 14:12:34 2006 red 1154110354 301
Fri Jul 28 14:17:35 2006 green 1154110655 9162
Fri Jul 28 16:50:17 2006 red 1154119817 254
Fri Jul 28 16:54:31 2006 green 1154120071

File requested:


I have not modified anything, so I am not sure how an unknown color text 
would be passed.

It also all happened at the same time, and not for all hosts or tests, 
although conn seems to be the hardest hit.  Every host I have looked at, 
had at least one Hostory graph failure; except for any new host eneterd 
after July 23rd.

Michael Frey
Intel Senior Systems Engineer
The Guardian Life Insurance Company of America
XXXX Burgess Place, 2-West
Bethlehem, PA XXXXX
E-Mail: user-0d6bef7dd02b@xymon.invalid
Phone: XXX-XXX-XXXX
Fax: XXX-XXX-XXXX


user-ce4a2c883f75@xymon.invalid (Henrik Stoerner) 
07/31/2006 10:40 AM
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid
cc

Subject
Re: [hobbit] hist files
quoted from Henrik Størner


Hi Michael,

On Mon, Jul 31, 2006 at 09:24:49AM -0400, Michael Frey wrote:
Henrik,

Last Sunday, July 23rd, at approximately 6:00 AM, almost all of my 
hosts' 
histfiles were cleared, and lost the 'color' status:

Sun Jul 23 06:06:25 2006  1153649185 888

This has caused the History page to fail.
Could you send one of the corrupted files from the data/hist/ directory
to user-ce4a2c883f75@xymon.invalid ? I'd like to see just what this corruption looks
like.

Also, there's a debugging tool included in Hobbit - the lib/availability
utility which is built together with Hobbit, but not installed. Could
you try running this with

   cd hobbit-4.2-beta*/lib
   ./availability ~hobbit/data/hist/myhost.conn 0 `date +%s`


The snippet you've copied above looks like the color text is missing
altogether. That could happen if there's some way that an unknown color
text is passed to the history module ... I'll make sure it doesn't trip
up the history log reporting.


Regards,
Henrik


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
Attachments (1)
list Henrik Størner · Mon, 31 Jul 2006 17:52:30 +0200 ·
On Mon, Jul 31, 2006 at 10:55:50AM -0400, Michael Frey wrote:

[snip]

ok, the attached patch should let you read the history file again.
It cannot bring back the events that were lost, of course - but at least
you should be able to view the history.
quoted from Michael Frey
It also all happened at the same time, and not for all hosts or tests, 
although conn seems to be the hardest hit.  Every host I have looked at, 
had at least one Hostory graph failure; except for any new host eneterd 
after July 23rd.
I cannot see how that could happen, but just in case the patch modifies
the history module to not log anything that doesn't have a valid color
code.

The time when this happened, would it happen to concide with any
cron-jobs, disk intensive activity, or anything else that might cause
file operations to fail or go slow ?


Regards,
Henrik

-------------- next part --------------
--- lib/availability.c	2006/07/20 16:06:41	1.42
+++ lib/availability.c	2006/07/31 15:28:39
@@ -219,6 +219,44 @@
 	return strdup(cause);
 }
 
+static char *get_historyline(char *buf, int bufsize, FILE *fd, int *err,
+			     char *colstr, unsigned int *start, unsigned int *duration, int *scanres)
+{
+	int ok;
• +	do {
+		ok = 1;
• +		if (fgets(buf, bufsize, fd) == NULL) {
+			return NULL;
+		}
• +		if (strlen(buf) < 25) {
+			ok = 0;
+			*err += 1;
+			dbgprintf("Bad history line (short): %s\n", buf);
+			continue;
+		}
• +		*scanres = sscanf(buf+25, "%s %u %u", colstr, start, duration);
+		if (*scanres < 2) {
+			ok = 0;
+			*err += 1;
+			dbgprintf("Bad history line (missing items): %s\n", buf);
+			continue;
+		}
• +		if (parse_color(colstr) == -1) {
+			ok = 0;
+			*err += 1;
+			dbgprintf("Bad history line (bad color string): %s\n", buf);
+			continue;
+		}
+	} while (!ok);
• +	return buf;
+}
• static int scan_historyfile(FILE *fd, time_t fromtime, time_t totime,
 		char *buf, size_t bufsize, 
 		time_t *starttime, time_t *duration, char *colstr)
@@ -235,9 +273,14 @@
 
 	/* Is start of history after our report-end time ? */
 	rewind(fd);
-	fgets(buf, bufsize, fd);
-	if (sscanf(buf+25, "%s %u %u", colstr, &uistart, &uidur) == 2) 
-		uidur = time(NULL)-uistart;
+	if (!get_historyline(buf, bufsize, fd, &err, colstr, &uistart, &uidur, &scanres)) {
+		*starttime = time(NULL);
+		*duration = 0;
+		strcpy(colstr, "clear");
+		return err;
+	}
• +	if (scanres == 2) uidur = time(NULL)-uistart;
 	start = uistart; dur = uidur;
 
 	if (start > totime) {
@@ -249,8 +292,7 @@
 
 	/* First, do a quick scan through the file to find the approximate position where we should start */
 	while ((start+dur) < fromtime) {
-		if (fgets(buf, bufsize, fd)) {
-			scanres = sscanf(buf+25, "%s %u %u", colstr, &uistart, &uidur);
+		if (get_historyline(buf, bufsize, fd, &err, colstr, &uistart, &uidur, &scanres)) {
 			start = uistart; dur = uidur;
 			if (scanres == 2) dur = time(NULL) - start;
 
@@ -262,11 +304,6 @@
 					fgets(buf, bufsize, fd); /* Skip partial line */
 				}
 			}
-			else {
-				err++;
-				dbgprintf("Bad line in history file '%s'\n", buf);
-				start = dur = 0; /* Try next line */
-			}
 		}
 		else {
 			start = time(NULL);
@@ -284,19 +321,11 @@
 
 	/* Read one line at a time until we hit start of our report period */
 	do {
-		if (fgets(buf, bufsize, fd)) {
-			scanres = sscanf(buf+25, "%s %u %u", colstr, &uistart, &uidur);
+		if (get_historyline(buf, bufsize, fd, &err, colstr, &uistart, &uidur, &scanres)) {
 			start = uistart; dur = uidur;
 			if (scanres == 2) dur = time(NULL) - start;
 
-			if (scanres < 2) {
-				err++;
-				dbgprintf("Bad line in history file '%s'\n", buf);
-				start = dur = 0; /* Try next line */
-			}
-			else {
-				dbgprintf("Got entry starting %lu lasting %lu\n", start, dur);
-			}
+			dbgprintf("Got entry starting %lu lasting %lu\n", start, dur);
 		}
 		else {
 			start = time(NULL);
@@ -350,7 +379,7 @@
 	unsigned int uistart, uidur;
 	char colstr[MAX_LINE_LEN];
 	int color, done, i, scanres;
-	int fileerrors;
+	int fileerrors = 0;
 
 	repinfo->fstate = "OK";
 	repinfo->withreport = 0;
@@ -377,11 +406,15 @@
 	}
 	else {
 		/* Already positioned (probably in a pipe) */
-		fgets(l, sizeof(l), fd);
-		scanres = sscanf(l+25, "%s %u %u", colstr, &uistart, &uidur);
-		starttime = uistart; duration = uidur;
-		if (scanres == 2) duration = time(NULL) - starttime;
-		fileerrors = 0;
+		if (get_historyline(l, sizeof(l), fd, &fileerrors, colstr, &uistart, &uidur, &scanres)) {
+			starttime = uistart; duration = uidur;
+			if (scanres == 2) duration = time(NULL) - starttime;
+		}
+		else {
+			starttime = time(NULL); duration = 0;
+			strcpy(colstr, "clear");
+			fileerrors = 1;
+		}
 	}
 
 	if (starttime > totime) {
@@ -437,8 +470,7 @@
 		}
 
 		if ((starttime + duration) < totime) {
-			if (fgets(l, sizeof(l), fd)) {
-				scanres = sscanf(l+25, "%s %u %u", colstr, &uistart, &uidur);
+			if (get_historyline(l, sizeof(l), fd, &fileerrors, colstr, &uistart, &uidur, &scanres)) {
 				starttime = uistart; duration = uidur;
 				if (scanres == 2) duration = time(NULL) - starttime;
 			}
--- hobbitd/hobbitd_history.c	2006/05/25 21:04:44	1.46
+++ hobbitd/hobbitd_history.c	2006/07/31 15:44:15
@@ -167,6 +167,11 @@
 			downtimeactive = (atoi(items[12]) > 0);
 			clienttstamp = atoi(items[13]);
 
+			if (newcolor == -1) {
+				errprintf("Bad message: newcolor is unknown '%s'\n", items[7]);
+				continue;
+			}
• p = hostnamecommas = strdup(hostname); while ((p = strchr(p, '.')) != NULL) *p = ',';
 
 			if (save_statusevents) {
@@ -224,7 +229,8 @@
 							/* Sun Oct 10 06:49:42 2004 red   1097383782 602 */
 
 							if ((strlen(l) > 24) && 
-							    (sscanf(l+24, " %s %d %d", oldcol, &lastchg_i, &dur_i) == 2)) {
+							    (sscanf(l+24, " %s %d %d", oldcol, &lastchg_i, &dur_i) == 2) &&
+							    (parse_color(oldcol) != -1)) {
 								/* 
 								 * Record the start location of the line
 								 */
@@ -262,7 +268,11 @@
 					 * Logfile does not exist.
 					 */
 					lastchg = tstamp;
-					statuslogfd = fopen(statuslogfn, "w");
+					statuslogfd = fopen(statuslogfn, "a");
+					if (statuslogfd == NULL) {
+						errprintf("Cannot open status historyfile '%s' : %s\n", 
+							statuslogfn, strerror(errno));
+					}
 				}
 
 				if (strcmp(oldcol, colorname(newcolor)) == 0) {
@@ -300,10 +310,6 @@
 
 					fclose(statuslogfd);
 				}
-				else {
-					errprintf("Cannot open status historyfile '%s' : %s\n", 
-						statuslogfn, strerror(errno));
-				}
 
 				MEMUNDEFINE(statuslogfn);
 				MEMUNDEFINE(oldcol);
list Michael Frey · Mon, 31 Jul 2006 13:38:20 -0400 ·
The following error occured while attempting to apply the patch:

[hobbit at nbtbigbro1 hobbit-4.2-beta-20060605]$ patch -p0 
<history-missing.patch 
(Stripping trailing CRs from patch.)
patching file lib/availability.c
Hunk #4 FAILED at 304.
Hunk #5 FAILED at 321.
2 out of 8 hunks FAILED -- saving rejects to file lib/availability.c.rej
(Stripping trailing CRs from patch.)
patching file hobbitd/hobbitd_history.c

cannot find file 'lib/availability.c.rej'

I can find no corelation of events to anything near the timeframe this 
happened.  Our environment was patched at 3 AM, and this all occured at 
5:30AM.

The Hobbit server is Linux, so it did not receive any patches.

Others said the Hobbit page was 'going crazy', and a supervisor reset the 
Hobbit server.  (the Hobbit server is a VMware virtual server, and 
resetting was the easy solution)

I have no details on what 'going crazy' means, no one is helpful.

Michael Frey


user-ce4a2c883f75@xymon.invalid (Henrik Stoerner) 
07/31/2006 11:52 AM
signature
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid
cc

Subject
Re: [hobbit] hist files


quoted from Michael Frey
On Mon, Jul 31, 2006 at 10:55:50AM -0400, Michael Frey wrote:

[snip]

ok, the attached patch should let you read the history file again.
It cannot bring back the events that were lost, of course - but at least
you should be able to view the history.
It also all happened at the same time, and not for all hosts or tests, 
although conn seems to be the hardest hit.  Every host I have looked at, 
had at least one Hostory graph failure; except for any new host eneterd 
after July 23rd.
I cannot see how that could happen, but just in case the patch modifies
the history module to not log anything that doesn't have a valid color
code.

The time when this happened, would it happen to concide with any
cron-jobs, disk intensive activity, or anything else that might cause
file operations to fail or go slow ?


Regards,
Henrik


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
Attachments (1)
list Michael Frey · Mon, 31 Jul 2006 17:06:17 -0400 ·
Could the error be caused by something inside of the patch?

Michael Frey


Michael Frey <user-0d6bef7dd02b@xymon.invalid> 07/31/2006 01:38 PM
quoted from Michael Frey
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid
cc

Subject
Re: [hobbit] hist files


The following error occured while attempting to apply the patch: 
[hobbit at nbtbigbro1 hobbit-4.2-beta-20060605]$ patch -p0 <history-missing.patch (Stripping trailing CRs from patch.) patching file lib/availability.c Hunk #4 FAILED at 304. Hunk #5 FAILED at 321. 2 out of 8 hunks FAILED -- saving rejects to file lib/availability.c.rej (Stripping trailing CRs from patch.) patching file hobbitd/hobbitd_history.c 
cannot find file 'lib/availability.c.rej' 
I can find no corelation of events to anything near the timeframe this happened.  Our environment was patched at 3 AM, and this all occured at 5:30AM. 
The Hobbit server is Linux, so it did not receive any patches. 
Others said the Hobbit page was 'going crazy', and a supervisor reset the Hobbit server.  (the Hobbit server is a VMware virtual server, and resetting was the easy solution) 
I have no details on what 'going crazy' means, no one is helpful.

Michael Frey


user-ce4a2c883f75@xymon.invalid (Henrik Stoerner) 07/31/2006 11:52 AM 
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid cc

Subject
Re: [hobbit] hist files


On Mon, Jul 31, 2006 at 10:55:50AM -0400, Michael Frey wrote:

[snip]

ok, the attached patch should let you read the history file again.
It cannot bring back the events that were lost, of course - but at least
you should be able to view the history.
It also all happened at the same time, and not for all hosts or tests, although conn seems to be the hardest hit.  Every host I have looked at, 
had at least one Hostory graph failure; except for any new host eneterd after July 23rd.
I cannot see how that could happen, but just in case the patch modifies
the history module to not log anything that doesn't have a valid color
code.

The time when this happened, would it happen to concide with any
cron-jobs, disk intensive activity, or anything else that might cause
file operations to fail or go slow ?


Regards,
Henrik


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited. If you have received this message in error, please
notify the sender immediately by return e-mail and delete the

message and any attachments. Thank you.To unsubscribe from the hobbit list, send an e-mail to
user-095ef1c764a2@xymon.invalid
list Henrik Størner · Tue, 1 Aug 2006 13:12:12 +0200 ·
quoted from Michael Frey
On Mon, Jul 31, 2006 at 01:38:20PM -0400, Michael Frey wrote:
The following error occured while attempting to apply the patch:

[hobbit at nbtbigbro1 hobbit-4.2-beta-20060605]$ patch -p0 
<history-missing.patch 
(Stripping trailing CRs from patch.)
patching file lib/availability.c
Hunk #4 FAILED at 304.
Hunk #5 FAILED at 321.
2 out of 8 hunks FAILED -- saving rejects to file lib/availability.c.rej
Oh, this patch was against the current release-candidate source.

I'd recommend grabbing the current snapshot and building that. If you
prefer, just copy the web/bb-hist.cgi and hobbitd/hobbitd_history
binaries over to your current ~hobbit/server/bin/ directory.


Regards,
Henrik
list Michael Frey · Tue, 1 Aug 2006 09:41:36 -0400 ·
I am unable to install 4.2-RC-20060712:

util.c:153: redefinition of `host_exists'
util.c:148: `host_exists' previously defined here
make[1]: *** [util.o] Error 1
make[1]: Leaving directory 
`/usr/local/hobbit/hobbit-4.2-rc/hobbit-4.2-RC-20060712/bbdisplay'
make: *** [bbdisplay-build] Error 2
[root at nbtbigbro1 hobbit-4.2-RC-20060712]# 

Michael Frey


user-ce4a2c883f75@xymon.invalid (Henrik Stoerner) 
08/01/2006 07:12 AM
signature
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid
cc

Subject
Re: [hobbit] hist files


quoted from Michael Frey
On Mon, Jul 31, 2006 at 01:38:20PM -0400, Michael Frey wrote:
The following error occured while attempting to apply the patch:

[hobbit at nbtbigbro1 hobbit-4.2-beta-20060605]$ patch -p0 
<history-missing.patch 
(Stripping trailing CRs from patch.)
patching file lib/availability.c
Hunk #4 FAILED at 304.
Hunk #5 FAILED at 321.
2 out of 8 hunks FAILED -- saving rejects to file lib/availability.c.rej
Oh, this patch was against the current release-candidate source.

I'd recommend grabbing the current snapshot and building that. If you
prefer, just copy the web/bb-hist.cgi and hobbitd/hobbitd_history
binaries over to your current ~hobbit/server/bin/ directory.


Regards,
Henrik


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law.  If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited.  If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments.  Thank you.
list Michael Frey · Tue, 1 Aug 2006 09:55:52 -0400 ·
Applied todays snapshot, and everything looks to back to normal with the 
history graphs.

Thanks Henrik,

Michael Frey


Michael Frey <user-0d6bef7dd02b@xymon.invalid> 
08/01/2006 09:41 AM
quoted from Michael Frey
Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid
cc

Subject
Re: [hobbit] hist files


I am unable to install 4.2-RC-20060712: 

util.c:153: redefinition of `host_exists' 
util.c:148: `host_exists' previously defined here 
make[1]: *** [util.o] Error 1 
make[1]: Leaving directory 
`/usr/local/hobbit/hobbit-4.2-rc/hobbit-4.2-RC-20060712/bbdisplay' 
make: *** [bbdisplay-build] Error 2 
[root at nbtbigbro1 hobbit-4.2-RC-20060712]# 

Michael Frey


user-ce4a2c883f75@xymon.invalid (Henrik Stoerner) 
08/01/2006 07:12 AM 

Please respond to
user-ae9b8668bcde@xymon.invalid


To
user-ae9b8668bcde@xymon.invalid 
cc

Subject
Re: [hobbit] hist files


On Mon, Jul 31, 2006 at 01:38:20PM -0400, Michael Frey wrote:
The following error occured while attempting to apply the patch:

[hobbit at nbtbigbro1 hobbit-4.2-beta-20060605]$ patch -p0 
<history-missing.patch 
(Stripping trailing CRs from patch.)
patching file lib/availability.c
Hunk #4 FAILED at 304.
Hunk #5 FAILED at 321.
2 out of 8 hunks FAILED -- saving rejects to file lib/availability.c.rej
Oh, this patch was against the current release-candidate source.

I'd recommend grabbing the current snapshot and building that. If you
prefer, just copy the web/bb-hist.cgi and hobbitd/hobbitd_history
binaries over to your current ~hobbit/server/bin/ directory.


Regards,
Henrik


This message, and any attachments to it, may contain information
that is privileged, confidential, and exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited. If you have received this message in error, please
notify the sender immediately by return e-mail and delete the
message and any attachments. Thank you.