dhcrelay prints these logs and doesn't live normally. [Can't initialize context: not enough free resources.]

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

dhcrelay prints these logs and doesn't live normally. [Can't initialize context: not enough free resources.]

박기당
thanks for reply Glenn.
Both dhcpd and dhcrelay can be run on one system, but only dhcrelay is currently used.
In addition, dhcrelay was well run and restarted, but logs occurred, and the restart failed continuously. The restart process is as follows.
kill -9 xxx; /usr/sbin/dhcrelay -i vlan200 A.B.C.D -i vlan100

The result of ulimit-n is 1024.
ISC_R_NORESOURCES is returned to its location: bind/bind-9.9.5/lib/isc/unix/socket.c.
The problem is when the fd value of the socket is greater than 1024, and when the fd value of the socket is less than 0.
I think the fd value is less than zero, what is the situation? It's not easy to reproduce.
regards,
pkd

_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: dhcrelay prints these logs and doesn't live normally. [Can't initialize context: not enough free resources.]

glenn.satchell
hi pkd

kill -9 kills the process and it does not allow it to do any cleanup
such as deleting pid files and the like. A normal kill without -9 should
work just fine.

What platform is this running on, and what operating system (centos,
ubuntu, etc) and version? Did you compile from source yourself or use a
provided package? If you compiled yourself, maybe try a newer version?
This looks like it is dhcp-4.2.x, which is

Do you get this error every time you run dhcrelay, or only sometimes?

Do you get the error if you remove one of the interfaces? eg
  /usr/sbin/dhcrelay -i vlan200 A.B.C.D
or
  /usr/sbin/dhcrelay -i vlan100 A.B.C.D

That might mean the other interface is incorrectly configured.

If it's always can you put a sleep, eg kill; sleep 2; dhcrelay ...  
between the kill and the startup to allow time for the old executables,
etc, to be released?

And finally the last test I can think of is to run using strace, eg:

kill <dhcrelay-pid>
strace /usr/sbin/dhcrelay -i vlan200 -i vlan100 A.B.C.D

and look at the system calls to see if there is something that happens
before the final error is printed that might suggest what the underlying
error is.

regards,
Glenn

On 2021-05-28 13:17, 박기당 wrote:

> thanks for reply Glenn.
>
> Both dhcpd and dhcrelay can be run on one system, but only dhcrelay is
> currently used.
> In addition, dhcrelay was well run and restarted, but logs occurred,
> and the restart failed continuously. The restart process is as
> follows.
> kill -9 xxx; /usr/sbin/dhcrelay -i vlan200 A.B.C.D -i vlan100
>
> The result of ulimit-n is 1024.
> ISC_R_NORESOURCES is returned to its location:
> bind/bind-9.9.5/lib/isc/unix/socket.c.
> The problem is when the fd value of the socket is greater than 1024,
> and when the fd value of the socket is less than 0.
> I think the fd value is less than zero, what is the situation? It's
> not easy to reproduce.
>
> regards,
> pkd
> _______________________________________________
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> dhcp-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/dhcp-users
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users