FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 12-14-2010, 01:15 PM
Jorge Fábregas
 
Default BIND and latest update (max open files WARNING)

Hi all,

After the latest security update for bind (which came out last night), now there's a new message on syslog, (facility: daemon, severity: warning) every time you restart named:

max open files (1024) is smaller than max sockets (4096)


After googling for a while the solution seems to be to add this to /etc/security/limits.conf:

named******* soft*** nofile******* 4096

...and mofity /etc/named.conf in order to add, under the options section:


files 4096;

That seems to work.* Of course, you may raise the 4096 but I guess that's the default in BIND and I was good with that.

I'm not sure why this happend. Maybe before the update bind had a value of 1024 for max.sockets and now it was raised to 4096.


*--
Jorge

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-14-2010, 02:17 PM
Radu Gheorghiu
 
Default BIND and latest update (max open files WARNING)

Hi all,



I can confirm this has happened to all my CentOS boxes in
production.



Regards,

Radu



On 12/14/2010 03:15 PM, Jorge Fábregas wrote:


Hi all,



After the latest security update for bind (which came out last
night), now there's a new message on syslog, (facility: daemon,
severity: warning) every time you restart named:



max open files (1024) is smaller than max sockets (4096)



After googling for a while the solution seems to be to add this to
/etc/security/limits.conf:



named******* soft*** nofile******* 4096



...and mofity /etc/named.conf in order to add, under the options
section:



files 4096;



That seems to work.* Of course, you may raise the 4096 but I guess
that's the default in BIND and I was good with that.



I'm not sure why this happend. Maybe before the update bind had a
value of 1024 for max.sockets and now it was raised to 4096.



*--

Jorge



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos






_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 12-15-2010, 09:50 PM
Ralph Angenendt
 
Default BIND and latest update (max open files WARNING)

Am 14.12.10 16:17, schrieb Radu Gheorghiu:
> Hi all,
>
> I can confirm this has happened to all my CentOS boxes in production.

Jorge has reported this as
https://bugzilla.redhat.com/show_bug.cgi?id=663112

Ra "trim your mails!" lph
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 12:56 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org