How do I know if the program has hung up?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I've had a simulation running for 12 hours and for the last several hours Mechanical Simulation Job Manager has told me the analysis is at 80%. I'm not sure how long to wait before I kill the job. The computer seems happy and all indications (that I've been able to find) are that the analysis is running. My workstation was dual quad-core processors and 24 Gb RAM. Right now the CPU is running at less than 10% and 4.5 Gb RAM is in use, whereas an hour into the analysis the CPU was bouncing off 100% and up to 8 Gb RAM was in use.
When I open the Log in Job Manager there are over 400 listings beginning with:
<20150505T223112 level=err source=HttpRequest code=304 proc=SimJobManager.exe:3168 message="request failed with 304
POST http://localhost:43912/job/submit/v1/V1%2BLAN%2Blocalhost%2Bdls-dsim-simmech-2016-solver-desktop%2Blocal%2B97a57ab1-ab4f-4e2b-a771-406451c7a820
request headers:
Content-Type=application/json
response headers:" >
and just now:
<20150506T114716 level=err source=HttpRequest code=304 proc=SimJobManager.exe:3168 message="request failed with 304
POST http://localhost:43912/job/submit/v1/V1%2BLAN%2Blocalhost%2Bdls-dsim-simmech-2016-solver-desktop%2Blocal%2B97a57ab1-ab4f-4e2b-a771-406451c7a820
request headers:
Content-Type=application/json
response headers:" >
What does this mean? How do I find out how to decode these arcane text strings? When should I kill this analysis? My guess is that the first log entry came in at 2231 yesterday, about a half hour after I launched the analysis (files time stamped 2202). Then I guess that the 80% has been the status since 2231 yesterday? The analysis is "running", but it is in a dead loop? Lesson: keep track of your analysis in Job Manager to make sure that a job is not only running but making progress towards a solution?