Re: Monit 5.8 dies with segfault in libc

2014-05-08 Thread Martin Pala
Hello,

the problem should be fixed in the development version. You can get the 
development version here:

https://bitbucket.org/tildeslash/monit/get/master.tar.gz

To compile:

1.) ./bootstrap
2.) ./configure
3.) make


Regards,
Martin


On 28 Apr 2014, at 22:50, Jan-Henrik Haukeland  wrote:

> Hello
> 
> Yes we noticed. We are looking into this and will release 5.8.1 as soon as we 
> have a fix. The problem is also mentioned in this issue, 
> https://bitbucket.org/tildeslash/monit/issue/37/segfault-on-ubuntu-12044-with-monit-58
> 
> 
> On 28 Apr 2014, at 21:44, Hans Kowallik  wrote:
> 
>> Greetings!
>> 
>> On our systems - Red Hat Linux 6.5 running on VMware - monit 5.8 dies after 
>> a few hours with a segfault.
>> 
>> In some cases  we get a syslog message:
>> kernel: monit[17399]: segfault at 19 ip 7f31034f078a sp 7fff9bdfaa80 
>> error 4 in libc-2.12.so[7f3103478000+18b000]
>> 
>> Starting monit with -Iv we also got a backtrace,
>> 
>> 
>> 'localhost-logstash_shipper' zombie check succeeded [status_flag=]
>> *** glibc detected *** /usr/bin/monit: double free or corruption (!prev): 
>> 0x0122e540 ***
>> === Backtrace: =
>> /lib64/libc.so.6(+0x76166)[0x7fcafc7f8166]
>> /lib64/libc.so.6(+0x78c93)[0x7fcafc7fac93]
>> /usr/bin/monit[0x41a71c]
>> /usr/bin/monit[0x428d0d]
>> /usr/bin/monit[0x40fd37]
>> /usr/bin/monit[0x410865]
>> /lib64/libc.so.6(__libc_start_main+0xfd)[0x7fcafc7a0d1d]
>> /usr/bin/monit[0x4048ea]
>> === Memory map: 
>> 0040-005aa000 r-xp  fd:00 7180   
>> /usr/bin/monit
>> 006aa000-006b7000 rw-p 001aa000 fd:00 7180   
>> /usr/bin/monit
>> 006b7000-006be000 rw-p  00:00 0
>> 011f5000-0124f000 rw-p  00:00 0  
>> [heap]
>> 7fcaf400-7fcaf402b000 rw-p  00:00 0
>> 7fcaf402b000-7fcaf800 ---p  00:00 0
>> 7fcafb2c4000-7fcafb2da000 r-xp  fd:00 9830   
>> /lib64/libgcc_s-4.4.7-20120601.so.1
>> 7fcafb2da000-7fcafb4d9000 ---p 00016000 fd:00 9830   
>> /lib64/libgcc_s-4.4.7-20120601.so.1
>> 7fcafb4d9000-7fcafb4da000 rw-p 00015000 fd:00 9830   
>> /lib64/libgcc_s-4.4.7-20120601.so.1
>> 7fcafb4da000-7fcafb4db000 ---p  00:00 0
>> 7fcafb4db000-7fcafbedb000 rw-p  00:00 0
>> 7fcafbedb000-7fcafbee r-xp  fd:00 3473   
>> /lib64/libnss_dns-2.12.so
>> 7fcafbee-7fcafc0df000 ---p 5000 fd:00 3473   
>> /lib64/libnss_dns-2.12.so
>> 7fcafc0df000-7fcafc0e r--p 4000 fd:00 3473   
>> /lib64/libnss_dns-2.12.so
>> 7fcafc0df000-7fcafc0e r--p 4000 fd:00 3473   
>> /lib64/libnss_dns-2.12.so
>> 7fcafc0e-7fcafc0e1000 rw-p 5000 fd:00 3473   
>> /lib64/libnss_dns-2.12.so
>> 7fcafc0e1000-7fcafc0ed000 r-xp  fd:00 3848   
>> /lib64/libnss_files-2.12.so
>> 7fcafc0ed000-7fcafc2ed000 ---p c000 fd:00 3848   
>> /lib64/libnss_files-2.12.so
>> 7fcafc2ed000-7fcafc2ee000 r--p c000 fd:00 3848   
>> /lib64/libnss_files-2.12.so
>> 7fcafc2ee000-7fcafc2ef000 rw-p d000 fd:00 3848   
>> /lib64/libnss_files-2.12.so
>> 7fcafc2ef000-7fcafc36 r-xp  fd:00 1632   
>> /lib64/libfreebl3.so
>> 7fcafc36-7fcafc55f000 ---p 00071000 fd:00 1632   
>> /lib64/libfreebl3.so
>> 7fcafc55f000-7fcafc561000 r--p 0007 fd:00 1632   
>> /lib64/libfreebl3.so
>> 7fcafc561000-7fcafc562000 rw-p 00072000 fd:00 1632   
>> /lib64/libfreebl3.so
>> 7fcafc562000-7fcafc566000 rw-p  00:00 0
>> 7fcafc566000-7fcafc57d000 r-xp  fd:00 3920   
>> /lib64/libaudit.so.1.0.0
>> 7fcafc57d000-7fcafc77c000 ---p 00017000 fd:00 3920   
>> /lib64/libaudit.so.1.0.0
>> 7fcafc77c000-7fcafc77d000 r--p 00016000 fd:00 3920   
>> /lib64/libaudit.so.1.0.0
>> 7fcafc77d000-7fcafc782000 rw-p 00017000 fd:00 3920   
>> /lib64/libaudit.so.1.0.0
>> 7fcafc782000-7fcafc90d000 r-xp  fd:00 3459   
>> /lib64/libc-2.12.so
>> 7fcafc90d000-7fcafcb0c000 ---p 0018b000 fd:00 3459   
>> /lib64/libc-2.12.so
>> 7fcafcb0c000-7fcafcb1 r--p 0018a000 fd:00 3459   
>> /lib64/libc-2.12.so
>> 7fcafcb1-7fcafcb11000 rw-p 0018e000 fd:00 3459   
>> /lib64/libc-2.12.so
>> 7fcafcb11000-7fcafcb16000 rw-p  00:00 0
>> 7fcafcb16000-7fcafcb2c000 r-xp  fd:00 3846   
>> /lib64/libnsl-2.12.so
>> 7fcafcb2c000-7fcafcd2b000 ---p 00016000 fd:00 3846   
>> /lib64/libnsl-2.12.so
>> 7fcafcd2b000-7fcafcd2c000 r--p 00015000 fd:00 3846   
>> /lib64/libnsl-2.12.so
>> 7fcafcd2c000-7fcafcd2d000 

