Bug#444650: can you test and verify with latest glibc (libc6) installed?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Patrick Winnertz-4
Hello,
can you verify this bug again with the newest glibc(libc6) installed on
these servers?
This might be related to the problem described in #369536 or #401115.
Hopefully this bug report is fixed with the update of libc6.

Greetings
Patrick Winnertz

--
 .''`.   Patrick Winnertz <[hidden email]>
:  :' :  GNU/Linux Debian Developer
`. `'`   http://www.der-winnie.de http://d.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Stéphane Glondu
Patrick Winnertz wrote:
> can you verify this bug again with the newest glibc(libc6) installed on
> these servers?
> This might be related to the problem described in #369536 or #401115.
> Hopefully this bug report is fixed with the update of libc6.

The bug still exists with libc6 2.3.6.ds1-13etch4.

Note: we do no longer use cfengine2 anymore. I've made the test with a
freshly-installed cfengine2 (on the same computer).

--
Stéphane Glondu


Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Henning Makholm-2
Stephane Glondu <[hidden email]> writes:

>> can you verify this bug again with the newest glibc(libc6) installed
>> on these servers?
>> This might be related to the problem described in #369536 or
>> #401115. Hopefully this bug report is fixed with the update of
>> libc6.
>
> The bug still exists with libc6 2.3.6.ds1-13etch4.
>
> Note: we do no longer use cfengine2 anymore. I've made the test with a
> freshly-installed cfengine2 (on the same computer).

Thanks alot for the testing!! Are you able to test with the newer
cfengine2-package (2.2.3) e.g. from backports.org [1]?

Can you also send me your cfagent.conf-file so I can try to reproduce?


- Werner

[1] http://backports.org/dokuwiki/doku.php?id=instructions



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Stéphane Glondu
Morten Werner Forsbring a écrit :
> Thanks alot for the testing!! Are you able to test with the newer
> cfengine2-package (2.2.3) e.g. from backports.org [1]?

It does not segfault anymore with this new version.

> Can you also send me your cfagent.conf-file so I can try to reproduce?

The segfault occurs with the attached cfagent.conf file.

I have narrowed it a lot. I should have done this earlier!

--
Stéphane Glondu

groups:
  ferme = ( IPRange(10.231.136.200-210) )
Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Patrick Winnertz-4
Am Dienstag, 15. Januar 2008 21:34:30 schrieb Stéphane Glondu:
> Morten Werner Forsbring a écrit :
> > Thanks alot for the testing!! Are you able to test with the newer
> > cfengine2-package (2.2.3) e.g. from backports.org [1]?
>
> It does not segfault anymore with this new version.
Mh.. this means this is fixed by new glibc and new cfengine2 package.
Morton what do you think? I'll try to reproduce it with the attached
cfagent.conf file and report after.
>
> > Can you also send me your cfagent.conf-file so I can try to reproduce?
>
> The segfault occurs with the attached cfagent.conf file.
>
> I have narrowed it a lot. I should have done this earlier!
Thanks for your work

Greetings
Winnie
--
 .''`.   Patrick Winnertz <[hidden email]>
:  :' :  GNU/Linux Debian Developer
`. `'`   http://www.der-winnie.de http://d.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#444650: can you test and verify with latest glibc (libc6) installed?

Morten Werner Forsbring
In reply to this post by Stéphane Glondu
fixed 444650 2.2.3-1
retitle 444650 cfagent segfaults when using IPRange(...)
severity 452352 important
thanks

Stéphane Glondu <[hidden email]> writes:

>> Thanks alot for the testing!! Are you able to test with the newer
>> cfengine2-package (2.2.3) e.g. from backports.org [1]?
>
> It does not segfault anymore with this new version.

Great! This is really helpful. I'll also lower the severity of #452352
to 'important' as this bug doesn't affect the version in unstable
(2.2.3-1).

>> Can you also send me your cfagent.conf-file so I can try to reproduce?
>
> The segfault occurs with the attached cfagent.conf file.
>
> I have narrowed it a lot. I should have done this earlier!

Great, thanks! I'll try to verify the bug in a qemu-machine. Not sure
if we should try to make a patch for stable though. :/

> groups:
>   ferme = ( IPRange(10.231.136.200-210) )

I'll rename the bug then.


- Werner


Reply | Threaded
Open this post in threaded view
|

Processed: Re: Bug#444650: can you test and verify with latest glibc (libc6) installed?

Debian Bug Tracking System
Processing commands for [hidden email]:

> fixed 444650 2.2.3-1
Bug#444650: cfengine2: cfagent segfaults immediately after startup
Bug marked as fixed in version 2.2.3-1.

> retitle 444650 cfagent segfaults when using IPRange(...)
Bug#444650: cfengine2: cfagent segfaults immediately after startup
Changed Bug title to `cfagent segfaults when using IPRange(...)' from `cfengine2: cfagent segfaults immediately after startup'.

> severity 452352 important
Bug#452352: cfengine2: should this package be orphaned?
Severity set to `important' from `serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]