couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1106) After Mac OS X update can not connect to CouchDB (10.6.6 0 => 10.6.7)
Date Tue, 19 Apr 2011 00:41:05 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021363#comment-13021363
] 

Dave Cottlehuber commented on COUCHDB-1106:
-------------------------------------------

Aram that's very odd. Normally we should see a whole lot more - mine is at https://gist.github.com/924372
for example. In particular there's nothing here about starting up couchdb - it's as if you're
only starting an erlang shell instead of couchdb itself.

Can you update local.ini to use debug level logging please & then from the Eshell you
get after running couchdb -i as user couchdb, can you send back the console output, via pastebin
or friendpaste?

os:getenv().
i().
m().
regs().
couch:stop().
crypto:stop().
crypto:start().
couch:start().

A+
Dave


> After Mac OS X update can not connect to CouchDB (10.6.6 0 => 10.6.7)
> ---------------------------------------------------------------------
>
>                 Key: COUCHDB-1106
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1106
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 1.0.1, 1.0.2
>            Reporter: Aram Karapetyan
>            Priority: Critical
>              Labels: installation, mac, tcpport
>
> After updating Mac OS X to 10.6.7 had problem connecting to couchdb and noticed that
it's running but not listening port.
> There are no logs. Even log file is missing and there is nothing in syslog. Launchctl
is stopping starting correctly without any error.
> I used macports to install couchdb 4 months ago it was fine before update.
> I tried to remove everything somehow connected to couchdb and setup new one but result
is same.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message