Xymon Service alert not showing proper status for stopped service - windows
Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic
Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
Don,
Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David.
Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
Hi David. Thanks for the information. I checked the webpage and it's running 4.3.7
Now, I am also getting similar port errors on the same server that appear to be false alarms. I setup a port 1433 (SQL) monitor and it's also telling me that isn't listening, but I see a port 1433 listens or connections.
red Tue Apr 10 08:00:07 2012 - Ports NOT ok &red local=1433 state=LISTENING : (found 0, req. 1 or more) &green Listen (found 51, req. none)
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:803 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2799 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:139 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1850 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1214 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1483 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4308 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4389 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4937 ESTABLISH
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
From: David Baldwin <david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au>> Date: Tue, 10 Apr 2012 12:22:53 +1000 To: Don Kuhlman <don.kuhlman at schawk.com<mailto:don.kuhlman at schawk.com>> Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don, Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David. Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic
Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au> Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit www.ausport.gov.au<http://www.ausport.gov.au>
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
Try something like LISTEN=%.*:1443, I think Xymon tries to match the entire entry.
Thanks, Larry Barber
On Tue, Apr 10, 2012 at 8:56 AM, Don Kuhlman <Don.Kuhlman at schawk.com> wrote:
Hi David. Thanks for the information. I checked the webpage and it's running 4.3.7
Now, I am also getting similar port errors on the same server that appear to be false alarms. I setup a port 1433 (SQL) monitor and it's also telling me that isn't listening, but I see a port 1433 listens or connections.
red Tue Apr 10 08:00:07 2012 - Ports NOT ok &red local=1433 state=LISTENING : (found 0, req. 1 or more) &green Listen (found 51, req. none)
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:803 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2799 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:139 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1850 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1214 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1483 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4308 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4389 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4937 ESTABLISH
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
From: David Baldwin <david.baldwin at ausport.gov.au> Date: Tue, 10 Apr 2012 12:22:53 +1000 To: Don Kuhlman <don.kuhlman at schawk.com> Cc: Xymon Email List <xymon at xymon.com> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don,
Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David.
Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic
Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Don,
It would help if you could post the relevant sections of your analysis.cfg file as well as the section of the client report.
David.
Hi David. Thanks for the information. I checked the webpage and it's running 4.3.7
Now, I am also getting similar port errors on the same server that appear to be false alarms. I setup a port 1433 (SQL) monitor and it's also telling me that isn't listening, but I see a port 1433 listens or connections.
red Tue Apr 10 08:00:07 2012 - Ports NOT ok &red local=1433 state=LISTENING : (found 0, req. 1 or more) &green Listen (found 51, req. none)
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:803 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2799 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:139 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1850 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1214 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1483 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4308 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4389 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4937 ESTABLISH
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
From: David Baldwin <david.baldwin at ausport.gov.au <mailto:david.baldwin at ausport.gov.au>> Date: Tue, 10 Apr 2012 12:22:53 +1000 To: Don Kuhlman <don.kuhlman at schawk.com <mailto:don.kuhlman at schawk.com>> Cc: Xymon Email List <xymon at xymon.com <mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don,
Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David.
Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit www.ausport.gov.au <http://www.ausport.gov.au>
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Hi folks. Here is the analysis.cfg section for the SQL server:
4/3/12 - Added Port and Service monitoring for SQL and Web
OUR SQL SERVER
HOST=OURHOST GROUP=DBA
SVC ReportServer status=started startup=automaticSVC MSSQLSERVER status=started startup=automatic SVC SQLBrowser status=started startup=automatic SVC SQLSERVERAGENT status=started startup=automatic SVC SQLWriter status=started startup=automatic PORT STATE=LISTENING LOCAL=1433 MIN=1 Test=SQLServer PROC ReportingServicesService.exe 1 1 PROC sqlservr.exe 1 1
Can you clarify where I should grab the section of the client report ? I went to the target agent in Xymon, clicked on the alert that was flashing, then it showed the info as below. Then I went in and clicked on the "Client Detail" link, but that's a very long report. If it's a section of the client detail link, I can grab what you think is relevent, or if it's in another report or link, just let me know.
Thanks!
Don K
From: David Baldwin <david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au>> Date: Thu, 12 Apr 2012 16:54:24 +1000 To: Don Kuhlman <don.kuhlman at schawk.com<mailto:don.kuhlman at schawk.com>> Cc: "xymon at xymon.com<mailto:xymon at xymon.com>" <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don,
It would help if you could post the relevant sections of your analysis.cfg file as well as the section of the client report.
David. Hi David. Thanks for the information. I checked the webpage and it's running 4.3.7
Now, I am also getting similar port errors on the same server that appear to be false alarms. I setup a port 1433 (SQL) monitor and it's also telling me that isn't listening, but I see a port 1433 listens or connections.
red Tue Apr 10 08:00:07 2012 - Ports NOT ok &red local=1433 state=LISTENING : (found 0, req. 1 or more) &green Listen (found 51, req. none)
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:803 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2799 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:139 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1850 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1214 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1483 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4308 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4389 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4937 ESTABLISH
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
From: David Baldwin <david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au>> Date: Tue, 10 Apr 2012 12:22:53 +1000 To: Don Kuhlman <don.kuhlman at schawk.com<mailto:don.kuhlman at schawk.com>> Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don, Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David. Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic
Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au> Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit www.ausport.gov.au<http://www.ausport.gov.au>
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au> Leverrier Street Bruce ACT 2617
Hi folks . I wanted to provide an update on the question I had about port monitoring for SQL servers. I went into the analysis.cfg file and change the entry as follows: It was: PORT STATE=LISTENING LOCAL=1433 MIN=1 Test=SQLServer
I changed it to:PORT STATE=LISTENING LOCAL=%.:$ MIN=1 TEXT=SQLServer Listener and it seems to be working now for the 1433 port. Maybe I had the "LOCAL=1433" syntax wrong for the analysis.
The "Test=SQLServer" was probably the wrong syntax as well – as the "TEXT=SQLServer Listener" is doing what I wanted it to do which is report "SQLServer Listener" in the web page reports.
If I am missing something please let me know, otherwise, I believe this will do the job. So I'm off to learn more xymon stuff :)
Thanks for the support!
Don K
From: David Baldwin <david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au>> Date: Thu, 12 Apr 2012 16:54:24 +1000 To: Don Kuhlman <don.kuhlman at schawk.com<mailto:don.kuhlman at schawk.com>> Cc: "xymon at xymon.com<mailto:xymon at xymon.com>" <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don,
It would help if you could post the relevant sections of your analysis.cfg file as well as the section of the client report.
David. Hi David. Thanks for the information. I checked the webpage and it's running 4.3.7
Now, I am also getting similar port errors on the same server that appear to be false alarms. I setup a port 1433 (SQL) monitor and it's also telling me that isn't listening, but I see a port 1433 listens or connections.
red Tue Apr 10 08:00:07 2012 - Ports NOT ok &red local=1433 state=LISTENING : (found 0, req. 1 or more) &green Listen (found 51, req. none)
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:803 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2799 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:139 0.0.0.0:0 LISTENING
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1850 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1214 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:1483 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4308 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4389 ESTABLISHED
TCP xx.xx.xx.nn:1433 xx.xx.xx.nn:4937 ESTABLISH
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
From: David Baldwin <david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au>> Date: Tue, 10 Apr 2012 12:22:53 +1000 To: Don Kuhlman <don.kuhlman at schawk.com<mailto:don.kuhlman at schawk.com>> Cc: Xymon Email List <xymon at xymon.com<mailto:xymon at xymon.com>> Subject: Re: [Xymon] Xymon Service alert not showing proper status for stopped service - windows
Don, Hi folks. I just received this alert and am trying to figure out why it's showing this way.
It's alerting on a service on a windows sql box - the service that looks stopped is SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER)
but the alert text shows &red SQLSERVERAGENT is started/automatic - want started/automatic
Is this a time delay, or is there something I'm missing that's causing the disconnect ?
Will Xymon try to restart this service or do we manually code something to do that? My goal is to setup specific MYSQL and MS SQL server monitoring on a DB page, but I hope to get a better understanding of how to watch and validate these items.
What version are you running? This was definitely an issue with 4.2.0 and fixed in 4.3.x
David. Thanks
Don K
red Fri Apr 06 13:02:17 2012 - Services NOT ok &green MSSQLSERVER is started/automatic - want started/automatic &green SQLBrowser is started/automatic - want started/automatic &red SQLSERVERAGENT is started/automatic - want started/automatic &green SQLWriter is started/automatic - want started/automatic &green BBWin is started/automatic - want started/automatic
Name StartupType Status DisplayName MSSQLSERVER automatic started SQL Server (MSSQLSERVER) MSSQLServerOLAPService automatic started SQL Server Analysis Services (MSSQLSERVER) SQLBrowser automatic started SQL Server Browser SQLSERVERAGENT automatic stopped SQL Server Agent (MSSQLSERVER) SQLWriter automatic started SQL Server VSS Writer BBWin automatic started Big Brother Xymon Client
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au> Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit www.ausport.gov.au<http://www.ausport.gov.au>
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au<mailto:david.baldwin at ausport.gov.au> Leverrier Street Bruce ACT 2617
On Fri, Apr 13, 2012 at 4:36 AM, Don Kuhlman <Don.Kuhlman at schawk.com> wrote:
It was: PORT STATE=LISTENING LOCAL=1433 MIN=1 Test=SQLServer
I changed it to:PORT STATE=LISTENING LOCAL=%.:$ MIN=1 TEXT=SQLServer Listener and it seems to be working now for the 1433 port. Maybe I had the "LOCAL=1433" syntax wrong for the analysis.
Correct. The man page defines the "LOCAL" parameter as "local address specification in the format used on the output from netstat." So you're trying to match a string in "address:port" format, rather than just a port number.
You could instead have used "0.0.0.0:1433", but the regular expression form (starting with "%") has the advantage of matching both IPv4 and IPv6 sockets. Your status is probably saying "found 2, req. 1 or more" - once for IPv4 and once for IPv6.
J
participants (4)
-
david.baldwin＠ausport.gov.au
-
Don.Kuhlman＠schawk.com
-
jlaidman＠rebel-it.com.au
-
lebarber＠gmail.com