QnaList > Groups > Couchdb-User > Jan 2014
faq

Cannot Connect To CouchDb On Windows 7 64 Bit Professional

Hello,
Service starts successfully but cannot connect.Tried netstat but don't see
the port used.
No log file created.
Trying to run from Start menu (couchdb.bat) I get this in Erlan console:
Erlang R14B04 (erts-5.8.5) [source] [smp:16:16] [rq:16] [async-threads:0]
Eshell V5.8.5  (abort with ^G)
1> {"init terminating in
do_boot",{{badmatch,{error,{{app_would_not_start,os_mon},{couch_app,start,[normal,["../etc/couchdb/default.ini","../etc/couchdb/local.ini"]]}}}},[{couch,start,0},{init,start_it,1},{init,start_em,1}]}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
Abnormal termination
And erl_crash.dump was not found on the machine...
Thanks,
Boaz

asked Jan 30 2014 at 02:54

Boaz Citrin 's gravatar image



14 Replies for : Cannot Connect To CouchDb On Windows 7 64 Bit Professional
Try 'erl' (or 'werl'?) then 'application:start(os_mon).' excluding single quotes and including the dot, and report what it says.

answered Jan 30 2014 at 03:06

Robert Samuel Newson 's gravatar image


answered Jan 30 2014 at 05:39

Boaz Citrin 's gravatar image


answered Jan 30 2014 at 06:09

Robert Samuel Newson 's gravatar image


C:\Program Files (x86)\Apache Software Foundation\CouchDB\bin>erl
Eshell V5.8.5  (abort with ^G)
1> application:start(sasl).
ok
=PROGRESS REPORT==== 30-Jan-2014::14:20:21 ==          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.37.0>},
                       {name,alarm_handler},
                       {mfargs,{alarm_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]
2>
=PROGRESS REPORT==== 30-Jan-2014::14:20:21 ==          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.38.0>},
                       {name,overload},
                       {mfargs,{overload,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]
2>
=PROGRESS REPORT==== 30-Jan-2014::14:20:21 ==          supervisor: {local,sasl_sup}
             started: [{pid,<0.36.0>},
                       {name,sasl_safe_sup},
                       {mfargs,
                           {supervisor,start_link,
                               [{local,sasl_safe_sup},sasl,safe]}},
                       {restart_type,permanent},
                       {shutdown,infinity},
                       {child_type,supervisor}]
2>
=PROGRESS REPORT==== 30-Jan-2014::14:20:21 ==          supervisor: {local,sasl_sup}
             started: [{pid,<0.39.0>},
                       {name,release_handler},
                       {mfargs,{release_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]
2>
=PROGRESS REPORT==== 30-Jan-2014::14:20:21 ==         application: sasl
          started_at: [email protected]
2> application:start(os_mon).
{error,{shutdown,{os_mon,start,[normal,[]]}}}
=CRASH REPORT==== 30-Jan-2014::14:21:16 ==  crasher:
    initial call: os_mon_sysinfo:init/1
    pid: <0.46.0>
    registered_name: []
    exception exit: {enoent,
                        [{erlang,open_port,
                             [{spawn,
                                  "c:/PROGRA~2/Apache Software
Foundation/CouchD
B/lib/os_mon-2.2.7/priv/bin/win32sysinfo.exe"},
                              [{packet,1}]]},
                         {os_mon_sysinfo,start_portprogram,0},
                         {os_mon_sysinfo,init,1},
                         {gen_server,init_it,6},
                         {proc_lib,init_p_do_apply,3}]}
      in function  gen_server:init_it/6
    ancestors: [os_mon_sup,<0.44.0>]
    messages: []
    links: [<0.45.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 987
    stack_size: 24
    reductions: 444
  neighbours:
3>
=SUPERVISOR REPORT==== 30-Jan-2014::14:21:16 ==     Supervisor: {local,os_mon_sup}
     Context:    start_error
     Reason:     {enoent,
                     [{erlang,open_port,
                          [{spawn,
                               "c:/PROGRA~2/Apache Software
Foundation/CouchDB/l
ib/os_mon-2.2.7/priv/bin/win32sysinfo.exe"},
                           [{packet,1}]]},
                      {os_mon_sysinfo,start_portprogram,0},
                      {os_mon_sysinfo,init,1},
                      {gen_server,init_it,6},
                      {proc_lib,init_p_do_apply,3}]}
     Offender:   [{pid,undefined},
                  {name,os_mon_sysinfo},
                  {mfargs,{os_mon_sysinfo,start_link,[]}},
                  {restart_type,permanent},
                  {shutdown,2000},
                  {child_type,worker}]
3>
=INFO REPORT==== 30-Jan-2014::14:21:16 ==    application: os_mon
    exited: {shutdown,{os_mon,start,[normal,[]]}}
    type: temporary
3>

answered Jan 30 2014 at 06:22

Boaz Citrin 's gravatar image


we should make os_mon optional (it�s buggy/broken in other situations, like if a mountpoint has a space in the name..)
It exists only for the compaction daemon which is disabled by default, so this is just breaking you for no upside.
B.

answered Jan 30 2014 at 06:32

Robert Samuel Newson 's gravatar image


any idea why it happens? any way to overcome it? any way to workaround it?
Thanks!!

answered Jan 30 2014 at 06:39

Boaz Citrin 's gravatar image


The error is;
{enoent,  [{erlang,open_port, [{spawn, "c:/PROGRA~2/Apache Software Foundation/CouchDB/lib/os_mon-2.2.7/priv/bin/win32sysinfo.exe"}
Meaning it can�t find that to launch it. Does it exist? Or is ~2 or the spaces confusing erlang?
B.

answered Jan 30 2014 at 06:42

Robert Samuel Newson 's gravatar image


it is there. no problem to run that command.

answered Jan 30 2014 at 06:51

Boaz Citrin 's gravatar image


Hrm, no clue then. Will need a Windows/Erlang developer.
B.

answered Jan 30 2014 at 06:55

Robert Samuel Newson 's gravatar image


btw, where does it take the "c:/PROGRA~2" from? can i instruct it to use
another path?
[note that we don't have the issue on many other windows 7 machines with
the exact paths]

answered Jan 30 2014 at 07:24

Boaz Citrin 's gravatar image


I think the "c:/PROGRA~2" may ultimately come from the erl.ini file in the
CouchDb bin directory but I'm not sure of that, and don't know if changing
it there would be sufficient. The "~2" business may not be an error either
- some programs still live in the days of 8.3 file names and use this
convention for reporting names that don't fit that convention.
If you want to try another path, the simplest way would be to uninstall
CouchDb and reinstall somewhere like C:\CouchDb which is short and has no
spaces. While the uninstall should leave your local.ini file and databases
alone, it would be best to back them up somewhere and then copy to the new
installation.
Nick

answered Jan 30 2014 at 08:17

Nick North 's gravatar image


From: Robert Samuel Newson 
To: user 
Subject: Cannot connect to CouchDb on Windows  
Date: 30. Jänner  
Hrm, no clue  
B.  
I’ve seen this periodically, but never reproduced it locally.
Somehow Windows (or possibly Erlang) is unable to handle this combination of an abbreviated 8.3 mangled path & a full path, even though on a default windows install this works perfectly.
The workaround for impacted boxes is simply to install to a path without spaces, which IMO is always a Good Thing Anyway.
A+
Dave

answered Jan 30 2014 at 08:44

Dave Cottlehuber 's gravatar image


Hi,
The path in erl.ini was just like on my machine where it works fine -
C:\\Program Files (x86)\\Apache Software Foundation\\CouchDB
So I followed the suggestion and installed on C:\ and all works fine :-)
Thanks!
Boaz

answered Feb 6 2014 at 07:19

Boaz Citrin 's gravatar image


Related discussions

Tagged

Group Couchdb-user

asked Jan 30 2014 at 02:54

active Feb 6 2014 at 07:19

posts:15

users:4

©2013 QnaList.com