On Mon, Dec 12, 2016 at 04:23:57PM +0100, Arthur Hoffmann wrote:
> It looks like this bug is fixed,
> I did "dpkg -i monit_5.4-2+deb7u3_amd64.deb", monit restarted and is
> running
> now.
> Thank you.
> >Source package was uploaded to
> >https://mentors.debian.net/package/monit
> >amd64 deb
It looks like this bug is fixed,
I did "dpkg -i monit_5.4-2+deb7u3_amd64.deb", monit restarted and is
running now.
Thank you.
Source package was uploaded to
https://mentors.debian.net/package/monit amd64 deb attached.
I'd like to help with what I can, but the problem is that I'm not a
C/C++ developer,
never seen the source code of monit and haven't got a development
environment for that.
Maybe I could setup and try it this weekend but I hope there is somebody
else who can do it "easier".
However I can test
On Mon, Dec 12, 2016 at 02:06:41PM +0100, Martin Pala wrote:
> The securitytoken in collector is not needed at all - the CSRF
> protection is related to Monit's own HTTP API (the securitytoken
> cookie is not present in upstream).
Ok, I see. Thank you, Martin.
> To fix the problem, just drop
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;
+
Sorry for typo in the explanation ... the "token" comes *after* "strlen(D)" in
the patch - in short:
integer "strlen(D)" is used as string argument for "Cookie:
securitytoken=%s\r\n" => CRASH
string "token" is used as integer argument for "Content-Length:
%d\r\n" ... harmless,
On Mon, Dec 12, 2016 at 01:11:38PM +0100, Arthur Hoffmann wrote:
> Ok, now I have checked my config files and found out that it
> works with the latest package if I remove the following line:
>
> set mmonit https://USER:PASSWORD@URL:PORT/collector
Ok, I see. I don't use closed-source software,
Ok, now I have checked my config files and found out that it
works with the latest package if I remove the following line:
set mmonit https://USER:PASSWORD@URL:PORT/collector
I'm using Monit with the latest M/Monit v3.6.2.
On Mon, Dec 12, 2016 at 12:24:31PM +0100, Arthur Hoffmann wrote:
> I just want to confirm that Monit is running again on all 5 Debian Wheezy
> (i386 and amd64) machines if I downgrade the package with "sudo apt-get
> install monit=1:5.4-2".
Unfortunately, I can't reproduce this on several testing
I just want to confirm that Monit is running again on all 5 Debian
Wheezy (i386 and amd64) machines if I downgrade the package with "sudo
apt-get install monit=1:5.4-2".
reopen 847196
thanks
Please don't reply personally (unless you want to share
some private info)! Either to bugtracker, or
add CC to bugtracker.
Meanwhile, bug reopened. Perhaps, backport is still broken.
(Also, co-mantainers, please use git!)
BTW, I can't reproduce this yet. Perhaps, this
On Wed, Dec 07, 2016 at 09:41:11AM +0100, Arthur Hoffmann wrote:
> I'm not sure whether this bug is the same that I have got,
> but it began with 1:5.4-2+deb7u1 and it is NOT fixed with 1:5.4-2+deb7u2.
Very likely.
> The service/process is starting and writes some INFO log lines without
> errors
Hello,
I'm not sure whether this bug is the same that I have got,
but it began with 1:5.4-2+deb7u1 and it is NOT fixed with 1:5.4-2+deb7u2.
I have got 5 Debian wheezy machines (i386 and amd64), and monit is not
starting on all of them
since 1:5.4-2+deb7u1 and also after upadting to
On Tue, Dec 06, 2016 at 01:52:04PM +0100, Victor Seva wrote:
> Yes, I just notice the security update is broken.
>
> I have prepared the fix for this and I was planing to contact the
> security team about this.
>
> Thanks for reporting,
> Victor Seva
Victor, you are in uploaders for the
Hi Marco, Victor, Chris,
Am 06.12.2016 um 14:04 schrieb Chris Lamb:
> [Adding Jonas as they made the relevant upload]
>
> Hey,
>
>> monit segfault on stop and start
>
> This appears to be a regression in the latest LTS upload so pinging
> the relevant people.
thanks to bugreport, patch and
[Adding Jonas as they made the relevant upload]
Hey,
> monit segfault on stop and start
This appears to be a regression in the latest LTS upload so pinging
the relevant people.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
On 12/06/2016 01:25 PM, Marco Innocenti wrote:
> Package: monit
> Version: 1:5.4-2+deb7u1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> after upgrading monit to version 1:5.4-2+deb7u1 monit stopped
> working in all the servers we maintain. Reverting back
Package: monit
Version: 1:5.4-2+deb7u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading monit to version 1:5.4-2+deb7u1 monit stopped
working in all the servers we maintain. Reverting back to 1:5.4-2
solved our problem.
We see a segfault after a stop or
18 matches
Mail list logo