Re: How to suppress monit alert if restart is successful?

2014-05-08 Thread Martin Pala
Hi,

you can filter out the "nonexist" event like this:

set alert foo@bar but not on { nonexist }

You will receive all other alert types, including the execution failure.

Regards,
Martin



On 06 May 2014, at 07:28, John Mee  wrote:

> Hi,
> 
> We only want to be alerted if the service fails to restart. Is this possible?
> 
> That is, if on the first check the service is down then restart it but don't 
> bother to send us an alert; if the service is still down two cycles in a row 
> - the restart failed - then we need to know about that so send an alert.
> 
> I tried if not exist for 2 cycles then alert but found that whilst we'd get 
> an alert it would not try to restart.
> 
> Tried it again with the below but same result: it sends an alert without 
> attempting to restart.
> 
> check process mysql with pidfile /var/run/mysqld/mysqld.pid
>start program = "/etc/init.d/mysql start"
>stop program = "/etc/init.d/mysql stop"
>if not exist then restart
>if not exist for 2 cycles then alert
> 
> Can we set it to only send the alert when pain persists?
> 
> 
> Thanks,
> John.
> 
> 
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general


Re: restarting ffmpeg process

2014-05-08 Thread Anthony Griffiths
On Thu, May 8, 2014 at 3:50 AM, Weedy  wrote:

> On Wed, May 7, 2014 at 11:44 AM, Anthony Griffiths wrote:
>
>> thankyou martin I think I've cracked it now (the hard way)
>> monit appeared to be interested only in '/etc/init.d/ start' so
>> I created the script /etc/init.d/stream and the command '/etc/init.d/stream
>> start' worked. I now have monit working and auto-restarting the ffmpeg
>> process when it (often) goes down. Now I just have to tweak it so monit
>> checks the process more than once a minute.
>>
>
> For the love of god stop top posting.
>
> I was half asleep when I wrote my previous email. You syntax is wrong,
> that's probably why it was acting weird.
> Example from my config.
>
>   check process sshd with pidfile /var/run/sshd.pid
> start program "/monit/daemonStart.sh sshd" with timeout 95 seconds
>
> 


I tried your command on another server weedy and it worked, thankyou. (nd I
also got round the problem of gmail top posting)
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Re: Syntax error trying to check program on php script

2014-05-08 Thread Paspao
Hello Martin,

You are right , in this server I have an older version.

Thank you !
P

Il giorno 08/mag/2014, alle ore 17:23, Martin Pala  ha 
scritto:

