I'm trying to use the eclipse delta pack, and I need to use the same exact version of the delta pack as the version of eclipse I'm using. When looking at Help>About Eclipse I see:
Version: 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f
Build id: I20110613-1736
However, it seems the versions listed on the eclipse site have a different format. Here are the versions listed here: http://archive.eclipse.org/eclipse/downloads/
3.7RC4 Fri, 3 Jun 2011 -- 09:09 (-0400)
3.7RC3 Thu, 26 May 2011 -- 17:08 (-0400)
3.7RC2 Thu, 19 May 2011 -- 11:38 (-0400)
3.7RC1 Thu, 12 May 2011 -- 20:00 (-0400)
3.7M7 Thu, 28 Apr 2011 -- 08:48 (-0400)
3.7M6 Thu, 10 Mar 2011 -- 11:19 (-0500)
3.7M5 Thu, 27 Jan 2011 -- 20:34 (-0500)
3.7M4 Wed, 8 Dec 2010 -- 13:00 (-0500)
3.7M3 Thu, 28 Oct 2010 -- 14:41 (-0400)
3.7M2a Tue, 21 Sep 2010 -- 10:24 (-0400)
3.7M1 Thu, 5 Aug 2010 -- 17:00 (-0400)
Which version do I use?
Assuming you have the latest version.
I would say you can go for 3.7RC4 Fri, 3 Jun 2011 -- 09:09 (-0400) looking at the Build id: I20110613-1736 - 2011 Jun 13 #17:36
You have the latest 3.7 build.
I20110613-1736 corresponds to 3.7 Mon, 13 Jun 2011 -- 17:36 (-0400)
It is not in the list of archived downloads you posted.
If you want you can try the one which is closest to yours: 3.7RC4 Fri, 3 Jun 2011 -- 09:09 (-0400)
Related
I'm running Lighthouse CI with a Azure DevOps YAML pipeline on a Windows agent and am getting cryptic errors. I run this command: npx lhci autorun and get this result:
Starting: Lighthouse Testing (windows_build_container)
==============================================================================
Task : Command line
Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version : 2.201.1
Author : Microsoft Corporation
Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
Script contents: shell
npm run ci:lighthouse
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\__w\_temp\769adb2-5ac7-4cfd-aff7-4efc2dc1b3b4.cmd""
> web#0.1.0 ci:lighthouse
> npx lhci autorun
✅ .lighthouseci/ directory writable
✅ Configuration file found
✅ Chrome installation found
Healthcheck passed!
Automatically determined ./public as `staticDistDir`.
Set it explicitly in lighthouserc.json if incorrect.
Started a web server on port 49236...
Running Lighthouse 3 time(s) on http://localhost:49236/index.html
Run #1...failed!
Error: Lighthouse failed with exit code 1
at ChildProcess.<anonymous> (C:\__w\1\s\web\node_modules\#lhci\cli\src\collect\node-runner.js:120:21)
at ChildProcess.emit (node:events:527:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
Wed, 06 Apr 2022 00:01:33 GMT LH:ChromeLauncher Waiting for browser.
Wed, 06 Apr 2022 00:01:33 GMT LH:ChromeLauncher Waiting for browser...
Wed, 06 Apr 2022 00:01:33 GMT LH:ChromeLauncher Waiting for browser.....
Wed, 06 Apr 2022 00:01:34 GMT LH:ChromeLauncher Waiting for browser.......
Wed, 06 Apr 2022 00:01:34 GMT LH:ChromeLauncher Waiting for browser.........
Wed, 06 Apr 2022 00:01:35 GMT LH:ChromeLauncher Waiting for browser...........
Wed, 06 Apr 2022 00:01:35 GMT LH:ChromeLauncher Waiting for browser.............
Wed, 06 Apr 2022 00:01:36 GMT LH:ChromeLauncher Waiting for browser...............
Wed, 06 Apr 2022 00:01:36 GMT LH:ChromeLauncher Waiting for browser.................
Wed, 06 Apr 2022 00:01:37 GMT LH:ChromeLauncher Waiting for browser...................
Wed, 06 Apr 2022 00:01:37 GMT LH:ChromeLauncher Waiting for browser.....................
Wed, 06 Apr 2022 00:01:38 GMT LH:ChromeLauncher Waiting for browser.......................
Wed, 06 Apr 2022 00:01:38 GMT LH:ChromeLauncher Waiting for browser.........................
Wed, 06 Apr 2022 00:01:39 GMT LH:ChromeLauncher Waiting for browser...........................
Wed, 06 Apr 2022 00:01:39 GMT LH:ChromeLauncher Waiting for browser.............................
Wed, 06 Apr 2022 00:01:40 GMT LH:ChromeLauncher Waiting for browser...............................
Wed, 06 Apr 2022 00:01:40 GMT LH:ChromeLauncher Waiting for browser.................................
Wed, 06 Apr 2022 00:01:41 GMT LH:ChromeLauncher Waiting for browser...................................
Wed, 06 Apr 2022 00:01:42 GMT LH:ChromeLauncher Waiting for browser.....................................
Wed, 06 Apr 2022 00:01:42 GMT LH:ChromeLauncher Waiting for browser.......................................
Wed, 06 Apr 2022 00:01:43 GMT LH:ChromeLauncher Waiting for browser.........................................
Wed, 06 Apr 2022 00:01:43 GMT LH:ChromeLauncher Waiting for browser...........................................
Wed, 06 Apr 2022 00:01:43 GMT LH:ChromeLauncher Waiting for browser...........................................√
Wed, 06 Apr 2022 00:01:44 GMT LH:config:warn IFrameElements gatherer requested, however no audit requires it.
Wed, 06 Apr 2022 00:01:44 GMT LH:config:warn FormElements gatherer requested, however no audit requires it.
Wed, 06 Apr 2022 00:01:44 GMT LH:status Connecting to browser
Wed, 06 Apr 2022 00:01:52 GMT LH:CriConnection:warn Cannot create new tab; reusing open tab.
Wed, 06 Apr 2022 00:01:52 GMT LH:status Disconnecting from browser...
Wed, 06 Apr 2022 00:01:52 GMT LH:status Cleaning origin data
Wed, 06 Apr 2022 00:01:52 GMT LH:CriConnection:error sendRawMessage() was called without an established connection.
Wed, 06 Apr 2022 00:01:52 GMT LH:GatherRunner disconnect:error sendRawMessage() was called without an established connection.
Wed, 06 Apr 2022 00:01:52 GMT LH:ChromeLauncher Killing Chrome instance 11444
Wed, 06 Apr 2022 00:01:53 GMT LH:ChromeLauncher:warn Chrome could not be killed Command failed: taskkill /pid 11444 /T /F
ERROR: The process "11444" not found.
Wed, 06 Apr 2022 00:01:53 GMT LH:CLI:warn Warning: Chrome process could not be killed because it already exited.
Unable to connect to Chrome
##[error]Cmd.exe exited with code '1'.
What does this error mean?
After much testing, I discovered that the agent I was using lacked certain graphics libraries for Chrome. This error essentially was saying Chrome was started but was impotent (Cannot create new tab) and was killed off.
try with the global form npx -g lhci autorun
i had the same problem but with lighthouse-batch for example:
lighthouse-batch -s <url> --> Local form
lighthouse-batch -g -s <url> --> Global form
you can also with more urls lighthouse-batch -g -s <url,url,url,url>
I have the following environment and I notice that the jobs are queued twice randomly after 2 minutes:
Web App based on PHP F3 framework
Pheanstalk 3.0.2 using composer in the app
Beanstalkd server
Beanstalkd console app
Supervisord
Worker scenario: entering multiple jobs to bulk delete clients
Issue: same job (already processed) is queued twice after 2 minutes with different ID
I use the following code:
$queue = new Pheanstalk\Pheanstalk("127.0.0.1:14803");
$queue->watch("tubeDelete");
while ($job = $queue->reserve()) {
$log->write("Entering Job {$job->getId()} \n");
$log->write("Job {$job->getId()} data : {$job->getData()} \n");
$data = json_decode($job->getData(), true);
try {
$deleteResponse = $client->deleteClient($clientId)
if($deleteResponse){
$log->write("client $clientId deleted successfully");
$queue->delete($job);
}else{
$log->write("Failed to delete client $clientId, check the log file");
$queue->bury($job);
}
} catch (Exception $e) {
$log->write("Failed to delete client $clientId with PHP exception, check the log file");
$queue->bury($job);
}
}
Log file:
Fri, 08 Dec 2017 13:00:23 +0200 Entering Job 92428501
Fri, 08 Dec 2017 13:00:23 +0200 Job 92428501 data : {"clientId":"1397"}
Fri, 08 Dec 2017 13:00:24 +0200 Client 1397 deleted successfully
Fri, 08 Dec 2017 13:00:24 +0200 Entering Job 92428502
Fri, 08 Dec 2017 13:00:24 +0200 Job 92428502 data : {"clientId":"1398"}
Fri, 08 Dec 2017 13:00:26 +0200 Client 1398 deleted successfully
Fri, 08 Dec 2017 13:00:26 +0200 Entering Job 92428503
Fri, 08 Dec 2017 13:00:26 +0200 Job 92428503 data : {"clientId":"1399"}
Fri, 08 Dec 2017 13:00:28 +0200 Client 1399 deleted successfully
Fri, 08 Dec 2017 13:00:28 +0200 Entering Job 92428504
Fri, 08 Dec 2017 13:00:28 +0200 Job 92428504 data : {"clientId":"1401"}
Fri, 08 Dec 2017 13:00:30 +0200 Client 1401 deleted successfully
Fri, 08 Dec 2017 13:00:30 +0200 Entering Job 92428505
Fri, 08 Dec 2017 13:00:30 +0200 Job 92428505 data : {"clientId":"1402"}
Fri, 08 Dec 2017 13:00:31 +0200 Client 1402 deleted successfully
Fri, 08 Dec 2017 13:00:31 +0200 Entering Job 92428506
Fri, 08 Dec 2017 13:00:31 +0200 Job 92428506 data : {"clientId":"1403"}
Fri, 08 Dec 2017 13:00:33 +0200 Client 1403 deleted successfully
Fri, 08 Dec 2017 13:00:33 +0200 Entering Job 92428507
Fri, 08 Dec 2017 13:00:33 +0200 Job 92428507 data : {"clientId":"1404"}
Fri, 08 Dec 2017 13:00:34 +0200 Client 1404 deleted successfully
Fri, 08 Dec 2017 13:00:34 +0200 Entering Job 92428508
Fri, 08 Dec 2017 13:00:34 +0200 Job 92428508 data : {"clientId":"1405"}
Fri, 08 Dec 2017 13:00:36 +0200 Client 1405 deleted successfully
Fri, 08 Dec 2017 13:00:36 +0200 Entering Job 92428509
Fri, 08 Dec 2017 13:00:36 +0200 Job 92428509 data : {"clientId":"1409"}
Fri, 08 Dec 2017 13:00:37 +0200 Client 1409 deleted successfully
Fri, 08 Dec 2017 13:00:37 +0200 Entering Job 92428510
Fri, 08 Dec 2017 13:00:37 +0200 Job 92428510 data : {"clientId":"1421"}
Fri, 08 Dec 2017 13:00:38 +0200 Client 1421 deleted successfully
Fri, 08 Dec 2017 13:02:23 +0200 Entering Job 92428511
Fri, 08 Dec 2017 13:02:23 +0200 Job 92428511 data : {"clientId":"1397"}
Fri, 08 Dec 2017 13:02:23 +0200 Client 1397 deleted successfully
Fri, 08 Dec 2017 13:02:23 +0200 Entering Job 92428512
Fri, 08 Dec 2017 13:02:23 +0200 Job 92428512 data : {"clientId":"1398"}
Fri, 08 Dec 2017 13:02:23 +0200 Client 1398 deleted successfully
Fri, 08 Dec 2017 13:02:23 +0200 Entering Job 92428513
Fri, 08 Dec 2017 13:02:23 +0200 Job 92428513 data : {"clientId":"1399"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1399 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428514
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428514 data : {"clientId":"1401"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1401 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428515
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428515 data : {"clientId":"1402"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1402 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428516
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428516 data : {"clientId":"1403"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1403 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428517
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428517 data : {"clientId":"1404"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1404 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428518
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428518 data : {"clientId":"1405"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1405 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428519
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428519 data : {"clientId":"1409"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1409 deleted successfully
Fri, 08 Dec 2017 13:02:24 +0200 Entering Job 92428520
Fri, 08 Dec 2017 13:02:24 +0200 Job 92428520 data : {"clientId":"1421"}
Fri, 08 Dec 2017 13:02:24 +0200 Client 1421 deleted successfully
So, you can find the repeated clients due to executing the same job after 2 minutes, for example:
Fri, 08 Dec 2017 13:00:23 +0200 Entering Job 92428501
Fri, 08 Dec 2017 13:00:23 +0200 Job 92428501 data : {"clientId":"1397"}
Fri, 08 Dec 2017 13:00:24 +0200 Client 1397 deleted successfully
Fri, 08 Dec 2017 13:02:23 +0200 Entering Job 92428511
Fri, 08 Dec 2017 13:02:23 +0200 Job 92428511 data : {"clientId":"1397"}
Fri, 08 Dec 2017 13:02:23 +0200 Client 1397 deleted successfully
Is it the issue related to TTR / DEADLINE_SOON / configuration issue or related to supervisord?
#! usr/bin/perl
#months=('Jan','feb','mar','apr','may','jun','jul','aug','sep','oct','nov','dec');
#new=('1','2');
print "#months\n";
splice(#months,0,1,#new);
print "#months\n";
When I run this I expect output to be as
Jan feb mar apr may jun jul aug sep oct nov dec
1 2 mar apr may jun jul aug sep oct nov dec
But I am getting output as
Jan feb mar apr may jun jul aug sep oct nov dec
1 2 feb mar apr may jun jul aug sep oct nov dec
The Feb should also be replaced by 2, right? But why it isn't happening.
Syntax of splice command is
splice ARRAY,OFFSET,LENGTH,LIST
You specify LENGTH to be 1, so only one element is removed from the original list (that element is Jan). If you want feb to be removed too, then you must use a LENGTH of 2
splice(#months, 0, 2, #new);
I perform the following query:
db.preference.find({}, {_id: 1}).sort({$natural: 1}).forEach(function(d) {
print(d._id.getTimestamp())
})
Here's part of the output:
Thu Mar 26 2015 12:39:06 GMT+0100 (CEST)
Thu Mar 26 2015 12:41:07 GMT+0100 (CEST)
Thu Mar 26 2015 12:48:55 GMT+0100 (CEST)
Mon Mar 30 2015 17:08:44 GMT+0200 (CEST)
Tue Mar 31 2015 12:34:36 GMT+0200 (CEST)
Tue Mar 31 2015 12:35:01 GMT+0200 (CEST)
Tue Mar 31 2015 12:34:47 GMT+0200 (CEST)
Thu Nov 20 2014 10:55:07 GMT+0100 (CEST)
Wed Apr 29 2015 10:02:33 GMT+0200 (CEST)
Wed Apr 29 2015 10:02:53 GMT+0200 (CEST)
Wed Apr 29 2015 10:03:13 GMT+0200 (CEST)
Wed Apr 29 2015 10:00:11 GMT+0200 (CEST)
Wed Apr 29 2015 10:18:23 GMT+0200 (CEST)
Mon Feb 23 2015 11:54:11 GMT+0100 (CEST)
Tue May 12 2015 16:40:45 GMT+0200 (CEST)
Fri May 15 2015 17:04:04 GMT+0200 (CEST)
Wed May 14 2014 18:13:40 GMT+0200 (CEST)
Tue Jun 09 2015 14:17:11 GMT+0200 (CEST)
Tue Jun 16 2015 16:03:31 GMT+0200 (CEST)
Tue Nov 04 2014 21:15:21 GMT+0100 (CEST)
Fri Mar 14 2014 10:16:48 GMT+0100 (CEST)
Wed Jun 17 2015 11:14:57 GMT+0200 (CEST)
Fri Mar 14 2014 10:15:30 GMT+0100 (CEST)
It's easy to see that the dates are seriously shuffled, while I expected strictly ascending order.
Collection is not capped, and the documents are often modified. ObjectIds are never generated in the code explicitly. Collection is not shared.
Any ideas why natural sorting works this way?
Can someone explain while natural ordering works in.
What did you expect?
Use the $natural operator to use natural order for the results of a
sort operation. Natural order refers to the logical ordering of
documents internally within the database.
The $natural operator uses the following syntax to return documents in
the order they exist on disk: ...
See MongoDB documentation.
I have a strange behavior on my g-wan server: each day at midnight g-wan loops on loading scripts. This is what I see in gwan.log:
[Tue Apr 09 00:00:00 2013 GMT] memory footprint: 1.47 MiB.
[Tue Apr 09 00:00:00 2013 GMT] Host /var/www/gwan/0.0.0.0_8082/#0.0.0.0
[Tue Apr 09 00:00:00 2013 GMT] log files enabled
[Tue Apr 09 00:00:00 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:00:00 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:00:00 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:f624bc05-f51507c3-61b20c9c-ecfe9e19
[Tue Apr 09 00:00:00 2013 GMT] Host /var/www/gwan/0.0.0.0_8083/#0.0.0.0
[Tue Apr 09 00:00:00 2013 GMT] log files enabled
[Tue Apr 09 00:00:00 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:00:00 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:00:00 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:525aa623-2728dd50-0e67a6ad-6763a30b
[Tue Apr 09 00:00:00 2013 GMT] memory footprint: 5.45 MiB.
[Tue Apr 09 00:00:01 2013 GMT] memory footprint: 1.47 MiB.
[Tue Apr 09 00:00:01 2013 GMT] Host /var/www/gwan/0.0.0.0_8082/#0.0.0.0
[Tue Apr 09 00:00:01 2013 GMT] log files enabled
[Tue Apr 09 00:00:01 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:00:01 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:00:01 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:f624bc05-f51507c3-61b20c9c-ecfe9e19
[Tue Apr 09 00:00:01 2013 GMT] Host /var/www/gwan/0.0.0.0_8083/#0.0.0.0
[Tue Apr 09 00:00:01 2013 GMT] log files enabled
[Tue Apr 09 00:00:01 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:00:01 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:00:01 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:525aa623-2728dd50-0e67a6ad-6763a30b
....
....
[Tue Apr 09 00:02:01 2013 GMT] memory footprint: 3.22 MiB.
[Tue Apr 09 00:02:01 2013 GMT] Host /var/www/gwan/0.0.0.0_8082/#0.0.0.0
[Tue Apr 09 00:02:01 2013 GMT] log files enabled
[Tue Apr 09 00:02:01 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:02:01 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:02:01 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:f624bc05-f51507c3-61b20c9c-ecfe9e19
[Tue Apr 09 00:02:01 2013 GMT] Host /var/www/gwan/0.0.0.0_8083/#0.0.0.0
[Tue Apr 09 00:02:01 2013 GMT] log files enabled
[Tue Apr 09 00:02:01 2013 GMT] loaded main.c 39.13 KiB MD5:15795d7c-42184ef2-c8075784-a3aa84aa
[Tue Apr 09 00:02:01 2013 GMT] loaded process_kv.c 44.44 KiB MD5:349b8978-bbebb4eb-120c6f1a-7d06f98e
[Tue Apr 09 00:02:01 2013 GMT] loaded Connection Handler main.c 18.71 KiB MD5:525aa623-2728dd50-0e67a6ad-6763a30b
[Tue Apr 09 00:02:01 2013 GMT] memory footprint: 7.13 MiB.
[Tue Apr 09 00:02:11 2013 GMT] ------------------------------------------------
[Tue Apr 09 00:02:11 2013 GMT] G-WAN 4.3.14 64-bit (Mar 14 2013 07:33:12)
[Tue Apr 09 00:02:11 2013 GMT] ------------------------------------------------
[Tue Apr 09 00:02:11 2013 GMT] Local Time: Tue, 09 Apr 2013 02:02:11 GMT+2
....
So during 2 minutes g-wan loops and after g-wan is started normally by monit I believe.
Do you have an explanation and a workaround?
I recently change my web hosting provider and from now I use a VM under Microsoft Hyper-V.
The problem remains: G-Wan is restarted by Monit which logged the following events:
Wed, 16 Oct 2013 02:02:12: process PID changed from 2171 to 20631
Wed, 16 Oct 2013 02:02:13: process PPID changed from 1 to 2171
Wed, 16 Oct 2013 02:02:43: process PID changed from 20631 to 20975
Wed, 16 Oct 2013 02:03:13: process PID changed from 20975 to 21318
Wed, 16 Oct 2013 02:03:44: process PID changed from 21318 to 21573
Wed, 16 Oct 2013 02:04:14: process PID changed from 21573 to 2171
Wed, 16 Oct 2013 02:04:14: process PPID changed from 2171 to 1
Wed, 16 Oct 2013 02:33:06: process is not running
Wed, 16 Oct 2013 02:33:37: process is running with pid 776
It happens every day even on my new VM with another hypervisor.
I am not the only one with this behavior.
Do you have an explanation and a workaround?
Thank you
Jerome
The loop means that the child process is not responding, hence the parent killing the old child and restarting a new child.
Could you email us the whole log files (trace and gwan.log)? Your partial post is missing the the informative parts.
UPDATE
That new problem for 4-years old code that worked fine so far is a platform issue, for which we have found a workaround, to be published with the next release in a few weeks.