comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Home » Public Forums » archive » IDL background job quits without error message
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend  		Switch to threaded view of this topic Create a new topic Submit Reply
IDL background job quits without error message [message #94648] Fri, 04 August 2017 01:54 Go to next message
trisb is currently offline  trisb
Messages: 18
Registered: November 2010
Junior Member
Hello everyone,

I keep on getting this weird problem that an IDL (v8.5) job running in the background on an Ubuntu 16.04.1 LTS server quits unexpectedly without any cause to be found. No clue what's happening.

Here is what I am doing. The job is started as follows:

idl my_list_of_commands.txt >& logfile &

the my_list_of_commands.txt file contains only to lines:

my_programme
exit

with "my_programme" being a data reduction pipeline. The server has 44 double-threaded cores and tons of memory. I usually run several (up to 8) of these jobs in parallel. However, after several hours they will have quit unexpectedly without any error. It is not linked to a specific function/procedure inside the code and may happen at any place. The logfiles just show the last line of whatever comment the code put out as it runs through the job. Neither memory nor cores run out of resources - even though the jobs are memory intensive, they use up only 1-2% of the total memory each.

Other non-IDL programmes do not show this behaviour. Any hint of what might be happening?

Thanks,
F

Report message to a moderator

Re: IDL background job quits without error message [message #94693 is a reply to message #94648] Fri, 25 August 2017 07:04 Go to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
On Friday, August 4, 2017 at 4:54:04 AM UTC-4, trisb wrote:
> Other non-IDL programmes do not show this behaviour. Any hint of what might be happening?

Process limits may be kicking in. Try using 'ulimit' (bash shell) or 'limit' ([t]csh shell) to see what your CPU time limit is.

Craig

Report message to a moderator

  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: DEFSYSV with /TEST option?
Next Topic: MPFITFUN .TIED

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 05:19:15 PDT 2025

Total time taken to generate the page: 0.00349 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software