I have developed NodeJS application and using OrientDB database in our project. Everything works fine until we left the application idle for sometime. We are facing time out error in OrientDB.
Please find the error below:
Unhandled rejection OrientDB.ConnectionError [2]: read ETIMEDOUT
at Connection.handleSocketError (/home/myuser/sample_app/node_modules/orientjs/lib/transport/binary/connection.js:352:9)
at Socket.emit (events.js:315:20)
at Socket.EventEmitter.emit (domain.js:485:12)
at emitErrorNT (internal/streams/destroy.js:100:8)
at emitErrorCloseNT (internal/streams/destroy.js:68:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Please advice
Related
I am using Elasticsearch6.8.3 docker on an AWS ec2 machine for the production environment. For this purpose, I have installed Elasticsearch via docker-compose. In a microservice architecture many of the other services using different languages like PHP and Python, are just working fine. But When it comes to the Node.js client it starts throwing this error:
Connect EADDRNOTAVAIL IP_ADDRESS:9200 - Local (IP_ADDRESS:0)
at onResponse (/var/app/current/node_modules/#elastic/elasticsearch/lib/Transport.js:228:13)
at ClientRequest.<anonymous>
(/var/app/current/node_modules/#elastic/elasticsearch/lib/Connection.js:113:9)
at ClientRequest.emit (events.js:314:20)
at ClientRequest.EventEmitter.emit (domain.js:483:12)
at Socket.socketErrorListener (_http_client.js:427:9)
at Socket.emit (events.js:314:20)
at Socket.EventEmitter.emit (domain.js:483:12)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
I have also verified the docker container is up and running at that time, as it was accessible through the web browser. I am not sure about the problem that is it a Node client issue or there is something wrong with docker networking? Also right after restarting the docker container, everything started working
I Suddenly got the below issue when I tried to run my next js project. it was run perfectly before and this happen without any changes in the system. Any idea regarding this
yarn run v1.22.17
$ next dev
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc.js" https://nextjs.org/docs/messages/swc-disabled
info - Using external babel configuration from /Users/subodha/Subodha/lab/rpm-web/.babelrc.js
postcss-resolve-url: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
node:events:368
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:211:20)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:28)
at TLSSocket.emit (node:domain:475:12)
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -54,
code: 'ECONNRESET',
syscall: 'read'
}
Node.js v17.2.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
subodha#Subodhas-MacBook-Pro rpm-web %```
I gave the same error.
To solve them, I disabled my VPN connection and built it successfully.
so this error should happen for your network connection.
i got the same error when i was using a vpn or without a vpn.
using another vpn solved this issue.
I want to integrate Botium Community Edition with our Kore.ai platform. I've created a Webhook channel and set the generated Webhook Url, Client ID and Client Secret in my testbot on Botium. When I select Live Chat and hit Connect I get a 'ChatBot Connected' message. However, when I try to chat with my bot I get the following error:
Failed sending to chatbot: rest request failed: { Error: tunneling socket could not be
established, cause=connect ECONNREFUSED 127.0.0.1:80 at ClientRequest.onError
(/app/server/node_modules/tunnel-agent/index.js:177:17) at Object.onceWrapper
(events.js:285:13) at ClientRequest.emit (events.js:197:13) at Socket.socketErrorListener
(_http_client.js:397:9) at Socket.emit (events.js:197:13) at emitErrorNT
(internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at
processTicksAndRejections (internal/process/next_tick.js:76:17) code: 'ECONNRESET' }
Please advice! Thanks!
I attempted to follow the guide here https://cloud.google.com/appengine/docs/flexible/nodejs/using-cloud-sql-postgres
to integrate my app with the Cloud SQL postgres instance. However I keep getting an error:
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Error Response: [9] Application startup
error:
testpostgres#1.0.0 start /app node app.js
Unhandled rejection SequelizeConnectionError: connect ENOENT
/cloudsql/test-postgress:us-central1:testpostgress/.s.PGSQL.5432 at
connection.connect.err
(/app/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:128:24) at Connection.connectingErrorHandler
(/app/node_modules/pg/lib/client.js:123:14) at emitOne
(events.js:116:13) at Connection.emit (events.js:211:7) at
Socket.reportStreamError
(/app/node_modules/pg/lib/connection.js:71:10) 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)
It must be a problem with my configuration, but I have tried everything I can think of. You can see or clone my project here:
https://github.com/fractalfrenzy/GCS_postgres_test
I know nothing of Node.js, but have a long experience with Java/Python/Go runtime.
Have you opened your CloudSQL instance for connection?
Try this: Configuring IP Connectivity
I keep getting this error while trying to set up this skeleton application. I have no idea how to fix it sadly. Any input would be much appreciated. I'm just trying to get the darn thing up.
C:\Users\x\Desktop\mean-stripdown-master>node server
Express app started on port 3000
events.js:72
throw er; // Unhandled 'error' event
^
Error: failed to connect to [localhost:27017]
at null.<anonymous> (C:\Users\x\Desktop\mean-stripdown-master\node_modul
es\mongoose\node_modules\mongodb\lib\mongodb\connection\server.js:540:74)
at EventEmitter.emit (events.js:106:17)
at null.<anonymous> (C:\Users\x\Desktop\mean-stripdown-master\node_modul
es\mongoose\node_modules\mongodb\lib\mongodb\connection\connection_pool.js:140:1
5)
at EventEmitter.emit (events.js:98:17)
at Socket.<anonymous> (C:\Users\x\Desktop\mean-stripdown-master\node_mod
ules\mongoose\node_modules\mongodb\lib\mongodb\connection\connection.js:478:10)
at Socket.EventEmitter.emit (events.js:95:17)
at net.js:441:14
at process._tickCallback (node.js:415:13)