linux client disk warning levels

10 messages in this thread

list Kris Springer · Mon, 30 Jan 2017 12:11:10 -0800 ·

I've got some linux clients set up and I'd like to adjust the disk warning levels, but I can't seem to get any custom settings to work. There's settings in the /etc/xymon/localclient.cfg file, but editing the defaults does nothing. In that file it specifies that I need to add --local to the xymonclient.sh command found in the /etc/xymon/cllientlaunch.cfg file, but when I do that the client goes purple. So I looked in the /etc/xymon/localclient.cfg file again and added a HOST= line as well as the custom disk levels I want, but that doesn't change anything. I should also note that I'm restarting the xymon-client service after each change to make sure it's applying it.

Can someone give me a clue as to how to make this seemingly simple adjustment on my client? Or is there a way to define the disk levels in my server's hosts file for this client?

Thanks.
Kris Springer

list Kris Springer · Mon, 30 Jan 2017 13:12:26 -0800 ·

list Scot Kreienkamp · Mon, 30 Jan 2017 21:23:50 +0000 ·

The disk warning levels are adjusted in the server, not the client.  They should go in files in the subfolder $XYMONHOME/analysis.d, which on my server would be /etc/xymon/analysis.d.

Unless it’s a custom written test that executes on the client all adjustments are made on the server.  The client forwards all the information about its status to the server, the server is responsible for parsing the information sent by the client and deciding the status of each test.


Scot Kreienkamp  | Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | | Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid

▸ quoted from Kris Springer

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Kris Springer
Sent: Monday, January 30, 2017 4:12 PM
To: xymon at xymon.com
Subject: [Xymon] linux client disk warning levels

I've got some linux clients set up and I'd like to adjust the disk warning levels, but I can't seem to get any custom settings to work.  There's settings in the /etc/xymon/localclient.cfg file, but editing the defaults does nothing.  In that file it specifies that I need to add --local to the xymonclient.sh command found in the /etc/xymon/cllientlaunch.cfg file, but when I do that the client goes purple.  So I looked in the /etc/xymon/localclient.cfg file again and added a HOST= line as well as the custom disk levels I want, but that doesn't change anything.  I should also note that I'm restarting the xymon-client service after each change to make sure it's applying it.

Can someone give me a clue as to how to make this seemingly simple adjustment on my client?  Or is there a way to define the disk levels in my server's hosts file for this client?

Thanks.
Kris Springer


This message is intended only for the individual or entity to which it is addressed.  It may contain privileged, confidential information which is exempt from disclosure under applicable laws.  If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information.  If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.

list Ralph Mitchell · Mon, 30 Jan 2017 16:24:50 -0500 ·

You would normally put warning levels in the server/etc/analysis.cfg file,
or in individual
 files in server/etc/analysis.d.  The server breaks the [df] section out of
the client report and applies the warning and panic levels to each
partition.

Ralph Mitchell


On Mon, Jan 30, 2017 at 4:12 PM, Kris Springer <user-c2caa0a7a8d5@xymon.invalid>

▸ quoted from Scot Kreienkamp

wrote:

I've got some linux clients set up and I'd like to adjust the disk warning
levels, but I can't seem to get any custom settings to work.  There's
settings in the /etc/xymon/localclient.cfg file, but editing the defaults
does nothing.  In that file it specifies that I need to add --local to the
xymonclient.sh command found in the /etc/xymon/cllientlaunch.cfg file, but
when I do that the client goes purple.  So I looked in the
/etc/xymon/localclient.cfg file again and added a HOST= line as well as the
custom disk levels I want, but that doesn't change anything.  I should also
note that I'm restarting the xymon-client service after each change to make
sure it's applying it.

Can someone give me a clue as to how to make this seemingly simple
adjustment on my client?  Or is there a way to define the disk levels in my
server's hosts file for this client?

Thanks.
Kris Springer

list Kris Springer · Mon, 30 Jan 2017 14:28:35 -0800 ·

Understood about the server doing the deciphering of the client data. Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder. I think I'll just add the custom levels into the analysis.cfg file and see what happens.

Thanks.
Kris Springer

▸ quoted from Ralph Mitchell

On 1/30/2017 1:24 PM, Ralph Mitchell wrote:

You would normally put warning levels in the server/etc/analysis.cfg file, or in individual

files in server/etc/analysis.d. The server breaks the [df] section out of the client report and applies the warning and panic levels to each partition.

