I have only a few sparse thoughts: - you can get latest log lines at http://localhost:5984/_log
- have a look at /root/build-couchdb/build/etc/init.d/couchdb or consider using upstart (I have posted here a sample startup script a few days ago) - first check if default configuration works fine, then change one configuration option and check again. Iterate until the problem shows up. - being root is not enough to avoid permission problems. HTH, Marcello 2011/12/24 Mark Hahn <[email protected]>: >> Have you looked into /root/build-couchdb/build/var/log/couchdb/couch.log ? > > Thanks for pointing that out. That file only has old info in it since I > changed /root/build-couchdb/build/etc/couchdb/local.ini to the settings > shown here. > > --------------- local.ini -------------- > [couchdb] > database_dir = /mnt/db/couch_dbs > view_index_dir = /mnt/db/couch_views > uri_file = /mnt/db/couch.uri > > [httpd] > bind_address = 0.0.0.0 > > [couch_httpd_auth] > secret = xxxxxxxxxxxxxxxxxxxxxx > require_valid_user = true > > [log] > level = debug > include_sasl = false > file = /mnt/db/couch.log > > [admins] > root = -xxxxxxxxxxxxxxxxxxxxxxxxxx > > [uuids] > algorithm = utc_random > > > After booting, /mnt/db/ is there, but the log file is missing. It isn't > being created. There is no permission issue since everything is running as > root. > > I just now discovered that when I run couchdb manually, futon works fine > but I'm still not getting a log file created. > > Is it possible this log problem is the root of the big problem? Can I > debug to find out where the log is ending up? I did a find / -name > *couchdb.log and only the one old location showed up. Can couch run > without a log file? > > I looked at the db configuration using futon and it matched my local.ini > file. > > Have I given any new hints to the problem? I need more help.
