On 10/12/2012 01:59 PM, Brodie, Kent wrote:
Scratch that. OK, now I'm stumped. Here is my qmaster log when simply 'restarting' the qmaster deamon: 10/12/2012 15:49:19| main|lima|I|controlled shutdown 8.1.2 10/12/2012 15:49:25| main|lima|I|read job database with 1 entries in 0 seconds 10/12/2012 15:49:25| main|lima|I|qmaster hard descriptor limit is set to 65536 10/12/2012 15:49:25| main|lima|I|qmaster soft descriptor limit is set to 8192 10/12/2012 15:49:25| main|lima|I|qmaster will use max. 8172 file descriptors for communication 10/12/2012 15:49:25| main|lima|I|qmaster will accept max. 1000 dynamic event clients 10/12/2012 15:49:25| main|lima|I|starting up SGE 8.1.2 (lx-amd64) Note, the 8192 and 65536. Yay! This comes from the /etc/security/limits.conf and also probably from the S_DESCRIPTORS / H_DESCRIPTORS setting. Now, look what happens when the system is rebooted: 10/12/2012 15:50:27| main|lima|I|controlled shutdown 8.1.2 10/12/2012 15:55:47| main|lima|I|read job database with 1 entries in 0 seconds 10/12/2012 15:55:47| main|lima|W|nr of dynamic event clients exceeds max file descriptor limit, setting MAX_DYN_EC=979 10/12/2012 15:55:47| main|lima|I|qmaster hard descriptor limit is set to 1024 10/12/2012 15:55:47| main|lima|I|qmaster soft descriptor limit is set to 1024 10/12/2012 15:55:47| main|lima|I|qmaster will use max. 1004 file descriptors for communication 10/12/2012 15:55:47| main|lima|I|qmaster will accept max. 979 dynamic event clients 10/12/2012 15:55:47| main|lima|I|starting up SGE 8.1.2 (lx-amd64) WHOA. Where the heck is the 1024 limit coming from?
I think those env settings are inherited from the parent process. So maybe qmaster is started up by some init process that didn't get its settings from limits.conf?
I bet if you restart the process, it'll get the settings from your current root shell, and all will be well.
Regards, -- Alex Chekholko [email protected] _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
