/etc/passwd Monitoring of Solaris Xymon Clients
list Nick Pettefar
Is there an established way of monitoring for /etc/passwd entriy changes/additions on Solaris servers? If not, is it possible to add it as a log to be fetched and then do some processing on the Xymon server? Regards, Nick Pettefar
list Henrik Størner
On Wed, 10 Apr 2013 11:48:51 +0100, Nick Pettefar <user-2027539dd102@xymon.invalid>
▸
wrote:Is there an established way of monitoring for /etc/passwd entriy changes/additions on Solaris servers?
If it is not supposed to change, then you can check an MD5 or SHA1 hash of the file matches. See the "FILE" check in analysis.cfg http://www.xymon.com/xymon/help/manpages/man5/analysis.cfg.5.html#lbAK http://www.xymon.com/xymon/help/manpages/man5/client-local.cfg.5.html#lbAI The "xymondigest" tool can calculate the hash for you, if the system doesn't have a pre-installed MD5/SHA1 hash tool installed. Regards, Henrik
list Mark Deiss
Maybe this is supported(?) or someone has a hack available: Would like to see support for a displayed description field for the hosts.cfg conn declaration for cases where there are multiple IPs. When there are a multiple IPs being tested on a given host, it can be a bit confusing figuring out what a particular failing IP is associated with. Ideally the description would show up in the status report to help identify the IP's purpose. For example in the hosts.cfg file: 1.2.3.1 main-host1 # conn=worst,1.2.4.10 (ILO address), 1.2.5.20 (PA-RISC Console port), 1.2.3.2 (Web Server Business Portal), 1.2.3.3 (Web Server https Business Portal), 1.2.3.4 (Oracle Listener/databases connections)...... In web status page: 1.2.3.1 is alive (1ms) 1.2.4.10 is alive (3 ms) ILO address 1.2.5.20 is alive (3 ms) PA-RISC Console port 1.2.3.2 is alive (1 ms) Web Server Business Portal 1.2.3.3 is unreachable Web Server https Business Portal 1.2.3.4 is alive (1 ms) Oracle Listener/databases connections The secondary IPs can be declared as separate entries in the hosts.cfg but that can lead to display "bloat". Even using the separate entries, there is still no user-friendly detail in the status messages on what is being tested. group-compress <B>Operations</B> 1.2.3.1 main-host1 # conn .... ... Group-compress <B>ILO ports</B> 1.2.4.10 main-host1 # conn .... Group-compress <B>Console ports</B> 1.2.5.20 main-host1 # conn .... Group-compress <B>Web Servers ports</B> 1.2.3.2 main-host1 # conn=worst,1.2.3.3 (so if the .3 address ip is unreachable, you don't know what the business impact is from just looking at the web status display) ....
list Bruce White
Use the COMMENT keyword in your hosts.cfg entry and it will display on the web page. Bruce White Senior Enterprise Systems Engineer | Phone: X-XXX-XXX-XXXX | Fax: XXX-XXX-XXXX | user-58f975e8bf9d@xymon.invalid | http://www.fellowes.com/ Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. -----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Deiss, Mark Sent: Wednesday, April 10, 2013 7:46 AM To: xymon Subject: [Xymon] Feature request: add description in hosts.cfg for conn multiple IP entry
▸
Maybe this is supported(?) or someone has a hack available: Would like
to see support for a displayed description field for the hosts.cfg conn
declaration for cases where there are multiple IPs.
When there are a multiple IPs being tested on a given host, it can be a
bit confusing figuring out what a particular failing IP is associated
with. Ideally the description would show up in the status report to help
identify the IP's purpose.
For example in the hosts.cfg file:
1.2.3.1 main-host1 # conn=worst,1.2.4.10 (ILO address), 1.2.5.20
(PA-RISC Console port), 1.2.3.2 (Web Server Business Portal), 1.2.3.3
(Web Server https Business Portal), 1.2.3.4 (Oracle Listener/databases
connections)......
In web status page:
1.2.3.1 is alive (1ms)
1.2.4.10 is alive (3 ms) ILO address
1.2.5.20 is alive (3 ms) PA-RISC Console port
1.2.3.2 is alive (1 ms) Web Server Business Portal
1.2.3.3 is unreachable Web Server https Business Portal
1.2.3.4 is alive (1 ms) Oracle Listener/databases connections
The secondary IPs can be declared as separate entries in the hosts.cfg
but that can lead to display "bloat". Even using the separate entries,
there is still no user-friendly detail in the status messages on what is
being tested.
group-compress <B>Operations</B>
1.2.3.1 main-host1 # conn ....
...
Group-compress <B>ILO ports</B>
1.2.4.10 main-host1 # conn
....
Group-compress <B>Console ports</B>
1.2.5.20 main-host1 # conn
....
Group-compress <B>Web Servers ports</B>
1.2.3.2 main-host1 # conn=worst,1.2.3.3 (so if the .3 address ip
is unreachable, you don't know what the business impact is from just
looking at the web status display)
....
list Mark Deiss
Thanks I will play around with that. I have already written an external server-side script that I am testing out now.
▸
-----Original Message----- From: White, Bruce [mailto:user-58f975e8bf9d@xymon.invalid] Sent: Wednesday, April 10, 2013 11:49 AM To: Deiss, Mark; xymon Subject: RE: [Xymon] Feature request: add description in hosts.cfg for conn multiple IP entry Use the COMMENT keyword in your hosts.cfg entry and it will display on the web page. Bruce White Senior Enterprise Systems Engineer | Phone: X-XXX-XXX-XXXX | Fax: XXX-XXX-XXXX | user-58f975e8bf9d@xymon.invalid | http://www.fellowes.com/ Disclaimer: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Fellowes, Inc. -----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Deiss, Mark Sent: Wednesday, April 10, 2013 7:46 AM To: xymon Subject: [Xymon] Feature request: add description in hosts.cfg for conn multiple IP entry Maybe this is supported(?) or someone has a hack available: Would like to see support for a displayed description field for the hosts.cfg conn declaration for cases where there are multiple IPs. When there are a multiple IPs being tested on a given host, it can be a bit confusing figuring out what a particular failing IP is associated with. Ideally the description would show up in the status report to help identify the IP's purpose. For example in the hosts.cfg file: 1.2.3.1 main-host1 # conn=worst,1.2.4.10 (ILO address), 1.2.5.20 (PA-RISC Console port), 1.2.3.2 (Web Server Business Portal), 1.2.3.3 (Web Server https Business Portal), 1.2.3.4 (Oracle Listener/databases connections)...... In web status page: 1.2.3.1 is alive (1ms) 1.2.4.10 is alive (3 ms) ILO address 1.2.5.20 is alive (3 ms) PA-RISC Console port 1.2.3.2 is alive (1 ms) Web Server Business Portal 1.2.3.3 is unreachable Web Server https Business Portal 1.2.3.4 is alive (1 ms) Oracle Listener/databases connections The secondary IPs can be declared as separate entries in the hosts.cfg but that can lead to display "bloat". Even using the separate entries, there is still no user-friendly detail in the status messages on what is being tested. group-compress <B>Operations</B> 1.2.3.1 main-host1 # conn .... ... Group-compress <B>ILO ports</B> 1.2.4.10 main-host1 # conn .... Group-compress <B>Console ports</B> 1.2.5.20 main-host1 # conn .... Group-compress <B>Web Servers ports</B> 1.2.3.2 main-host1 # conn=worst,1.2.3.3 (so if the .3 address ip is unreachable, you don't know what the business impact is from just looking at the web status display) ....
list Jeremy Laidman
▸
On 11 April 2013 01:49, White, Bruce <user-58f975e8bf9d@xymon.invalid> wrote:
Use the COMMENT keyword in your hosts.cfg entry and it will display on the web page.
I think that's only per-host, and not per-IP. However, I wonder if the "route:" tag might be used to leverage the COMMENT keyword. You could define the other IP addresses as other hostnames, and then use the route: tag to bind them to the main host. Like so: 1.2.3.1 main-host1 # conn=worst,1.2.4.10,1.2.5.20,1.2.3.2,1.2.3.3,1.2.3.4 route:main-host1-ilo,main-host1-con,main-host1-wsbp,main-host-wshbp,main-host-ora 1.2.4.10 main-host1-ilo # "COMMENT:ILO address" 1.2.5.20 main-host1-con # "COMMENT:PA-RISC Console port" 1.2.3.2 main-host1-wsbp # "COMMENT:Web Server Business Portal" 1.2.3.3 main-host1-wshbp # "COMMENT:Web Server https Business Portal" 1.2.3.4 main-host1-ora # "COMMENT:Oracle Listener/databases" The key result from using the "route:" tag is (from the man page): "The status message will include information about the hosts in the router-list that are down". J