couchdb 0.8.1 does not fully start

[sethladd@…]

Hello,

I've installed couchdb 0.8.1 via macports, but when I run it via the command line, it does not fully initialize and start.

Asking on #couchdb, they seem to believe it's an issue the macports version, and that they have heard this before. CouchDB servers installed from source work fine.

Here's what I see when I start couchdb:

seth-ladds-macbook-pro:Development sethladd$ sudo couchdb
Apache CouchDB 0.8.1-incubating (LogLevel=info)
Apache CouchDB is starting.

Config Info /opt/local/etc/couchdb/couch.ini:
	CurrentWorkingDir=/Users/sethladd/Development
	DbRootDir=/opt/local/var/lib/couchdb
	BindAddress="127.0.0.1"
	Port="5984"
	DocumentRoot=/opt/local/share/couchdb/www
	LogFile=/opt/local/var/log/couchdb/couch.log
	UtilDriverDir=/opt/local/lib/couchdb/erlang/lib/couch-0.8.1-incubating/priv/lib
	DbUpdateNotificationProcesses=
	FullTextSearchQueryServer=
	javascript=/opt/local/bin/couchjs /opt/local/share/couchdb/server/main.js

I have confirmed, via netstat, that the port is never opened and that the directories like /opt/local/var/lib/couchdb are never created.

[mf2k (Frank Schima)]

Assigning to maintainer.

[oddsimons@…]

The install script needs to create the directory for the log file, so try this manually and see if that fixes it for you as well:

> sudo mkdir -p /opt/local/var/log/couchdb/
> /opt/local/bin/couchdb
Apache CouchDB 0.8.1-incubating (LogLevel=info)
Apache CouchDB is starting.

Apache CouchDB has started. Time to relax.

The same directory creation is missing from the couchdb-devel version as well. Both work fine once the log directory is created.

[oddsimons@…]

Heh. My mistake in the commands write-up - it needs to be sudo /opt/local/bin/couchdb of course...

[oddsimons@…]

Fix by creating directory with proper permissions was confirmed by another user on the CouchDB IRC channel today.

[oddsimons@…]

Some further digging into the issue made me discover the +server variant of the port. So this actually works:

sudo port install couchdb +server
# or
sudo port install couchdb-devel +server

I think most users would expect to be able to serve databases when installing couchdb, and especially since the startup item is not enabled by default anyway. Is there really a good reason for keeping this variant? A CouchDB install as client/libs-only does not make all that much sense to me - but if it does to someone then the /opt/local/bin/coucdb startup script shouldn't be created either when not +server. It is very confusing.

BTW, the URL for the repository has changed now that CouchDB has graduated from incubator. New URL is http://svn.apache.org/repos/asf/couchdb/trunk.

[jyrkiwahlstedt]

Hi, sorry for the late comment. Probably I'll do not change this for the current version, but this might be a good idea to implement, when a new version is released. I'd guess the server variant will be default, then (it just is usual to make a server variant for this type of port). Thanks for the update of the development version URL, this seems to be quite new, as I regularly livecheck the ports, and this affects the check.

[(none)]

Milestone Port Bugs deleted