You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2021/12/20 01:51:18 UTC
[GitHub] [couchdb-nano] trames57 opened a new issue #287: Error happened in your connection
trames57 opened a new issue #287:
URL: https://github.com/apache/couchdb-nano/issues/287
<!--- Provide a general summary of the issue in the Title above -->
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
Connection to couchdb database should happen
<!--- If you're suggesting a change/improvement, tell us how it should work -->
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
When trying to connect to couchdb, I get an "error happened in your connection". This started when I upgraded my Linode Arch Linux system to:
Linux kernel 5.15.10
Node 17.2 (and subsequently to 17.3 which did not help)
Couchdb 3.2.0-2
I did update the nano package in my website to 9.0.5, but no help
The error is in nano/lib/nano.js at statement 137 (socket error)
I debugged that statement and I get a status code 500 back
I did downgrade the Node package to 16.11.1 and 2 other dependent packages (brotli and icu). The website then worked fine. The problem is that couchdb 3.2.0 needs the icu-70 package and I had to downgrade that to icu-69.1. When I rebooted the system today, couchdb then failed. So my current workaround is that once the system reboots and couchdb starts, I can downgrade Node again. Ouch.
At the command line doing a curl http://localhost:5984/<db> works fine. So I can connect to couchdb and it is returning a response. I assume that something changed in Node 17 with socket handling, but I am not sure what.
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->
## Steps to Reproduce (for bugs)
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1.
2.
3.
4.
## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
## Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->
Linode with Arch Linux installed
Linux kernel 5.15.10
Node 17.2 (and subsequently to 17.3 which did not help)
Couchdb 3.2.0-2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-nano] trames57 commented on issue #287: Error happened in your connection
Posted by GitBox <gi...@apache.org>.
trames57 commented on issue #287:
URL: https://github.com/apache/couchdb-nano/issues/287#issuecomment-998179655
I was able to get everything working on my local machine with all the upgrades. Not sure why it is not working with the Linode VM. I suspect it is something other than nano or node, so closing this issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-nano] trames57 closed issue #287: Error happened in your connection
Posted by GitBox <gi...@apache.org>.
trames57 closed issue #287:
URL: https://github.com/apache/couchdb-nano/issues/287
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org