Ralph Mitchell

On Mon, Jan 30, 2017 at 4:12 PM, Kris Springer <user-c2caa0a7a8d5@xymon.invalid> wrote:

I've got some linux clients set up and I'd like to adjust the disk warning levels, but I can't seem to get any custom settings to work. There's settings in the /etc/xymon/localclient.cfg file, but editing the defaults does nothing. In that file it specifies that I need to add --local to the xymonclient.sh command found in the /etc/xymon/cllientlaunch.cfg file, but when I do that the client goes purple. So I looked in the /etc/xymon/localclient.cfg file again and added a HOST= line as well as the custom disk levels I want, but that doesn't change anything. I should also note that I'm restarting the xymon-client service after each change to make sure it's applying it.

Can someone give me a clue as to how to make this seemingly simple adjustment on my client? Or is there a way to define the disk levels in my server's hosts file for this client?

Thanks.
Kris Springer

Xymon@xymon.com

list Alessandro Tinivelli · Tue, 31 Jan 2017 07:56:58 +0000 ·

Hi Kris,

believe me, it’s always better to write settings on server side instead of client side.

And, for windows clients, I strongly suggest you to switch to the Zak’s great powershell client, you can get out from svn

"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient  ."

This behaves more like a linux client, and that’s cool

Alessandro

Da: Xymon [mailto:xymon-bounces at xymon.com] Per conto di Kris Springer

▸ quoted from Kris Springer


Understood about the server doing the deciphering of the client data.  Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder.  I think I'll just add the custom levels into the analysis.cfg file and see what happens.

list Richard Hamilton · Tue, 31 Jan 2017 19:26:49 -0500 ·

For those wishing to switch, here's my notes on uninstalling BBWin, since I
didn't find any.  All this assumes one is using the Administrator account,
or at least an account with Administrator privileges.  Also, if you use zip
somewhere else to package up the WinPSClient files, do NOT use cygwin's
unzip to extract them; it will get some Windows permissions wrong, and nssm
(if not more) won't work properly.  Aside from that, I haven't figured out
how to use the svcs test to detect that the XymonPSClient service is
running; maybe I can change it to check for nssm, or have procs check for
nssm.  But otherwise, WinPSClient seems to be working as well or better as
BBWin did on Windows 8, at least on the Windows 10.1 VM on my Mac laptop.

To remove BBWin:

Stop the BBWin service (may be named Big Brother Xymon Client) using the
usual service management GUI.

Remove the service; from command line: sc delete BBWin

Once that's done, some quick regedit searches seem to show no leftovers in
the registry.

Remove the software; from the command line: rd/s "Program Files (x86)\BBWin"


On Tue, Jan 31, 2017 at 2:56 AM, Alessandro Tinivelli <

▸ quoted from Alessandro Tinivelli

user-fdda70e8b835@xymon.invalid> wrote:

Hi Kris,


believe me, it’s always better to write settings on server side instead of
client side.


And, for windows clients, I strongly suggest you to switch to the Zak’s
great powershell client, you can get out from svn


"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient  ."


This behaves more like a linux client, and that’s cool


Alessandro


*Da:* Xymon [mailto:xymon-bounces at xymon.com] *Per conto di *Kris Springer


Understood about the server doing the deciphering of the client data.
Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder.  I think I'll just add the custom
levels into the analysis.cfg file and see what happens.

list Brandon Dale · Wed, 1 Feb 2017 00:45:33 +0000 ·

I would assume it’s just  putting this into the analysis.cfg file for the host you want to monitor:

SVC XymonPSClient status=started startup=automatic

However… not sure that will do anything useful? If the service stops it will never send the data to the xymon server  so the alert would never trigger, not for the status anyway. As long as you have alerting setup for stuff going purple then you should be fine.

Regards,


Brandon

▸ quoted from Richard Hamilton

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Richard Hamilton
Sent: Wednesday, 1 February 2017 11:27 AM
To: Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid>
Cc: xymon at xymon.com
Subject: Re: [Xymon] [EXCH Prio5]R: [EXCH Prio5]Re: linux client disk warning levels

For those wishing to switch, here's my notes on uninstalling BBWin, since I didn't find any.  All this assumes one is using the Administrator account, or at least an account with Administrator privileges.  Also, if you use zip somewhere else to package up the WinPSClient files, do NOT use cygwin's unzip to extract them; it will get some Windows permissions wrong, and nssm (if not more) won't work properly.  Aside from that, I haven't figured out how to use the svcs test to detect that the XymonPSClient service is running; maybe I can change it to check for nssm, or have procs check for nssm.  But otherwise, WinPSClient seems to be working as well or better as BBWin did on Windows 8, at least on the Windows 10.1 VM on my Mac laptop.

