couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CGS <cgsmcml...@gmail.com>
Subject Re: Error upgrading from 1.1 to 1.2
Date Tue, 19 Jun 2012 15:39:41 GMT
The problem is in the fact that Erlang doesn't have the correct path for
its ebin dirs.

To solve this problem, you have 2 options:
1. See what breaks Erlang paths (in the ultimate case, install Erlang
again) - you can ask for help at "Erlang-Questions" <
erlang-questions@erlang.org> (there is the place where you can discuss
problems related to Erlang) or Ubuntu forum (if you installed Erlang from
Ubuntu repository).
2. execute this in a BASH environment (a quick and dirty solution):

ERLSCRDIR="/usr/lib/erlang/bin" && sudo mv ${ERLSCRDIR}/erl
${ERLSCRDIR}/erl_old && ERLPA=$(ERLEBIN="/usr/lib/erlang/lib" && for var in
$(ls ${ERLEBIN}) ; do echo -n " ${ERLEBIN}/${var}/ebin" ; done) && echo -e
"#\x21/usr/bin/env bash" > erl && echo "" >> erl && echo
"${ERLSCRDIR}/erl_old -pa ${ERLPA}" >> erl && sudo mv erl ${ERLSCRDIR}/erl
&& sudo chmod ugoa+x ${ERLSCRDIR}/erl

This last option is a hack into your Erlang installation to force Erlang to
read its ebin dirs. It does the followings:
1. it renames erl to erl_old in /usr/lib/erlang/bin
2. it creates again erl in that path, but its action is to redirect all the
erl commands to "erl_old -pa <path_to_erlang_ebin_dirs>"

Note: It is recommended to follow the first option.

If you have problems in executing that command, let me know.

CGS






On Tue, Jun 19, 2012 at 3:51 PM, Juan José Sánchez Mesa <
juanjo.listas@doblej.net> wrote:

> Thanks.
>
> Now, the application:start(os_mon). was succesfull:
>
> 2> application:start(os_mon).
>
> =PROGRESS REPORT==== 19-Jun-2012::13:49:09 ===
>          supervisor: {local,os_mon_sup}
>             started: [{pid,<0.48.0>},
>                       {name,disksup},
>                       {mfa,{disksup,start_link,[]}},
>                       {restart_type,permanent},
>                       {shutdown,2000},
>                       {child_type,worker}]
>
> =PROGRESS REPORT==== 19-Jun-2012::13:49:09 ===
>          supervisor: {local,os_mon_sup}
>             started: [{pid,<0.49.0>},
>                       {name,memsup},
>                       {mfa,{memsup,start_link,[]}},
>                       {restart_type,permanent},
>                       {shutdown,2000},
>                       {child_type,worker}]
>
> =PROGRESS REPORT==== 19-Jun-2012::13:49:09 ===
>          supervisor: {local,os_mon_sup}
>             started: [{pid,<0.51.0>},
>                       {name,cpu_sup},
>                       {mfa,{cpu_sup,start_link,[]}},
>                       {restart_type,permanent},
>                       {shutdown,2000},
>                       {child_type,worker}]
> ok
> 3>
> =PROGRESS REPORT==== 19-Jun-2012::13:49:09 ===
>         application: os_mon
>          started_at: nonode@nohost
> 3>
> =INFO REPORT==== 19-Jun-2012::13:49:09 ===
>    alarm_handler: {set,{system_memory_high_**watermark,[]}}
> 3>
> =PROGRESS REPORT==== 19-Jun-2012::13:49:09 ===
>          supervisor: {local,kernel_safe_sup}
>             started: [{pid,<0.55.0>},
>                       {name,timer_server},
>                       {mfa,{timer,start_link,[]}},
>                       {restart_type,permanent},
>                       {shutdown,1000},
>                       {child_type,worker}]
> 3>
>
>
> So, what's the problem ???
>
> Thanks!
>
> El 19/06/2012 15:47, CGS escribió:
>
>> It may be a problem in your Erlang installation. To test that, please,
>> start an Erlang shell like this (in BASH):
>>
>> ERLPA=$(ERLEBIN="/usr/lib/**erlang/lib/" && for var in $(ls ${ERLEBIN})
>> ; do
>> echo -n " ${ERLEBIN}/${var}/ebin" ; done) && erl -pa ${ERLPA} -init_debug
>>
>> and try to start again sasl and os_mon:
>>
>> application:start(sasl).
>> application:start(os_mon).
>>
>> CGS
>>
>>
>> On Tue, Jun 19, 2012 at 3:24 PM, Juan José Sánchez Mesa <
>> juanjo.listas@doblej.net> wrote:
>>
>>  With the 'application:start(os_mon).' command I got same error:
>>>
>>>
>>> {error,{"no such file or directory","os_mon.app"}}
>>>
>>>
>>> os_mon.app file is located at:
>>> /usr/lib/erlang/lib/os_mon-2.****2.4/ebin/os_mon.app
>>>
>>>
>>>
>>> What can I do ?
>>>
>>> Thanks!
>>>
>>> El 19/06/2012 15:12, CGS escribió:
>>>
>>>  Hi Juan,
>>>>
>>>> Could you provide the output of the followings:
>>>> 1. start an Erlang shell in the debug mode (erl -init_debug);
>>>> 2. copy and paste:
>>>>
>>>> application:start(sasl).
>>>> application:start(os_mon).
>>>>
>>>> You should get something like I attached here if everything goes well.
>>>>
>>>> CGS
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jun 19, 2012 at 2:32 PM, Juan José Sánchez Mesa
>>>> <juanjo.listas@doblej.net <mailto:juanjo.listas@doblej.****net<
>>>> juanjo.listas@doblej.net>**>>
>>>>
>>>> wrote:
>>>>
>>>>    Hi!
>>>>
>>>>    I'm new to the list.
>>>>
>>>>    I was using CouchDB 1.10 on Ubuntu 10.04 and was working pretty well.
>>>>
>>>>    Now, I've upgraded to 1.20 using sources, and now, CouchDB don't
>>>>    start with this error:
>>>>
>>>>    {"init terminating in do_boot",{{badmatch,{error,{"_****_no such
>>>> file or
>>>>    directory","os_mon.app"}}},[{_****_couch,start,0},{init,start_****
>>>>
>>>> it,__1},{init,start_em,1}]}}
>>>>
>>>>    init terminating in do_boot ()
>>>>
>>>>
>>>>    This error suggests that erlang-os-mon package is not installed.
>>>>    But, it's already installed.
>>>>
>>>>    I've tried to delete files in /usr/local/lib/couchdb/erlang/**
>>>> **__lib
>>>>    has suggested in
>>>>    http://wiki.apache.org/__****couchdb/Installing_on_Ubuntu<http://wiki.apache.org/__**couchdb/Installing_on_Ubuntu>
>>>> <h**ttp://wiki.apache.org/__**couchdb/Installing_on_Ubuntu<http://wiki.apache.org/__couchdb/Installing_on_Ubuntu>
>>>> >
>>>>
>>>>    <http://wiki.apache.org/****couchdb/Installing_on_Ubuntu<http://wiki.apache.org/**couchdb/Installing_on_Ubuntu>
>>>> <h**ttp://wiki.apache.org/couchdb/**Installing_on_Ubuntu<http://wiki.apache.org/couchdb/Installing_on_Ubuntu>
>>>> >>
>>>>
>>>> and do 'make
>>>>    install' but still not working.
>>>>
>>>>    Version 1.10 was working perfect.
>>>>
>>>>    Any idea ?
>>>>
>>>>    Thanks!
>>>>
>>>>
>>>>
>>>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message