[GH-ISSUE #238] Getting crawl errors for ambar instance. #232

New issue

Closed

opened 2026-02-27 15:55:45 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:55:45 +03:00

Owner

Originally created by @abpattnayakAptus on GitHub (May 14, 2019).
Original GitHub issue: https://github.com/RD17/ambar/issues/238

I was fiddling with custom tagging but i keep getting these errors in the crawling. I am also not seeing any changes in the logs for ambar pipeline. Maybe i am looking in the wrong place. Can someone please help me out ?

my-files_1 | { RequestError: Error: connect ECONNREFUSED 192.168.48.6:8080 my-files_1 | at new RequestError (/node_modules/request-promise-core/lib/errors.js:14:15) my-files_1 | at Request.plumbing.callback (/node_modules/request-promise-core/lib/plumbing.js:87:29) my-files_1 | at Request.RP$callback [as _callback] (/node_modules/request-promise-core/lib/plumbing.js:46:31) my-files_1 | at self.callback (/node_modules/request/request.js:185:22) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at Request.emit (events.js:211:7) my-files_1 | at Request.onRequestError (/node_modules/request/request.js:881:8) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at ClientRequest.emit (events.js:211:7) my-files_1 | at Socket.socketErrorListener (_http_client.js:387:9) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at Socket.emit (events.js:211:7) my-files_1 | at emitErrorNT (internal/streams/destroy.js:64:8) my-files_1 | at _combinedTickCallback (internal/process/next_tick.js:138:11) my-files_1 | at process._tickCallback (internal/process/next_tick.js:180:9) my-files_1 | name: 'RequestError', my-files_1 | message: 'Error: connect ECONNREFUSED 192.168.48.6:8080',

#162 I have gone through this issue and it is different than my case.

Originally created by @abpattnayakAptus on GitHub (May 14, 2019). Original GitHub issue: https://github.com/RD17/ambar/issues/238 I was fiddling with custom tagging but i keep getting these errors in the crawling. I am also not seeing any changes in the logs for ambar pipeline. Maybe i am looking in the wrong place. Can someone please help me out ? ` my-files_1 | { RequestError: Error: connect ECONNREFUSED 192.168.48.6:8080 my-files_1 | at new RequestError (/node_modules/request-promise-core/lib/errors.js:14:15) my-files_1 | at Request.plumbing.callback (/node_modules/request-promise-core/lib/plumbing.js:87:29) my-files_1 | at Request.RP$callback [as _callback] (/node_modules/request-promise-core/lib/plumbing.js:46:31) my-files_1 | at self.callback (/node_modules/request/request.js:185:22) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at Request.emit (events.js:211:7) my-files_1 | at Request.onRequestError (/node_modules/request/request.js:881:8) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at ClientRequest.emit (events.js:211:7) my-files_1 | at Socket.socketErrorListener (_http_client.js:387:9) my-files_1 | at emitOne (events.js:116:13) my-files_1 | at Socket.emit (events.js:211:7) my-files_1 | at emitErrorNT (internal/streams/destroy.js:64:8) my-files_1 | at _combinedTickCallback (internal/process/next_tick.js:138:11) my-files_1 | at process._tickCallback (internal/process/next_tick.js:180:9) my-files_1 | name: 'RequestError', my-files_1 | message: 'Error: connect ECONNREFUSED 192.168.48.6:8080', ` #162 I have gone through this issue and it is different than my case.

kerem

2026-02-27 15:55:45 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-27 15:55:45 +03:00

Author

Owner

@SiddhantRoutray commented on GitHub (May 14, 2019):

I also faced the same issues when I tried working on it.

@SiddhantRoutray commented on GitHub (May 14, 2019): I also faced the same issues when I tried working on it.

kerem commented

2026-02-27 15:55:45 +03:00

Author

Owner

@RaginiSharma17 commented on GitHub (May 14, 2019):

I tried doing the same but I'm not able to proceed with the desired log messages.

@RaginiSharma17 commented on GitHub (May 14, 2019): I tried doing the same but I'm not able to proceed with the desired log messages.

kerem commented

2026-02-27 15:55:45 +03:00

Author

Owner

@smstern commented on GitHub (May 17, 2019):

I faced the same issue and found a workaround.

From my POV the crawler wants to connect to the wrong instance. The crawler should connect to the webapi instance instead of the configured (see src/config.js) serviceapi.

The workaround for now can be applied by adding the links block as shown here.

     image: ambar/ambar-local-crawler
     links:
       - webapi:serviceapi
     restart: always

@smstern commented on GitHub (May 17, 2019): I faced the same issue and found a workaround. From my POV the crawler wants to connect to the wrong instance. The crawler should connect to the `webapi` instance instead of the configured (see src/config.js) `serviceapi`. The workaround for now can be applied by adding the `links` block as shown here. ``` image: ambar/ambar-local-crawler links: - webapi:serviceapi restart: always ```

kerem commented

2026-02-27 15:55:45 +03:00

Author

Owner

@stale[bot] commented on GitHub (Jun 1, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 1, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.