To remove BBWin:

Stop the BBWin service (may be named Big Brother Xymon Client) using the
usual service management GUI.

Remove the service; from command line: sc delete BBWin

Once that's done, some quick regedit searches seem to show no leftovers in
the registry.

Remove the software; from the command line: rd/s "Program Files (x86)\BBWin"

On Tue, Jan 31, 2017 at 2:56 AM, Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid<mailto:user-fdda70e8b835@xymon.invalid>> wrote:
Hi Kris,

believe me, it’s always better to write settings on server side instead of client side.

And, for windows clients, I strongly suggest you to switch to the Zak’s great powershell client, you can get out from svn

"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient  ."

This behaves more like a linux client, and that’s cool

Alessandro


Da: Xymon [mailto:xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] Per conto di Kris Springer

▸ quoted from Richard Hamilton


Understood about the server doing the deciphering of the client data.  Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder.  I think I'll just add the custom levels into the analysis.cfg file and see what happens.

list Richard Hamilton · Tue, 31 Jan 2017 20:03:17 -0500 ·

That got it; I didn't have startup=automatic as part of that entry.

Granted it's fairly pointless, but it serves both as a test of that
functionality, and as something so the column is green rather than clear.
:-)  I don't think I have any other extra services of interest on there
(notwithstanding stuff like Google Update Service).


On Tue, Jan 31, 2017 at 7:45 PM, Brandon Dale <user-bf8ff8e1cedb@xymon.invalid>

▸ quoted from Brandon Dale

wrote:

I would assume it’s just  putting this into the analysis.cfg file for the
host you want to monitor:


SVC XymonPSClient status=started startup=automatic


However… not sure that will do anything useful? If the service stops it
will never send the data to the xymon server  so the alert would never
trigger, not for the status anyway. As long as you have alerting setup for
stuff going purple then you should be fine.


Regards,


*Brandon *


*From:* Xymon [mailto:xymon-bounces at xymon.com] *On Behalf Of *Richard
Hamilton
*Sent:* Wednesday, 1 February 2017 11:27 AM
*To:* Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid>
*Cc:* xymon at xymon.com
*Subject:* Re: [Xymon] [EXCH Prio5]R: [EXCH Prio5]Re: linux client disk
warning levels


For those wishing to switch, here's my notes on uninstalling BBWin, since
I didn't find any.  All this assumes one is using the Administrator
account, or at least an account with Administrator privileges.  Also, if
you use zip somewhere else to package up the WinPSClient files, do NOT use
cygwin's unzip to extract them; it will get some Windows permissions wrong,
and nssm (if not more) won't work properly.  Aside from that, I haven't
figured out how to use the svcs test to detect that the XymonPSClient
service is running; maybe I can change it to check for nssm, or have procs
check for nssm.  But otherwise, WinPSClient seems to be working as well or
better as BBWin did on Windows 8, at least on the Windows 10.1 VM on my Mac
laptop.


To remove BBWin:


Stop the BBWin service (may be named Big Brother Xymon Client) using the

usual service management GUI.


Remove the service; from command line: sc delete BBWin


Once that's done, some quick regedit searches seem to show no leftovers in

the registry.


Remove the software; from the command line: rd/s "Program Files
(x86)\BBWin"


On Tue, Jan 31, 2017 at 2:56 AM, Alessandro Tinivelli <
user-fdda70e8b835@xymon.invalid> wrote:

Hi Kris,


believe me, it’s always better to write settings on server side instead of
client side.


And, for windows clients, I strongly suggest you to switch to the Zak’s
great powershell client, you can get out from svn


"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient  ."


This behaves more like a linux client, and that’s cool


Alessandro


*Da:* Xymon [mailto:xymon-bounces at xymon.com] *Per conto di *Kris Springer


Understood about the server doing the deciphering of the client data.
Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder.  I think I'll just add the custom
levels into the analysis.cfg file and see what happens.

list John Rothlisberger · Thu, 2 Feb 2017 14:06:44 +0000 ·

Of course monitoring for the Xymon Client sounds reasonable except for one important part:

-          If it’s not running its not sending statuses back to the server and thus it will never show the client services as anything other than started.

