starred/ambar
1
0
Fork 0
mirror of https://github.com/RD17/ambar.git synced 2026-04-25 15:35:49 +03:00
Code Issues 2 Projects Releases 3 Packages Wiki Activity

[GH-ISSUE #167] connection errors to http://serviceapi:8080/api/logs #163

New issue
Closed
opened 2026-02-27 15:55:24 +03:00 by kerem · 4 comments
kerem commented 2026-02-27 15:55:24 +03:00
Owner
Copy link

Originally created by @chesty on GitHub (Jun 21, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/167

This is amazing software for such a small team, which I think is 1. well done.

Should the apiURL in config.js https://github.com/RD17/ambar/blob/master/LocalCrawler/src/config.js for the crawlers be http://webapi:8080 ?

This is from a crawler

{ RequestError: Error: connect ECONNREFUSED 172.22.0.6:8080
    at new RequestError (/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/node_modules/request/request.js:186:22)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at Request.onRequestError (/node_modules/request/request.js:878:8)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at Socket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  name: 'RequestError',
  message: 'Error: connect ECONNREFUSED 172.22.0.6:8080',
  cause: 
   { Error: connect ECONNREFUSED 172.22.0.6:8080
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)
     code: 'ECONNREFUSED',
     errno: 'ECONNREFUSED',
     syscall: 'connect',
     address: '172.22.0.6',
     port: 8080 },
  error: 
   { Error: connect ECONNREFUSED 172.22.0.6:8080
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)
     code: 'ECONNREFUSED',
     errno: 'ECONNREFUSED',
     syscall: 'connect',
     address: '172.22.0.6',
     port: 8080 },
  options: 
   { uri: 'http://serviceapi:8080/api/logs',
     method: 'POST',
     body: '{"source_id":"group-drive","type":"info","message":"Creating fork for the file-watcher process","created_datetime":"2018-06-20 15:00:03.148"}',
     headers: { 'Content-Type': 'application/json' },
     callback: [Function: RP$callback],
     transform: undefined,
     simple: true,
     resolveWithFullResponse: false,
     transform2xxOnly: false },
  response: undefined }
Originally created by @chesty on GitHub (Jun 21, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/167 This is amazing software for such a small team, which I think is 1. well done. Should the apiURL in config.js https://github.com/RD17/ambar/blob/master/LocalCrawler/src/config.js for the crawlers be http://webapi:8080 ? This is from a crawler ``` { RequestError: Error: connect ECONNREFUSED 172.22.0.6:8080 at new RequestError (/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/node_modules/request/request.js:186:22) at emitOne (events.js:116:13) at Request.emit (events.js:211:7) at Request.onRequestError (/node_modules/request/request.js:878:8) at emitOne (events.js:116:13) at ClientRequest.emit (events.js:211:7) at Socket.socketErrorListener (_http_client.js:387:9) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at emitErrorNT (internal/streams/destroy.js:64:8) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickCallback (internal/process/next_tick.js:180:9) name: 'RequestError', message: 'Error: connect ECONNREFUSED 172.22.0.6:8080', cause: { Error: connect ECONNREFUSED 172.22.0.6:8080 at Object._errnoException (util.js:1022:11) at _exceptionWithHostPort (util.js:1044:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) code: 'ECONNREFUSED', errno: 'ECONNREFUSED', syscall: 'connect', address: '172.22.0.6', port: 8080 }, error: { Error: connect ECONNREFUSED 172.22.0.6:8080 at Object._errnoException (util.js:1022:11) at _exceptionWithHostPort (util.js:1044:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) code: 'ECONNREFUSED', errno: 'ECONNREFUSED', syscall: 'connect', address: '172.22.0.6', port: 8080 }, options: { uri: 'http://serviceapi:8080/api/logs', method: 'POST', body: '{"source_id":"group-drive","type":"info","message":"Creating fork for the file-watcher process","created_datetime":"2018-06-20 15:00:03.148"}', headers: { 'Content-Type': 'application/json' }, callback: [Function: RP$callback], transform: undefined, simple: true, resolveWithFullResponse: false, transform2xxOnly: false }, response: undefined } ```
kerem 2026-02-27 15:55:24 +03:00
kerem commented 2026-02-27 15:55:25 +03:00
Author
Owner
Copy link

@sochix commented on GitHub (Jun 28, 2018):

Yep, it should.

<!-- gh-comment-id:400969879 --> @sochix commented on GitHub (Jun 28, 2018): Yep, it should.
kerem commented 2026-02-27 15:55:25 +03:00
Author
Owner
Copy link

@ratio91 commented on GitHub (Aug 1, 2018):

+1
I also have this problem. Can you please fix this and upload a new build on docker hub? thanks!

<!-- gh-comment-id:409544916 --> @ratio91 commented on GitHub (Aug 1, 2018): +1 I also have this problem. Can you please fix this and upload a new build on docker hub? thanks!
kerem commented 2026-02-27 15:55:25 +03:00
Author
Owner
Copy link

@musical10441 commented on GitHub (Aug 10, 2018):

+1

<!-- gh-comment-id:412210372 --> @musical10441 commented on GitHub (Aug 10, 2018): +1
kerem commented 2026-02-27 15:55:26 +03:00
Author
Owner
Copy link

@stale[bot] commented on GitHub (Sep 10, 2018):

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.

<!-- gh-comment-id:419949950 --> @stale[bot] commented on GitHub (Sep 10, 2018): 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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v2.1.18
v2.1.8
v2.0.0rc
Labels
Clear labels   
$$ Paid Support

   
bug

   
bug

   
enhancement

   
help wanted

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
wontfix
No labels
$$ Paid Support
bug
bug
enhancement
help wanted
invalid
pull-request
question
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ambar#163
No description provided.