Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Problems running couch 1.0.1 on RedHat Linux
From: "Tracy Flynn (couchdb)" <couchdb@thisonejustforme.com>
In-Reply-To: <AANLkTimevU=n7Q4o+kP1tSgRnkoOvspVx-4JMM9647Nr@mail.gmail.com>
Date: Sun, 10 Oct 2010 20:01:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E17A6DF-0583-48F1-BF8D-2A9A6029F0DE@thisonejustforme.com>
References: <5CB400CF-9DC9-4EA6-ABF3-FF3F593669B4@thisonejustforme.com>
 <AANLkTimevU=n7Q4o+kP1tSgRnkoOvspVx-4JMM9647Nr@mail.gmail.com>
To: user@couchdb.apache.org

Failing installation is on a Linux box - ports is a Mac OS X - only tool =
- and everything works on OS X.

What am I missing?


On Oct 10, 2010, at 6:18 PM, Paul Davis wrote:

> On Sun, Oct 10, 2010 at 5:54 PM, couchdb =
<couchdb@thisonejustforme.com> wrote:
>> Hello,
>> I'm new to CouchDB.
>> I've successfully installed and used CouchDB 1.0.1 on Mac OS X.
>> MacOS X Installation summary
>> ---------------------------------------
>> sudo port install icu erlang spidermonkey curl
>> Then conventional installation from source
>> apache-couchdb-1.0.1.tar.gz
>> Automated Linux installation
>> ---------------------------------------
>> su -c 'rpm -Uvh
>> =
http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.=
rpm'
>> sudo yum install couchdb
>> Installs a runnable couchdb
>> couchdb.x86_64                         0.11.2-2.el5
>>  installed
>>=20
>> Manual Linux Installation summary - apache-couchdb-1.0.1.tar.gz
>> =
--------------------------------------------------------------------------=
---------
>> (Details attached)
>> Manually from sources - no errors during build / install
>> When run via
>> sudo -u couchdb couchdb
>> Multiple errors - samples below - full log in attachment
>>> {error_logger,{{2010,10,10},{17,35,37}},std_error,"File operation =
error:
>>> eacces. Target: .. Function: read_file_info. Process: code_server."}
>>> {error_logger,{{2010,10,10},{17,35,37}},std_error,"File operation =
error:
>>> eacces. Target: ./beam_lib.beam. Function: get_file. Process: =
code_server."}
>>  =3DCRASH REPORT=3D=3D=3D=3D 10-Oct-2010::17:35:37 =3D=3D=3D
>>>   crasher:
>>>     initial call: application_master:init/4
>>>     pid: <0.29.0>
>>>     registered_name: []
>>>     exception exit: {bad_return,
>>>                         {{couch_app,start,
>>>                              [normal,
>>>=20
>>> ["/usr/local/couchdb-1.0.1/etc/couchdb/default.ini",
>>>=20
>>>  "/usr/local/couchdb-1.0.1/etc/couchdb/local.ini"]]},
>>>                          {'EXIT',
>>>                              "libicuuc.so.44: cannot open shared =
object
>>> file: No such file or directory"}}}
>>>       in function  application_master:init/4
>> This second error suggests that the appropriate libraries are not =
accessible
>> - however, they show up with correct ownership and permissions.
>> Any insights would be appreciated.
>>=20
>> Regards,
>> Tracy Flynn
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
> Looks like your not linked against ICU properly. Seeing as you're
> using ports, is your DYLD_LIBRARY_PATH set correctly?