Couch soft crashes and restart fails to bind to port
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
[NOTE]: # ( ^^ Provide a general summary of the issue in the title above. ^^ )
## Description
CouchDB service is running but has failed to bind to port even after restarting the service
## Steps to Reproduce
[NOTE]: # ( Include commands to reproduce, if possible. curl is preferred. )
install on Debian Buster, setup with standard dedicated database
## Expected Behaviour
Server to be active, bound to port and reporting well when I run status
## Your Environment
NGINX setup for front websites
the port is open, have used CouchDB web panel before
after possible crash or restart - software will not bind to port
this is the second time it has happened, last time it was fixed by resetting the admin password.
* CouchDB version used: 3.2.0
* Browser name and version: ANY
* Operating system and version: ANY
## Additional Context
I can't seem to get logging to log anything
output from console:
```
admin@server:/opt$ sudo netstat -tulpn | grep LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 5972/nginx: worker
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 563/sshd
tcp6 0 0 :::2080 :::* LISTEN 6854/node
tcp6 0 0 :::4080 :::* LISTEN 6846/node
tcp6 0 0 :::22 :::* LISTEN 563/sshd
admin@server:~$ /etc/init.d/couchdb status
● couchdb.service - Apache CouchDB
Loaded: loaded (/lib/systemd/system/couchdb.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-03-13 04:51:12 UTC; 15ms ago
Main PID: 32309 (couchdb)
Tasks: 3 (limit: 2330)
Memory: 612.0K
CGroup: /system.slice/couchdb.service
├─32309 /bin/sh /opt/couchdb/bin/couchdb
├─32317 /bin/sh /opt/couchdb/bin/couchdb
└─32319 /bin/sh /opt/couchdb/bin/couchdb
admin@server:~$ curl http://127.0.0.1:5984/
curl: (7) Failed to connect to 127.0.0.1 port 5984: Connection refused
```
Contributor guide
Research direction
Start with the Debian couchdb.service status and the curl request to 127.0.0.1:5984 shown in the report, then inspect the service's available logging and startup output. Done means identifying why CouchDB reports as running without listening on port 5984 and documenting a reproducible fix for restart failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, nginx
- Domain
- backend, databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100