ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001436ClearOSapp-base - Base Systempublic2013-11-21 10:332015-02-05 12:21
Reporteruser2 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version6.6.0 Beta 2Fixed in Version6.6.0 Beta 2 
Summary0001436: Ulimits defined in /etc/security/limits.conf (or limits.d) are not effective on boot
DescriptionThe /etc/security/limits.d/95-clearos.conf file in the ClearOS base package sets the number of file descriptors to 16384 (default is 1024) and number of processes to 4096 (default is 1024). These limits work when a daemon is restarted, but the old defaults are still used on boot. Wah!? This little gem confirms the behavior -- original @ http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Fc_special_considerations_linux.html [^]

   Important: If you use a system startup script such as /etc/init.d/was
   or /etc/rc.*/SXXWebSphere to start WebSphere Application Server at
   system boot up time, init.d invokes the startup scripts with the maximum
   number of file descriptors set to 1024 instead of the system default value
   that is set in /etc/security/limits.conf (65536). To avoid this problem, after
   a system boot up, manually run /etc/init.d/was restart from a root shell.
   This will ensure that WebSphere Application Server is restarted with the
   correct file descriptor limit.

Well... that's certainly unexpected behavior.
Steps To Reproduce
Additional InformationFor ClearOS 6, add a workaround for the web proxy.
TagsNo tags attached.
Relationships
related to 0001701closed user2 Ulimits defined in /etc/security/limits.conf (or limits.d) are not effective on boot 
related to 0002195closed user2 Remove ulimit workaround needed in ClearOS 6 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-11-21 10:33user2New Issue
2013-11-21 10:33user2Statusnew => confirmed
2013-11-21 10:41user2Target Version => 6.5.0 Beta 3
2013-11-21 10:42user2Description Updatedbug_revision_view_page.php?rev_id=102#r102
2013-11-21 19:11user2Target Version6.5.0 Beta 3 => 6.5.0
2013-12-09 15:35user2Target Version6.5.0 => 6.6.0 Beta 1
2014-05-08 08:09user2Target Version6.6.0 Beta 1 => 6.6.0 Beta 2
2014-05-14 10:06user2Issue cloned: 0001701
2014-05-14 10:06user2Relationship addedrelated to 0001701
2014-05-14 10:15user2Categoryclearos-base - Base System => app-web-proxy - Web Proxy
2014-05-14 10:15user2Additional Information Updatedbug_revision_view_page.php?rev_id=117#r117
2014-06-10 14:05user2Categoryapp-web-proxy - Web Proxy => app-base - Base System
2014-06-10 15:18user2Statusconfirmed => resolved
2014-06-10 15:18user2Fixed in Version => 6.6.0 Beta 2
2014-06-10 15:18user2Resolutionopen => fixed
2014-06-10 15:18user2Assigned To => user2
2014-07-10 12:46user2Statusresolved => closed
2015-02-05 12:21user2Issue cloned: 0002195
2015-02-05 12:21user2Relationship addedrelated to 0002195

There are no notes attached to this issue.