> Hello,
> 
> what Monit version it is? The "check program" was added in Monit 5.3.
> 
> Regards,
> Martin
> 
> 
> On 08 May 2014, at 16:16, Paspao  wrote:
> 
>> Hello,
>> 
>> I want to monitor a PHP script but I get a Sytax error .
>> 
>> 
>> This is the monit script:
>> 
>> check program test with path "/home/user/test.php"
>> if status != 0 then alert 
>> 
>> I always get 
>> 
>> /etc/monit/monitrc:23: Error: syntax error 'test'
>> 
>> test.php is executable and contains :
>> 
>> #!/usr/bin/php -q
>> > $err=1 ;
>> if($err != 0) exit(1);
>> ?> 
>> 
>> If I run it in shell I get the correct $? of 0 or 1
>> 
>> Anyone knows how to solve this?
>> 
>> Thank you
>> P. 
>> 
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Reaching tildeslash - mmonit issues

2014-05-08 Thread Francisco Reyes

Does anyone know of an alternate way to get in touch with TildeDash?
2 emails to their support address have gone unreplied about an issue 
with mmonit.


Can't find a ticket system for them.

Are mmonit questions/issues allowed in the monit list?

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general


Re: Syntax error trying to check program on php script

2014-05-08 Thread Martin Pala
Hello,

what Monit version it is? The "check program" was added in Monit 5.3.

Regards,
Martin


On 08 May 2014, at 16:16, Paspao  wrote:

> Hello,
> 
> I want to monitor a PHP script but I get a Sytax error .
> 
> 
> This is the monit script:
> 
> check program test with path "/home/user/test.php"
> if status != 0 then alert 
> 
> I always get 
> 
> /etc/monit/monitrc:23: Error: syntax error 'test'
> 
> test.php is executable and contains :
> 
> #!/usr/bin/php -q
>  $err=1 ;
> if($err != 0) exit(1);
> ?> 
> 
> If I run it in shell I get the correct $? of 0 or 1
> 
> Anyone knows how to solve this?
> 
> Thank you
> P. 
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Re: Syntax error trying to check program on php script

2014-05-08 Thread Paspao
Hello Werner,

I tried changing name with no success.

Thank you
P


--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general


Re: Syntax error trying to check program on php script

2014-05-08 Thread Werner Flamme
Paspao [08.05.2014 16:16]:
> Hello,
> 
> I want to monitor a PHP script but I get a Sytax error .
> 
> 
> This is the monit script:
> 
> check program test with path "/home/user/test.php"
> if status != 0 then alert 
> 
> I always get 
> 
> /etc/monit/monitrc:23: Error: syntax error 'test'
> 
[..]
> 
> Anyone knows how to solve this?

Try something like

check program testprog with path "/home/user/test.php"

do not use "test" as the program name!

HTH, Werner


-- 



smime.p7s
Description: S/MIME Cryptographic Signature
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Syntax error trying to check program on php script

2014-05-08 Thread Paspao
Hello,

I want to monitor a PHP script but I get a Sytax error .


This is the monit script:

check program test with path "/home/user/test.php"
if status != 0 then alert 

I always get 

/etc/monit/monitrc:23: Error: syntax error 'test'

test.php is executable and contains :

#!/usr/bin/php -q
 

If I run it in shell I get the correct $? of 0 or 1

Anyone knows how to solve this?

Thank you
P. 

--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

RE: restarting ffmpeg process

2014-05-08 Thread Mehul Ved
?


From: monit-general-bounces+mehul.ved=nexsales@nongnu.org 
 on behalf of Anthony 
Griffiths 
Sent: Thursday, May 08, 2014 3:49 PM
To: This is the general mailing list for monit
Subject: Re: restarting ffmpeg process

> that's gmail doing the top posting, sorry I can't help it because gmail 
> doesn't give you the > option of where your text is placed, it just gives a 
> reply box and that's all, however thankyou > for your further advice which 
> I'm going to try on another server.

It does. There are 3 dots at the bottom, if you click on them, it show you the 
whole text. After which you can reply inline.
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general

Re: restarting ffmpeg process

2014-05-08 Thread Anthony Griffiths
that's gmail doing the top posting, sorry I can't help it because gmail
doesn't give you the option of where your text is placed, it just gives a
reply box and that's all, however thankyou for your further advice which
I'm going to try on another server.


On Thu, May 8, 2014 at 3:50 AM, Weedy  wrote:

> On Wed, May 7, 2014 at 11:44 AM, Anthony Griffiths wrote:
>
>> thankyou martin I think I've cracked it now (the hard way)
>> monit appeared to be interested only in '/etc/init.d/ start' so
>> I created the script /etc/init.d/stream and the command '/etc/init.d/stream
>> start' worked. I now have monit working and auto-restarting the ffmpeg
>> process when it (often) goes down. Now I just have to tweak it so monit
>> checks the process more than once a minute.
>>
>
> For the love of god stop top posting.
>
> I was half asleep when I wrote my previous email. You syntax is wrong,
> that's probably why it was acting weird.
> Example from my config.
>
>   check process sshd with pidfile /var/run/sshd.pid
> start program "/monit/daemonStart.sh sshd" with timeout 95 seconds
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general