The tests instead will go purple.  ☺

Thanks,
John
Upcoming PTO:
John Rothlisberger
IT Strategy, Infrastructure & Security - Technology Growth Platform
TGP for Business Process Outsourcing
Accenture
XXX.XXX.XXXX office

▸ quoted from Brandon Dale

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Brandon Dale
Sent: Tuesday, January 31, 2017 6:46 PM
To: Richard Hamilton <user-af55987f6d56@xymon.invalid>; Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid>
Cc: xymon at xymon.com
Subject: Re: [Xymon] [EXCH Prio5]R: [EXCH Prio5]Re: linux client disk warning levels

I would assume it’s just  putting this into the analysis.cfg file for the host you want to monitor:

SVC XymonPSClient status=started startup=automatic

However… not sure that will do anything useful? If the service stops it will never send the data to the xymon server  so the alert would never trigger, not for the status anyway. As long as you have alerting setup for stuff going purple then you should be fine.

Regards,

Brandon

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Richard Hamilton
Sent: Wednesday, 1 February 2017 11:27 AM
To: Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid<mailto:user-fdda70e8b835@xymon.invalid>>
Cc: xymon at xymon.com<mailto:xymon at xymon.com>
Subject: Re: [Xymon] [EXCH Prio5]R: [EXCH Prio5]Re: linux client disk warning levels

For those wishing to switch, here's my notes on uninstalling BBWin, since I didn't find any.  All this assumes one is using the Administrator account, or at least an account with Administrator privileges.  Also, if you use zip somewhere else to package up the WinPSClient files, do NOT use cygwin's unzip to extract them; it will get some Windows permissions wrong, and nssm (if not more) won't work properly.  Aside from that, I haven't figured out how to use the svcs test to detect that the XymonPSClient service is running; maybe I can change it to check for nssm, or have procs check for nssm.  But otherwise, WinPSClient seems to be working as well or better as BBWin did on Windows 8, at least on the Windows 10.1 VM on my Mac laptop.

To remove BBWin:

Stop the BBWin service (may be named Big Brother Xymon Client) using the
usual service management GUI.

Remove the service; from command line: sc delete BBWin

Once that's done, some quick regedit searches seem to show no leftovers in
the registry.

Remove the software; from the command line: rd/s "Program Files (x86)\BBWin"

On Tue, Jan 31, 2017 at 2:56 AM, Alessandro Tinivelli <user-fdda70e8b835@xymon.invalid<mailto:user-fdda70e8b835@xymon.invalid>> wrote:
Hi Kris,

believe me, it’s always better to write settings on server side instead of client side.

And, for windows clients, I strongly suggest you to switch to the Zak’s great powershell client, you can get out from svn


"svn checkout http://svn.code.sf.net/p/xymon/code/sandbox/WinPSClient<https://urldefense.proofpoint.com/v2/url?u=http-3A__svn.code.sf.net_p_xymon_code_sandbox_WinPSClient&d=DwMGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=u6KtIBCRNAeN-AbgJjdZe5zZJVFEfq04dnWD-hYNPL_fxJIIFncbL8W6k0NMJtuq&m=2LLVwzjuwWtD2msAwi88xfviUQVcsmgYQxlyCBS0tbQ&s=Q0HJ-IHcGjBIEfh2BvmDsanePlTeIsN0SJD6Qh5cGDs&e=>;  ."

▸ quoted from Richard Hamilton


This behaves more like a linux client, and that’s cool

Alessandro

Da: Xymon [mailto:xymon-bounces at xymon.com<mailto:xymon-bounces at xymon.com>] Per conto di Kris Springer

Understood about the server doing the deciphering of the client data.  Strange that the Windows clients are easily adjusted on the client end.

I don't have an analysis.d folder.  I think I'll just add the custom levels into the analysis.cfg file and see what happens.


Xymon at xymon.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xymon.com_mailman_listinfo_xymon&d=DwMGaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=u6KtIBCRNAeN-AbgJjdZe5zZJVFEfq04dnWD-hYNPL_fxJIIFncbL8W6k0NMJtuq&m=2LLVwzjuwWtD2msAwi88xfviUQVcsmgYQxlyCBS0tbQ&s=e2xeYd84G9RJ68tDzqcyMHRqNHqTYV-DtCdShiC9xUI&e=>;


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

www.accenture.com

linux client disk warning levels 🔗 link

linux client disk warning levels