topic Re: Simjobmanager / DSSP.log in Moldflow Insight Forum

Simjobmanager / DSSP.log

KlausMüller8028 — Wed, 04 Jul 2018 12:26:09 GMT

Hello
I notice that the simjob manager writes to the logfile every minute
how can this be turned off?
in the default settings, no logs are active.
Currently no analysis is running!
here's an example

<20180704T140634 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T140713 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T140713 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T140713 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T140713 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 4 ms." >
<20180704T140735 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T140735 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T140836 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T140836 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T140937 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T140937 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141038 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141038 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141139 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141139 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141228 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T141228 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141228 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T141228 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141240 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141240 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141341 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141341 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141442 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141442 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141543 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141543 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141644 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141644 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141743 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T141743 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141743 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T141743 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T141745 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141745 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141844 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T141844 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141846 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141846 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T141947 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T141947 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T142048 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T142048 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T142149 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T142149 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 5 ms." >
<20180704T142250 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T142250 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T142258 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T142258 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T142258 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="started." >
<20180704T142258 level=info source=getResponse code=0 proc=SimJobManager.exe:5812 message="finished in 6 ms." >
<20180704T142351 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="started." >
<20180704T142351 level=info source=getResponse code=1001 proc=SimJobManager.exe:5812 message="finished in 6 ms." >

Re: Simjobmanager / DSSP.log

Javier.Jubierre — Thu, 05 Jul 2018 14:19:43 GMT

Hi @KlausMüller8028

Thanks for posting in this forum.

Honestly, I never saw my Simulation Job Manager (SJM) logging in any activity when I am not running a job. My guess is that you might have a zombie simulation that is not able to conclude by itself.

One trick you might do is to stop the SJM service. For do it so, you need to close the SJM located on your system tray (close to the Windows clock) and to restart (stop and start) the service adsk_dssp_job_server (or adsk_dssp_job_server_7 if you already installed the release 2019) on the task manager.

I hope it helps!

Cheers,

Javier

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

Re: Simjobmanager / DSSP.log

Javier.Jubierre — Mon, 09 Jul 2018 10:12:00 GMT

Hi @KlausMüller8028

Thanks again for your post!

Did my reply help you out to troubleshooting your issue? Did you managed to stop the logging on the DSSP file?

Cheers,

Javier
______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

Re: Simjobmanager / DSSP.log

alois.neumaier — Mon, 09 Jul 2018 13:29:30 GMT

The services stopped started same behavior

@Javier.Jubierre wrote:
Hi @KlausMüller8028

Thanks again for your post!
Did my reply help you out to troubleshooting your issue? Did you managed to stop the logging on the DSSP file?

Cheers,
Javier
______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

Re: Simjobmanager / DSSP.log

Javier.Jubierre — Mon, 16 Jul 2018 09:55:13 GMT

Hi @alois.neumaier

Thanks for your feedback!

In order to give you a more accurate diagnostic I would need that you send me some further information. If you want reach me to my email javier.jubierre@autodesk.com and we discuss this topic privately.

Cheers,

Javier

P.D: Are you both @alois.neumaier and @KlausMüller8028 working on the same machine/server?
______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

Re: Simjobmanager / DSSP.log

LadisR — Mon, 23 Jul 2018 00:51:21 GMT

Hi @KlausMüller8028

With the release of Autodesk Moldflow 2019 Update 1 we also released the new Simulation Job Manager 7.2

This new SJM 7.2 has a new configuration parameter : dssp_logger_maxlogsize.

This new configuration parameter set's the maximum size in bytes that the log file is allowed to grow to.

Once the log file size is greater than or equal to this size, the current DSSP.log file is renamed to DSSP_OLD.log (deleting any existing DSSP_OLD.log file) and a new DSSP.log is created.

The default for this value is 52428800 (50mb).

You can define the DSSP.log file size in the JSON file C:\Program Files\Autodesk\Simulation Job Manager 7\dsspjobclient.config

example:

{
"dssp_logger_maxlogsize": 10000
}

However, if this value is set to zero, the log file size is not capped and will grow indefinitely.

Regards

Ladis

Re: Simjobmanager / DSSP.log

porca_paletta — Thu, 26 Jul 2018 08:16:06 GMT

Is Update1 already available? Is it for Adviser as well?

Thanks a lot.

Re: Simjobmanager / DSSP.log

Javier.Jubierre — Thu, 26 Jul 2018 08:55:14 GMT

Hi @porca_paletta,

Thanks for your post!

The Update 1 should be avilable on your Autodesk Account from next Monday, July 30th.

Cheers,

Javier

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!