[smokeping-users] probes tcpping : ERROR: TCPPing 'binary' does not point to an executable
    Adrian Sevcenco 
    adrian.sev at gmail.com
       
    Tue Feb 12 17:33:40 CET 2019
    
    
  
Hi! It seems that tcpping is required to be a binary? Or what exactly is 
going on? I have the following :
*** Probes ***
+ FPing
binary = /usr/sbin/fping
blazemode = true
+ TCPPing
binary = /root/bin/tcpping
forks = 1
*** Targets ***
ls -lago /root/bin/tcpping
-rwsr-xr-x. 1 9738 Feb 12 14:39 /root/bin/tcpping
stat /root/bin/tcpping
   File: ‘/root/bin/tcpping’
   Size: 9738            Blocks: 24         IO Block: 4096   regular file
Device: fe01h/65025d    Inode: 2359891     Links: 1
Access: (4755/-rwsr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Context: unconfined_u:object_r:bin_t:s0
i ask if it is binary because i see in
/usr/share/smokeping/Smokeping/probes/TCPPing.pm
sub probevars {
         my $class = shift;
         return $class->_makevars($class->SUPER::probevars, {
                 _mandatory => [ 'binary' ],
                 binary => {
                         _doc => "The location of your tcpping script.",
                         _example => '/usr/bin/tcpping',
                         _sub => sub {
                                 my $val = shift;
                                 return "ERROR: TCPPing 'binary' does 
not point to an executable"
                                         unless -f $val and -x _;
i have the script from https://raw.githubusercontent.com/deajan/tcpping
but i don't think that even the former incarnation of tcpping was binary
...
Does anyone have an idea about this?
Thank you!!
Adrian
    
    
More information about the smokeping-users
mailing list