TS - YELLOW problem in history
list Tom Schmitt
I have a problem on a Windows server/PC that shows YELLOW on UP-TIME
using the BBWin server?
The server has been rebooted many times, etc.
The History shows:
Top of Form
Bottom of Form
2009-Dec-18 09:10:41 [netsupport.csw.L-3com.com] - uptime
machine has been up more than 365 days
2040 days 20 hours 2 minutes 46 seconds
Status unchanged in 4 days,3 hours, 37 minutes
Status message received from 128.170.7.16
The XYMON system has only been up for less than a year?
This server also shows in the event log that:
Top of Form
Bottom of Form
2009-Dec-18 09:12:30 [netsupport.csw.L-3com.com]
application: warning - 2009/12/18 09:05:10 - OMCI (1253) - n/a
"Chassis intrusion detected. This typically does NOT indicate a
hardware failure.
1. Contact your Help Desk if you did not personally open your chassis.
2. Enter
System Setup & Set Chassis Intrusion to 'Clear'."
application: warning - 2009/12/18 08:35:10 - OMCI (1253) - n/a
"Chassis intrusion detected. This typically does NOT indicate a
hardware failure.
1. Contact your Help Desk if you did not personally open your chassis.
2. Enter
System Setup & Set Chassis Intrusion to 'Clear'."
EventLog Statistics:
- application
10463 events since 406 days (25.77 events/day)
current size is 4544 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
- internet explorer
error : can't get eventlog file path
0 events since 14596 days (0.00 events/day)
current size is 0 kb (max size is set to 0 kb)
retention is set to : Overwrite events as needed
- security
3467 events since 311 days (11.15 events/day)
current size is 1600 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
- system
24253 events since 255 days (95.11 events/day)
current size is 5120 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
Summary:
- Events Analyzed: 2
- Events Matched: 2
- Events Ignored: 0
Status unchanged in 2 days,0 hours, 2 minutes
Status message received from 128.170.7.16
Can you give me a place to begin correcting this problem.
Thanks,
Tom Schmitt
Senior IT Staff - R&D
Phone (XXX) XXX-XXXX
Cell (XXX) XXX-XXXX
eFax (XXX) XXX-XXXX
user-9c1ae820b621@xymon.invalid
\\\\||////
\ ~ ~ /
| @ @ |
--oOo---(_)---oOo--
list Greg Hubbard
Tom, What problem are you trying to correct? It looks like Xymon is working correctly -- are you asking how to fix the problems that Xymon has reported? The "uptime" problem sounds fishy. Uptime is reported by the Xymon agent, and it believes whatever the operating system tells it, unless there is a parsing problem. Xymon presents alarms for uptime if it is very low (meaning a system has been rebooted) or very high (meaning a system SHOULD be rebooted). The other alarms have been snagged by the agent when it was processing a log. You did not mention what agent you are using -- bbwin? Unix?
▸
On Fri, Dec 18, 2009 at 10:18 AM, <user-9c1ae820b621@xymon.invalid> wrote:
I have a problem on a Windows server/PC that shows YELLOW on UP-TIME using the BBWin server? The server has been rebooted many times, etc. The History shows: Top of Form Bottom of Form
*2009-Dec-18 09:10:41 [netsupport.csw.L-3com.com<http://netsupport.csw.l-3com.com/>;] - uptime* [image: yellow] machine has been up more than 365 days
▸
2040 days 20 hours 2 minutes 46 seconds
Status unchanged in 4 days,3 hours, 37 minutes
Status message received from 128.170.7.16
The XYMON system has only been up for less than a year?
This server also shows in the event log that:
Top of Form
Bottom of Form
*2009-Dec-18 09:12:30 [netsupport.csw.L-3com.com<http://netsupport.csw.l-3com.com/>;] • [image: yellow] application: warning - 2009/12/18 09:05:10 - OMCI (1253) -
▸
n/a
"Chassis intrusion detected. This typically does NOT indicate a hardware
failure.
1. Contact your Help Desk if you did not personally open your chassis. 2.
Enter
System Setup & Set Chassis Intrusion to 'Clear'."
[image: yellow] application: warning - 2009/12/18 08:35:10 - OMCI (1253) -
▸
n/a
"Chassis intrusion detected. This typically does NOT indicate a hardware
failure.
1. Contact your Help Desk if you did not personally open your chassis. 2.
Enter
System Setup & Set Chassis Intrusion to 'Clear'."
EventLog Statistics:
- application
10463 events since 406 days (25.77 events/day)
current size is 4544 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
- internet explorer
error : can't get eventlog file path
0 events since 14596 days (0.00 events/day)
current size is 0 kb (max size is set to 0 kb)
retention is set to : Overwrite events as needed
- security
3467 events since 311 days (11.15 events/day)
current size is 1600 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
- system
24253 events since 255 days (95.11 events/day)
current size is 5120 kb (max size is set to 5120 kb)
retention is set to : Overwrite events as needed
Summary:
- Events Analyzed: 2
- Events Matched: 2
- Events Ignored: 0
Status unchanged in 2 days,0 hours, 2 minutes
Status message received from 128.170.7.16
Can you give me a place to begin correcting this problem.
*Thanks,*
* *
*Tom Schmitt*
*Senior IT Staff - R&D*
Phone (801) *594-3030 *
Cell (XXX) XXX-XXXX
eFax (413) *480-6873*
*user-9c1ae820b621@xymon.invalid*
* **\\\\||////***
* **\ ~ ~ / ***
* **| @ @ | ***
*--oOo---(_)---oOo--***
-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.
list Jerald Sheets
You can also modify this for systems that are ok to be up over a year. For instance, many of my Linux boxes can have over 1000 days uptime, and it is expected of them. The docs suggest a way to make your yellow go away in hobbit-clients.cfg: *UP bootlimit toolonglimit* • * *The cpu status goes yellow if the system has been up for less than "bootlimit" time, or longer than "toolonglimit". The time is in minutes, or you can add h/d/w for hours/days/weeks - eg. "2h" for two hours, or "4w" for 4 weeks.* • * *Defaults: bootlimit=1h, toolonglimit=-1 (infinite). * I hope that helps. --- Jerald M. Sheets jr.
▸
On Fri, Dec 18, 2009 at 11:33 AM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid> wrote:
Tom, What problem are you trying to correct? It looks like Xymon is working correctly -- are you asking how to fix the problems that Xymon has reported? The "uptime" problem sounds fishy. Uptime is reported by the Xymon agent, and it believes whatever the operating system tells it, unless there is a parsing problem. Xymon presents alarms for uptime if it is very low (meaning a system has been rebooted) or very high (meaning a system SHOULD be rebooted). The other alarms have been snagged by the agent when it was processing a log. You did not mention what agent you are using -- bbwin? Unix? On Fri, Dec 18, 2009 at 10:18 AM, <user-9c1ae820b621@xymon.invalid> wrote:I have a problem on a Windows server/PC that shows YELLOW on UP-TIME using the BBWin server? The server has been rebooted many times, etc. The History shows: Top of Form Bottom of Form *2009-Dec-18 09:10:41 [netsupport.csw.L-3com.com<http://netsupport.csw.l-3com.com/>;] - uptime* [image: yellow] machine has been up more than 365 days 2040 days 20 hours 2 minutes 46 seconds Status unchanged in 4 days,3 hours, 37 minutes Status message received from 128.170.7.16 The XYMON system has only been up for less than a year? This server also shows in the event log that: Top of Form Bottom of Form *2009-Dec-18 09:12:30 [netsupport.csw.L-3com.com<http://netsupport.csw.l-3com.com/>;] • [image: yellow] application: warning - 2009/12/18 09:05:10 - OMCI (1253) - n/a "Chassis intrusion detected. This typically does NOT indicate a hardware failure. 1. Contact your Help Desk if you did not personally open your chassis. 2. Enter System Setup & Set Chassis Intrusion to 'Clear'." [image: yellow] application: warning - 2009/12/18 08:35:10 - OMCI (1253) - n/a "Chassis intrusion detected. This typically does NOT indicate a hardware failure. 1. Contact your Help Desk if you did not personally open your chassis. 2. Enter System Setup & Set Chassis Intrusion to 'Clear'." EventLog Statistics: - application 10463 events since 406 days (25.77 events/day) current size is 4544 kb (max size is set to 5120 kb) retention is set to : Overwrite events as needed - internet explorer error : can't get eventlog file path 0 events since 14596 days (0.00 events/day) current size is 0 kb (max size is set to 0 kb) retention is set to : Overwrite events as needed - security 3467 events since 311 days (11.15 events/day) current size is 1600 kb (max size is set to 5120 kb) retention is set to : Overwrite events as needed - system 24253 events since 255 days (95.11 events/day) current size is 5120 kb (max size is set to 5120 kb) retention is set to : Overwrite events as needed Summary: - Events Analyzed: 2 - Events Matched: 2 - Events Ignored: 0 Status unchanged in 2 days,0 hours, 2 minutes Status message received from 128.170.7.16 Can you give me a place to begin correcting this problem. *Thanks,* * * *Tom Schmitt* *Senior IT Staff - R&D* Phone (801) *594-3030 * Cell (XXX) XXX-XXXX eFax (413) *480-6873* *user-9c1ae820b621@xymon.invalid* * **\\\\||////*** * **\ ~ ~ / *** * **| @ @ | *** *--oOo---(_)---oOo--***-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.