Omapi makes DHCPD up to 100 % CPU Usage

[Jürgen Dietl]

Hello,

thanx again for the hint. IT WORKS NOW. I just used a link to the old
omshell. So yes the new RC1 solved my problem with OMAPI.

thanx for that,
cheers,
Juergen


2011/2/23 Jürgen Dietl <juergen.dietl at googlemail.com>

> Hello,
>
> thanx for the hint. I tried the new 4.2.1rc1. When I use my script for stop
> or when I try to connect via osshell - still 100 % CPU usage on test server.
> I dont have this on the production server, so it might be also a OS problem.
> So I also try to find a fix for SuSE. When you know about I would be happy
> to get another hint.
>
> cheers,
> Juergen
>
>
> 2011/2/23 Shawn Routhier <sar at isc.org>
>
> On 02/21/2011 08:26, Peter Rathlev wrote:
>>
>>> On Mon, 2011-02-21 at 16:25 +0100, Jürgen Dietl wrote:
>>>
>>>> Operating System: SUSE Enterprise Server 11 (x86_64)
>>>> Version = 11
>>>> PatchLevel = 1
>>>>
>>>> ISC-DHCP Server 4.2.0-P2
>>>>
>>>> When I try to open an omapi port via the omshell or script the dhcpd
>>>> process raises to 100 % of CPU usage and when I try to connect over
>>>> omapi I get the message
>>>>
>>>
>>> Redhat har the following bug entry on that:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=666441
>>>
>>> The patch is "dhcp-4.2.0-P2-omapi.patch" which can be found in the
>>> source RPM.  If you have trouble finding the patch (and trust a
>>> stranger) it's this:
>>>
>>> diff -up dhcp-4.2.0-P2/omapip/protocol.c.omapi
>>> dhcp-4.2.0-P2/omapip/protocol.c
>>> --- dhcp-4.2.0-P2/omapip/protocol.c.omapi       2009-11-20
>>> 02:49:02.000000000 +0100
>>> +++ dhcp-4.2.0-P2/omapip/protocol.c     2011-01-03 16:30:25.000000000
>>> +0100
>>> @@ -386,7 +386,7 @@ isc_result_t omapi_protocol_signal_handl
>>>         /* Should only receive these when opening the initial
>>> authenticator. */
>>>         if (!strcmp (name, "status")) {
>>>                 status = va_arg (ap, isc_result_t);
>>> -               if (status != ISC_R_SUCCESS) {
>>> +               if ((status != ISC_R_SUCCESS)&&  (status>=
>>> ISC_RESULTCLASS_DHCP)) {
>>>                         omapi_signal_in (h ->  inner, "status", status,
>>>                                          (omapi_object_t *)0);
>>>                         omapi_disconnect (p ->  outer, 1);
>>>
>>> It's not in vanilla 4.2.0-P2. Beware that there might be a reason for
>>> this, though I wouldn't know any. We use the patch on our servers and
>>> haven't seen any problems.
>>>
>>>
>> 4.2.1rc1 has now been released.  It contains a different fix that should
>> address the underlying omapi issue.
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20110223/25d67224/attachment.html>