[Xymon] How to use xymond_rootlogin.pl (was RE: root login script)

[Morsiani, Massimo]

Hi,

I have changed CMD line as suggested and it works now!

>	ROOT login active
>	red ROOT login detected!
>	root     pts/0        Apr 18 10:22 (<... machine name ...>)

Thank you so much for your support.


Regards.

Massimo Morsiani 
Information Technology Dept. 
------ 
Gilbarco S.r.l. 
via de' Cattani, 220/G 
50145 Firenze, Italy 
tel:    +39-055-30941 
fax:    +39-055-318603 
email:  massimo.morsiani at gilbarco.com 
web:    http://www.gilbarco.it

 Please consider the environment before printing this e-mail



-----Original Message-----
From: cleaver at terabithia.org [mailto:cleaver at terabithia.org] 
Sent: mercoledì 17 aprile 2013 21:12
To: Morsiani, Massimo
Cc: Xymon Email List
Subject: Re: [Xymon] How to use xymond_rootlogin.pl (was RE: root login script)

The xymond_rootlogin.pl script is an example of a server-side external script. It runs on the server at a single point and listens to the incoming "client" stream. When it sees relevant data, it then fires off a "status" command with details about that test.

In this respect, it's identical to how xymond_client works, and an example of munging the raw data coming in in new and creative ways w/o having to modify the client reporter.


>>> [xymond_rootlogin]
>>> ENVFILE /usr/lib/xymon/server/etc/xymonserver.cfg
>>> NEEDS xymond
>>> CMD $XYMONHOME/ext/xymond_rootlogin.pl
>>> LOGFILE $XYMONSERVERLOGS/xymond_rootlogin.log
>>> INTERVAL 1m

Change CMD to
 CMD xymond_channel --channel=client $XYMONHOME/ext/xymond_rootlogin.pl

...and remove the INTERVAL line.


From the perl source, you should start seeing "login" statuses show up as soon as the clients next report in.


HTH,

-jc




> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Actually, what you may be missing is that some external scripts are 
> run on the server, or the machine doing the network tests (they tend 
> to be scripts to test network services remotely). Most external 
> scripts I think, however, run as part of the Xymon client (which is 
> installed per machine). The internal tasks to check the disk space are 
> an example, and any others that require commands to be run on each 
> machine (as I'd guess this one does). It's in the documentation though.
>
> On 04/17/2013 01:51 PM, Novosielski, Ryan wrote:
>> Massimo,
>>
>> I'm unfamiliar with this extension, but all of the extension scripts 
>> I've worked work essentially the same way -- you install the client 
>> and then add them to the client as per the documentation. Rehashing 
>> the documentation is not something I'm planning to do on the mailing 
>> list, but I'm happy to help if you read it and something is unclear.
>>
>> =R
>>
>> On 04/17/2013 12:27 PM, Morsiani, Massimo wrote:
>>> Hi,
>>
>>> I'm trying to run it on Xymon *itself*, but nothing happens...
>>
>>> Henrik could you please explain me how to use your ext? Thanks in 
>>> advance.
>>
>>
>>> Regards.
>>
>>> Massimo Morsiani Information Technology Dept. ------ Gilbarco S.r.l. 
>>> via de' Cattani, 220/G 50145 Firenze, Italy tel:
>>> +39-055-30941 fax:    +39-055-318603 email:
>>> massimo.morsiani at gilbarco.com web:    http://www.gilbarco.it
>>
>>>  Please consider the environment before printing this e-mail
>>
>>
>>
>>> -----Original Message----- From: Novosielski, Ryan 
>>> [mailto:novosirj at umdnj.edu] Sent: mercoledì 17 aprile 2013 14:05
>>>  To: Morsiani, Massimo; 'xymon at xymon.com' Subject: Re: [Xymon] root 
>>> login script
>>
>>> What are you trying to do with this test. Wouldn't it normally be 
>>> run on each client machine you're checking? In any case, my guess is 
>>> another logfile is logging something about it (maybe xymond.log -- I 
>>> forget the names off the top of my head).
>>
>>
>>> ----- Original Message ----- From: Morsiani, Massimo 
>>> [mailto:massimo.morsiani at gilbarco.com] Sent: Wednesday, April 17, 
>>> 2013 08:00 AM To: Novosielski, Ryan; 'xymon at xymon.com'
>>> <xymon at xymon.com> Subject: RE: [Xymon]  root login script
>>
>>> Hi,
>>
>>> I have tried to use "xymond_rootlogin.pl" but w/o any result.
>>
>>> I have copied it in .../xymon/server/ext/ and I have added the 
>>> following to tasks.cfg.
>>
>>> [xymond_rootlogin] ENVFILE
>>> /usr/lib/xymon/server/etc/xymonserver.cfg NEEDS xymond CMD 
>>> $XYMONHOME/ext/xymond_rootlogin.pl LOGFILE 
>>> $XYMONSERVERLOGS/xymond_rootlogin.log INTERVAL 1m
>>
>>> After these actions nothing happens that is no result at all 
>>> (neither new login test, nor xymond_rootlogin.log file).
>>
>>> Where am I wrong? Thanks in advance.
>>
>>
>>> Regards.
>>
>>> Massimo Morsiani Information Technology Dept. ------ Gilbarco S.r.l. 
>>> via de' Cattani, 220/G 50145 Firenze, Italy tel:
>>> +39-055-30941 fax:    +39-055-318603 email:
>>> massimo.morsiani at gilbarco.com web:    http://www.gilbarco.it
>>
>>> ü Please consider the environment before printing this e-mail
>>
>>
>>
>>
>>> -----Original Message----- From: Novosielski, Ryan 
>>> [mailto:novosirj at umdnj.edu] Sent: mercoledì 17 aprile 2013 13:14
>>>  To: Morsiani, Massimo; 'xymon at xymon.com' Subject: Re: [Xymon] root 
>>> login script
>>
>>> I can't imagine it would be much different than any other external 
>>> client script. What is the real question? What have you tried?
>>
>>
>>
>>> ----- Original Message ----- From: Morsiani, Massimo
>>> [mailto:massimo.morsiani at gilbarco.com] Sent: Wednesday, April
>>> 17, 2013 07:09 AM To: 'xymon at xymon.com' <xymon at xymon.com>
>>> Subject: [Xymon]  root login script
>>
>>> Hi all,
>>
>>> is there anyone that is using one script to check if root user
>>> is logged on Unix/Linux machines? Or is there anyone that is
>>> using "xymond_rootlogin.pl" and can explain me how to use it?
>>> Thanks in advance for the support.
>>
>>
>>> Regards.
>>
>>> Massimo Morsiani Information Technology Dept.



Please be advised that this email may contain confidential 
information.  If you are not the intended recipient, please notify us 
by email by replying to the sender and delete this message.  The 
sender disclaims that the content of this email constitutes an offer 
to enter into, or the acceptance of, any agreement; provided that the 
foregoing does not invalidate the binding effect of any digital or 
other electronic reproduction of a manual signature that is included 
in any attachment.