Hello,
the problem is in debian patch (5.4-2+deb7u2):
--- a/src/collector.c
+++ b/src/collector.c
@@ -64,10 +64,13 @@
*/
static int data_send(Socket_T socket, Mmonit_T C, const char *D) {
char *auth = Util_getBasicAuthHeader(C->url->user, C->url->password);
+MD_T token;
+
argument for "Content-Length:
%d\r\n" ... harmless, but will give wrong content length, so the POST request
will fail
Best regards,
Martin
> On 12 Dec 2016, at 14:06, Martin Pala wrote:
>
> Hello,
>
> the problem is in debian patch (5.4-2+deb7u2):
>
> --
> On 08 Jun 2015, at 11:15, Sergey Kirpichev wrote:
>
> tags 787400 +moreinfo
> thanks
>
> Hello,
>
> On Mon, Jun 1, 2015 at 2:43 PM, Martin Pala wrote:
>> regarding the hostname … please check your monit configuration - if the
>> “check system ” statement
Hello,
please try to upgrade monit … the SSL implementation was refactored in 5.12, it
solved similar problem reported by other user
(https://bitbucket.org/tildeslash/monit/issue/117/failed-to-connect-to-collector).
Latest release is recommended: monit 5.13.
Regards,
Martin
> On 01 Jun 2015
On 05 Mar 2014, at 22:07, Sergey B Kirpichev wrote:
> On Wed, Mar 05, 2014 at 09:34:19PM +0100, Martin Pala wrote:
>> If the process existence is monitored by both Monit and systemd, then it's no
>> problem as long as Monit uses systemd's start/stop methods
>
>
On 05 Mar 2014, at 16:06, Sergey B Kirpichev wrote:
>> The restart of process via Monit (both old and new way) is exactly the same
>> risk as restarting it via systemd.
>
> But what if your system was configured to restart some service *both*
> with monit and systemd (this can be e.g. a defaul
On 05 Mar 2014, at 12:46, Sergey B Kirpichev wrote:
> On Wed, Mar 05, 2014 at 11:35:49AM +0100, Martin Pala wrote:
>> Monit can work in systemd environment fine, you just need to
>> use systemd's start/stop methods as Monit's start/stop program.
>
> Yes, it
On 05 Mar 2014, at 10:02, Adrien CLERC wrote:
>> monit is not about its web gui. It is a system for proactive
>> monitoring, and these features of monit can conflict with
>> systemd's configuration (e.g. Restart=on-failure).
> Yes, I know that monit is really useful with stateless init systems.
Hello,
good point, there is no need to emit warning in this case - we have removed the
warning from the upstream source code, the next release (monit 5.3.2) will be
silent if no include files were found.
Best regards,
Martin
On Dec 20, 2011, at 10:15 AM, Vincent Lefevre wrote:
> Package: mo
Hi,
we we have added support for GNU/kFreeBSD to Monit … it will be part of next
release (monit 5.4). It is necessary to install the libkvm-dev package to
compile Monit on kFreeBSD.
Regards,
Martin
On Sep 26, 2011, at 6:06 PM, Christoph Egger wrote:
> Package: src:monit
> Version: 1:5.3-1
>
Hello,
the patch is attached
Best regards,
Martin
ssl.patch
Description: Binary data
On Apr 6, 2011, at 6:10 AM, Cyril Brulebois wrote:
> Source: monit
> Version: 1:5.2.5-1
> Severity: serious
> Justification: FTBFS
>
> Hi,
>
> your package FTBFS with:
> | gcc -rdynamic alert.o collec
omain Francoise wrote:
> Martin Pala writes:
>
>> Monit sends EHLO first and waits for "250" response ... if it
>> fails or , then it tries HELO. It seems that your mailserver
>> returned some different response.
>
> Here's a network capture (edited for
Hello,
Monit sends EHLO first and waits for "250" response ... if it fails or , then
it tries HELO. It seems that your mailserver returned some different response.
Please can you provide monit log (should contain more details) and network
trace of the communication? Or if your mailserver is ac
The -d option is not necessary if 'set daemon ' is used in
monit configuration file - monit will then start in daemon mode and test
services every x seconds.
For example (test every 180s ... no need for '-d 180' command line option):
set daemon 180
Best regards,
Martin
On Jul 22, 2010, a
Hi,
please run monit in verbose mode (using -v option) and check logs. Did monit
started successfully? Is there any other process listening on port 2812?
Regards,
Martin
On Nov 11, 2009, at 4:17 PM, Fladischer Michael wrote:
> Package: monit
> Version: 1:5.0.3-3
> Severity: normal
>
> Running
Thanks :)
Added to upstream. There were yet two additional gethostbyname()
instances used in ICMP test and Monit's httpd server socket ... i have
replaced them too.
Martin
On Aug 12, 2009, at 7:56 AM, Stefan Alfredsson wrote:
Michael Stapelberg wrote:
This is easily fixed by using getad
Hi,
this error was fixed in upcoming monit-5.0 which will be release ca.
during February-March.
Cheers,
Martin
On Feb 10, 2009, at 10:59 AM, General Stone wrote:
Package: monit
Severity: important
Version: 4.10.1-4
Hi,
Monit says that the event queue is full if "SLOTS" are not defined in
Thanks for report, fixed in monit cvs, will be fixed in next monit
release.
Martin
On Nov 26, 2008, at 12:32 AM, Chris Lawrence wrote:
Package: monit
Version: 1:4.10.1-4
Severity: minor
In the output of 'monit status' for a process, monit refers to the #
of child processes for a daemon as
Georges Toth wrote:
Quoting Martin Pala <[EMAIL PROTECTED]>:
Please can you provide your monit configuration? (the "set httpd ..."
part is sufficient).
set httpd port 28000 and
use address 123.123.123.123
ssl enable
pemfile /etc/ssl/ca_priv_pub.pem
cl
Please can you provide your monit configuration? (the "set httpd ..."
part is sufficient).
Is the certificate self-signed or using public CA?
Thanks,
Martin
Georges Toth wrote:
Package: monit
Version: 1:4.10.1-4
Severity: grave
Justification: renders package unusable
After having upgraded
Note that it's possible to set the path to monitrc using the
--sysconfdir configure option.
If Debian package uses /etc/monit/monitrc by default (which is not in
the hardcoded search path), it could be good to use the --sysconfdir to
set the path properly.
If on the other side the movement t
Thanks for report :)
the problem was fixed in monit cvs and will be part of next monit
release (planned for next week).
Btw. the htpasswd usage is described in monit manual
(http://www.tildeslash.com/monit/doc/manual.php#basic_authentication),
the default is cleartext, but you can set crypt
Hi, thanks for report ... it crashes in the http testing module. Can
you please:
1.) get the snoop/tcpdump of the communication between monit and the
target webserver? (so we can get the request/response which led to
the crash)
2.) send the part of the monit configuration file which speci
Thanks for update :)
The patch fixes the loader, so even common event queue and state or
other file in /var/lib/monit/ directory will work (although i still
recommend to set the event queue to other directory).
Martin
Michal Čihař wrote:
Hi
On Sat, 18 Nov 2006 00:44:23 +0100
Martin Pala
Hi,
the patch which solves the problem is in the attachment (will be part of
next monit release).
Thanks,
Cheers,
Martin
Michal Čihař wrote:
Package: monit
Version: 1:4.8.1-2.1
Severity: important
Hi
I see this problem for more time, but didn't yet find time to report.
Monit segfaults f
... looking on your trace in more detail i was able to reproduce the crash.
You have set the event queue directory and the state file to the same
directory:
set statefile /var/lib/monit/monit.state
set eventqueue basedir /var/lib/monit
This causes the crash, since monit tries to load on s
Hi,
i have tested it but i'm not able to reproduce the problem. Can you send
me your monit configuration and the state file?
Thanks,
Martin
Michal Čihař wrote:
Package: monit
Version: 1:4.8.1-2.1
Severity: important
Hi
I see this problem for more time, but didn't yet find time to report.
wrote:
Hi,
Martin Pala wrote:
there is support for large files (>2GB) in monit cvs already and it will
be part of next monit version.
Would this be easy to backport to 4.8.1 or are there major changes involved?
As we are nearing the next official debian release, I'm hesitant to
in
Hi,
there is support for large files (>2GB) in monit cvs already and it will
be part of next monit version.
Another solution which works even with current monit versions is to
compile it with 64-bit support on platforms which supports it (the large
files then aren't problem).
Martin
Thom
Hi,
monit-4.8.1 was released yesterday ...
Martin
Stefan Alfredsson wrote:
(forwarding for reference. In summary - monit needs to be compiled on
amd64 for the patch to be effective. It fails when started from
initscripts but works with manual start -- I'll await 4.8.1 before doing
further inv
Hi,
this is AMD64 only related bug which is addressed by this patch for
monit-4.8:
http://www.tildeslash.com/monit/dist/monit-4.8-patch01
We will release monit-4.8.1 soon which will contain the fix.
Martin
Neil Broderick wrote:
Package: monit
Version: 1:4.8-1
Severity: grave
Justificatio
Hi,
fixed in monit cvs ... will be part of next monit release (4.8) which
will be ready soon.
Thanks for report,
Martin
root wrote:
Package: monit
Version: 1:4.7-1
Severity: important
Monit's docs state:
-
PID TESTING
monit tests the process id (pid) of processes for change
Hello,
the priority logging support was added to the monit cvs and will be part
of next monit release (4.8) which will be released soon.
Thanks,
Martin
Stefan Alfredsson wrote:
Hello!
Wouter Verhelst said:
I'm attaching a quick-and-dirty patch which applies to monit-4.5 as it
is in sarge
Joerg Jaspert wrote:
Package: monit
Severity: important
Hi
monit has the useful "exec" way to run an application whenever a
condition is there. The only problem is that this does not work for
"if X restarts within X cycles then exec foo"
Hi,
this is not bug, but feature request. This sta
Thanks, you are right :) It is fixed in monit cvs now - will be part of
next monit release.
Cheers,
Martin
Janusz Krzysztofik wrote:
Package: monit
Version: 1:4.5-1
Severity: normal
Tags: patch
I use monit to monitor a pool of my real ntp servers in an lvs cluster.
From time to time a serve
Hi,
thanks for report, it was fixed in current cvs version and will be part
of next monit version.
Martin
Tadas Zelionis wrote:
Package: monit
Version: 1:4.5-1
Severity: normal
exim4 often gives this error, and then smpt check fails:
SMTP protocol violation: synchronization error
36 matches
Mail list logo
