<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Thanks Nicolas for your help. This
brought me to check the status of the job in NAS which was really
failed. The reason was "Job xxx has exceeded its timeout of 10080
minutes. Changing status to FAILED. ". Setting back the job status
to 2 (Started) for that job in the database, brings back the
complete Details and Actions Page of this Running job!<br>
<br>
</div>
<blockquote type="cite"
cite="mid:d805bf127a704376bf586dbc3b5bfbc2@kb.dk">
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<p>And not if you look directory in the job definition.</p>
<p>Sometimes the job is set to failed but is showing as running
in the running jobs pages.</p>
<p>Anyway if the the job is not set to failed yet it should be a
bit easier to re-register it.</p>
<p>I'm guessing that progress reports for jobs that are not
"known" to be running are silent ignored.</p>
<p>And the running jobs page "only" shows what is in the
progress reports table.</p>
<p>So somehow from progress report it should be possible to
re-register jobs which appear to still be running.</p>
<p>This could maybe be done fairly easily. Someone would need to
look in the code to see if progress reports are just ignored
for jobs that the GUI does not think are running.<br>
</p>
<p><br>
</p>
<p>Best<br>
</p>
<p>Nicholas<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
Netarchivesuite-devel
<a class="moz-txt-link-rfc2396E" href="mailto:netarchivesuite-devel-bounces@ml.sbforge.org"><netarchivesuite-devel-bounces@ml.sbforge.org></a> on behalf
of <a class="moz-txt-link-abbreviated" href="mailto:aponb@gmx.at">aponb@gmx.at</a> <a class="moz-txt-link-rfc2396E" href="mailto:aponb@gmx.at"><aponb@gmx.at></a><br>
<b>Sent:</b> Wednesday, April 11, 2018 11:14:45 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:netarchivesuite-devel@ml.sbforge.org">netarchivesuite-devel@ml.sbforge.org</a><br>
<b>Subject:</b> Re: [Netarchivesuite-devel] Reconnect NAS to
running jobs</font>
<div> </div>
</div>
<div>
<div class="moz-cite-prefix">Hi Nicholas,<br>
<br>
thanks for your quick response!<br>
<br>
The job was not set to failed after restarting NAS. Actually
the ob is running and also appears in the running jobs
overview, but it is not showing the correct progress and
queued files and so on.<br>
<br>
Yeah, that would be nice if NAS would check for running jobs
and could reconnect to it. Doesn't need to be automatically. A
manual step would be ok. But I understand that it seems to be
a lot of work to redesign the current behavior.
<br>
<br>
Regards<br>
a.<br>
<br>
<br>
<br>
On 2018-04-11 10:38, Nicholas Grooss Clarke wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6fa1ede239664f09b7c4ef59a9deb747@kb.dk">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<p>Hi Andreas</p>
<p><br>
</p>
<p>When you did a restart did the job get set to failed and
also does not appear in the running jobs overview?<br>
</p>
<p><br>
</p>
<p>Basically you would like the GUI to check for running
jobs when it is restarted?<br>
</p>
<p><br>
</p>
<p>One problem with this is that the harvestcontrollers do
not listen to JMS when busy.</p>
<p>The H3 monitor does not yet have a list of all
hosts/ports where H3 instances are configured to run.</p>
<p>So currently the H3 monitor only read the state of jobs
from the database to see want to monitor.<br>
</p>
<p><br>
</p>
<p>I think Søren changed the GUI code at some point so
HarvestControllers reconnected with the GUI when it gets a
message from an "unknown" source.</p>
<p><br>
</p>
<p>I have no idea how difficult it would be to change the
GUI/Jobscheduler to identify running job during a restart.</p>
<p>I would need to have a grace period of 5-10 minuttes for
progress reports to "magically" appear to know an orphaned
job needs to be registered.<br>
</p>
<p><br>
</p>
<p>Redesigning the jobscheduler would make this
functionality straightforward. If/when that happens.</p>
<p>Theoretically it should also be possible to restart the
HarvestController and reconnect to the H3 job.</p>
<p>But not with the existing design.<br>
</p>
<p><br>
</p>
<p>Best</p>
<p>Nicholas</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
Netarchivesuite-devel
<a class="moz-txt-link-rfc2396E"
href="mailto:netarchivesuite-devel-bounces@ml.sbforge.org"
moz-do-not-send="true">
<netarchivesuite-devel-bounces@ml.sbforge.org></a>
on behalf of <a class="moz-txt-link-abbreviated"
href="mailto:aponb@gmx.at" moz-do-not-send="true">
aponb@gmx.at</a> <a class="moz-txt-link-rfc2396E"
href="mailto:aponb@gmx.at" moz-do-not-send="true"><aponb@gmx.at></a><br>
<b>Sent:</b> Wednesday, April 11, 2018 10:04:50 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated"
href="mailto:netarchivesuite-devel@ml.sbforge.org"
moz-do-not-send="true">
netarchivesuite-devel@ml.sbforge.org</a><br>
<b>Subject:</b> [Netarchivesuite-devel] Reconnect NAS to
running jobs</font>
<div> </div>
</div>
<div>
<p>I had to restart NAS (5.4) without jmsbroker , just the
running Heritrix /HarvestControllerApplications kept
alive. After restarting NAS I am not getting the services
of "Details and Actions on Running Job"-Page on
<a class="moz-txt-link-freetext"
href="http://nasurl/History/history/job/xxx/"
moz-do-not-send="true">
http://nasurl/History/history/job/xxx/</a><br>
</p>
<p>I am only receiving <br>
</p>
<h3 class="page_heading">Details and Actions on Running Job
xxx</h3>
NAS Job xxx is in state FAILED.<br>
<br>
I only can access the job directly via the heritrix3
WebConsole.<br>
<br>
Is there any chance to reconnect the NAS-App with this
running job?<br>
<br>
Regards<br>
a.<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Netarchivesuite-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Netarchivesuite-devel@ml.sbforge.org" moz-do-not-send="true">Netarchivesuite-devel@ml.sbforge.org</a>
<a class="moz-txt-link-freetext" href="https://ml.sbforge.org/mailman/listinfo/netarchivesuite-devel" moz-do-not-send="true">https://ml.sbforge.org/mailman/listinfo/netarchivesuite-devel</a>
</pre>
</blockquote>
<p><br>
</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Netarchivesuite-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Netarchivesuite-devel@ml.sbforge.org">Netarchivesuite-devel@ml.sbforge.org</a>
<a class="moz-txt-link-freetext" href="https://ml.sbforge.org/mailman/listinfo/netarchivesuite-devel">https://ml.sbforge.org/mailman/listinfo/netarchivesuite-devel</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>