I'm trying to run tests using Karma + HeadlessChrome from an amzn2 AMI (I have a Jenkins installed there).
The tests run successful from my local machine, however I'm getting stuck when trying to execute them in Jenkins.
I changed the log level of Karma to debug and this is the relevant output:
14 07 2020 06:51:39.801:INFO [karma-server]: Karma v4.1.0 server started at http://0.0.0.0:9876/
14 07 2020 06:51:39.804:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency unlimited
14 07 2020 06:51:39.815:INFO [launcher]: Starting browser ChromeHeadless
14 07 2020 06:51:39.815:DEBUG [launcher]: null -> BEING_CAPTURED
14 07 2020 06:51:39.816:DEBUG [temp-dir]: Creating temp dir at /tmp/karma-99510655
[...]
14 07 2020 06:51:56.165:DEBUG [karma-server]: A browser has connected on socket 1HnLJZHDqfyg-11TAAAA
14 07 2020 06:51:56.187:DEBUG [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: undefined -> CONNECTED
14 07 2020 06:51:56.187:INFO [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: Connected on socket 1HnLJZHDqfyg-11TAAAA with id 99510655
14 07 2020 06:51:56.189:DEBUG [launcher]: BEING_CAPTURED -> CAPTURED
14 07 2020 06:51:56.189:DEBUG [launcher]: ChromeHeadless (id 99510655) captured in 16.382 secs
14 07 2020 06:51:56.191:DEBUG [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: CONNECTED -> CONFIGURING
[...]
14 07 2020 06:51:57.356:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/vendor.js
14 07 2020 06:51:58.119:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/vendor.js
14 07 2020 06:51:58.128:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/vendor.js
14 07 2020 06:51:59.599:DEBUG [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: Disconnected during run, waiting 2000ms for reconnecting.
14 07 2020 06:51:59.605:DEBUG [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: CONFIGURING -> EXECUTING_DISCONNECTED
14 07 2020 06:52:01.610:WARN [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: Disconnected (0 times)reconnect failed before timeout of 2000ms (transport close)
14 07 2020 06:52:01.610:DEBUG [HeadlessChrome 84.0.4147 (Linux 0.0.0)]: EXECUTING_DISCONNECTED -> DISCONNECTED
HeadlessChrome 84.0.4147 (Linux 0.0.0) ERROR
Disconnectedreconnect failed before timeout of 2000ms (transport close)
HeadlessChrome 84.0.4147 (Linux 0.0.0) ERROR
Disconnectedreconnect failed before timeout of 2000ms (transport close)
14 07 2020 06:52:01.683:DEBUG [launcher]: CAPTURED -> BEING_KILLED
14 07 2020 06:52:01.684:DEBUG [launcher]: BEING_KILLED -> BEING_FORCE_KILLED
14 07 2020 06:52:01.709:DEBUG [karma-server]: Run complete, exiting.
14 07 2020 06:52:01.710:DEBUG [launcher]: Disconnecting all browsers
14 07 2020 06:52:01.710:DEBUG [launcher]: BEING_FORCE_KILLED -> BEING_FORCE_KILLED
14 07 2020 06:52:01.736:DEBUG [launcher]: Process ChromeHeadless exited with code null and signal SIGTERM
Following https://github.com/karma-runner/karma-chrome-launcher/issues/137 I'm using Puppeteer:
I've added process.env.CHROME_BIN = require('puppeteer').executablePath() in the karma.conf.js and:
logLevel: config.LOG_DEBUG,
autoWatch: true,
browsers: ['ChromeHeadlessNoSandbox'],
customLaunchers: {
ChromeHeadlessNoSandbox: {
base: 'ChromeHeadless',
flags: ['--no-sandbox']
}
},
I don't know what else I can try, any ideas?
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?
When i try to do base line index it is getting success but ProductCatalogOutputConfig returining zero results. I am using 11.2 version.
I have verified my switching datas and site ids for all(catalog,category,products,skus). all are being properly associated. even i able to generate the test data from ProductCatalogOutputConfig compononent in dyn/admin.
PreIndexing (Duration: 0:00:00)
/atg/commerce/endeca/index/CategoryTreeService COMPLETE (Succeeded) RepositoryExport (Duration: 0:00:11)
/atg/commerce/endeca/index/SchemaExporter *79* 0 COMPLETE (Succeeded)
/atg/commerce/endeca/index/CategoryToDimensionOutputConfig *18* 0 COMPLETE (Succeeded)
/atg/commerce/endeca/index/RepositoryTypeDimensionExporter *15* 0 COMPLETE (Succeeded)
/atg/commerce/search/ProductCatalogOutputConfig *0* 0 COMPLETE (Succeeded)
EndecaIndexing (Duration: 0:00:37)
/atg/commerce/endeca/index/EndecaScriptService COMPLETE (Succeeded)
I have enabled debug for bulk load component and noticed one error like in the below
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691248 /atg/search/repository/BulkLoader itemDescriptor: [ItemDesc: product]
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691249 /atg/search/repository/BulkLoader repositoryView: atg.adapter.gsa.GSAView#21be285c
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691250 /atg/search/repository/BulkLoader client calling take() with 0 items in item queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691250 /atg/search/repository/BulkLoader ProcessRanges() calling take() with 0 items in range queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691259 /atg/search/repository/BulkLoader Got: 4
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691259 /atg/search/repository/BulkLoader batchCount:20,000, startIndex:0, endIndex:20,000
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader ii=0, lastItem=null, query options=range 0-20000<sortby>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader <sortbyvalue value="id" dir=ascending case sensitive>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691266 /atg/search/repository/BulkLoader </sortby>
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691275 /atg/search/repository/BulkLoader ids == [], size=0
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691277 /atg/search/repository/BulkLoader createIdRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691277 /atg/search/repository/BulkLoader ProcessRanges() took range: IdRange{firstItem:null, lastItem:null, inclusive?: false, terminal?:true}
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691280 /atg/search/repository/BulkLoader Put: 4
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691280 /atg/search/repository/BulkLoader First page returned 4 items.
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691281 /atg/search/repository/BulkLoader ProcessRanges() calling take() with 1 items in range queue
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691283 /atg/search/repository/BulkLoader ProcessRanges() took range: IdRange{firstItem:null, lastItem:null, inclusive?: false, terminal?:true}
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691285 /atg/search/repository/BulkLoader processRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691288 /atg/search/repository/BulkLoader processRanges() thread is done
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691289 /atg/search/repository/BulkLoader Interrupting taker thread: Thread[Thread-90,5,Pooled Threads]
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader Interrupted fetching via ThreadedItemQueue java.lang.InterruptedException
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.ThreadedItemQueue.take(ThreadedItemQueue.java:383)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.fetchItemsUsingThreadedQueue(BulkLoaderImpl.java:530)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.loadPagedIteration(BulkLoaderImpl.java:599)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.BulkLoaderImpl.bulkLoad(BulkLoaderImpl.java:997)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1771)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.repository.search.indexing.IndexingOutputConfig.bulkLoadForDiagnostics(IndexingOutputConfig.java:1715)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.EndecaIndexingOutputConfig.performBaselineUpdate(EndecaIndexingOutputConfig.java:1197)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingTask.doTask(IndexingTask.java:445)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingTask.performTask(IndexingTask.java:388)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.endeca.index.admin.IndexingPhase$IndexingTaskJob.invoke(IndexingPhase.java:501)
debug Tue Jul 19 19:11:31 +05:30 2016 1468935691290 /atg/search/repository/BulkLoader at atg.common.util.ThreadDispatcherThread.run(ThreadDispatcherThread.java:178)
Please help me out from this issue.
I deployed a site successfully a few days ago and was able to configure logins and do other stuff but today it is down. The strange thing is I deploy to a different location without any changes and now I couldn't even access the page to configure stuff. I don't really know how to debug these things. Here is the logs
[Wed Sep 11 2013 15:19:16 GMT+0000 (UTC)] INFO STATUS waiting -> starting
[Wed Sep 11 2013 15:19:16 GMT+0000 (UTC)] INFO STATUS starting -> running
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING timers.js:103
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING ^
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING if (!process.listeners('uncaughtException').length) throw e;
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] WARNING Error: Could not locate any valid servers in initial seed list
at MongoClient.connect.connectFunction (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/mongo_client.js:281:52)
at Db.open (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/db.js:267:16)
at Server.connect.connectionPool.on.server._serverState (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/server.js:499:7)
at EventEmitter.emit (events.js:126:20)
at connection.on._self._poolState (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:168:15)
at EventEmitter.emit (events.js:99:17)
at Socket.timeoutHandler (/meteor/containers/6c32717b-367c-bd8f-b229-ad69088fe830/bundle/programs/server/npm/mongo-livedata/main/node_modules/mongodb/lib/mongodb/connection/connection.js:463:10)
at Socket.EventEmitter.emit (events.js:93:17)
at Socket._onTimeout (net.js:188:8)
at Timer.list.ontimeout (timers.js:101:19)
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] ERROR Application crashed with code: 1
[Wed Sep 11 2013 15:19:17 GMT+0000 (UTC)] INFO STATUS running -> waiting
Given the timing, looks like the very brief outage from this morning. Could you check it again and let me know if everything is back to normal?
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.