Hi Reuti, Ok it looks you have been right - the core limits defined in complex configuration (qconf -sc) were indeed zero, but core limits defined on queues were unlimited. After defining these on queue config, problem went away. Thanks,
Ondrej -----Original Message----- From: Reuti [mailto:[email protected]] Sent: Monday, January 25, 2016 5:46 PM To: Ondrej Valousek <[email protected]> Subject: Re: [SGE-discuss] Core files generation > Am 25.01.2016 um 17:43 schrieb Ondrej Valousek <[email protected]>: > > Strange: > dummy 68 > qrsh limit > cputime unlimited > filesize unlimited > datasize unlimited > stacksize unlimited > coredumpsize unlimited > memoryuse unlimited > vmemoryuse unlimited > descriptors 1024 > memorylocked 64 kbytes > maxproc 257599 > > (using tcsh here, so ulimit -> limit) > > If I ssh to the exec host instead, I get "coredumpsize 0" correctly: But ssh is unrelated to the setting in the queue definition of SGE. -- Reuti > [root@rineen teeling]# ssh ondrejv@skynet16 ondrejv@skynet16's > password: > > [ondrejv@skynet16 /home/ondrejv: ] > HOME 51 > limit > cputime unlimited > filesize unlimited > datasize unlimited > stacksize 10240 kbytes > coredumpsize 0 kbytes > memoryuse unlimited > vmemoryuse unlimited > descriptors 1024 > memorylocked 64 kbytes > maxproc 1024 > > Ondrej > > > -----Original Message----- > From: Reuti [mailto:[email protected]] > Sent: Monday, January 25, 2016 5:23 PM > To: Ondrej Valousek <[email protected]> > Cc: [email protected] <[email protected]> > Subject: Re: [SGE-discuss] Core files generation > > >> Am 25.01.2016 um 17:06 schrieb Ondrej Valousek <[email protected]>: >> >> Thanks, >> H_core defaults to 0 already :-( > > This is quite strange, as a normal user can only lower the ulimit. Can you > please submit a job with. > > ulimit -aH > echo > ulimit -aS > > -- Reuti > > >> Ondrej >> >> -----Original Message----- >> From: Reuti [mailto:[email protected]] >> Sent: Monday, January 25, 2016 4:47 PM >> To: Ondrej Valousek <[email protected]> >> Cc: [email protected] <[email protected]> >> Subject: Re: [SGE-discuss] Core files generation >> >> Hi, >> >>> Am 25.01.2016 um 16:20 schrieb Ondrej Valousek >>> <[email protected]>: >>> >>> Hi list, >>> >>> I have a strange problem. Jobs submitted to GE tend to crash and >>> generate core files. I want avoid generation of core files as they tend to >>> hog our shared storage, so I defined system-wide policy in >>> /etc/security/limits.conf My problem – if I submit the job normally via >>> qrsh, core files are now not generated even if the job segfaults. >>> But they still tend to generate cores is I use the “-noshell” parameter for >>> qrsh. >>> >>> How can I avoid that? >> >> You can define a h_core limit in the queue definition of 0. >> >> -- Reuti >> >> >>> I guess, that with –noshell, no shell is being started and hence limits >>> defined in /etc/security/limits.conf are not effective any longer, right? >>> As a simple example job, I used “/usr/bin/yes” + sent signal SIGSEGV to it. >>> Thanks, >>> >>> Ondrej >>> ----- >>> >>> The information contained in this e-mail and in any attachments is >>> confidential and is designated solely for the attention of the intended >>> recipient(s). If you are not an intended recipient, you must not use, >>> disclose, copy, distribute or retain this e-mail or any part thereof. If >>> you have received this e-mail in error, please notify the sender by return >>> e-mail and delete all copies of this e-mail from your computer system(s). >>> Please direct any additional queries to: >>> [email protected]. Thank You. Silicon and Software Systems Limited >>> (S3 Group). Registered in Ireland no. 378073. Registered Office: South >>> County Business Park, Leopardstown, Dublin 18. >>> _______________________________________________ >>> SGE-discuss mailing list >>> [email protected] >>> https://arc.liv.ac.uk/mailman/listinfo/sge-discuss >> >> >> ----- >> >> The information contained in this e-mail and in any attachments is >> confidential and is designated solely for the attention of the intended >> recipient(s). If you are not an intended recipient, you must not use, >> disclose, copy, distribute or retain this e-mail or any part thereof. If you >> have received this e-mail in error, please notify the sender by return >> e-mail and delete all copies of this e-mail from your computer system(s). >> Please direct any additional queries to: [email protected]. Thank >> You. Silicon and Software Systems Limited (S3 Group). Registered in Ireland >> no. 378073. Registered Office: South County Business Park, Leopardstown, >> Dublin 18. >> > > > ----- > > The information contained in this e-mail and in any attachments is > confidential and is designated solely for the attention of the intended > recipient(s). If you are not an intended recipient, you must not use, > disclose, copy, distribute or retain this e-mail or any part thereof. If you > have received this e-mail in error, please notify the sender by return e-mail > and delete all copies of this e-mail from your computer system(s). Please > direct any additional queries to: [email protected]. Thank You. > Silicon and Software Systems Limited (S3 Group). Registered in Ireland no. > 378073. Registered Office: South County Business Park, Leopardstown, Dublin > 18. > ----- The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: [email protected]. Thank You. Silicon and Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office: South County Business Park, Leopardstown, Dublin 18. _______________________________________________ SGE-discuss mailing list [email protected] https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
