[asterisk-users] *End Of Life ASTERISK 1.2.X Was:
INSTRUCTIONSFORTHE ASTERISK COMMUNITY - PLEASEREAD NOW *
shadowym
shadowym at hotmail.com
Wed May 30 09:08:11 MST 2007
Can you cut and paste the last few relevant lines of your log file? That
should help determine what is causing the core dumps. After that is
determined you can file a bug report with the log file cut and paste if
necessary. Is there some reason you cannot test patches on a separate test
system. If it's a legitimate bug there will likely be others looking for a
solution that would be willing to test.
Doing things that way helps everyone including yourself. I have found the
developers VERY responsive to well documented bug reports.
-----Original Message-----
From: Eric "ManxPower" Wieling [mailto:eric at fnords.org]
Sent: Tuesday, May 29, 2007 6:18 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] *End Of Life ASTERISK 1.2.X Was:
INSTRUCTIONSFORTHE ASTERISK COMMUNITY - PLEASEREAD NOW *
Tzafrir Cohen wrote:
> On Tue, May 29, 2007 at 01:06:54PM -0500, Eric ManxPower Wieling wrote:
>> Michael Collins wrote:
>>>> I think its a fair decision . 1.2 is very stable and they are not
>>>> closing it all together , security issues will still be fixed .
>>>> They need to concentrate more on 1.4 to make it bugfree .
>>> Fair indeed. I would guess that a completely stable 1.2 w/ security
>>> maintenance is acceptable to the majority of users. Those folks
>>> still using 1.0.x certainly aren't clamoring for new features! The
>>> great many
>> Except that for some users 1.2.18 is NOT stable. I've had to roll
>> back to 1.2.15 on my production servers in order to prevent core
>> dumps at least once per day. No, I am not willing to turn my
>> production servers into testing servers to solve this. Doing so
>> would make me a "former consultant" for these customers.
>
> So basically what you're saying is that some efforts should be
> concentrated on 1.2 as well.
>
> So let's start with your specific problems. Are there open bugs for them?
My specific problem is that Asterisk 1.2.17 and 1.2.18 (I've not tried
1.2.16) core dumps at least once per day. 1.2.15 works just fine for me. I
don't know if there are open bugs. I've not opened any bugs.
Any time I open a bug for a problem I have on a production server, all
people want me to do is test patches to see if they fix the issue. They
don't seem to understand the term "production server".
Sorry, but this is my JOB, not my hobby. Perhaps the customers of the
developers don't care if the PBX crashes once per day, but my customers do
care and I will do whatever is required to make them stop yelling at me.
What made them stop yelling at me is moving back to 1.2.15.
More information about the asterisk-users
mailing list